From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Gavin via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: \unit parser ignoring case, in some cases.
Date: Tue, 14 Mar 2023 22:26:42 +0100 [thread overview]
Message-ID: <9c1255b3-c9e8-eadd-c190-826fe191a486@freedom.nl> (raw)
In-Reply-To: <839FF8CC-EFC7-4A03-B717-1BBDFAC23BD0@comcast.net>
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 first unit module showed up
in (what wasn't even call;ed mkii) because it is one of the oldest
context modules and we use(d) for typesetting education related
documents. Among the reasons for it was that in the pre-unicode times
one had to compromise on a math / text mixture due to the way fonts and
input was handled.
> I’m happy to have the unit command accept a variety of different forms for the unit, but I’d really like one of the acceptable forms to be the form prescribed by Le Système international d'unités, so that “m s” is a meter second and “ms” is a millisecond. However, I’m not sure if this goal conflicts with other important goals.
>
> Would you like to explore \unit{} this summer to see if we can find a consistent solution? Perhaps we can produce a plan for \unit{} that does not conflict with other \unit{} features, or perhaps we can make a module that lacks some of the features of \unit{} but conforms to the SI for input as well as output. I would be happy with either.
In principle one can think of different schemes (for different purposes
even), after all everything is in tables; that is probably easier than
tring to come up with some complex compromise. There can be instances of
unit with different properties.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-03-14 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 13:04 Gavin via ntg-context
2023-03-13 21:44 ` Hans Hagen via ntg-context
2023-03-13 21:55 ` Gavin via ntg-context
2023-03-14 2:10 ` Alan Braslau via ntg-context
2023-03-14 16:33 ` Gavin via ntg-context
2023-03-14 16:43 ` Gavin via ntg-context
2023-03-14 16:56 ` Hans Hagen via ntg-context
2023-03-14 14:36 ` Hans Hagen via ntg-context
2023-03-14 16:08 ` Alan Braslau via ntg-context
2023-03-14 18:03 ` Gavin via ntg-context
2023-03-14 18:14 ` Alan Braslau via ntg-context
2023-03-14 21:32 ` Hans Hagen via ntg-context
2023-03-14 22:00 ` Gavin via ntg-context
2023-03-14 21:26 ` Hans Hagen via ntg-context [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c1255b3-c9e8-eadd-c190-826fe191a486@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).