CJK Unified Ideographs Extension I
CJK Unified Ideographs Extension I | |
---|---|
Range | U+2EBF0..U+2EE5F (624 code points) |
Plane | SIP |
Scripts | Han |
Assigned | 622 code points |
Unused | 2 reserved code points |
Unicode version history | |
15.1 (2023) | 622 (+622) |
Unicode documentation | |
Code chart ∣ Web page | |
Note: [1][2] |
CJK Unified Ideographs Extension I is a Unicode block comprising CJK Unified Ideographs included in drafts of an amendment to China's GB 18030 standard circulated in 2022 and 2023, which were fast-tracked into Unicode in 2023.
Background
Unlike most other sets of CJK unified ideographs, Extension I was not prepared and submitted by the Ideographic Research Group (IRG).[3]
In late 2022, the PRC made a draft of a further amendment to be made to GB 18030 available for public consultation. This draft would have placed 897 new
However, since the intent of ISO 10646 was for Plane 10 to be reserved for future allocation by ISO 10646 and Unicode via their usual ballot process, not for it to be allocated
As an alternative, the
At its next meeting in October 2023, the IRG expressed concerns about bypassing the IRG for large collections of CJK characters, and noted that two of the characters in Extension I had, for the purposes of other regions' character sources, previously been unified with existing characters under IRG unification rules:[3][12]
- Allowing for interchangeable forms of the grass radical, U+2ED9D <RESERVED-2ED9D> corresponds to the pre-existing T-source (Taiwan) glyph for U+8286 芆 CJK UNIFIED IDEOGRAPH-8286 (referenced from CNS 11643),[13] as well as to a proposed J-source (Japan) glyph for the same.[14] A character corresponding to the other (G-source, i.e. Mainland China) glyph of U+8286 does exist elsewhere in more recent editions of CNS 11643, so the addition of U+2ED9D impacts the existing correspondences between CNS 11643 and Unicode although, due to neither character being in planes 1 or 2, there are no implications for the Unicode mapping of Big5.[12]
- U+2EDE0 <RESERVED-2EDE0> corresponds to a proposed J-source (Japan) glyph for U+8FF3 迳 CJK UNIFIED IDEOGRAPH-8FF3.[15] It had previously been proposed as a new character twice (once with reference to CNS 11643, and once by Japan), but rejected on the basis that it was unifiable with U+8FF3.[12] The proposed glyph was later moved to the new U+2EDE0 <RESERVED-2EDE0> code point, per a request by the Japanese national body.[16]
In response, the IRG recommended that, in future, submitters of proposed CJK characters be required to provide information about the impact on other CJK character sources of any disunifications proposed by the submission, and that the IRG be given time to review all large submissions of CJK characters. The IRG encouraged the Chinese body to propose solutions to the issues caused by the addition of these two characters at the next IRG meeting.[3]
Block
CJK Unified Ideographs Extension I[1][2] Official Unicode Consortium code chart (PDF) | ||||||||||||||||
0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F | |
U+2EBFx | | | | | | | | | | | | | | | | |
U+2EC0x | | | | | | | | | | | | | | | | |
U+2EC1x | | | | | | | | | | | | | | | | |
U+2EC2x | | | | | | | | | | | | | | | | |
U+2EC3x | | | | | | | | | | | | | | | | |
U+2EC4x | | | | | | | | | | | | | | | | |
U+2EC5x | | | | | | | | | | | | | | | | |
U+2EC6x | | | | | | | | | | | | | | | | |
U+2EC7x | | | | | | | | | | | | | | | | |
U+2EC8x | | | | | | | | | | | | | | | | |
U+2EC9x | | | | | | | | | | | | | | | | |
U+2ECAx | | | | | | | | | | | | | | | | |
U+2ECBx | | | | | | | | | | | | | | | | |
U+2ECCx | | | | | | | | | | | | | | | | |
U+2ECDx | | | | | | | | | | | | | | | | |
U+2ECEx | | | | | | | | | | | | | | | | |
U+2ECFx | | | | | | | | | | | | | | | | |
U+2ED0x | | | | | | | | | | | | | | | | |
U+2ED1x | | | | | | | | | | | | | | | | |
U+2ED2x | | | | | | | | | | | | | | | | |
U+2ED3x | | | | | | | | | | | | | | | | |
U+2ED4x | | | | | | | | | | | | | | | | |
U+2ED5x | | | | | | | | | | | | | | | | |
U+2ED6x | | | | | | | | | | | | | | | | |
U+2ED7x | | | | | | | | | | | | | | | | |
U+2ED8x | | | | | | | | | | | | | | | | |
U+2ED9x | | | | | | | | | | | | | | | | |
U+2EDAx | | | | | | | | | | | | | | | | |
U+2EDBx | | | | | | | | | | | | | | | | |
U+2EDCx | | | | | | | | | | | | | | | | |
U+2EDDx | | | | | | | | | | | | | | | | |
U+2EDEx | | | | | | | | | | | | | | | | |
U+2EDFx | | | | | | | | | | | | | | | | |
U+2EE0x | | | | | | | | | | | | | | | | |
U+2EE1x | | | | | | | | | | | | | | | | |
U+2EE2x | | | | | | | | | | | | | | | | |
U+2EE3x | | | | | | | | | | | | | | | | |
U+2EE4x | | | | | | | | | | | | | | | | |
U+2EE5x | | | | | | | | | | | | | | | ||
Notes |
History
The following Unicode-related documents record the purpose and process of defining specific characters in the CJK Unified Ideographs Extension I block:
Version | Final code points[a] | Count | L2 ID | WG2 ID | IRG ID |
Document |
---|---|---|---|---|---|---|
15.1 | U+2EBF0..2EE5D | 622 | L2/23-011 | Lunde, Ken (2023-01-11), "18) GB 18030-2022 Amendment", CJK & Unihan Group Recommendations for UTC #174 Meeting | ||
L2/23-057 | N5201 | N2591 | Draft GB 18030-2022 Amendment Feedback & Recommendations, 2023-02-03 | |||
L2/23-100 | GB 18030-2022 Amendment, Draft 2 + Disposition of Comments, Draft 1, 2023-04-10 | |||||
L2/23-082 | Lunde, Ken (2023-04-22), "02 and 03", CJK & Unihan Group Recommendations for UTC #175 Meeting | |||||
L2/23-106 | N5214 | Lunde, Ken (2023-04-24), "The Alternate Proposal—Unicode Version 15.1", Proposal to provisionally assign or accept 603 urgently-needed ideographs | ||||
L2/23-076 | Constable, Peter (2023-05-01), "E.4.2 Proposal to provisionally assign or accept 603 urgently-needed ideographs", UTC #175 Minutes | |||||
L2/23-114R | N5214R2 | Lunde, Ken (2023-07-05), Proposal to encode 622 urgently needed ideographs in UCS | ||||
L2/23-115 | Constable, Peter (2023-05-01), USNB Comments on Draft 2 of GB 18030-2020 Amendment 1 and recommendation for ISO/IEC 10646:2022 Amendment 2 | |||||
L2/23-154 | N5238 | Revision of 622 UNCs of China (Feedback on WG2 N5214), 2023-06-30 | ||||
L2/23-163 | Lunde, Ken (2023-07-11), "01", CJK & Unihan Group Recommendations for UTC #176 Meeting | |||||
L2/23-157 | Constable, Peter (2023-07-31), "E.1 Section 1) CJK Unified Ideographs Extension I", UTC #176 Minutes | |||||
|
References
- ^ "Unicode character database". The Unicode Standard. Retrieved 2023-09-12.
- ^ "Enumerated Versions of The Unicode Standard". The Unicode Standard. Retrieved 2023-09-12.
- ^ UTCL2/23-250.
- ^ Kaplan, Michael S (2013-03-28). "You call it GB18030, I call it UTF-GBK..." Sorting it all out.
- ^ UTCL2/23-115.
- ^ UTCL2/23-240.
- UTCL2/23-087.
- ^ "CJK Unified Ideographs Extension I" (PDF). The Unicode Standard, Version 15.1. Unicode Consortium. 2023.
- ^ Lunde, Ken; Cook, Richard, eds. (2023-09-01). "kIRG_GSource". Unicode Han Database (Unihan). Unicode 15.1.0. UAX #38.
- UTCL2/23-082.
- ^ "CJK/Unihan Changes". Unicode 15.1.0. Unicode Consortium. 2023-09-12.
To keep the CJK block ranges as compact as possible, Extension I has been added to Plane 2, instead of directly after Extension H on Plane 3. Implementers should also check that their code does not assume that CJK extensions all occur in alphabetic order by the extension letter.
- ^ a b c Sim, Cheon-hyeong (2023-05-17). "2. Newly introduced half-duplicated characters" (PDF). Application for Horizontal Extensions of Multiple Sources in CJK-ExtI. pp. 3–5. ISO/IEC JTC1/SC2/WG2/IRG N2635. (Note: the referenced document refers to an earlier draft of Extension I with code points that differ from those in the final version accepted into Unicode. U+2ED90 in the referenced document corresponds to U+2ED9D <RESERVED-2ED9D> in the final version, while U+2EDD1 in the referenced document corresponds to U+2EDE0 <RESERVED-2EDE0> in the final version.)
- ^ "CJK Unified Ideographs" (PDF). The Unicode Standard, Version 15.0. Unicode Consortium. p. 823.
- UTCL2/23-144.
- UTCL2/23-144.
- UTCL2/24-016.
Further reading
- Lunde, Ken (2023-07-15). "The First Amendment". This article details how the CJK Unified Ideographs Extension I block became standardized, and its relationship with two drafts of the GB 18030-2022 amendment.
- ^ As of version 15.1