From: "egmont at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/18943] Collation of NFD strings
Date: Thu, 10 Sep 2015 06:40:00 -0000 [thread overview]
Message-ID: <bug-18943-716-H1e9I6A4D0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18943-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18943
--- Comment #2 from Egmont Koblinger <egmont at gmail dot com> ---
(In reply to keld@keldix.com from comment #1)
> Both NFC and NFD data should collate as expected. And you can mix then as
> you like,
> you do not need to normalize them.
Not sure what you mean by "should" or "can"... whether you agree with me that
this should be the desired behavior (glad to hear it), or claim that this is
what actually happens (which is unfortunately false).
Revert a broken change pointed out in bug 18589 (to make the tests pass
deterministicly at the first place). Run "make tests" -> success.
Then use "uconv -x any-nfd" to convert fr_FR.in, si_LK.in, tr_TR.in, uk_UA.in
(and perhaps hu_HU.in from bug 18934) to NFD. Re-run "make tests" -> failure.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-09-10 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 21:19 [Bug localedata/18943] New: " egmont at gmail dot com
2015-09-10 5:51 ` Keld Simonsen
2015-09-10 5:52 ` [Bug localedata/18943] " keld at keldix dot com
2015-09-10 6:40 ` egmont at gmail dot com [this message]
2015-09-10 6:49 ` Keld Simonsen
2015-09-10 6:52 ` keld at keldix dot com
2015-09-10 7:25 ` egmont at gmail dot com
2017-10-21 8:12 ` maiku.fabian 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-18943-716-H1e9I6A4D0@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).