Re: Locales: Thousands separator

[Marko Myllynen <myllynen@redhat.com>]

Hi Stanislav,

On 04/12/2019 18.57, Stanislav Brabec wrote:
> 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

Thanks for the heads-up. However, I'm unable to find where this
intention is clearly stated, could you please share a public reference
for this that could be used to pass the news onwards?

Thanks,

-- 
Marko Myllynen