public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike FABIAN <mfabian@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	 Carlos O'Donell <carlos@redhat.com>
Subject: Re: Locales: Thousands separator
Date: Wed, 27 Jun 2018 06:31:00 -0000	[thread overview]
Message-ID: <s9dlgb0yc3u.fsf@taka.site> (raw)
In-Reply-To: <84160848.326497.1529613070136@poczta.nazwa.pl> (Rafal Luzynski's message of "Thu, 21 Jun 2018 22:31:10 +0200 (CEST)")

Rafal Luzynski <digitalfreak@lingonborough.com> さんはかきました:

> 21.06.2018 16:15 Carlos O'Donell <carlos@redhat.com> wrote:
>> [...]
>> We could switch to NBSP, and just wait for the CLDR ticket to be
>> resolved, and then switch back to NNBSP and we would both match.
>>
>> The goal is to try harmonize this data across the various
>> implementations. There is nothing more frustrating for users
>> than to have different display data like this.
>>
>> Does that make sense?
>
> As I said previously, I will not object.  But I have one suggestion:
> as the new ticket has been reported to CLDR let's wait few days
> and push our change just before the freeze which will be soon anyway.
> Just in case if CLDR responds "OK, NNBSP would be better" within
> those few days.  I would like to avoid switching back and forth.
>
> I hope the change is as simple as "git revert", otherwise we may
> prepare a patch already and keep it around.

It looks like CLDR agrees that NNBSP is better:

https://unicode.org/cldr/trac/ticket/11217#no2

     Status changed from new to accepted

     Need to check that these are parse variants. Typographically the right
     approach. For discussion.

-- 
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。

      reply	other threads:[~2018-06-27  6:31 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
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 [this message]

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=s9dlgb0yc3u.fsf@taka.site \
    --to=mfabian@redhat.com \
    --cc=carlos@redhat.com \
    --cc=digitalfreak@lingonborough.com \
    --cc=libc-alpha@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).