From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 2CBB53959C2C; Tue, 23 Jun 2020 07:08:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2CBB53959C2C
From: "maiku.fabian at gmail dot com" <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: Tue, 23 Jun 2020 07:08:49 +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: maiku.fabian at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: maiku.fabian at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26120-716-14bMBa2xCd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26120-716@http.sourceware.org/bugzilla/>
References: <bug-26120-716@http.sourceware.org/bugzilla/>
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 <libc-locales.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/libc-locales>,
 <mailto:libc-locales-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/libc-locales/>
List-Help: <mailto:libc-locales-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/libc-locales>,
 <mailto:libc-locales-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2020 07:08:50 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D26120

--- Comment #11 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Thorsten Glaser from comment #10)
> Looks okay (but now you can use 0xD800 in the range call),=20

Yes, I could. But if 0xD7FE and 0xD7FF ever get assigned,=20
would they be characters of the same type? I would have to check=20
that manually anyway.

> The output I get (for UCD 13.0.0) is identical to yours.

Great!

--=20
You are receiving this mail because:
You are on the CC list for the bug.=