public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug locale/18927] Different strings should never collate as equal Date: Wed, 09 Sep 2015 13:58:00 -0000 [thread overview] Message-ID: <bug-18927-131-4JUk32MV5J@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18927-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18927 --- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Wed, 9 Sep 2015, fweimer at redhat dot com wrote: > I find it extremely surprising that strcoll is not to supposed to perform some > form of normalization in UTF-8 and similar locales. Is this really the > intent? The intent is that, to avoid various surprising effects discussed in those issues (and the previous discussions on the Austin Group mailing list), byte-distinct strings do not collate the same (although if they normalize the same, I'd expect them to collate together relative to all other strings - differences in normalization being of the lowest precedence in collation). > Is there a reason not to use the Unicode Collation Algorithm? > > <http://www.unicode.org/reports/tr10/> Well, our collation data is based on ISO 14651, which is meant to be equivalent, but updating it requires understanding just how the existing files relate to an old version of ISO 14651 and which local changes are or are not still relevant when updating to a newer version. See bug 14095. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-09-09 13:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-06 22:21 [Bug locale/18927] New: " egmont at gmail dot com 2015-09-07 12:17 ` [Bug locale/18927] " fweimer at redhat dot com 2015-09-09 7:21 ` fweimer at redhat dot com 2015-09-09 8:13 ` egmont at gmail dot com 2015-09-09 8:15 ` egmont at gmail dot com 2015-09-09 8:37 ` egmont at gmail dot com 2015-09-09 10:21 ` joseph at codesourcery dot com 2015-09-09 11:10 ` egmont at gmail dot com 2015-09-09 11:41 ` fweimer at redhat dot com 2015-09-09 13:58 ` joseph at codesourcery dot com [this message] 2015-09-09 15:28 ` egmont at gmail dot com 2015-09-09 19:23 ` egmont at gmail dot com 2023-05-31 16:57 ` carenas 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-18927-131-4JUk32MV5J@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).