From: Marko Myllynen <myllynen@redhat.com>
To: Chris Leonard <cjlhomeaddress@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH 1/3] localedata: use same comment_char/escape_char in these files
Date: Sat, 12 Mar 2016 12:19:00 -0000 [thread overview]
Message-ID: <56E40938.3010708@redhat.com> (raw)
In-Reply-To: <CAHdAatZoQ-G0Y-m1O0+vjysCT++Nek_kKdfMc5FQoH3MPZL9PA@mail.gmail.com>
Hi,
On 2016-03-11 16:24, Chris Leonard wrote:
> I know that there are a number of glibc locales that I have
> contributed that are not represented in CLDR. Working with OLPC and
> Sugar Labs as I do, we are often on the bleeding edge of supporting
> new languages on GNUI/Linux-based systems.
Yes, locales only present in glibc but not in CLDR can't be
automatically updated (and most definitely won't be tossed away).
Do you have any rough estimate how many such locales there might be?
Thanks,
--
Marko Myllynen
next prev parent reply other threads:[~2016-03-12 12:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 7:54 Mike Frysinger
2016-02-20 7:54 ` [PATCH 2/3] localedata: standardize first few lines Mike Frysinger
2016-02-20 7:55 ` [PATCH 3/3] localedata: standardize copyright/license information [BZ #11213] Mike Frysinger
2016-02-25 20:13 ` [PATCH 1/3] localedata: use same comment_char/escape_char in these files Mike Frysinger
2016-03-09 22:24 ` Mike Frysinger
2016-03-11 10:31 ` Marko Myllynen
2016-03-11 14:24 ` Chris Leonard
2016-03-12 12:19 ` Marko Myllynen [this message]
2016-03-12 19:10 ` Chris Leonard
2016-03-13 17:50 ` Chris Leonard
2016-03-14 18:06 ` Carlos O'Donell
2016-04-11 18:58 ` Mike Frysinger
2016-04-11 20:46 ` Chris Leonard
2016-04-12 2:11 ` Mike Frysinger
2016-04-12 2:50 ` Chris Leonard
2016-03-14 18:20 ` Carlos O'Donell
2016-03-14 19:43 ` keld
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=56E40938.3010708@redhat.com \
--to=myllynen@redhat.com \
--cc=carlos@redhat.com \
--cc=cjlhomeaddress@gmail.com \
--cc=fweimer@redhat.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).