From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/10501] bn_IN collation does not have canonical equivalence definitions
Date: Wed, 03 Jan 2024 16:09:40 +0000 [thread overview]
Message-ID: <bug-10501-716-jJJBJ6x1Cl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10501-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10501
Mike FABIAN <maiku.fabian at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |maiku.fabian at gmail dot com
--- Comment #4 from Mike FABIAN <maiku.fabian at gmail dot com> ---
glibc-2.38 seems to sort the way you want to:
mfabian@hathi:/local/mfabian/src/glibc/localedata (master $%)
$ cat bn_IN.UTF-8.in
কো
কৈ
কো
mfabian@hathi:/local/mfabian/src/glibc/localedata (master $%)
$ LC_ALL=bn_IN.UTF-8 sort < bn_IN.UTF-8.in
কৈ
কো
কো
mfabian@hathi:/local/mfabian/src/glibc/localedata (master $%)
$ rpm -q glibc
glibc-2.38-14.fc39.x86_64
mfabian@hathi:/local/mfabian/src/glibc/localedata (master $%)
$
The Bengali locale bn_IN just includes the standard iso sort order
LC_COLLATE
% Copy the template from ISO/IEC 14651
copy "iso14651_t1"
%
END LC_COLLATE
That iso sort order should be the same as DUCET:
https://unicode.org/reports/tr10/#Default_Unicode_Collation_Element_Table
It used to be extremely out of date but in 2018 I did an update to the 2016
version,
see this commit:
commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4
Author: Mike FABIAN <mfabian@redhat.com>
Date: Tue Jan 30 17:59:00 2018 +0100
Update iso14651_t1_common file to ISO14651_2016_TABLE1_en.txt [BZ
#14095]
[BZ #14095] - Review / update collation data from Unicode / ISO 14651
File downloaded from:
http://standards.iso.org/iso-iec/14651/ed-4/ISO14651_2016_TABLE1_en.txt
Updating this file alone is not enough, there are problems in the new
file which need to be fixed and the collation rules for many locales
need to be adapted. This is done by the following patches.
This update also fixes the problem that many characters are treated as
identical when sorting because they were not yet in the old
iso14651_t1_common file, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1336308
- Infinite (∞) and empty set (∅) are treated as if they were the same
character by sort and uniq
[BZ #14095]
* localedata/locales/iso14651_t1_common: Update file to
latest version from ISO (ISO14651_2016_TABLE1_en.txt).
This might have fixed the problem reported here.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-01-03 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10501-716@http.sourceware.org/bugzilla/>
2014-07-01 9:36 ` fweimer at redhat dot com
2024-01-03 16:09 ` maiku.fabian at gmail dot com [this message]
2024-01-03 16:10 ` maiku.fabian at gmail dot com
2009-08-09 5:12 [Bug localedata/10501] New: " santhosh dot thottingal at gmail dot com
2009-08-10 4:16 ` [Bug localedata/10501] " pravin dot d dot s at gmail dot com
2009-08-17 11:40 ` santhosh dot thottingal at gmail dot com
2009-08-17 12:18 ` sayamindu 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-10501-716-jJJBJ6x1Cl@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).