[Bug locale/30243] Add full support for GB18030-2022

["liqingqing3 at huawei dot com" <sourceware-bugzilla@sourceware.org>]

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

--- 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. 
> > By the way, the Annex C table in the above PDF contains a typo in the first
> > column, last row: it should be U+8612, not U+8162.
> 
> 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. 
> 
> 
> I could compile and install it. I wrote a small python test program to test
> iconv with and without the patch.
> 
> https://mfabian.fedorapeople.org/misc/iconv-test.py
> 
>  The patch made all the codepoints mentioned in the tables in
> 
> https://www.unicode.org/L2/L2022/22274-disruptive-changes.pdf
> 
> work correctly for the 2022 version of the standard.
> 
> 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. 
> 
> The patch is also needed to make the conversions in the Annex B and Annex C
> tables work.
> 
> By the way, the Annex C table in the above PDF contains a typo in the first
> 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=online&hcno=A1931A578FE14957104988029B0833D3

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

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

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