From: TAMUKI Shoichi <tamuki@linet.gr.jp>
To: libc-alpha@sourceware.org
Subject: [PATCH] manual: Fix the wording to "alternative" rather than "alternate"
Date: Thu, 17 Jan 2019 15:34:35 +0900 [thread overview]
Message-ID: <201901170634.AA04186@tamuki.linet.gr.jp> (raw)
ChangeLog:
* manual/time.texi (strftime): Fix the wording to "alternative" rather
than "alternate".
---
manual/time.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/manual/time.texi b/manual/time.texi
index 9e981314876..fd7781c5317 100644
--- a/manual/time.texi
+++ b/manual/time.texi
@@ -1339,7 +1339,7 @@ POSIX.2-1992 and by @w{ISO C99}, are:
@table @code
@item E
-Use the locale's alternate representation for date and time. This
+Use the locale's alternative representation for date and time. This
modifier applies to the @code{%c}, @code{%C}, @code{%x}, @code{%X},
@code{%y} and @code{%Y} format specifiers. In a Japanese locale, for
example, @code{%Ex} might yield a date format based on the Japanese
@@ -1347,7 +1347,7 @@ Emperors' reigns.
@item O
With all format specifiers that produce numbers: use the locale's
-alternate numeric symbols.
+alternative numeric symbols.
With @code{%B}, @code{%b}, and @code{%h}: use the grammatical form for
month names that is appropriate when the month is named by itself,
@@ -1355,7 +1355,7 @@ rather than the form that is appropriate when the month is used as
part of a complete date. This is a GNU extension.
@end table
-If the format supports the modifier but no alternate representation
+If the format supports the modifier but no alternative representation
is available, it is ignored.
The conversion specifier ends with a format specifier taken from the
--
2.12.2
next reply other threads:[~2019-01-17 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 6:34 TAMUKI Shoichi [this message]
2019-01-23 17:37 ` [PATCH] manual: Fix the wording to "alternative" rather than "alternate" Carlos O'Donell
2019-01-23 20:39 ` Zack Weinberg
2019-01-23 21:12 ` Carlos O'Donell
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201901170634.AA04186@tamuki.linet.gr.jp \
--to=tamuki@linet.gr.jp \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).