This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug localedata/21547] Tibetan script collation broken (Dzongkha and Tibetan)
- From: "maiku.fabian at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 16 Jan 2018 07:38:28 +0000
- Subject: [Bug localedata/21547] Tibetan script collation broken (Dzongkha and Tibetan)
- Auto-submitted: auto-generated
- References: <bug-21547-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21547
--- Comment #19 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Elie Roux from comment #18)
> well, things are supposed to be sorted just like in the sorted list attached
> to this bug report.
>
> Now, I agree there is some magic going on here, and it's not totally obvious
> to me how this works, but it works.
>
> Even though it's not clear what line 7 does, it clearly does something,
> because if you remove it, the tests on the tibetan-collation github repo
> fails with:
Yes, it does something. You see that also in my simple Latin example
in comment#13:
https://sourceware.org/bugzilla/show_bug.cgi?id=21547#c13
In
&b<z
&d<b
The rule &b<z does something, although b is reordered again by the next rule.
But z is not reordered and stays where it was reordered by the first rule.
So one could have written
&a<z
&d<b
to achieve the same effect to get the order
a
z
c
d
b
e
f
and that would have been much clearer and easier to understand rules.
I have adapted the collation rules for many locales during the last weeks
because I am updating to a new iso14651_t1_common file. And none of the
locales had a collation rule which reordered some character after an
anchor character and then reordered that anchor. It is not that this cannot
work, it just seems very weird.
--
You are receiving this mail because:
You are on the CC list for the bug.