CJK Unified Ideographs Extension I
CJK Unified Ideographs Extension I | |
---|---|
Range | U+2EBF0..U+2EE5F (624 code points) |
Plane | SIP |
Scripts | Han |
Unused | 624 reserved code points |
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]
GB 18030 is a mandatory national standard of the People's Republic of China (PRC). It defines a Unicode Transformation Format which retains compatibility with existing data in the earlier GBK and EUC-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 Unicode code points, rather than to private 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 new sinographic characters in Plane 10 (hexadecimal: 0A), a yet-untitled astral Unicode plane.[5] This was motivated by a "strong need of citizen real-name certification in China".[6] Since it would impact ISO/IEC 10646 (the Universal Coded Character Set, the ISO standard synchronised with Unicode), the draft was circulated in ISO/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 allocated unilaterally 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] effectively forking 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, the repertoire (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] The CJK 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 become Extension E.[10] For compactness, the block was allocated to the available space in the Supplementary Ideographic Plane after CJK Unified Ideographs Extension F, as opposed to on the Tertiary Ideographic Plane after CJK 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]
- Allowing for interchangeable forms of the grass radical, U+2ED9D corresponds to the pre-existing T-source (Taiwan) glyph for U+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 corresponds to a proposed J-source (Japan) glyph for U+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]
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
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[lower-alpha 1] | Count | L2 ID | WG2 ID | IRG ID | Document |
---|---|---|---|---|---|---|
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), CJK & Unihan Group Recommendations for UTC #175 Meeting | |||||
L2/23-106 | N5214 | Lunde, Ken (2023-04-24), Proposal to provisionally assign or accept 603 urgently-needed ideographs | ||||
L2/23-076 | Constable, Peter (2023-05-01), 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), CJK & Unihan Group Recommendations for UTC #176 Meeting | |||||
L2/23-157 | Constable, Peter (2023-07-31), UTC #176 Minutes | |||||
|
References
- ↑ "Unicode character database". The Unicode Standard. https://www.unicode.org/ucd/.
- ↑ "Enumerated Versions of The Unicode Standard". The Unicode Standard. https://www.unicode.org/versions/enumeratedversions.html.
- ↑ 3.0 3.1 3.2 Ideographic Research Group (2023-10-20). "Recommendation IRG M61.12: Issue of Extension I to Other CJK Source Characters (IRGN2635 & Feedback, IRGN2622)". IRG Meeting #61 Recommendations and Action Items. https://www.unicode.org/L2/L2023/23250-irgn2620-recs.pdf#page=4.
- ↑ Kaplan, Michael S (2013-03-28). "You call it GB18030, I call it UTF-GBK...". Sorting it all out. https://archives.miloush.net/michkap/archive/2013/03/28/10405914.html.
- ↑ 5.0 5.1 5.2 5.3 United States National Body (May 1, 2023). "USNB Comments on Draft 2 of GB 18030-2022 Amendment 1 and recommendation for ISO/IEC 10646:2020 Amendment 2". https://www.unicode.org/wg2/docs/n5222_USNB-Comments-on-Draft-2-of-GB%2018030-2022-Amendment-1.pdf.
- ↑ 6.0 6.1 China National Body (2023-10-13). "IRG #61 Activity Report". https://www.unicode.org/L2/L2023/23240-irgn2623-china-ar.pdf.
- ↑ Ideographic Research Group (2023-03-24). "Recommendation IRG M60.7: Draft GB18030-2022 Amendment Feedback (IRGN2591, IRGN2605)". IRG Meeting #60 Recommendations and Action Items. https://www.unicode.org/L2/L2023/23087-irgn2600-irg60-recs.pdf#page=3.
- ↑ "CJK Unified Ideographs Extension I". The Unicode Standard, Version 15.1. Unicode Consortium. 2023. https://www.unicode.org/charts/PDF/U2EBF0.pdf.
- ↑ "kIRG_GSource". Unicode Han Database (Unihan). 2023-09-01. https://www.unicode.org/reports/tr38/#kIRG_GSource.
- ↑ Lunde, Ken (2023-04-22). "03) L2/23-100: GB 18030-2022 Amendment, Draft 2 + Disposition of Comments, Draft 1". CJK & Unihan Group Recommendations for UTC #175 Meeting. https://www.unicode.org/L2/L2023/23082-cjk-unihan-group-utc175.pdf#page=3.
- ↑ Unicode 15.1.0, Unicode Consortium, 2023-09-12, https://www.unicode.org/versions/Unicode15.1.0/
- ↑ 12.0 12.1 12.2 Sim, Cheon-hyeong (2023-05-17). "2. Newly introduced half-duplicated characters". Application for Horizontal Extensions of Multiple Sources in CJK-ExtI. pp. 3–5. https://appsrv.cse.cuhk.edu.hk/~irg/irg/irg61/IRGN2635_HorizontalExtension.pdf#page=3. (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 in the final version, while U+2EDD1 in the referenced document corresponds to U+2EDE0 in the final version.)
- ↑ "CJK Unified Ideographs". The Unicode Standard, Version 15.0. p. 823. https://unicode.org/charts/PDF/Unicode-15.0/U150-4E00.pdf#page=342.
- ↑ Japan National Body (2023-04-24), Request for Horizontal Extension in the J-column of ISO/IEC 10646, p. 414, ISO/IEC JTC1/SC2/WG2 N5221; UTC L2/23-144, https://www.unicode.org/L2/L2023/23144-n5221-japan.pdf
- ↑ Japan National Body (2023-04-24), Request for Horizontal Extension in the J-column of ISO/IEC 10646, p. 458, ISO/IEC JTC1/SC2/WG2 N5221; UTC L2/23-144, https://www.unicode.org/L2/L2023/23144-n5221-japan.pdf
Further reading
- Lunde, Ken (2023-07-15). "The First Amendment". https://ken-lunde.medium.com/the-first-amendment-fe064d9d7d8. 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.
Original source: https://en.wikipedia.org/wiki/CJK Unified Ideographs Extension I.
Read more |