From: Keld Simonsen <keld@keldix.com>
To: carlos at redhat dot com <sourceware-bugzilla@sourceware.org>
Cc: libc-locales@sourceware.org
Subject: Re: [Bug localedata/20664] Unexpected collation in en_US.UTF-8, different to ICU CLDR
Date: Tue, 20 Dec 2016 16:00:00 -0000 [thread overview]
Message-ID: <20161220160001.GA6703@rap.rap.dk> (raw)
In-Reply-To: <bug-20664-716-8uryFdUWGW@http.sourceware.org/bugzilla/>
On Mon, Oct 03, 2016 at 11:10:56PM +0000, carlos at redhat dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=20664
>
> Carlos O'Donell <carlos at redhat dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |WAITING
> Last reconfirmed| |2016-10-03
> CC| |carlos at redhat dot com
> Ever confirmed|0 |1
>
> --- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
> Going forward we want glibc to track CLDR more closely. Therefore if you can
> find a glibc version that exhibits meaningful difference between CLDR, then
> please file a report, like this one.
>
> However, you have too many moving pieces for us to validate this, for example
> sort is not a good test case because it might itself not use glibc's collation
> tables for sorting.
>
> Can you construct a test case with strcoll that exhibits this problem?
I do not think we should aim at following CLDR closely, but we should minimize
differences. I actually think we should get CLDR to follow us more closely:-)
Bestregards
keld
next prev parent reply other threads:[~2016-12-20 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 22:56 [Bug localedata/20664] New: " meta at pobox dot com
2016-10-03 23:34 ` [Bug localedata/20664] " carlos at redhat dot com
2016-12-20 16:00 ` Keld Simonsen [this message]
2016-10-04 0:50 ` meta at pobox dot com
2016-10-04 19:08 ` meta at pobox dot com
2016-12-20 14:07 ` carlos at redhat dot com
2016-12-20 16:04 ` keld at keldix dot com
2016-12-21 21:08 ` carlos at redhat dot com
2021-10-11 20:18 ` kirelagin at gmail dot com
2021-10-11 20:51 ` carlos at redhat dot com
2021-10-11 21:00 ` kirelagin 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=20161220160001.GA6703@rap.rap.dk \
--to=keld@keldix.com \
--cc=libc-locales@sourceware.org \
--cc=sourceware-bugzilla@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).