From: Walter Harms <wharms@bfs.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org, Time Zone Mailing List <tz@iana.org>
Subject: Re: [tz] "time zone" vs "timezone" in documentation
Date: Wed, 4 Jul 2018 09:35:03 +0200 (CEST) [thread overview]
Message-ID: <1372798594.84631.1530689704630@ox-groupware.bfs.de> (raw)
In-Reply-To: <c79ebe96-ee49-5805-28bf-bdeab61930b1@cs.ucla.edu>
> Paul Eggert <eggert@cs.ucla.edu> hat am 27. Juni 2018 um 21:46 geschrieben:
>
>
> Paul Eggert wrote:
> > We could distinguish "time zone" in the usual English-language sense (a set
> > of
> > geographic locations that currently share the same standard time offset from
> >
> > UTC) from "timezone" in the POSIX sense (a history and predicted future of
> > UTC
> > offsets, abbreviations and isdst flags). If so, the tzdb documentation could
> > be
> > more careful about using "time zone" for the former and "timezone" for the
> > latter, and this would make for fewer changes to the GNU/Linux man-pages for
> >
> > tzdb. I can look into this and propose an updated set of tzdb-related
> > patches
> > accordingly.
>
> I've done that, plus a few other minor fixups, and have installed the attached
>
> proposed patches into the development tzdb repository on GitHub. I plan to
> follow up by emailing to linux-man a corresponding set of patches to the
> GNU/Linux man pages.
I would suggest adding a glossary with "timezone" and "time zone". In a few
years everyone will have forgotten about this and everyone is confused why
this was done.
re,
wh
next prev parent reply other threads:[~2018-07-04 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180619013049.4097-1-eggert@cs.ucla.edu>
[not found] ` <9838498d-0dc2-b51f-08af-fb447196cce5@gmail.com>
[not found] ` <26ec9696-f120-15e7-9d9f-9a66eefce9a0@cs.ucla.edu>
2018-06-22 16:18 ` [tz] "time zone" vs "timezone" in documentation Paul Eggert
2018-06-22 18:21 ` Philip Paeps
2018-06-27 19:46 ` Paul Eggert
2018-07-04 7:35 ` Walter Harms [this message]
2018-06-22 18:52 ` Robert Elz
2018-06-22 19:54 ` Paul Eggert
2018-06-22 20:14 ` Clive D.W. Feather
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=1372798594.84631.1530689704630@ox-groupware.bfs.de \
--to=wharms@bfs.de \
--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;
as well as URLs for NNTP newsgroup(s).