This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/12349] Incorrect thousands separator and first weekday for eu_ES locale
- From: "keld at keldix dot com" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sourceware dot org
- Date: Tue, 01 Jul 2014 19:58:55 +0000
- Subject: [Bug localedata/12349] Incorrect thousands separator and first weekday for eu_ES locale
- Auto-submitted: auto-generated
- References: <bug-12349-716 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12349
--- Comment #11 from keld at keldix dot com <keld at keldix dot com> ---
On Tue, Jul 01, 2014 at 09:11:46AM +0000, myllynen at redhat dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=12349
>
> Marko Myllynen <myllynen at redhat dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |myllynen at redhat dot com
>
> --- Comment #10 from Marko Myllynen <myllynen at redhat dot com> ---
> Perhaps there are certain locales where glibc is better maintained but in
> general CLDR looks to have more experts involved. For example, in some cases
> there are national initiatives which work directly with CLDR. This is not
> surprising given the vendor independent nature of CLDR. Now that Microsoft has
> also joined CLDR [1] as contributing partner (alongside with Google, IBM, and
> others) it certainly looks like CLDR has notable momentum and should not be
> ignored.
>
> 1)
> http://unicode-inc.blogspot.com/2014/05/cldr-v26-open-for-data-submission.html
Yes, we should not ignore CLDR. But there are also national initiatives
that work directly with ISO on their national conventions, where they do not
work
directly with CLDR. CLDR is an American initiative and is very much
dominated by US companies, as you also indicate.
Best regards
keld
--
You are receiving this mail because:
You are the assignee for the bug.