public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "keld at keldix dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/12349] Incorrect thousands separator and first weekday for eu_ES locale
Date: Tue, 01 Jul 2014 21:35:00 -0000	[thread overview]
Message-ID: <bug-12349-716-56S4U768XM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12349-716@http.sourceware.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.

  parent reply	other threads:[~2014-07-01 21:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 12:00 [Bug localedata/12349] New: " julenx at gmail dot com
2011-05-09 17:55 ` [Bug localedata/12349] " drepper.fsp at gmail dot com
2011-05-11  9:35 ` mikel at olasagasti dot info
2012-06-04 16:42 ` pasky at ucw dot cz
2012-11-20 12:21 ` cjlhomeaddress at gmail dot com
2014-06-27 14:42 ` fweimer at redhat dot com
2014-06-27 14:42 ` julenx at gmail dot com
2014-06-27 15:49 ` carlos at redhat dot com
2014-06-27 16:07   ` Keld Simonsen
2014-06-27 16:09 ` keld at keldix dot com
2014-06-29 13:18 ` julenx at gmail dot com
2014-06-29 17:20   ` Keld Simonsen
2014-06-29 20:38 ` keld at keldix dot com
2014-07-01  9:38 ` myllynen at redhat dot com
2014-07-01 19:58   ` Keld Simonsen
2014-07-01 21:35 ` keld at keldix dot com [this message]
2016-02-19 10:47 ` [Bug localedata/12349] eu_ES: incorrect thousands separator and first weekday vapier at gentoo dot org
2016-04-16  7:38 ` vapier at gentoo dot org
2016-04-23  7:12 ` [Bug localedata/12349] eu_ES: incorrect thousands separator vapier at gentoo dot org
2016-05-16 21:46 ` [Bug core/12349] " gobisha6355 at gmail dot com
2016-05-16 21:46 ` [Bug localedata/12349] " jsm28 at gcc dot gnu.org
2017-08-14 12:42 ` maiku.fabian at gmail dot com
2017-08-14 14:33 ` cvs-commit at gcc dot gnu.org
2017-08-14 14:34 ` maiku.fabian at gmail dot com
2017-08-14 14:54 ` maiku.fabian at gmail dot com
2017-09-14 11:07 ` jsm28 at gcc dot gnu.org

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=bug-12349-716-56S4U768XM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).