From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23831] nl_NL missing LC_NUMERIC thousands_sep
Date: Fri, 21 Jun 2019 18:51:00 -0000 [thread overview]
Message-ID: <bug-23831-716-o1fbGc7pg6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23831-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23831
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rafal Luzynski <rl@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=fefa21790b5081e5d04662a240e2efd18603ef86
commit fefa21790b5081e5d04662a240e2efd18603ef86
Author: Rafal Luzynski <digitalfreak@lingonborough.com>
Date: Fri Jun 21 20:18:48 2019 +0200
nl_{AW,NL}: Correct the thousands separator and grouping (bug 23831).
According to CLDR 35.1 and the bug report the thousands grouping
separator should be always "." (a single dot) and digits should be
grouped by 3.
[BZ #23831]
* localedata/locales/nl_AW (mon_thousands_sep): Set to ".".
* localedata/locales/nl_NL (mon_thousands_sep): Likewise.
(thousands_sep): Likewise.
(grouping): Set to 3;3.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-06-21 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 16:11 [Bug localedata/23831] New: " sourceware.org at troep dot com
2019-05-10 8:04 ` [Bug localedata/23831] " pander at users dot sourceforge.net
2019-05-28 22:43 ` digitalfreak at lingonborough dot com
2019-06-19 10:50 ` sourceware.org at troep dot com
2019-06-21 18:51 ` cvs-commit at gcc dot gnu.org [this message]
2019-06-21 18:53 ` digitalfreak at lingonborough dot com
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-23831-716-o1fbGc7pg6@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).