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 #1 from keld at keldix dot com <keld at keldix dot com> ---
On Wed, Sep 09, 2015 at 07:46:02PM +0000, egmont at gmail dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=18943
> 
>             Bug ID: 18943
>            Summary: Collation of NFD strings
>            Product: glibc
>            Version: 2.22
>             Status: NEW
>           Severity: enhancement
>           Priority: P2
>          Component: localedata
>           Assignee: unassigned at sourceware dot org
>           Reporter: egmont at gmail dot com
>                 CC: libc-locales at sourceware dot org
>   Target Milestone: ---
> 
> Forking off from bug 18927 comment 8 & 11:
> 
> Collate definitions currently assume the input to be in NFC. If the available
> UTF-8 unittests are converted to NFD (the localedata/*.in files which have
> UTF-8 in Makefile's test-input) then they fail.
> 
> It would be nice to automatically make normalization the lowest priority factor
> when deciding on collation, so that different normalizations of the same word
> are as close to each other as possible. That is, to implement it once (e.g. in
> iso14651_common) without having to modify individual locale definitions.

Both NFC and NFD data should collate as expected. And you can mix then as you
like,
you do not need to normalize them.

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]