Per document IRG N2709, this particular ideograph is officially being proposed as a UNC by TCA, and if accepted during the IRG #63, it should be removed from this working set. As stated in Comments #1814, China can submit a horizontal proposal after Unicode Version 17.0 has been released (2025). If the ideograph is considered urgent for China, which I suspect it is not given that it is in an IRG working set, China can submit a UNC proposal.
It may be unifiable with 𰀾 (U+3003E). Henry's comment for 00083 in the ORT for IRG Working Set 2015 suggests that U+3003E is cognate with U+8FFA, which is claimed to be a synonym (aka cognate) of this ideograph.
This ideograph is a disunification of U+6ECB 滋 that also affects U+FA99 滋. If accepted, the kIRG_KPSource property value of U+FA99, KP1-52B4, should be moved to the new code point, the kIRG_KPSource property value of U+FA99 should be changed to KPU-0FA99, and the kIRG_USource property value of U+6ECB, UTC-00777, should be removed.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
My personal opinion is that until someone—or a member body—prepares and submits a formal proposal to create a new CJK Components (or similar) block, we should continue to encode radical-like components as CJK Unified Ideographs.
My personal opinion is that until someone—or a member body—prepares and submits a formal proposal to create a new CJK Components (or similar) block, we should continue to encode radical-like components as CJK Unified Ideographs.
This ideograph is a disunification of U+7DF4 練 that also affects U+FAB0 練. If accepted, the kIRG_KPSource property value of U+FAB0, KP1-671B, should be moved to the new code point, and the kIRG_KPSource property value of U+FAB0 should be changed to KPU-0FAB0. As with the most recent disunification, Japan will not want to move the kIRG_JSource property value of U+7DF4, J0-4E7D, to the new code point due to compatibility concerns.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
This ideograph is a disunification of U+233D5 𣏕 that also affects U+FAD1 𣏕. If accepted, the kIRG_KPSource property value of U+FAD1, KP1-4B26, should be moved to the new code point, and the kIRG_KPSource property value of U+FAD1 should be changed to KPU-0FAD1.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
This ideograph is a disunification of U+5F50 彐 and U+2B739 𫜹.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
To mirror Vietnam's comments in 02657, this ideograph should not be unified with 𠯇 (U+20BC7), because the phonetic components, 己 (kỷ) and 已 (dĩ), are very different. UTC-03296 would therefore be non-cognate with U+20BC7 in Vietnamese.
While I agree that the abstract shape is the same, there is a significant structural difference that requires discussion before unification can be considered.
The person who submitted this ideograph to the UTC pointed out that U+2B7B9 in the Extension D block is a disunification example. My own checking found that U+2D5FB in the Extension F block, which appears to be cognate with 巠 (U+5DE0) according to the Moji Jōhō Kiban database, is another example.
The person who submitted this ideograph to the UTC provided this evidence image, which is from the Meiji era. It shows that it is a variant of U+62DC, which in turn is a variant of U+62DD.
The structure of the glyph in the evidence images looks like ⿹彧虫. If the representative glyph is changed, the IDS should be changed as provided in the previous sentence.
The source reference for this ideograph, GDM-00377, conflicts with the new source reference for U+2B80B 𫠋 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00434, conflicts with the new source reference for U+2B74B 𫝋 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00435, conflicts with the new source reference for U+2B767 𫝧 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00436, conflicts with the new source reference for U+2B768 𫝨 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00437, conflicts with the new source reference for U+2B76A 𫝪 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00438, conflicts with the new source reference for U+2B785 𫞅 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00439, conflicts with the new source reference for U+2B7A2 𫞢 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00440, conflicts with the new source reference for U+2B7A7 𫞧 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00441, conflicts with the new source reference for U+2B7B7 𫞷 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00442, conflicts with the new source reference for U+2B7D1 𫟑 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00443, conflicts with the new source reference for U+2B7E0 𫟠 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00444, conflicts with the new source reference for U+2B7E2 𫟢 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00445, conflicts with the new source reference for U+2B7E5 𫟥 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00446, conflicts with the new source reference for U+2B7EB 𫟫 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00447, conflicts with the new source reference for U+2B7EC 𫟬 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00449, conflicts with the new source reference for U+2B7F5 𫟵 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00450, conflicts with the new source reference for U+2B7F6 𫟶 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00451, conflicts with the new source reference for U+2B7F8 𫟸 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00452, conflicts with the new source reference for U+2B801 𫠁 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00453, conflicts with the new source reference for U+2B802 𫠂 in Unicode Version 16.0 per document IRG N2679.
The source reference for this ideograph, GXM-00454, conflicts with the new source reference for U+2B805 𫠅 in Unicode Version 16.0 per document IRG N2679.
Strongly agree with Comment #1509. This appears to be the only instance of this component in this working set. Radical #151 still serves as the best primary radical, but Radical #140 should be its secondary radical. The previous working set also had a single instance of this component, #03392, which specifies 140 as its radical, though in the current draft of the Extension J block, U+332B0, it serves as the secondary radical. For all previous blocks, I queued up feedback for making similar adjustments that will be targeted for Unicode Version 17.0 (2025), which was submitted today. This particular feedback prompted me to submit the feedback for previous blocks. In other words, Radical #140 will be set as either the primary or secondary radical when this component appears in an ideograph..
The reading of こっとい is the result of the person who submitted the ideograph to UAX #45 making a personal enquiry to the Kyotango City Hall tax department (京丹後市役所税務課) by telephone on 2021-07-13. While there are no published literature sources that confirm this reading, the Kyotango City Hall responded that the reading of the place name 歩⿰牛化 is ほごっとい. Therefore, the reading of ⿰牛化 is likely to be こっとい.
While this comment has nothing to do with the submitted ideograph, I am curious as to why U+3004 〄 JAPANESE INDUSTRIAL STANDARD SYMBOL appears on the third line from the bottom.
IRG Working Set 2024v1.0
Source: Ken LUNDE
Date: Generated on 2026-07-28
Unification
Showing 28 comments.
It may be unifiable with 𰀾 (U+3003E). Henry's comment for 00083 in the ORT for IRG Working Set 2015 suggests that U+3003E is cognate with U+8FFA, which is claimed to be a synonym (aka cognate) of this ideograph.
This is U+32FF7 in the DRAFT Extension J code chart.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
Agree to unify with 縠 (U+7E20).
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
Note that disunifications have been processed via previous IRG working sets, which is why the UTC decided to submit this ideograph. UTC-01159, UTC-01162, and UTC-02972 in IRG Working Set 2017 served as precedents.
Attributes
Showing 178 comments.
Evidence
Showing 9 comments.
Glyph Design & Normalization
Showing 20 comments.
Editorial
Showing 21 comments.
Other
Showing 10 comments.
[WS2021-00765]
Data for Unihan
Showing 138 comments.
U+9C88 鲈
U+27E86 𧺆
kSpoofingVariant U+535D 卝
kSpoofingVariant U+5EFE 廾
kSpoofingVariant U+8279 艹
kSpoofingVariant U+21B1D 𡬝