From: "egmont at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24314] charmaps: Some of UTF-8 characters have invalid width
Date: Fri, 08 Mar 2019 13:56:00 -0000 [thread overview]
Message-ID: <bug-24314-716-jxXfmLtsaM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24314-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24314
Egmont Koblinger <egmont at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egmont at gmail dot com
--- Comment #1 from Egmont Koblinger <egmont at gmail dot com> ---
(In reply to Łukasz Stelmach from comment #0)
> grep '^[^;]*;[WF]' EastAsianWidth.txt | grep 2693
>
> returns no results which means the line 47261 (as of commit c5f65462a2)
This command _does_ print "2693;W" for me, as of the aforementioned commit,
assuming the input file is glibc's localedata/unicode-gen/EastAsianWidth.txt
(line 1210).
Note that the width of many codepoints, including this one, changed from narrow
to wide with Unicode 9.0. Compare these two files:
ftp://ftp.unicode.org/Public/8.0.0/ucd/EastAsianWidth.txt ("2670..269D;N")
ftp://ftp.unicode.org/Public/9.0.0/ucd/EastAsianWidth.txt ("2693;W")
Any chance you worked from a Unicode 8 (or older) EastAsianWidth.txt, rather
than the one in glibc's source?
(Also note that your grep command can easily miss matches, since the file
defines ranges. It's not the case with U+2693 though.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-08 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 11:24 [Bug localedata/24314] New: " stlman at poczta dot fm
2019-03-08 13:56 ` egmont at gmail dot com [this message]
2019-03-08 19:03 ` [Bug localedata/24314] " stlman at poczta dot fm
2019-03-08 20:03 ` fweimer at redhat 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-24314-716-jxXfmLtsaM@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).