From: Paul Eggert <eggert@cs.ucla.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: linux-man@vger.kernel.org, Time Zone Mailing List <tz@iana.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [tz] "time zone" vs "timezone" in documentation
Date: Fri, 22 Jun 2018 12:54:03 -0700 [thread overview]
Message-ID: <bad33c62-5c37-fbc4-a6d2-f0e24c2b74c5@cs.ucla.edu> (raw)
In-Reply-To: <26348.1529693539@jinx.noi.kre.to>
On 06/22/2018 11:52 AM, Robert Elz wrote:
> Whether timezone, timestamp, or filesystem have reached that state yet
> or not isn't clear - personally, I think they have
Yes, I also think they're words in reasonably common use. The question
is whether they're the preferred spelling, and whether their
connotations differ from those of the corresponding two-word phrases. In
my Google-based survey, I found that "timestamp" and "time stamp" are
within shouting distance in the New York Times (about 164 vs 295 hits
overall). In contrast, the Times almost invariably uses "time zone": I
found thousands of instances of "time zone" but just one instance of
"timezone" (other than in proper names or blogs) and it was originally
printed "time-" at the end of one line and "zone changes" at the start
of the next, so it was possibly the old-fashioned "time-zone" or a
disambiguating hyphen placed between the nouns "time" and "zone", before
the noun "changes" (for the full context, see
<https://www.nytimes.com/1975/11/06/archives/science-seeks-to-end-the-miseries-of-aging-pacemakers-and-clocks.html>
and look for the scanned image). Of course this is just one newspaper,
but it's a major one and it's clear that the New York Time style frowns
on "timezone" whereas it permits either "timestamp" or "time stamp". I
expect that similar results would be found in other reliable sources.
Overall, my impression is that "time zone" is by far the common spelling
for the common notion of the regions that you see on maps, whereas
"timezone" is primarily used in computer-related material, where its
interpretation is often the one I'm suggesting.
next prev parent reply other threads:[~2018-06-22 19:54 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
2018-06-22 18:52 ` Robert Elz
2018-06-22 19:54 ` Paul Eggert [this message]
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=bad33c62-5c37-fbc4-a6d2-f0e24c2b74c5@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=kre@munnari.OZ.AU \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.