From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/20664] Unexpected collation in en_US.UTF-8, different to ICU CLDR
Date: Wed, 21 Dec 2016 21:08:00 -0000 [thread overview]
Message-ID: <bug-20664-716-rD6iS0GgWR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20664-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20664
--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to keld@keldix.com from comment #4)
> 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
> > 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:-)
I certainly agree that harmonization between both projects would be a great
goal. Having the best of both projects would be great. While I say "following
CLDR" what I mean is probably more accurate to say "harmonized with CLDR." So I
will endeavour to use such language in the future.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-21 21:08 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
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 [this message]
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=bug-20664-716-rD6iS0GgWR@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).