This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug localedata/18943] Collation of NFD strings


https://sourceware.org/bugzilla/show_bug.cgi?id=18943

--- Comment #3 from keld at keldix dot com <keld at keldix dot com> ---
On Thu, Sep 10, 2015 at 06:38:43AM +0000, egmont at gmail dot com wrote:
> 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.

What I mean is that ISO 14651 tables are made to have this feature - I
specified it.
Whether this is then the case for the i18n locale in glibc, I understand
that this is not the case at this point. Whether this is because of old data
or insufficient implementation of the standard I don't know.

best regards
keld

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]