GCCPP-00035 |
Exact Match: 𬶘 (U+2CD98)
| Date | Description |
|---|---|
| IRG #64 2025-03-18 (Tue) 10:33 am +0800 Recorded by CHEN Zhuang | back to m set, no change of U+2CD98 (GB 18030) glyph in unicode 17. |
| IRG #63 2024-10-22 (Tue) 9:25 am +0900 Recorded by CHEN Zhuang | Postponed for unification to 𬶘 U+2CD98 |
| Version | Description |
|---|---|
| 2.0 | For 04489, change Status to Postponed |
| 2.0 | For 04489, add Discussion Record "Postponed for unification to 𬶘 U+2CD98, IRG 63." |
| 3.0 | For 04489, add Discussion Record "Not unified to 𬶘 U+2CD98, no change to G-glyph for 𬶘 U+2CD98, IRG 64." |
| 3.0 | For 04489, change Status to OK |
| Source Reference | Glyph |
|---|---|
| GCCPP-00035 |
| Character Reference | GCCPP-00035 |
| Codepoint | E022 |
| Radical | 195'.8 |
| Stroke Count | 8 |
| First Stroke | 2 |
| Total Stroke | 16 |
| IDS | ⿰鱼昂 |
| Variants | Trad VariantGCCPP-00034 |
| Pronunciation | ang2 |
| Total No. of Evidences | 2 |
| Notes | N/A |
| Secondary Radical | N/A |
| Secondary Stroke Count | N/A |
| Secondary First Stroke | N/A |
Review Comments
Unify to 𬶘.
Consider 㹧𱮒, the phonetic symbol should be 昂 < 卬, instead of 昴 < 卯.
Update the representative glyph of 𬶘 to |⿰鱼昂|.
But, the current draft of the new version of GB/T 22321.1 shows the glyph like the code chart.
It is better to encode them separately to make everyone more easily.
▲ p. 7 of IRG N2119
▲ p. 2 of IRG N2747
If China’s request to change the G glyph for U+2CD98 𬶘 back to the previous one, this character should be withdrawn by China in future.