strxfrm() fails for certain characters
We fail to create correct entries for these:
<LATIN_CAPITAL_LETTER_A_WITH_RING_ABOVE> <X2700>;"<X05><X99>";"<X8F><X05>";"<A><COMBINING_RING_ABOVE>" <ANGSTROM_SIGN> <X2700>;"<X05><X99>";"<X8F><X05>";"<A><COMBINING_RING_ABOVE>"
Updated by Yuri Pankov over 3 years ago
Took a look at this..
Those are the only entries that have final weight defined as
<char><char>, and we treat it as substitution. The problem, however, is that while the priority for
<A> is well defined,
<COMBINING_RING_ABOVE> doesn't show up anywhere in collation order list. Not sure why these two use what looks to be the decomposed form of
IMO, this is neither a bug in our localedef, nor it's a bug in our *xfrm() functions, and should be reported upstream - probably an artifact of converting the CLDR data to POSIX format.
Updated by Electric Monk about 3 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
commit f862e02cb8d597e430ef5067be483718a65c3370 Author: Yuri Pankov <firstname.lastname@example.org> Date: 2017-06-28T15:21:31.000Z 7962 strxfrm() fails for certain characters Reviewed by: Toomas Soome <email@example.com> Reviewed by: Igor Kozhukhov <firstname.lastname@example.org> Reviewed by: Garrett D'Amore <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>