On Mar 14, 2023, at 3:32 PM, Hans Hagen via ntg-context
wrote:
> On 3/14/2023 7:14 PM, Alan Braslau via ntg-context wrote:
>> On Tue, 14 Mar 2023 12:03:23 -0600
>> Gavin wrote:
>>> I’d really like one of the acceptable forms to be the form prescribed
>>> by Le Système international d'unités
>
>
On 3/14/2023 7:14 PM, Alan Braslau via ntg-context wrote:
On Tue, 14 Mar 2023 12:03:23 -0600
Gavin wrote:
I’d really like one of the acceptable forms to be the form prescribed
by Le Système international d'unités
Maybe the french title is one of the reasons for the USA not picking up
on the
On 3/14/2023 7:03 PM, Gavin via ntg-context wrote:
I’d like to better understand how the \unit{} command works and why those
choices were made. Some of the choices seem to be “asking for troubles,” but
perhaps they are essential for some users.
I wonder if Alan was using context when the fir
On Tue, 14 Mar 2023 12:03:23 -0600
Gavin wrote:
> I’d really like one of the acceptable forms to be the form prescribed
> by Le Système international d'unités
I believe that this point is essential, regardless of history of use of
the \unit{} command. Non-standard use of units can be *tolerated*
On Mar 14, 2023, at 10:08 AM, Alan Braslau via ntg-context
wrote:
> Right now, \unit{1 mm-1} and \unit{1 m m-1} give the same result:
> inverse millimeters (whereas the second should be m•m^{-1}…)
>
> Alan
Alan,
I’d like to better understand how the \unit{} command works and why those
choices
On 3/14/2023 5:33 PM, Gavin via ntg-context wrote:
Hi Alan, Hans, and List,
On Mar 13, 2023, at 8:10 PM, Alan Braslau via ntg-context
wrote:
On Mon, 13 Mar 2023 15:55:50 -0600 Gavin via ntg-context
wrote:
you can look at phys-dim and see plenty of short and long keys and
making all case i
I wrote
> Perhaps we could use a \registershortcut command that does not get the
> “lower" treatment.
without seeing that Hans had already read my mind and provided:
\registerunitshortcut
[unit]
[C=coulomb]
That should work great.
Thanks!
Gavin
___
Hi Alan, Hans, and List,
> On Mar 13, 2023, at 8:10 PM, Alan Braslau via ntg-context
> wrote:
> On Mon, 13 Mar 2023 15:55:50 -0600 Gavin via ntg-context
> wrote:
>>> you can look at phys-dim and see plenty of short and long keys and
>>> making all case insensitive is asking for troubles
>>
On Tue, 14 Mar 2023 15:36:37 +0100
Hans Hagen via ntg-context wrote:
> > Indeed, I would like to make NONE of them case insensitive. But
> > currently, when I register an upper case key (C=coulomb) it messes
> > up the lower case prefix (“cm" gets typeset as C•m). I was
> > expecting the parser t
On 3/13/2023 10:55 PM, Gavin wrote:
On Mar 13, 2023, at 3:44 PM, Hans Hagen via ntg-context
wrote:
On 3/9/2023 2:04 PM, Gavin via ntg-context wrote:
\startformula
\unit{3 meter} \qquad
\unit{6 Meter} \qquad
\unit{3 mEtEr} \qquad
\stopformula
Units with lowercase prefixes (c, k, n)
On Mon, 13 Mar 2023 15:55:50 -0600
Gavin via ntg-context wrote:
> > you can look at phys-dim and see plenty of short and long keys and
> > making all case insensitive is asking for troubles
>
> Indeed, I would like to make NONE of them case insensitive. But
> currently, when I register an uppe
> On Mar 13, 2023, at 3:44 PM, Hans Hagen via ntg-context
> wrote:
>
> On 3/9/2023 2:04 PM, Gavin via ntg-context wrote:
>> \startformula
>> \unit{3 meter} \qquad
>> \unit{6 Meter} \qquad
>> \unit{3 mEtEr} \qquad
>> \stopformula
>> Units with lowercase prefixes (c, k, n).
>> \startformul
On 3/9/2023 2:04 PM, Gavin via ntg-context wrote:
\startformula
\unit{3 meter} \qquad
\unit{6 Meter} \qquad
\unit{3 mEtEr} \qquad
\stopformula
Units with lowercase prefixes (c, k, n).
\startformula
\unit{3cm} \qquad
\unit{6kg} \qquad
\unit{3ns} \qquad
\stopformula
Units with c
Hello list,
I continue to work with the \unit command, and found some behavior very
surprising. When I try to register units with capital letter names, it breaks
lowercase metric prefixes. For example, registering C=coulomb, K=kelvin and
N=newton breaks metric units cm, kg, and ns. The file bel
14 matches
Mail list logo