From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Rudd, Kevin" <kevin@lps.umd.edu>
Subject: Re: ntg-context Digest, Vol 205, Issue 1 // log: use \thinspace instead of \,
Date: Wed, 21 Jul 2021 11:48:57 +0200 [thread overview]
Message-ID: <9ae5f768-f03e-c2c7-5eb7-67e9953074f8@xs4all.nl> (raw)
In-Reply-To: <8657D6F7-BA32-4CC9-AC1E-080172AFD0B6@lps.umd.edu>
On 7/21/2021 11:04 AM, Rudd, Kevin wrote:
> Revisiting this one---as noted in the thread \, used to work in text mode;
> according to the logs it was deprecated and now produces an error
> preventing most of my documents from compiling.
>
> Is there solution that restores \, (and friends) for abbreviated spacing
> in text mode
> that doesn't require bulk changes to all of my documents
> (and making the source documents hard to type/read)?
> I appreciate using the more verbose \thinspace in macros
> but the abbreviations have real value in bulk text,
> especially when heavily used.
>
> I have many uses throughout my documents where I need a thin space
> (such as working with SI units) where it would be very awkward
> to use \thinspace everywhere in the source text.
>
> for example, consider a simple example that used to work but no longer does
> with the alternatives that I'm aware of:
>
> 32\,MiB--64\,MiB
>
> 32$\,$MiB--64$\,$MiB
> 32\thinspace MiB--64\thinspace MiB
>
> The difference in both writeability and readability for these cases is
> significant
afaikt
\starttext
test\,test
\stoptext
just works (\unit {32 mebibyte}--\unit {64 mebibyte} also works)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-07-21 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.301.1625101378.1143.ntg-context@ntg.nl>
2021-07-21 9:04 ` Rudd, Kevin
2021-07-21 9:48 ` Hans Hagen [this message]
2021-07-21 10:01 ` Rudd, Kevin
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=9ae5f768-f03e-c2c7-5eb7-67e9953074f8@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=kevin@lps.umd.edu \
--cc=ntg-context@ntg.nl \
/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).