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] New: bn_IN collation does not have canonical equivalence definitions Date: Sun, 09 Aug 2009 05:12:00 -0000 [thread overview] Message-ID: <20090809051246.10501.santhosh.thottingal@gmail.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1235 bytes --] Th bn_IN collation definitions does not have canonical equivalence definitions for the canonical decomposition of the following letters : U+09CB BENGALI VOWEL SIGN O U+09CC BENGALI VOWEL SIGN AU U+09DC BENGALI LETTER RRA U+09DD BENGALI LETTER RHA U+09DF BENGALI LETTER YYA How to reproduce : Sort the following sequences in LANG =bn_IN.UTF-8 à¦à§à¦¾ written using canonical decomposition of U+09CB BENGALI VOWEL SIGN O à¦à§ à¦à§ The expected sorting order is à¦à§ à¦à§à¦¾ à¦à§ But the actual result is à¦à§à¦¾ à¦à§ à¦à§ -- Summary: bn_IN collation does not have canonical equivalence definitions Product: glibc Version: 2.10 Status: NEW Severity: normal Priority: P2 Component: localedata AssignedTo: libc-locales at sources dot redhat dot com ReportedBy: santhosh dot thottingal at gmail dot com CC: glibc-bugs at sources dot redhat dot com 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 reply other threads:[~2009-08-09 5:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-08-09 5:12 santhosh dot thottingal at gmail dot com [this message] 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=20090809051246.10501.santhosh.thottingal@gmail.com \ --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: linkBe 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).