From: Gavin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Gavin <gavinpublic@comcast.net>
Subject: Re: \unit parser ignoring case, in some cases.
Date: Tue, 14 Mar 2023 16:00:45 -0600 [thread overview]
Message-ID: <4BCAF1DC-1F74-42C9-A1CE-836E45160ADC@comcast.net> (raw)
In-Reply-To: <7ffd5e8d-93c8-9def-a07c-9e219360c4da@freedom.nl>
On Mar 14, 2023, at 3:32 PM, Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
> On 3/14/2023 7:14 PM, Alan Braslau via ntg-context wrote:
>> On Tue, 14 Mar 2023 12:03:23 -0600
>> Gavin <gavinpublic@comcast.net> 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 these units? (So let me threaten once again to kick the "in" unit out of context.)
>
>> I believe that this point is essential,….
Alan and I will come up with a scheme that fastidiously follows the SI, and release it as a “North American localization.” That should leave everyone sufficiently puzzled, annoyed, or amused.
Signing off of this subject until 27 May. Thanks for all your help!
Gavin
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-03-14 22:00 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 [this message]
2023-03-14 21:26 ` Hans Hagen via ntg-context
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=4BCAF1DC-1F74-42C9-A1CE-836E45160ADC@comcast.net \
--to=ntg-context@ntg.nl \
--cc=gavinpublic@comcast.net \
/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).