public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Eidur Eidsson <eidurkr@outlook.com>,
	"libc-locales@sourceware.org" <libc-locales@sourceware.org>
Subject: Re: English locale for Europe – en_150
Date: Mon, 6 Jul 2020 20:28:06 -0400	[thread overview]
Message-ID: <cf0e948a-6aae-7cb3-c481-41d5c3fb4c7d@redhat.com> (raw)
In-Reply-To: <DB8PR04MB6972403CB63E4ED6A38CBDA9AA690@DB8PR04MB6972.eurprd04.prod.outlook.com>

On 7/6/20 7:38 PM, Eidur Eidsson via Libc-locales wrote:
> Hello to you all and thank you for your efforts
> 
> I have been wondering whether it would be feasible to include the
> locale "en_150" in glibc. This is a standard CLDR/ICU-defined locale
> (not a personal invention) that has been mentioned here before:
> https://sourceware.org/legacy-ml/libc-locales/2016-q2/msg00245.html
> .
> 
> I have prepared the following prototype by visually inspecting the
> ICU demonstration at
> https://icu4c-demos-7hxm2n5zgq-uc.a.run.app/icu-bin/locexp . Of
> course it would be better to automatically derive the locale from the
> library itself, but this shows what it could look like. The only
> immediate problem I can see is the use of "XXX" as a currency code.
> Perhaps "EUR" could be used instead (and "@euro" appended to the
> name) although this is strictly not an EU locale.

Thanks for submitting this work. We are currently in the freeze period
for glibc 2.32 which will release on August 1st, and so many developers
are busy with the release.

Is it OK to wait until after August 1st to resume this discussion and
review the changes for glibc 2.33?

-- 
Cheers,
Carlos.


  reply	other threads:[~2020-07-07  0:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 23:38 Eidur Eidsson
2020-07-07  0:28 ` Carlos O'Donell [this message]
2020-07-07  1:36   ` Eidur Eidsson
2020-07-07 17:28 ` English locale for Europe ? en_150 Keld Simonsen
2020-07-09 22:38   ` Eidur Eidsson
2020-07-12 15:57     ` Keld Simonsen
2020-07-13 19:19       ` Eidur Eidsson

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=cf0e948a-6aae-7cb3-c481-41d5c3fb4c7d@redhat.com \
    --to=carlos@redhat.com \
    --cc=eidurkr@outlook.com \
    --cc=libc-locales@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).