public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Marko Myllynen <myllynen@redhat.com>
To: Stanislav Brabec <sbrabec@suse.cz>,
	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: Thu, 12 Dec 2019 15:16:00 -0000	[thread overview]
Message-ID: <aa3b05a0-e2b6-20ac-dfe2-352fc5f9fa65@redhat.com> (raw)
In-Reply-To: <8a842055-d3d3-5fc2-1e16-b1c38d6d7b3d@suse.cz>

Hi,

On 12/12/2019 16.15, Stanislav Brabec wrote:
> Marko Myllynen wrote:
>> On 04/12/2019 18.57, Stanislav Brabec wrote:
>>> On 06/20 2018 at 05:20 PM Stanislav Brabec wrote:
>>>> Marko Myllynen wrote:
>>> 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?
> 
> https://unicode-org.atlassian.net/browse/CLDR-11217 comment 6.

I don't think that's conclusive; the comment was made on Dec 2018 and
e.g. this later ticket on the subject still seems unresolved:

https://unicode-org.atlassian.net/browse/CLDR-11423

Also, CLDR 34 release notes mention French migration from NBSP to NNBSP
but CLDR 35/36 notes do not mention anything NNBSP related, surely that
kind of change would have been release notes worthy?

http://cldr.unicode.org/index/downloads/cldr-34
http://cldr.unicode.org/index/downloads/cldr-35
http://cldr.unicode.org/index/downloads/cldr-36

Thanks,

-- 
Marko Myllynen

  reply	other threads:[~2019-12-12 15:16 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
2019-12-12 13:03     ` Marko Myllynen
2019-12-12 14:16       ` Stanislav Brabec
2019-12-12 15:16         ` Marko Myllynen [this message]
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=aa3b05a0-e2b6-20ac-dfe2-352fc5f9fa65@redhat.com \
    --to=myllynen@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mfabian@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).