From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/15262] LC_MESSAGES.yesexpr/noexpr: inconsistent use of romanisation
Date: Sat, 23 Apr 2016 07:56:00 -0000 [thread overview]
Message-ID: <bug-15262-716-hVnI29L9g6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15262-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15262
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via 06f61f191b9217c2b65f568297c0e76d3e0cce3c (commit)
from f982160ead05503667c0e27efdc09e24e8b39d15 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=06f61f191b9217c2b65f568297c0e76d3e0cce3c
commit 06f61f191b9217c2b65f568297c0e76d3e0cce3c
Author: Mike Frysinger <vapier@gentoo.org>
Date: Tue Apr 19 00:00:58 2016 -0400
localedata: LC_MESSAGES.{yes,no}expr: standardize yY/nN [BZ #15262]
The vast majority of languages include yY/nN in their yes/no regexes.
Standardize the few that were missing them.
ms_MY: noexpr: add nN
nan_TW@latin: yesexpr: add yY
nan_TW@latin: noexpr: add nN
se_NO: noexpr: add nN
This also highlighted a few that were incorrectly using yY/nN because
they clashed with their localized messages:
uz_UZ: yesexpr: change ^[+1YyHh] to ^[+1ҲҳHh]
uz_UZ: noexpr: change ^[-0JjNn] to ^[-0ЙйNnYyJj]
uz_UZ@cyrillic: yesexpr: change ^[+1ҲҳYy] to ^[+1ҲҳHh]
uz_UZ@cyrillic: noexpr: change ^[-0ЙйNn] to [-0ЙйNnYyJj]
yo_NG: move nN (short for Bẹ́ẹ̀ni) from noexpr to yesexpr
-----------------------------------------------------------------------
Summary of changes:
localedata/ChangeLog | 13 +++++++++++++
localedata/locales/ms_MY | 2 +-
localedata/locales/nan_TW@latin | 4 ++--
localedata/locales/se_NO | 2 +-
localedata/locales/uz_UZ | 8 +++++---
localedata/locales/uz_UZ@cyrillic | 7 +++++--
localedata/locales/yo_NG | 4 ++--
7 files changed, 29 insertions(+), 11 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-04-23 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 11:42 [Bug localedata/15262] New: inconsistent use of romanisation in in yesexpr/noexpr LC_MESSAGES daxim at cpan dot org
2014-06-13 19:15 ` [Bug localedata/15262] " fweimer at redhat dot com
2016-04-15 21:27 ` [Bug localedata/15262] LC_MESSAGES.yesexpr/noexpr: inconsistent use of romanisation vapier at gentoo dot org
2016-04-18 2:46 ` vapier at gentoo dot org
2016-04-23 7:56 ` cvs-commit at gcc dot gnu.org [this message]
2016-04-23 7:56 ` vapier at gentoo dot org
2016-08-02 3:28 ` cvs-commit at gcc dot gnu.org
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=bug-15262-716-hVnI29L9g6@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).