public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egmont at gmail 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 15:28:00 -0000 [thread overview] Message-ID: <bug-18927-131-mwSA6kkPOc@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 #9 from Egmont Koblinger <egmont at gmail dot com> --- (In reply to joseph@codesourcery.com from comment #8) > On Wed, 9 Sep 2015, fweimer at redhat dot com wrote: > 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). I'd love to see it, this is what this bugreport is about :) tr10's A.3.2 shows the wrappers that turn a non-deterministic coll/xfrm methods into deterministic ones - pretty much what I outlined here, although they forget to mention that SEPARATOR needs to sort before any possible byte within old_sort_key. The wrapper around strcoll() is more obvious. The fact that they talk about these wrappers as possible external methods, rather than having to be build inside the collate implementation, makes me uncertain whether my request is in align with the standard. (I'm yet to read the whole docs.) Btw, a side question: What happens, and what should happen, if the input to strcoll() or strxfrm() is not valid UTF-8? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-09-09 15:28 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 2015-09-09 15:28 ` egmont at gmail dot com [this message] 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-mwSA6kkPOc@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).