linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennart Jablonka <vol@ljabl.com>
To: Alejandro Colomar <alx.manpages@gmail.com>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, Guillem Jover <guillem@hadrons.org>,
	Alejandro Colomar <alx@kernel.org>
Subject: Re: [PATCH] man*/: ffix
Date: Tue, 18 Apr 2023 17:32:01 +0000	[thread overview]
Message-ID: <ZD7UEaKv9Gvui9ib@beryllium> (raw)
In-Reply-To: <12c2889f-7f05-8338-b758-5d9b83af536c@gmail.com>

Quoth Alejandro Colomar:
>>> What do standards say about formatting dates?
>>
>> Nothing that I know of.
>>
>>> Do they specify the character?
>>
>> Not that I know of.

ISO 8601:2004 (not the newest revision, but the one I found), the 
standard defining the YYYY‐MM‐DD explicitly calls for a “hyphen,” 
stating additionally:

>In an environment where use is made of a character repertoire based on 
>ISO/IEC 646, “hyphen” and “minus” are both mapped onto “hyphen-minus”.

This is not the case here.  A hyphen is the character to use; that is, 
an unescaped hyphen-minus in the input.

>> Most RFCs don't concern themselves with typography.  :)

RFCs usually tell you that they are talking about ASCII.

>>> However, date(1) only accepts hyphen-minus, so it would be nice to use
>>> a compatible format, even if standards didn't mandate it.

The standard mandates a hyphen.  A hyphen-minus is to be used where the 
date is to be interpreted as a string to be given to \fIdate\fP.

>> By analogy, we don't compose man pages to write "don\[aq]t", even if for
>> some reason a person might want to type "don't" as input to a Unix
>> command.  (I hope they've prepared for its potential interaction with
>> the shell's quoting mechanisms.)  People have gradually realized over
>> the years that typing "don\[aq]t" is derpy and awkward.  Typesetting
>> enthusiasts also note that it gives you a wrongly-shaped apostrophe in
>> DVI, PostScript, and PDF output.
>
>I'm not convinced, because dates are not prose.  Why should we use hyphens
>in dates formatted with standards-like formats?  I would agree in using
>hyphens in dates if we spelled out dates unformatted, in plain English.
>But if we use ISO-like or RFC-like formats, I think we should adhere to
>them completely.

Great!  Exactly my opinion.  An RFC usually tells you to use ASCII, so 
we should do that where applicable.  Luckily, we aren’t concerned with 
RFCs here, but with ISO 8601.

>> I unflinchingly agree with the remainder of the patch.  I simply want to
>> caution against a robotic process of demoting perfectly legitimate
>> hyphens to the crudely compromised hyphen-minus character.
>
>Please explain why they are reasonable there?  What's the use of a
>hyphen in a date?  It's not a compound noun, or something like that.

The use of a hyphen is that it is a character not used in date formats 
preceding ISO 8601.

  reply	other threads:[~2023-04-18 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 23:19 [PATCH] man*/: ffix Guillem Jover
2023-04-16 23:51 ` G. Branden Robinson
2023-04-17 18:14   ` Alejandro Colomar
2023-04-17 21:10     ` G. Branden Robinson
2023-04-18 13:33       ` Alejandro Colomar
2023-04-18 17:32         ` Lennart Jablonka [this message]
2023-04-18 20:48           ` Alejandro Colomar
2023-04-19  6:34             ` G. Branden Robinson
2023-04-18  0:27     ` Guillem Jover

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=ZD7UEaKv9Gvui9ib@beryllium \
    --to=vol@ljabl.com \
    --cc=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=guillem@hadrons.org \
    --cc=linux-man@vger.kernel.org \
    /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).