From: Gavin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Gavin <gavinpublic@comcast.net>, Max Chernoff <mseven@telus.net>
Subject: Re: Spacing in \unit - SOLVED
Date: Wed, 12 Oct 2022 15:54:43 -0600 [thread overview]
Message-ID: <5B9BE319-5660-48E4-A195-CE4705587F66@comcast.net> (raw)
In-Reply-To: <2606f89be66bdc33f9db2e6d9ba773521535f3f5.camel@telus.net>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hi Max, Alan, Bruce, Hans, et.al
I solved my four issues with \unit spacing. In the process, I prevented unwanted line breaks and removed an overzealous backspace before division symbols. Below is a MWE that shows all of these issues, as well as pictures of the result with the unmodified phys-dim.mkxl and with my modified phys-dim.mkxl. The final result is exactly what I wanted.
If anyone wants my changes, either for their own use or to improve the distributed phys-dim.mkxl, I’m happy to share.
Thanks for all of your comments!
Gavin
MWE:
\setuppapersize[A5]
\starttext
The \type{\unit} command in text produces \unit{1.23e5 kg m^2/s^2}.
Inline math \type{$\unit$} produces $\unit{1.23e5 kg m^2/s^2}$.
Display math produces
\startformula
\unit{1.23e5 kg m^2/s^2} + \unit{8.64e5 newton m} = \unit{987,000 joule}
\stopformula
Line breaking in math:
{\hsize=0pt $G = \unit{6.6743e-11 m3 kg-1 s-2}$}
\blank
Line breaking in text:
{\hsize=0pt \unit{6.6743e-11 m3 kg-1 s-2}}
\stoptext
Output with unmodified phys-dim.mkxl:
[-- Attachment #2: PastedGraphic-3.pdf --]
[-- Type: application/pdf, Size: 16028 bytes --]
[-- Attachment #3: Type: text/plain, Size: 41 bytes --]
Output with my modified phys-dim.mkxl:
[-- Attachment #4: PastedGraphic-2.pdf --]
[-- Type: application/pdf, Size: 16052 bytes --]
[-- Attachment #5: Type: text/plain, Size: 2009 bytes --]
> On Oct 10, 2022, at 12:15 AM, Max Chernoff via ntg-context <ntg-context@ntg.nl> wrote:
>
> Hi Alan,
>
>> 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.
>
> Yes, I agree completely here.
>
>> 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.
>
> The current behaviour doesn't break the unit from the number, but it
> does split the scientific notation.
>
> This test file:
>
> \starttext
> \hsize=0pt Math: $G = \unit{6.6743e-11 m3 kg-1 s-2}$
>
> \hsize=0pt Text: \unit{6.6743e-11 m3 kg-1 s-2}
> \stoptext
>
> gives:
>
> Math:
> 𝐺=
> 6.6743×
> 10–11m3⋅kg–1⋅s–2
> Text:
> 6.6743
> ×
> 10−11 m3⋅kg−1⋅s−2
>
> which isn't great. In my opinion, the \unit command should be typeset in an
> \hbox (or similar) since I can't think of any circumstances where breaking
> it would be reasonable.
>
> Thanks,
> -- Max
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #6: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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-12 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 17:59 Spacing in \unit Gavin via ntg-context
2022-10-10 1:32 ` Alan Braslau via ntg-context
2022-10-10 6:15 ` Max Chernoff via ntg-context
2022-10-12 21:54 ` Gavin via ntg-context [this message]
2022-10-12 22:11 ` Spacing in \unit - SOLVED 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
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=5B9BE319-5660-48E4-A195-CE4705587F66@comcast.net \
--to=ntg-context@ntg.nl \
--cc=gavinpublic@comcast.net \
--cc=mseven@telus.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).