From: "stlman at poczta dot fm" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24314] New: charmaps: Some of UTF-8 characters have invalid width
Date: Fri, 08 Mar 2019 11:24:00 -0000 [thread overview]
Message-ID: <bug-24314-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24314
Bug ID: 24314
Summary: charmaps: Some of UTF-8 characters have invalid width
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: stlman at poczta dot fm
CC: libc-locales at sourceware dot org
Target Milestone: ---
Some characters are assigned invalid width in localedata/charmaps/UTF-8 file
(lines below 47072). For example \u2693 (ANCHOR) is described as double-width
character.
There is a procedure for deriving the data from the standard files, which says
that double width characters come from EastAsianWidth.txt file.
grep '^[^;]*;[WF]' EastAsianWidth.txt | grep 2693
returns no results which means the line 47261 (as of commit c5f65462a2) which
says
<U2693> 2
is wrong. At least 28 other characters seem to be improperly classified as
double-width too. Use the following command to find them.
perl -ne 'next if (1..47080 or /\.\.\./); print if (/2$/);'
localedata/charmaps/UTF-8
None of these characters can be found in the output of
grep '^[^;]*;[WF]' EastAsianWidth.txt
Apparently the localedata/unicode-gen/utf8_gen.py script has failed to filter
out these characters.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-03-08 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 11:24 stlman at poczta dot fm [this message]
2019-03-08 13:56 ` [Bug localedata/24314] " egmont at gmail dot com
2019-03-08 19:03 ` 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@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).