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: Mon, 11 Oct 2021 20:51:47 +0000 [thread overview]
Message-ID: <bug-20664-716-Gd1kBPv59k@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20664-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20664
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |2.33
--- Comment #7 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Kirill Elagin from comment #6)
> I am getting collation results as expected (meaning, no difference between
> en_US.UTF-8 and POSIX) for the example strings with glibc 2.32.
>
> Is this issue safe to close?
In glibc 2.32 we upgraded to Unicode 13.0.0, and glibc 2.35 (Feb 2, 2022) will
include Unicode 14.0.0 support. Neither of these updates substantially changed
collation (involved in sort). However, I agree with you that Fedora 34 with
glibc 2.33 that we get matching results:
echo -e "+00\n-0c\n+02\n-02" | LC_ALL=en_US.UTF-8 sort
+00
+02
-02
-0c
The collation data always had <U002B> < <U002D> which results in + < -. I'm
marking this as RESOLVED/FIXED in glibc 2.33. We can reopen if we run into this
again to determine what is the root cause of the original mis-ordering in 2.32.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-11 20:51 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
2021-10-11 20:18 ` kirelagin at gmail dot com
2021-10-11 20:51 ` carlos at redhat dot com [this message]
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-Gd1kBPv59k@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).