This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales 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: libc-locales at sourceware dot org
- Date: Tue, 23 Jan 2018 17:32:28 +0000
- Subject: [Bug localedata/21547] Tibetan script collation broken (Dzongkha and Tibetan)
- Auto-submitted: auto-generated
- References: <bug-21547-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21547
--- Comment #25 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Elie Roux from comment #24)
> That's really great, thank you so much! Is it possible to have the exact
> same collation rules for the bo locale(s)? bo, bo_IN and bo_CN
Yes, I did this:
$ grep -A3 ^LC_COLLATE dz_* bo_*
dz_BT:LC_COLLATE
dz_BT-% Using the rules.txt attached to:
dz_BT-% http://unicode.org/cldr/trac/ticket/9895
dz_BT-% See also: https://sourceware.org/bugzilla/show_bug.cgi?id=21547
--
bo_CN:LC_COLLATE
bo_CN-copy "dz_BT"
bo_CN-END LC_COLLATE
bo_CN-
--
bo_IN:LC_COLLATE
bo_IN-copy "bo_CN"
bo_IN-END LC_COLLATE
bo_IN-
So dz_BT implements the rules and bo_CN and bo_IN just copy them.
--
You are receiving this mail because:
You are on the CC list for the bug.