I don’t think end users are going to distinguish different forms of this character in running text. They are only distinguished when they are symbols at the most. I suggest only encoding one traditional form and one simplified form of the character. And if you really find the distinction important, you can always either register for an IVD or submit a proposal to WG2/Unicode for encoding as CJK Symbols.
Neither piece of evidence shows the character has been used in running text. Given Evidence 25, I support the proposal in L2/22-207R to encode this character in the Musical Symbols block and withdraw it from the working set.
Per Henry’s feedback on IRGN2540, it would be advisable for Eiso to consider including an additional character for the non-abbreviated form 散 in the proposal document to WG2.
IRG Working Set 2024v1.0
Source: KWAN Ching Kit (Daniel)
Date: Generated on 2026-05-18
Unification
Showing 7 comments.
Unifiable to 𱎚 (U+3139A)?
Unify to 冓 (U+5193). ⿱玨冉聲 indicates that ⿱玨冉 is the 聲旁 of 搆, which suggests that ⿱玨冉 and 冓 are interchangeable.
Isn’t it merely a common handwriting form of 必? It’s just that the hook of the slanted stroke is not that visible, perhaps related to printing.
Unify to 冀 (U+5180). Clearly a corruption of 冀 that does not worth a codepoint. Consider a new UCV.
Unifiable to 製?
Attributes
Showing 10 comments.
Evidence 4 and the above evidence from 干祿字書 shows ⿰⿺乚丶丶.
Evidence
Showing 1 comments.
Glyph Design & Normalization
Showing 5 comments.
Other
Showing 9 comments.
[WS2021-00315]
Per Henry’s feedback on IRGN2540, it would be advisable for Eiso to consider including an additional character for the non-abbreviated form 散 in the proposal document to WG2.
Data for Unihan
Showing 41 comments.
kCantonese zik1
kCantonese go1
kCantonese zin2
kCantonese kek6
kJapaneseOn GEKI KEKI GYAKU
kKorean KUK