public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
	Time zone mailing list <tz@iana.org>
Subject: Re: [PATCH v2 2/4] zic.8: s/time zone/timezone/ for consistency
Date: Wed, 23 Nov 2022 20:02:15 +0100	[thread overview]
Message-ID: <72f5ab02-4756-5c20-5ee8-91f9826d094e@gmail.com> (raw)
In-Reply-To: <0b1c6659-6a1f-a1aa-daf2-91e86ab17efd@cs.ucla.edu>


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

Hi Paul,

On 11/23/22 19:42, Paul Eggert wrote:
> On 2022-11-23 05:48, Alejandro Colomar wrote:
>> This adds consistency across other manual pages, and with POSIX.1.
> 
> The tzdb project documentation uses the phrase "time zone" for the ordinary 
> English meaning that you'll see in time zone maps or in phrases like "time zone 
> abbreviation", whereas it uses the single word "timezone" to mean the POSIX idea 
> of a set of rules that map UTC to local time. So, for example, this proposed 
> change:
> 
>> -A time zone abbreviation uses a
>> +A timezone abbreviation uses a
> 
> would not be right, because an time zone abbreviation like "PDT" doesn't denote 
> a set of rules like a TZ string would.
> 
> I suggest modifying other Linux manual pages to be consistent with this usage, 
> rather than trying to use the single word "timezone" for both usages. Quite 
> possibly most other Linux manual pages typically use "timezone" because they're 
> typically talking about the POSIX meaning, which would mean they're already OK.

It makes sense.  Thanks.

Cheers,

Alex

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-23 19:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 13:48 [PATCH v2 1/4] zic.8: Add public domain notice Alejandro Colomar
2022-11-23 13:48 ` [PATCH v2 2/4] zic.8: s/time zone/timezone/ for consistency Alejandro Colomar
2022-11-23 18:42   ` Paul Eggert
2022-11-23 19:02     ` Alejandro Colomar [this message]
2022-11-23 19:14   ` G. Branden Robinson
2022-11-23 13:48 ` [PATCH v2 3/4] zic.8: Use correct escape sequences instead of special characters Alejandro Colomar
2022-11-23 18:18   ` G. Branden Robinson
2022-11-23 18:43   ` Paul Eggert
2022-11-26  2:31     ` Paul Eggert
2022-11-26  3:07       ` G. Branden Robinson
2022-11-26 21:19       ` G. Branden Robinson
2022-11-27  0:12         ` Paul Eggert
2022-12-13 23:24           ` G. Branden Robinson
2022-11-23 13:48 ` [PATCH v2 4/4] zic.8: Use correct letter case in page title (TH) Alejandro Colomar
2022-11-23 18:45   ` Paul Eggert
2022-11-23 18:32 ` [PATCH v2 1/4] zic.8: Add public domain notice Paul Eggert
2022-11-23 19:01   ` Alejandro Colomar
2022-11-23 19:19     ` Paul Eggert
2022-11-23 19: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=72f5ab02-4756-5c20-5ee8-91f9826d094e@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=eggert@cs.ucla.edu \
    --cc=linux-man@vger.kernel.org \
    --cc=tz@iana.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