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: Spacing in \unit
Date: Sun, 9 Oct 2022 19:32:58 -0600 [thread overview]
Message-ID: <20221009193258.6abd2cae@boo.my.domain> (raw)
In-Reply-To: <DDE9DDAB-986E-490D-8ACE-B7539CDE3C37@comcast.net>
On Sat, 8 Oct 2022 11:59:04 -0600
Gavin via ntg-context <ntg-context@ntg.nl> wrote:
> I’m trying to fix four issues:
> - No space between the number and the following units. Should be a
> thin space.
> - No space between the units and the following symbol (+ and =
> above). Should be appropriate “bin" or “rel" space.
> - Too much space around the \cdot in the units. Should be treated
> like an “ord" when used to separate units.
> - Too much space around the \times in the scientific notation.
> Should be treated like an "ord" when used in scientific notation.
> (I'm not sure there is consensus on this.)
Gavin (and the mailing list),
I would very strongly argue that the space between the number and the
following units be UNBREAKABLE. Perhaps a thin space (preference), but
most certainly non-breakable.
Similarly around the times in scientific notation.
I further cannot imagine that a line break be acceptable around a \cdot
in composite units.
This can possibly lead to overfill and underfill, something that I find
*infinitely* more acceptable then breaking numbers and units.
I do not know or use the \units command. Maybe it uses unbreakable
spaces, maybe not. I would never use it unless it could be configured
to only use nonbreakable spaces.
Perhaps others feel differently?
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:[~2022-10-10 1:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 17:59 Gavin via ntg-context
2022-10-10 1:32 ` Alan Braslau via ntg-context [this message]
2022-10-10 6:15 ` Max Chernoff via ntg-context
2022-10-12 21:54 ` Spacing in \unit - SOLVED Gavin via ntg-context
2022-10-12 22:11 ` Rik Kabel via ntg-context
2022-10-12 22:49 ` Max Chernoff via ntg-context
2022-10-12 23:55 ` Spacing in \unit - degrees Alan Braslau via ntg-context
2022-10-13 3:14 ` Gavin via ntg-context
2022-10-13 13:26 ` Alan Braslau via ntg-context
2022-10-13 0:11 ` Spacing in \unit - SOLVED Gavin via ntg-context
2022-10-13 7:03 ` Oliver Sieber via ntg-context
2022-10-13 11:52 ` Gavin via ntg-context
2022-10-14 8:12 ` Hans Hagen via ntg-context
2022-10-21 18:20 ` Gavin via ntg-context
2022-10-21 19:07 ` Gavin via ntg-context
2022-10-12 16:50 ` Dimension atom in math? (was: Spacing in \unit) Gavin via ntg-context
-- strict thread matches above, loose matches on Subject: below --
2022-09-25 13:30 Spacing in \unit Gavin via ntg-context
2022-09-25 15:19 ` Hans Hagen via ntg-context
2022-09-25 15:29 ` Gavin via ntg-context
2022-09-25 15:39 ` Hans Hagen via ntg-context
2022-09-25 16:31 ` Bruce Horrocks 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=20221009193258.6abd2cae@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).