public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stanislav Brabec <sbrabec@suse.cz>
To: Marko Myllynen <myllynen@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Cc: Mike Fabian <mfabian@redhat.com>, Carlos O'Donell <carlos@redhat.com>
Subject: Re: Locales: Thousands separator
Date: Wed, 04 Dec 2019 16:57:00 -0000	[thread overview]
Message-ID: <1b931a1c-8646-960a-c51e-8f65a7f384f1@suse.cz> (raw)
In-Reply-To: <c96c4d03-2433-e3be-cc96-0f4cee0aba42@suse.cz>

On 06/20 2018 at 05:20 PM Stanislav Brabec wrote:
> 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.
...
>> I have been under impression that the long-term plan for glibc locales
>> would be to use CLDR data as source to the extent possible so this
>> change would seem to be at odds with that plan. I found no indications
>> from CLDR Trac that CLDR would be switching to NNBSP. This inconsistency
>> also presents a dilemma for keymap definitions when there is only one
>> feasible key combination available for producing non-breaking space:
>> which variant to choose, the glibc one or the CLDR one.
>>
>> Given the considerations above, what do the glibc maintainers think
>> about the current situation, is this inconsistency seen as an issue?
> 
> When I proposed this change, I was not aware of use of CLDR.
> 
> Created ticket now:
> https://unicode.org/cldr/trac/ticket/11217
> 
CLDR decided to accept the NNBSP approach.

In the CLDR version 36, they decided to use French as a NNBSP trial:
https://www.unicode.org/cldr/charts/36/by_type/numbers.symbols.html#a1ef41eaeb6982d

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                         e-mail: sbrabec@suse.com
Křižíkova 148/34 (Corso IIa)                    tel: +420 284 084 060
186 00 Praha 8-Karlín                          fax:  +420 284 084 001
Czech Republic                                    http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76

  parent reply	other threads:[~2019-12-04 16:57 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
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 [this message]
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=1b931a1c-8646-960a-c51e-8f65a7f384f1@suse.cz \
    --to=sbrabec@suse.cz \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mfabian@redhat.com \
    --cc=myllynen@redhat.com \
    /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).