From: "meta at pobox dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/20664] New: Unexpected collation in en_US.UTF-8, different to ICU CLDR
Date: Mon, 03 Oct 2016 22:56:00 -0000 [thread overview]
Message-ID: <bug-20664-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=20664
Bug ID: 20664
Summary: Unexpected collation in en_US.UTF-8, different to ICU
CLDR
Product: glibc
Version: 2.23
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: meta at pobox dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
On Fedora 24 with glibc-2.23.1 I get the following interesting sort behavior:
% echo -e "+00\n-0c\n+02\n-02" | LC_ALL=en_US.UTF-8 sort
+00
-02
+02
-0c
On Mac OS X 10.11 I get less surprising behavior:
% echo -e "+00\n-0c\n+02\n-02" | LC_ALL=en_US.UTF-8 sort
+00
+02
-02
-0c
I've tried to reproduce the first result using
<http://demo.icu-project.org/icu-bin/collation.html> but have not managed to
find a set of options that will do so.
So I'm not sure if it is technically a bug, but I would say that it's at least
unexpected and apparently diverges from ICU & CLDR.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-10-03 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 22:56 meta at pobox dot com [this message]
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
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@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).