From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: libc-alpha@sourceware.org
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: [PATCH 1/1] NEWS: Avoid the words "nominative" and "genitive".
Date: Fri, 27 Jul 2018 09:48:00 -0000 [thread overview]
Message-ID: <1290992034.436125.1532684872492@poczta.nazwa.pl> (raw)
In-Reply-To: <1656545809.435941.1532684630776@poczta.nazwa.pl>
Glibc supports two grammatical forms of month names and we keep adding
the locale data which actually use this feature but those two forms are
not necessarily nominative and genitive. It is better to use a more
generic term.
---
NEWS | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/NEWS b/NEWS
index b08fee6..c946ba2 100644
--- a/NEWS
+++ b/NEWS
@@ -48,13 +48,14 @@ Major new features:
- fdiv, fdivl, ddivl and corresponding fMdivfN, fMdivfNx, fMxdivfN and
fMxdivfNx functions.
-* Nominative and genitive month names are now supported for the following
+* Two grammatical forms of month names are now supported for the following
languages: Armenian, Asturian, Catalan, Czech, Kashubian, Occitan, Ossetian,
Scottish Gaelic, Upper Sorbian, and Walloon. The following languages now
- support abbreviated alternative month names: Catalan, Greek, and Kashubian.
+ support two grammatical forms in abbreviated month names: Catalan, Greek,
+ and Kashubian.
* Newly added locales: Lower Sorbian (dsb_DE) and Yakut (sah_RU) also
- include the support of the nominative and genitive month names.
+ include the support for two grammatical forms of month names.
* Building and running on GNU/Hurd systems now works without out-of-tree
patches.
--
2.7.5
next prev parent reply other threads:[~2018-07-27 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 9:44 [PATCH 0/1] " Rafal Luzynski
2018-07-27 9:48 ` Rafal Luzynski [this message]
2018-07-27 11:50 ` [PATCH 1/1] " Carlos O'Donell
2018-07-27 19:50 ` Rafal Luzynski
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=1290992034.436125.1532684872492@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=carlos@redhat.com \
--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).