From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23318] Use thousands separator matching CLDR
Date: Wed, 20 Jun 2018 13:18:00 -0000 [thread overview]
Message-ID: <bug-23318-716-EUmrupcTN2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23318-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23318
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Marko Myllynen from comment #0)
> Since commit 70a6707 many locales use U+202F as thousands separator instead
> of U+00A0, only the latter is used in CLDR. Please change locales currently
> using U+202F to use U+00A0 instead to be consistent with CLDR.
>
> For more background, please see the thread starting at:
>
> https://sourceware.org/ml/libc-alpha/2018-06/msg00598.html
>
> Thanks.
Marko,
Are you going to work to fix this? I'd be happy to review a patch from you to
correct this. Testing this should be relatively straight forward too.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-06-20 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 13:12 [Bug localedata/23318] New: " myllynen at redhat dot com
2018-06-20 13:18 ` carlos at redhat dot com [this message]
2018-06-20 13:25 ` [Bug localedata/23318] " myllynen at redhat dot com
2018-06-20 15:22 ` sbrabec at suse dot cz
2018-06-28 11:11 ` myllynen at redhat dot com
2024-01-02 12:06 ` maiku.fabian at gmail dot com
2024-01-02 12:07 ` maiku.fabian at gmail 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-23318-716-EUmrupcTN2@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).