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 F230D3858C2A; Thu, 17 Aug 2023 01:55:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F230D3858C2A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1692237300;
	bh=6LaZQ+6A2+MnsNZxXEvPSlT+yT+kHO5T+2nK05eKXEY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=t07FkVZxyAo7iu1Z0AoXgK9dOT7bE3TcYe5RqwWZXuZ0f3SZ7q6aYV0upXax7SrsH
	 u7RMGyDViSd1VtMC/q5uLJGGjNDA75NR/Kn+tZxXwOmGC/6OJos+CuppXjPb0e4k9Y
	 RBJsip9mgYUY9m+hkT11Nt4uDFIGij/VvmMqIf6A=
From: "liqingqing3 at huawei dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/30243] Add full support for GB18030-2022
Date: Thu, 17 Aug 2023 01:55:00 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: locale
X-Bugzilla-Version: 2.39
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: liqingqing3 at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30243-131-aJstM5disM@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30243-131@http.sourceware.org/bugzilla/>
References: <bug-30243-131@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
List-Id: <glibc-bugs.sourceware.org>

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

--- Comment #17 from liqingqing <liqingqing3 at huawei dot com> ---
(In reply to Carlos O'Donell from comment #16)
> (In reply to Mike FABIAN from comment #15)
> > I tested v3 a while ago (2023-07-26). I think it is good.=20
> > By the way, the Annex C table in the above PDF contains a typo in the f=
irst
> > column, last row: it should be U+8612, not U+8162.
>=20
> Does v3 correct this problem?

(In reply to Mike FABIAN from comment #15)
> I tested v3 a while ago (2023-07-26). I think it is good.=20
>=20
>=20
> I could compile and install it. I wrote a small python test program to te=
st
> iconv with and without the patch.
>=20
> https://mfabian.fedorapeople.org/misc/iconv-test.py
>=20
>  The patch made all the codepoints mentioned in the tables in
>=20
> https://www.unicode.org/L2/L2022/22274-disruptive-changes.pdf
>=20
> work correctly for the 2022 version of the standard.
>=20
> Without the patch, only the two byte GB18030 code points in the Annex A
> table work, the 4 byte GB18030 codepoints work only with the patch.=20
>=20
> The patch is also needed to make the conversions in the Annex B and Annex=
 C
> tables work.
>=20
> By the way, the Annex C table in the above PDF contains a typo in the fir=
st
> column, last row: it should be U+8612, not U+8162.

yes, you are right, I checked the GB18030-2022 standard,
http://c.gb688.cn/bzgk/gb/showGb?type=3Donline&hcno=3DA1931A578FE1495710498=
8029B0833D3

page67 list the below code point:=20
unicode code point U+8612 <--> GB18030 code point: CC55

so, the above PDF is  wrong, it should be U+8612

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