From: Mike FABIAN <mfabian@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Marko Myllynen <myllynen@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Stanislav Brabec <sbrabec@suse.cz>
Subject: Re: Locales: Thousands separator
Date: Wed, 20 Jun 2018 15:36:00 -0000 [thread overview]
Message-ID: <s9d602dzd06.fsf@taka.site> (raw)
In-Reply-To: <3c30deb6-d0cb-ed92-6403-d7588719c543@redhat.com> (Carlos O'Donell's message of "Wed, 20 Jun 2018 09:01:24 -0400")
Carlos O'Donell <carlos@redhat.com> ããã¯ããã¾ãã:
> On 06/20/2018 04:10 AM, Marko Myllynen wrote:
>> Commit 70a6707 [1] changed many locales to use U+202F NARROW NO-BREAK
>> SPACE (NNBSP) as the thousands separator instead of U+00A0 NO-BREAK
>> SPACE (NBSP). The patch submission nor the follow-up discussion [2] did
>> not cite any standards or references as rationale for this change.
>
> No standards need citing. It was clear that SPACE was wrong.
>
>> Given the considerations above, what do the glibc maintainers think
>> about the current situation, is this inconsistency seen as an issue?
>
> ... the mistake is that we didn't check to harmonize with CLDR.
>
> Please file a bug and we'll change from NNBSP->NBSP to match CLDR.
CLDR usually has U+0020 SPACE, *not* U+00A0 NO-BREAK-SPACE.
See for example:
http://unicode.org/cldr/trac/browser/trunk/common/main/fi.xml
which contains:
5751 <symbols numberSystem="latn">
5752 <decimal>,</decimal>
5753 <group> </group>
^ This is a regular space U+0020 SPACE
5754 <list>;</list>
5755 <percentSign>%</percentSign>
5756 <plusSign>+</plusSign>
5757 <minusSign>â</minusSign>
5758 <exponential>E</exponential>
5759 <superscriptingExponent>Ã</superscriptingExponent>
5760 <perMille>â°</perMille>
5761 <infinity>â</infinity>
5762 <nan>epäluku</nan>
5763 <timeSeparator>.</timeSeparator>
5764 </symbols>
> Even though I think NBSP is visually wrong, we need to change both
> CLDR and glibc at the same time to match.
>
> Cheers,
> Carlos.
--
Mike FABIAN <mfabian@redhat.com>
ç¡ç ä¸è¶³ã¯ããä»äºã®æµã ã
next prev parent reply other threads:[~2018-06-20 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 8:11 Marko Myllynen
2018-06-20 13:01 ` Carlos O'Donell
2018-06-20 13:17 ` Marko Myllynen
2018-06-20 15:36 ` Mike FABIAN [this message]
2018-06-20 17:25 ` Marko Myllynen
2018-06-20 21:26 ` Andreas Schwab
2018-06-21 13:07 ` Marko Myllynen
2018-06-25 16:48 ` Marko Myllynen
2018-06-20 16:42 ` Florian Weimer
2018-06-20 15:20 ` Stanislav Brabec
2018-06-20 15:52 ` Mike FABIAN
2019-12-04 16:57 ` Stanislav Brabec
2019-12-12 13:03 ` Marko Myllynen
2019-12-12 14:16 ` Stanislav Brabec
2019-12-12 15:16 ` Marko Myllynen
2018-06-20 22:42 ` Rafal Luzynski
2018-06-21 14:16 ` Carlos O'Donell
2018-06-21 20:31 ` Rafal Luzynski
2018-06-27 6:31 ` Mike FABIAN
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=s9d602dzd06.fsf@taka.site \
--to=mfabian@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=myllynen@redhat.com \
--cc=sbrabec@suse.cz \
/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).