From: Alejandro Colomar <alx.manpages@gmail.com>
To: tz@iana.org, Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>
Subject: [PATCH v2 2/4] zic.8: s/time zone/timezone/ for consistency
Date: Wed, 23 Nov 2022 14:48:27 +0100 [thread overview]
Message-ID: <20221123134827.10420-2-alx@kernel.org> (raw)
In-Reply-To: <20221123134827.10420-1-alx@kernel.org>
This adds consistency across other manual pages, and with POSIX.1.
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
zic.8 | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/zic.8 b/zic.8
index c2c61739..7fb51dde 100644
--- a/zic.8
+++ b/zic.8
@@ -212,7 +212,7 @@ .SH OPTIONS
.B zic
prohibit this.
.PP
-A time zone abbreviation uses a
+A timezone abbreviation uses a
.B %z
format.
Pre-2015 versions of
@@ -270,7 +270,7 @@ .SH OPTIONS
pre-2014 versions of the reference client support at most 1200
transitions.
.PP
-A time zone abbreviation has fewer than 3 or more than 6 characters.
+A timezone abbreviation has fewer than 3 or more than 6 characters.
POSIX requires at least 3, and requires implementations to support
at least 6.
.PP
@@ -297,7 +297,7 @@ .SH FILES
\*<https://pubs\*:.opengroup\*:.org/\*:onlinepubs/\*:9699919799/\*:basedefs/\*:V1_chap06\*:.html\*>
and the encoding's non-unibyte characters should consist entirely of
non-PPCS bytes. Non-PPCS characters typically occur only in comments:
-although output file names and time zone abbreviations can contain
+although output file names and timezone abbreviations can contain
nearly any character, other software will work better if these are
limited to the restricted syntax described under the
.B \*-v
@@ -521,7 +521,7 @@ .SH FILES
.q "EST"
or
.q "EDT" )
-of time zone abbreviations to be used when this rule is in effect.
+of timezone abbreviations to be used when this rule is in effect.
If this field is
.q \*- ,
the variable part is null.
@@ -574,12 +574,12 @@ .SH FILES
this amount matters.
.TP
.B FORMAT
-The format for time zone abbreviations.
+The format for timezone abbreviations.
The pair of characters
.B %s
is used to show where the
.q "variable part"
-of the time zone abbreviation goes.
+of the timezone abbreviation goes.
Alternatively, a format can use the pair of characters
.B %z
to stand for the UT offset in the form
@@ -596,12 +596,12 @@ .SH FILES
Alternatively,
a slash (/)
separates standard and daylight abbreviations.
-To conform to POSIX, a time zone abbreviation should contain only
+To conform to POSIX, a timezone abbreviation should contain only
alphanumeric ASCII characters,
.q "+"
and
.q "\*-".
-By convention, the time zone abbreviation
+By convention, the timezone abbreviation
.q "\*-00"
is a placeholder that means local time is unspecified.
.TP
@@ -609,7 +609,7 @@ .SH FILES
The time at which the UT offset or the rule(s) change for a location.
It takes the form of one to four fields YEAR [MONTH [DAY [TIME]]].
If this is specified,
-the time zone information is generated from the given UT offset
+the timezone information is generated from the given UT offset
and rule change until the time specified, which is interpreted using
the rules in effect just before the transition.
The month, day, and time of day have the same format as the IN, ON, and AT
@@ -867,7 +867,7 @@ .SH "EXTENDED EXAMPLE"
and
.q "BMT"
were initially used, respectively. Since
-Swiss rules and later EU rules were applied, the time zone abbreviation
+Swiss rules and later EU rules were applied, the timezone abbreviation
has been CET for standard time and CEST for daylight saving
time.
.SH FILES
--
2.38.1
next prev parent reply other threads:[~2022-11-23 13:55 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 ` Alejandro Colomar [this message]
2022-11-23 18:42 ` [PATCH v2 2/4] zic.8: s/time zone/timezone/ for consistency Paul Eggert
2022-11-23 19:02 ` Alejandro Colomar
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=20221123134827.10420-2-alx@kernel.org \
--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