[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gnu-libiconv] gb18030 for 0x215d7
From: |
Bruno Haible |
Subject: |
Re: [bug-gnu-libiconv] gb18030 for 0x215d7 |
Date: |
Sat, 27 May 2023 17:55:59 +0200 |
Hello,
> Found bizarre exceptions in gb18030ext.h
>
> else if (wc == 0x20087)
> c = 0xfe51;
> else if (wc == 0x20089)
> c = 0xfe52;
> else if (wc == 0x200cc)
> c = 0xfe53;
> else if (wc == 0x215d7)
> c = 0xfe6c;
> else if (wc == 0x2298f)
> c = 0xfe76;
> else if (wc == 0x241fe)
> c = 0xfe91;
>
> For example:
> According to GB18030-2000/2005:
> 0xFE6C -> U+E831
> 0x9536B937 -> U+215D7
Nope. GB18030-2000 is not relevant any more.
GB18030-2005 maps
0xFE6C -> U+215D7
0x9536B937 -> U+215D7
And the code you are looking at does not implement the GB18030 → Unicode
direction, but the opposite direction: Unicode → GB18030:
U+215D7 -> 0xFE6C
U+E831 -> 0xFE6C
Bruno
- [bug-gnu-libiconv] gb18030 for 0x215d7, Link, 2023/05/27
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7,
Bruno Haible <=
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7, Link, 2023/05/27
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7, Bruno Haible, 2023/05/27
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7, Link, 2023/05/27
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7, Bruno Haible, 2023/05/27
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7, Link, 2023/05/28
- Re: [bug-gnu-libiconv] gb18030 for 0x215d7, Bruno Haible, 2023/05/29