ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: Gavin <gavinpublic@comcast.net>
Cc: Alan Braslau <alan.braslau@icloud.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \unit parser ignoring case, in some cases.
Date: Tue, 14 Mar 2023 12:14:46 -0600	[thread overview]
Message-ID: <20230314121446.4156a551@boo.my.domain> (raw)
In-Reply-To: <839FF8CC-EFC7-4A03-B717-1BBDFAC23BD0@comcast.net>

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

I believe that this point is essential, regardless of history of use of
the \unit{} command. Non-standard use of units can be *tolerated* as
long as they do not conflict with the SI and do not impose non-standard
syntax.

Alan

P.S. It is our guarded secret that the weather is nice here in
Colorado. I do not know of any other place that has real seasons AND
where it is (almost) always sunny! :-)
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-03-14 18:14 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 [this message]
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=20230314121446.4156a551@boo.my.domain \
    --to=ntg-context@ntg.nl \
    --cc=alan.braslau@icloud.com \
    --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).