From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: Gavin via ntg-context <ntg-context@ntg.nl>
Cc: Alan Braslau <alan.braslau@icloud.com>
Subject: Re: \unit parser ignoring case, in some cases.
Date: Mon, 13 Mar 2023 20:10:56 -0600 [thread overview]
Message-ID: <20230313201056.7cf3e579@boo.my.domain> (raw)
In-Reply-To: <C5115C91-E4A0-4793-90B8-17E965E98DD0@comcast.net>
On Mon, 13 Mar 2023 15:55:50 -0600
Gavin via ntg-context <ntg-context@ntg.nl> 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 upper case key (C=coulomb) it messes up
> the lower case prefix (“cm" gets typeset as C•m). I was expecting the
> parser to distinguish between the “C” and “c”, but it doesn’t. Is
> that intended?
Indeed, \unit{} should allow (and presently does not) K, C, etc.
Alan
___________________________________________________________________________________
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 2:10 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 [this message]
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
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=20230313201056.7cf3e579@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@icloud.com \
/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).