public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/16608] es_US locale has invalid collation rules for 'ch' and 'll'
Date: Wed, 19 Feb 2014 20:05:00 -0000	[thread overview]
Message-ID: <bug-16608-716-gs5BvLvoN5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16608-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16608

--- Comment #3 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Aldo from comment #2)
> Not entirely sure if this link is the right one, but it seems they agree
> with the rules:
> 
> http://st.unicode.org/cldr-apps/v#/es_EC/Alphabetic_Information/

That doesn't provide enough information. For example if instead you use libicu
(http://site.icu-project.org/) to do the sorting and it comes out as expected
then that argues CLDR has the same interpretation. In the light of our desire
to harmonize better with CLDR we would make the change locally.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2014-02-19 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 20:03 [Bug localedata/16608] New: " aldocassola at gmail dot com
2014-02-19 20:03 ` [Bug localedata/16608] " aldocassola at gmail dot com
2014-02-19 20:04 ` carlos at redhat dot com
2014-02-19 20:05 ` aldocassola at gmail dot com
2014-02-19 20:05 ` aldocassola at gmail dot com
2014-02-19 20:05 ` carlos at redhat dot com [this message]
2014-02-19 21:06 ` aldocassola at gmail dot com
2014-02-19 21:31 ` aldocassola at gmail dot com
2014-06-13  8:14 ` fweimer at redhat dot com
2017-10-21  8:25 ` maiku.fabian at gmail dot com
2024-01-04 12:05 ` maiku.fabian at gmail dot com

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-16608-716-gs5BvLvoN5@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).