This is the mail archive of the libc-locales@sourceware.org mailing list for the GNU libc locales 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/21547] Tibetan script collation broken (Dzongkha and Tibetan)


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

--- Comment #20 from Elie Roux <elie.roux@telecom-bretagne.eu> ---
I agree it's counter-intuitive. I think the reason why the rule is there is
because of some Tibetan way of expressing things, let me elaborate:

I could replace

&གཉ<གཉྫ

with

&གངས<གཉྫ

this would keep all tests passing, but the reason I don't really want to do
that is the following:

གངས may not be the very last element before གཉྫ, it's very possible that some
not-very common suffix combination (in Dzongkha for instance). And, although
that would be quite exceptional, a strange suffix combination could happen
between གངས and གཉྫ. While basically nothing could happen between the initial
version of གཉ and གཉྫ, so the rule as it is is quite safe. Does it make more
sense? If these rules are the only ones to use this pattern and you think it's
confusing, I'll remove it though, I suppose

&གངས<གཉྫ

is a good enough replacement.

What do you think?

-- 
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]