From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8416C385801F; Thu, 30 Dec 2021 00:35:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8416C385801F From: "bruno at clisp dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bruno at clisp dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: maiku.fabian at gmail dot com X-Bugzilla-Target-Milestone: 2.32 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: libc-locales@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-locales mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2021 00:35:10 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26120 Bruno Haible changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno at clisp dot org --- Comment #17 from Bruno Haible --- (In reply to Florian Weimer from comment #6) > Yes, I think it's here: >=20 > http://git.savannah.gnu.org/gitweb/?p=3Dgnulib.git;a=3Dblob;f=3Dlib/uniwi= dth/width.c;h=3Dc760ad33183418a8f103152ff43d57fabbc3949d;hb=3DHEAD I have applied an equivalent change to the uc_width function in gnulib: https://git.savannah.gnu.org/gitweb/?p=3Dgnulib.git;a=3Dcommitdiff;h=3D8026= 587b94e4274f3406a36bc89348a24ea86b6a Experiments with xterm did not convince me, but experiments with gnome-term= inal 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/ mak= es it clear that its focus is about traditional Japanese rendering engines - b= ut 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=