ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Rudd, Kevin" <kevin@lps.umd.edu>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ntg-context Digest, Vol 205, Issue 1 // log: use \thinspace instead of \,
Date: Wed, 21 Jul 2021 10:01:12 +0000	[thread overview]
Message-ID: <87E2EEAF-A02D-41B8-82AC-444056D35B22@lps.umd.edu> (raw)
In-Reply-To: <9ae5f768-f03e-c2c7-5eb7-67e9953074f8@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2279 bytes --]

Argh; mea culpa. Thanks for the very quick reply, Hans. It does work "as expected" (albeit deprecated)---Tracking down errors, I was misled by an error immediately following the deprecation warning and associated it with the warning, not the subsequent text.

Thanks,
 ---K

Kevin W. Rudd, Ph.D.
CAPT, USN (Ret)

Computer Architecture & Computer Engineering
Advanced Computing Systems (ACS) Research Program
Laboratory for Physical Sciences (LPS)

443-654-7878
kevin@lps.umd.edu<mailto:kevin@lps.umd.edu>

Visiting Research Professor
United States Naval Academy

rudd@usna.edu<mailto:rudd@usna.edu>


On Jul 21, 2021, at 05:48, Hans Hagen <j.hagen@xs4all.nl<mailto:j.hagen@xs4all.nl>> wrote:

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<http://www.pragma-ade.nl> | www.pragma-pod.nl<http://www.pragma-pod.nl>
-----------------------------------------------------------------


[-- Attachment #1.2: Type: text/html, Size: 5138 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2021-07-21 10:01 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
2021-07-21 10:01     ` Rudd, Kevin [this message]

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=87E2EEAF-A02D-41B8-82AC-444056D35B22@lps.umd.edu \
    --to=kevin@lps.umd.edu \
    --cc=j.hagen@xs4all.nl \
    --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).