public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "infinity0 at pwned dot gg" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/30149] New: en_GB thinks "㐬" and "㒼" are the same character, other locales are fine
Date: Mon, 20 Feb 2023 21:59:26 +0000	[thread overview]
Message-ID: <bug-30149-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30149

            Bug ID: 30149
           Summary: en_GB thinks "㐬" and "㒼" are the same character, other
                    locales are fine
           Product: glibc
           Version: 2.36
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: locale
          Assignee: unassigned at sourceware dot org
          Reporter: infinity0 at pwned dot gg
  Target Milestone: ---

$ cat test2.txt
㐬
㒼

$ for l in C.UTF-8 en_GB.UTF-8 en_US.UTF-8 zh_CN.UTF-8; do echo $(LC_COLLATE=$l
sort -u test2.txt | wc -l) $l; done
2 C.UTF-8
1 en_GB.UTF-8
2 en_US.UTF-8
2 zh_CN.UTF-8

Not sure why en_GB thinks it should be treating Chinese characters specially.

Other characters may be affected, I didn't do a thorough check across all
Unicode characters x locales.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-02-20 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 21:59 infinity0 at pwned dot gg [this message]
2023-03-28 11:04 ` [Bug locale/30149] " schwab@linux-m68k.org
2023-03-28 11:06 ` [Bug localedata/30149] " schwab@linux-m68k.org
2023-04-14 13:46 ` infinity0 at pwned dot gg
2023-04-14 13:56 ` infinity0 at pwned dot gg
2023-04-14 16:34 ` carlos at redhat dot com
2023-04-14 20:51 ` infinity0 at pwned dot gg

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-30149-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).