In favour of unifiation to 𠽏 U+20F4F.

It is extremely clear that the right hand side phonetic should be 陷. This is a completely different phonetic from 舀. I don't agree that the semantics are hard to clarify for GZ-2352301.

Historically it is common for 𠂊 and 爫 to be swapped.

I don't understand why "Annex S records source separation examples" would imply not suitable for a new UCV. All examples in the Source Code Separation mean they were deemed unifiable, but not unified, because they are encoded separately in the original source tables.

There are already multiple transcriptions of this, and there are more unencoded transcriptions.

U+20767 𠝧
U+2641F 𦐟
U+26431 𦐱
U+2647E 𦑾
U+2678B 𦞋
U+31ED7 𱻗
U+31EDD 𱻝




I do not suggest that we allow more transcriptions. The IVD is precisely suitable for encoding these cases.

I think precisely because people sometimes failed to recognize it was the same character, unification to 頓 with IVD would help people find this character, without the need for the end user to install additional IMEs or the digitization system to maintain an internal mapping system.

While it may be common for systems in mainland China for academic tools to also come with an ecosystem of tools, such tools are inherently proprietary or specific to a certain system and is not beneficial for data exchange.

It would not make sense for just the base glyph to be encoded as a character, and the glyph with the 口 radical to be coded separately, as that means (1) either there is an explicit decision to discard the variant or (2) the system will need to adopt IVD anyways.

Unify to 褺 U+893A with UCV for upper part 𡙕 and 執.

Unify to 㒓 (U+3493) and add new UCV of 達 and 𨔶.

See also 01960 which is a variant of 橽 (U+6A7D):

01960

木 75.13.1

SAT-09425

TS 17 · IDS ⿰木𨔶

Per Kushim's comment, there are two variants which are disunified, but are in Extension B:

𣿔 ~ 澾
𩍠 ~ 韃

Suggest to add a new UCV of 𢉙 and 庶 (in addition to existing NUCV #403 火/灬).

Potential unification to 𣑭 (U+2346D).

Unifiable to 媟 U+5A9F per UCV #452



Suggest unification to avoid confusion with 媒.

Unify to 磔 (U+78D4); new UCV for ⿱𤘆木 and 桀.

Unification to 蚸 (U+86B8)?

Potential new UCV of 斥 / ⿸广干 / ⿸广千.

00858 would also be unified to 坼.

Unify to 𧵍 (U+27D4D) and add a new UCV for the whole top component

Unify to 𥿳 (U+25FF3).

Both U+25FF3 and SAT-10235 are variants of 細.

Unify to 貾 (U+8CBE) per UCV #453

Note: the link given in comment #6908 is broken, the new link is https://db.history.go.kr/unicode/getCodeDetailHtml.do?code=75462

Potential unification to 鋑?

Not sure how widespread ⿱幺友 ~ 夋 is.

SC=9, TS=14.

务 should be counted as ⿱攵力 here per Kangxi conventions.

Supplementary info to Tao Yang:

② is already encoded at 𧸅 U+27E05




① and ③ can be unified to it if they are submitted in the future.

The glyph on the company website doesn't match the glyph used by the business registration for the same glyph, can TCA confirm which one should be the correct one?

Removal of the stroke from 幼 is pretty common historically:



(Quoted from the MOE Dictionary entry for A01549)

Potentially this could be a UCV level 2 if there are a huge number of variants of 幼 from V source.

Support normalization to ⿱艹剑 as the traditional form 𧁴 ⿱艹劍 is coded as U+27074.

The evidence seems to show ⿱山六 (𡴆) instead of ⿱山大, of which 𡴆 is a common transliteration of 𧶠

The Traditional Variant needs to be checked as the Traditional Variant is currently under radical moon instead of expected meat.

Semantic Variant of 𣶒?

Potential G or T-glyph change for U+27E15.

The G glyph quotes GHZ:



However, per the MOE dictionary, one version of the original source writes it as ⿰貝㒼

See also: https://hc.jsecs.org/irg/ws2017/app/?id=01867
Another form of this character is ⿰睪毛.