From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/26120] New: column width of of some Korean JUNGSEONG/JONGSEONG characters wrong (should be 0)
Date: Tue, 16 Jun 2020 05:43:43 +0000 [thread overview]
Message-ID: <bug-26120-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26120
Bug ID: 26120
Summary: column width of of some Korean JUNGSEONG/JONGSEONG
characters wrong (should be 0)
Product: glibc
Version: 2.31
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: maiku.fabian at gmail dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
Robert Ross <rob.ross@ymail.com> writes:
> Thank you for maintaining glibc's "localedata/charmaps/UTF-8". It is
> good that most "HANGUL JUNGSEONG" characters have zero width due to
> "<U1160>...<U11FF> 0" on line 48775 but strange that the newer "HANGUL
> JUNGSEONG" characters have width 1 since there is no
> "<UD7B0>...<UD7C6> 0". Similarly most "HANGUL JONGSEONG" characters
> have width 0 due to line 48775 but the newer ones have width 1 since
> there is no "<UD7CB>...<UD7FB> 0". Please correct this if it's an
> error or explain if it's not.
In https://www.unicode.org/Public/13.0.0/ucd/EastAsianWidth.txt all of these
have width "N".
http://www.unicode.org/reports/tr11/ says:
6.2 Combining Marks
> Combining marks have been classified and are given a property
> assignment based on their typical applicability. For example,
> combining marks typically applied to characters of class N, Na, or W
> are classified as A. Combining marks for purely non-East Asian scripts
> are marked as N, and nonspacing marks used only with wide characters
> are given a W. Even more so than for other characters, the
> East_Asian_Width property for combining marks is not the same as their
> display width.
>
> In particular, nonspacing marks do not possess actual advance
> width. Therefore, even when displaying combining marks, the
> East_Asian_Width property cannot be related to the advance width of
> these characters. However, it can be useful in determining the
> encoding length in a legacy encoding, or the choice of font for the
> range of characters including that nonspacing mark. The width of the
> glyph image of a nonspacing mark should always be chosen as the
> appropriate one for the width of the base character.
See also: https://sourceware.org/bugzilla/show_bug.cgi?id=21750#c5
> We also agree that the Hangul Jamo U+1160‥U+11FF are sort
> of "combining characters" although they are not marked as such
> in the Unicode data. But they are fragments of Hangul characters
> which combine. So it seems correct to mark them as width 0.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-16 5:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 5:43 maiku.fabian at gmail dot com [this message]
2020-06-16 5:44 ` [Bug localedata/26120] " maiku.fabian at gmail dot com
2020-06-16 5:45 ` maiku.fabian at gmail dot com
2020-06-16 5:46 ` maiku.fabian at gmail dot com
2020-06-16 5:47 ` maiku.fabian at gmail dot com
2020-06-16 5:47 ` maiku.fabian at gmail dot com
2020-06-16 5:58 ` maiku.fabian at gmail dot com
2020-06-16 8:26 ` maiku.fabian at gmail dot com
2020-06-16 11:53 ` fweimer at redhat dot com
2020-06-16 17:32 ` maiku.fabian at gmail dot com
2020-06-16 17:35 ` fweimer at redhat dot com
2020-06-20 21:19 ` tg at mirbsd dot de
2020-06-21 9:00 ` maiku.fabian at gmail dot com
2020-06-21 9:07 ` maiku.fabian at gmail dot com
2020-06-21 14:20 ` tg at mirbsd dot de
2020-06-23 7:08 ` maiku.fabian at gmail dot com
2020-06-23 7:33 ` tg at mirbsd dot de
2020-06-23 8:50 ` maiku.fabian at gmail dot com
2020-06-23 9:03 ` maiku.fabian at gmail dot com
2020-06-25 13:05 ` maiku.fabian at gmail dot com
2020-06-26 12:26 ` maiku.fabian at gmail dot com
2020-06-26 12:27 ` maiku.fabian at gmail dot com
2020-06-28 12:50 ` maiku.fabian at gmail dot com
2021-12-30 0:35 ` bruno at clisp dot org
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-26120-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).