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 08:37:00 -0000 [thread overview] Message-ID: <bug-18927-131-A8AtFf5KIF@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 #4 from Egmont Koblinger <egmont at gmail dot com> --- Going further with the example that strcoll("ssz", "szsz") == 0 (as it used to be in hu_HU): It's possible that "sort" prints multiple occurrences of these strings in mixed order. E.g. it might legally output this: szsz ssz szsz ssz ssz szsz (etc.) based on random, or stableness. In turn, when this is piped to "uniq", it might make some sense to print the first entry only (although it's still random whether that'll be "ssz" or "szsz"). Piping it to "LC_ALL=C uniq" instead wouldn't make much more sense either, its output (even the number of lines) would also be random. Trying to think of the big picture rather than the details, in my opinion this unexpected behavior should ideally be stopped at the very core, that is, in the locale implementation of strcoll() and strxfrm(), so that "sort" cannot produce the output shown above. Then there's no subsequent problem with "uniq" whatsoever. Otherwise, the only reliable way to print each line exactly once would be "LC_ALL=C sort | LC_ALL=C uniq" (or "LC_ALL=C sort -u" for short), and if you wanted to have the output sorted according to your current locale, you'd have to issue "LC_ALL=C sort | LC_ALL=C uniq | sort" (or "LC_ALL=C sort -u | sort" for short). Currently if you issue the obvious locale-dependent "sort | uniq" or "sort -u", you could never be sure whether the underlying locale's definition might cause unexpected (i.e. faulty - as seen by the user) behavior. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-09-09 8:37 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 [this message] 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 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-A8AtFf5KIF@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).