| 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 aUnicode block comprisingCJK Unified Ideographs included in drafts of an amendment to China'sGB 18030 standard circulated in 2022 and 2023, which were fast-tracked intoUnicode in 2023.
Unlike most other sets of CJK unified ideographs, Extension I was not prepared and submitted by theIdeographic Research Group (IRG).[3]
GB 18030 is a mandatory national standard of thePeople's Republic of China (PRC). It defines aUnicode Transformation Format which retains compatibility with existing data in the earlierGBK andEUC-CN character encodings, and specifies particular Unicode characters which devices sold in China must support.[4] Its 2022 edition,GB 18030-2022, changed a number of required characters to map to standard Unicodecode points, rather than toprivate use area code points.
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 newsinographic characters in Plane 10 (hexadecimal: 0A), ayet-untitled astral Unicode plane.[5] This was motivated by a "strong need of citizen real-name certification in China".[6] Since it would impactISO/IEC 10646 (the Universal Coded Character Set, theISO standard synchronised with Unicode), the draft was circulated inISO/IEC JTC 1/SC 2, the ISO subcommittee responsible for ISO 10646. The Chinese national body maintained that "ISO/IEC 10646 do not specify the purpose of the 0A plane", which ISO 10646 denotes as "reserved for future standardization", and that this use was therefore "not inappropriate".[5]
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 allocatedunilaterally by national standards bodies, this proposed move was criticised by experts and other national bodies as one which would "destabilize the synchronization" between GB 18030 and ISO/IEC 10646 (and thus Unicode), and which would make it impossible to conform to both with a single implementation,[5] effectivelyforking Unicode. At its meeting in March 2023, the IRG emphasised the importance of providing any subsequent GB 18030 amendment drafts to IRG experts in a timely manner, and of not "using the ISO/IEC 10646 standard inappropriately".[7]
As an alternative, therepertoire (eventually reduced to 622 characters after expert review) was fast-tracked into Unicode version 15.1 in September 2023, as the CJK Unified Ideographs Extension I block.[5] The characters constitute the "GIDC23"Unihan source,[8] defined as sourced from the "ID system of the Ministry of Public Security of China, 2023".[9] TheCJK Unified Ideographs Extension D block was cited as a precedent, since it comprised a repertoire of urgently needed characters (UNCs) from IRG member bodies, whereas the IRG working-set initially slated to become Extension D would instead becomeExtension E.[10] For compactness, the block was allocated to the available space in theSupplementary Ideographic Plane afterCJK Unified Ideographs Extension F, as opposed to on theTertiary Ideographic Plane afterCJK Unified Ideographs Extension H; this means that the CJK extension blocks are no longer in alphabetical order by extension letter.[11] Following this, the draft GB 18030 amendment was modified to use the Extension I code points.[6]
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]
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]
The CJK Unified Ideographs Extension I block has two ideographicvariation sequences registered in the Unicode Ideographic Variation Database (IVD).[17][18] These sequences specify the desired glyph variant for a given Unicode character.
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 and E.1 Section 9 [Affects U+2EDE3]",UTC #176 Minutes | |||||
| ||||||
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.