From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Brian Inglis" <Brian.Inglis@Shaw.ca>,
наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: Linux Man-Pages <linux-man@vger.kernel.org>
Subject: Re: Using C23 digit separators not locale digit grouping characters
Date: Sun, 29 Jan 2023 15:38:21 +0100 [thread overview]
Message-ID: <717e8fb9-9159-65f8-093e-a117c82be704@gmail.com> (raw)
In-Reply-To: <19a71139-7807-2692-3eec-16a0f754911d@Shaw.ca>
[-- Attachment #1.1: Type: text/plain, Size: 2291 bytes --]
Hi Brian and наб!
On 1/28/23 21:40, Brian Inglis wrote:
> Hi folks,
>
> Seeing the recent tv_nsec patches drop the standard locale digit grouping
> characters "," from the member range [0-999,999,999] made me regret the loss of
> the punctuation which provides better and quicker comprehension of long strings
> of digits.
Nice! Didn't remember about that separator. It makes a lot of sense to use it
in comments and the likes in the pages. Maybe we should be a bit more cautious
in source code examples, but definitely for big numbers outside of running code
should have them.
наб, would you please update your patches with that? I also have a few comments
that I'll write in a moment in answers to your patches.
Cheers,
Alex
>
> It may be time to consider using the locale independent C23 digit separator
> characters "'" wherever more than a handful of digits occur, possibly convert
> grouping character uses in existing man pages as they are changed, and specify a
> future standard policy approach to provide better and quicker comprehension of
> long strings of digits: perhaps using a new digit separator register and glyph
> escape sequence \*ds \*[ds] \[ds] \(ds if not in use by base groff?
The sequence for the unslanted single quote is \(aq.
We could add somewhere in man-pages(7) that decimal numbers should use a
separator every 3 digits, and hex and binary should use it every 4 digits.
>
> As well as the recently modified pages:
>
> clock_getres.2
> timer_settime.2
> timerfd_create.2
> utimensat.2
>
> there appear to be obvious occurrences in only the following pages:
>
> futex.2
> read.2
> sendfile.2
> write.2
> mallopt.3
> keyrings.7
> mq_overview.7
> sched.7
> time_namespaces.7
>
> but there appear to be about 400 pages with more than 6 decimal digit strings
> (some spurious glibc hex commits and address outputs) where it could perhaps
> help, such as in POSIX version dates e.g. 2001'12L, and undoubtedly more with
> long digit strings in other radixes.
Would you mind preparing a patch for all of those? If you'll do it, better wait
until we merge наб's patches, to avoid conflicts.
Cheers,
Alex
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-29 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 20:40 Using C23 digit separators not locale digit grouping characters Brian Inglis
2023-01-29 14:38 ` Alejandro Colomar [this message]
2023-01-29 21:04 ` Brian Inglis
2023-01-29 21:19 ` Alejandro Colomar
2023-02-02 22:29 ` Brian Inglis
2023-02-02 23:59 ` Alejandro Colomar
2023-02-03 13:27 ` Tom Schwindl
2023-02-05 13:47 ` Alejandro Colomar
2023-02-08 21:00 ` Jakub Wilk
2023-02-08 21:06 ` Alejandro Colomar
2023-02-08 22:10 ` Brian Inglis
2023-02-09 12:47 ` Alejandro Colomar
2023-02-04 7:19 ` Brian Inglis
2023-02-05 13:32 ` Alejandro Colomar
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=717e8fb9-9159-65f8-093e-a117c82be704@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Brian.Inglis@Shaw.ca \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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