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 11:10:00 -0000	[thread overview]
Message-ID: <bug-18927-131-fmBEczBfaQ@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 #6 from Egmont Koblinger <egmont at gmail dot com> ---
Joseph, thanks a lot for your research and the pointers!

Tests in "make tests" checking for the data is indeed another possible
approach.

It'd have the advantage that it points locale maintainers to actual ambiguous
cases and let them explicitly decide on the ordering, rather than this
remaining unnoticed and caught silently by the safeguard code.

It'd have some disadvantage on the other hand:
- Probably several current locales would fail this test; who would fix them?
- It would probably not catch bugs introduced by custom downstream patches to
locales (unless of course downstream packager runs "make tests").
- Sounds magnitudes harder for me to implement than my proposal; actually I
have no idea at this moment how to approach this problem. (E.g. for hu_HU I
_hope_ that I came up with a total ordering, but I'm not entirely certain.) It
sounds like kind of an automated mathematical proof for a rather complex
question.

That being said, I'd be fine with either approach.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-09-09 11:10 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 [this message]
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-fmBEczBfaQ@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: 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).