From: "elie.roux@telecom-bretagne.eu" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/21547] New: Tibetan script collation broken (Dzongkha and Tibetan)
Date: Mon, 05 Jun 2017 10:37:00 -0000 [thread overview]
Message-ID: <bug-21547-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=21547
Bug ID: 21547
Summary: Tibetan script collation broken (Dzongkha and Tibetan)
Product: glibc
Version: 2.24
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: elie.roux@telecom-bretagne.eu
CC: libc-locales at sourceware dot org
Target Milestone: ---
Hello,
Tibetan or Dzongkha sorting do not work properly with the current locale data.
With the following test file:
$ cat tibt_order_test.txt
ལྔ
ང
ཅ
རྔ
སྔ
བརྔ
བསྔ
I get the following wrong result:
$ LC_COLLATE="dz_BT.utf8" sort tibt_order_test.txt
ང
བརྔ
བསྔ
རྔ
ལྔ
སྔ
ཅ
The correct result would be
ང
རྔ
ལྔ
སྔ
བརྔ
བསྔ
ཅ
Dz and bo have the same collation data in CLDR.
See https://github.com/eroux/tibetan-collation for more on tibetan collation.
Result of locale -a:
bo_CN
bo_CN.utf8
bo_IN
bo_IN.utf8
C
C.UTF-8
dz_BT
dz_BT.utf8
en_GB.utf8
en_US.utf8
fr_FR.utf8
POSIX
Thank you,
--
Elie
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-06-05 10:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 10:37 elie.roux@telecom-bretagne.eu [this message]
2017-06-16 9:03 ` [Bug localedata/21547] " elie.roux@telecom-bretagne.eu
2017-10-21 8:26 ` maiku.fabian at gmail dot com
2017-12-14 15:51 ` maiku.fabian at gmail dot com
2017-12-18 17:15 ` maiku.fabian at gmail dot com
2017-12-18 17:58 ` elie.roux@telecom-bretagne.eu
2017-12-18 18:00 ` elie.roux@telecom-bretagne.eu
2018-01-15 10:25 ` maiku.fabian at gmail dot com
2018-01-15 10:50 ` elie.roux@telecom-bretagne.eu
2018-01-15 10:51 ` elie.roux@telecom-bretagne.eu
2018-01-15 14:35 ` maiku.fabian at gmail dot com
2018-01-15 14:36 ` maiku.fabian at gmail dot com
2018-01-15 14:47 ` elie.roux@telecom-bretagne.eu
2018-01-15 14:56 ` maiku.fabian at gmail dot com
2018-01-15 15:06 ` maiku.fabian at gmail dot com
2018-01-15 15:14 ` elie.roux@telecom-bretagne.eu
2018-01-15 15:15 ` maiku.fabian at gmail dot com
2018-01-15 15:18 ` maiku.fabian at gmail dot com
2018-01-15 15:25 ` maiku.fabian at gmail dot com
2018-01-15 19:09 ` elie.roux@telecom-bretagne.eu
2018-01-15 20:58 ` maiku.fabian at gmail dot com
2018-01-15 22:03 ` elie.roux@telecom-bretagne.eu
2018-01-16 7:38 ` maiku.fabian at gmail dot com
2018-01-16 8:11 ` elie.roux@telecom-bretagne.eu
2018-01-22 15:17 ` maiku.fabian at gmail dot com
2018-01-22 15:18 ` maiku.fabian at gmail dot com
2018-01-22 15:22 ` maiku.fabian at gmail dot com
2018-01-22 21:45 ` elie.roux@telecom-bretagne.eu
2018-01-23 17:32 ` maiku.fabian at gmail dot com
2018-01-23 21:57 ` elie.roux@telecom-bretagne.eu
2018-01-24 0:04 ` maiku.fabian at gmail dot com
2018-01-24 8:49 ` elie.roux@telecom-bretagne.eu
2018-02-27 16:55 ` cvs-commit at gcc dot gnu.org
2018-03-01 14:40 ` maiku.fabian at gmail dot com
2018-03-02 12:59 ` cvs-commit at gcc dot gnu.org
2018-03-31 12:32 ` jeremip11 at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-21547-716@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).