From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 35
Date: Mon, 17 Jun 2019 22:33:00 -0000 [thread overview]
Message-ID: <bug-24614-716-0inmyy1eo6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24614-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24614
--- Comment #10 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
I don't yet close this bug report because this question has just come to my
mind: shouldn't the same change be applied to nl_AW (Dutch for Aruba)?
Links:
*
https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/nl_AW;hb=HEAD
* https://st.unicode.org/cldr-apps/v#/nl_AW/Number_Formatting_Patterns/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-06-17 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24614-716@http.sourceware.org/bugzilla/>
2019-05-23 15:49 ` [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 schwab@linux-m68k.org
2019-05-24 22:47 ` digitalfreak at lingonborough dot com
2019-05-25 5:23 ` wesley at weha dot be
2019-05-25 9:40 ` Keld Simonsen
2019-05-25 9:41 ` keld at keldix dot com
2019-05-25 9:54 ` sjon at hortensius dot net
2019-05-25 15:11 ` wesley at weha dot be
2019-05-28 22:35 ` digitalfreak at lingonborough dot com
2019-06-05 23:22 ` [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 35 digitalfreak at lingonborough dot com
2019-06-17 21:44 ` cvs-commit at gcc dot gnu.org
2019-06-17 22:33 ` digitalfreak at lingonborough dot com [this message]
2019-06-19 21:46 ` cvs-commit at gcc dot gnu.org
2019-06-19 21:50 ` 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-24614-716-0inmyy1eo6@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).