public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "santhosh dot thottingal at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug localedata/10501] bn_IN collation does not have canonical equivalence definitions
Date: Mon, 17 Aug 2009 11:40:00 -0000 [thread overview]
Message-ID: <20090817114027.25810.qmail@sourceware.org> (raw)
In-Reply-To: <20090809051246.10501.santhosh.thottingal@gmail.com>
------- Additional Comments From santhosh dot thottingal at gmail dot com 2009-08-17 11:40 -------
Refer the collation rules of UCA -
http://www.unicode.org/Public/UCA/latest/allkeys.txt
[...]
09CB ; [.1B48.0020.0002.09CB] # BENGALI VOWEL SIGN O
09C7 09BE ; [.1B48.0020.0002.09CB] # BENGALI VOWEL SIGN O
09CC ; [.1B49.0020.0002.09CC] # BENGALI VOWEL SIGN AU
09C7 09D7 ; [.1B49.0020.0002.09CC] # BENGALI VOWEL SIGN AU
[...]
It is implemented in UCA and should be available in glibc localedata too. ie,
Collation weights of canonically equivalent sequences should be explicitly
defined in glibc and there should not be any assumption on the input to the
collation.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10501
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-08-17 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-08-17 12:18 ` sayamindu at gmail dot com
[not found] <bug-10501-131@http.sourceware.org/bugzilla/>
2014-07-01 7:21 ` fweimer at redhat dot com
2024-01-03 16:09 ` maiku.fabian at gmail dot com
2024-01-03 16:10 ` maiku.fabian 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=20090817114027.25810.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).