From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/26120] column width of of some Korean JUNGSEONG/JONGSEONG characters wrong (should be 0)
Date: Thu, 30 Dec 2021 00:35:10 +0000 [thread overview]
Message-ID: <bug-26120-716-OsN9rmkdSh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26120-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26120
Bruno Haible <bruno at clisp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruno at clisp dot org
--- Comment #17 from Bruno Haible <bruno at clisp dot org> ---
(In reply to Florian Weimer from comment #6)
> Yes, I think it's here:
>
> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/uniwidth/width.c;h=c760ad33183418a8f103152ff43d57fabbc3949d;hb=HEAD
I have applied an equivalent change to the uc_width function in gnulib:
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=8026587b94e4274f3406a36bc89348a24ea86b6a
Experiments with xterm did not convince me, but experiments with gnome-terminal
did, since gnome-terminal is widely used and is ahead in terms of Unicode
support.
And the fact that Unicode's EastAsianWidth.txt assigns width 2 to these
characters is irrelevant, because https://www.unicode.org/reports/tr11/ makes
it clear that its focus is about traditional Japanese rendering engines - but
such traditional code cannot handle conjoining Hangul Jamo anyway. Here we need
to care about the Unicode-compliant rendering engines (such as the one in
gnome-terminal), not the legacy rendering engines.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-12-30 0:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 5:43 [Bug localedata/26120] New: " maiku.fabian at gmail dot com
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 [this message]
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-OsN9rmkdSh@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).