From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: log: use \thinspace instead of \,
Date: Tue, 29 Jun 2021 14:06:02 +0200 [thread overview]
Message-ID: <6CC767DB-5C1F-4A7F-8161-6BA327499D40@fiee.net> (raw)
In-Reply-To: <2018690b-1c01-0821-2275-3c6091553975@xs4all.nl>
> Am 29.06.2021 um 12:34 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 6/29/2021 1:08 AM, Rik Kabel wrote:
>> All,
>> Examining recent log files, I see the message
>> suggestion > use \thinspace instead of \,
>> When was this instituted?
>
> a while ago
>
>> What does it mean? Has \, been deprecated? For many years it was recommended as a short form of \thinspace, and implementing the replacement would certainly result in much less readable source.
> not depricated but these single character commands are somewhat weird (i always forget what they mean, not that i ever use them; when many are needed one can wonder if something else should be fixed instead)
>
> (for instance in macro definitions i'd not use \, but the more verbose \thinspace)
Maybe, but in running text I use \, all the time e.\,g. in abbreviations or for numbers (10\,000). At least in German typography these “spatiums” are necessary.
Hraban
___________________________________________________________________________________
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-06-29 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 23:08 Rik Kabel
2021-06-29 10:34 ` Hans Hagen
2021-06-29 12:06 ` Henning Hraban Ramm [this message]
2021-06-29 15:40 ` Alan Braslau
2021-06-30 20:57 ` Wolfgang Schuster
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=6CC767DB-5C1F-4A7F-8161-6BA327499D40@fiee.net \
--to=texml@fiee.net \
--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).