From: Marko Myllynen <myllynen@redhat.com>
To: libc-alpha@sourceware.org
Cc: 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: Fri, 11 Mar 2016 10:31:00 -0000 [thread overview]
Message-ID: <56E29E8F.50209@redhat.com> (raw)
In-Reply-To: <20160309222439.GZ6588@vapier.lan>
Hi,
On 2016-03-10 00:24, Mike Frysinger wrote:
> On 25 Feb 2016 15:12, Mike Frysinger wrote:
>> ping this series ...
>
> ping some more ...
I think the silence here underlines once again that we simply don't have
enough "resources" in this area when a trivial change doesn't get a
timely review even when the patch is straightforward. Meaning that if we
want to keep the actual locale data in glibc in proper shape, using CLDR
is the only realistic and sustainable way forward.
Carlos and Florian exchanged few emails about CLDR/Unicode/glibc locale
copyright status, was there still something to be clarified on that front?
Mike's recent patch deprecated tel/fax fields in LC_IDENTIFICATION, are
there anything else we should could / should deprecate or remove?
(There's the PR https://sourceware.org/bugzilla/show_bug.cgi?id=14641 at
least but it's still being discussed, not sure how to deal with that.)
If/when those aspects are agreed upon, is there anything else or can we
then start using Mike's script to sync from CLDR? Perhaps the situation
with day abbreviations was left a bit open?
Mike, do you have a gut feeling how complete coverage the current CLDR
data provides per glibc locale, how many categories / keywords would
still need to be maintained without input from CLDR?
Oh, wrt the patch itself, LGTM.
Thanks,
--
Marko Myllynen
next prev parent reply other threads:[~2016-03-11 10:31 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 [this message]
2016-03-11 14:24 ` Chris Leonard
2016-03-12 12:19 ` Marko Myllynen
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=56E29E8F.50209@redhat.com \
--to=myllynen@redhat.com \
--cc=carlos@redhat.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).