Please wait while loading

IRG Working Set 2024v3.0

Source: Henry CHAN
Date: Generated on 2025-12-08

Show Deleted | Show comments from version: 1.0 2.0 3.0 | Show comments with status: Show All New Only Unresolved Only

Unification

Showing 13 comments.

SnImage/SourceComment TypeDescription
00619
00619
口 30.13.2
GZ-2352301
TS 16 · IDS
Unification
U+20F4F
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.
00272
00272
刀 18.8.5
GZHSJ-0067
TS 10 · IDS 𠚪
Unification
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.
04155
04155
頁 181.5.1
GZHSJ-0083
TS 14 · IDS
Unification
U+9813
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.
00166
00166
人 9.13.1
SAT-09038
TS 15 · IDS 𨔶
Unification
[ Unresolved from v2.0 ]
U+3493
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:

𣿔 ~ 澾
𩍠 ~ 韃
01627
01627
手 64.10.1
SAT-09161
TS 13 · IDS 𢉙
UCV
Suggest to add a new UCV of 𢉙 and 庶 (in addition to existing NUCV #403 火/灬).
03402
03402
虫 142.6.4
SAT-09867
TS 12 · IDS 𢇛
Unification
U+86B8
Unification to 蚸 (U+86B8)?
UCV
Potential new UCV of 斥 / ⿸广干 / ⿸广千.

00858 would also be unified to 坼.
03576
03576
貝 154.5.3
SAT-10042
TS 12 · IDS
Unification
U+27D4D
Unify to 𧵍 (U+27D4D) and add a new UCV for the whole top component
UCV
02969
02969
糸 120.6.3
SAT-10235
TS 12 · IDS 𠆢
Unification
U+25FF3
Unify to 𥿳 (U+25FF3).

Both U+25FF3 and SAT-10235 are variants of 細.
03418
03418
虫 142.9.3
SAT-10653
TS 15 · IDS
Unification
[ Unresolved from v1.0 ]
U+8771
Support unification to 蝱.

There are a huge number of variants involving 亡 and 亾, and the bulk of encoded ones are in Extension B:

㠩 U+3829 = 巟 U+5DDF
㡃 U+3843 = 㡆 U+3846
𧠬 U+2782C = 𧠰 U+27830
𮎰 U+2E3B0 = 荒 U+8352
𥞙 U+25799 = 𥡃 U+25843
𥿪 U+25FEA = 𥿼 U+25FFC
𩢯 U+298AF = 𩣇 U+298C7

There are some other unencoded examples:



Source: https://dict.variants.moe.edu.tw/dictView.jsp?ID=14706



Source: https://dict.variants.moe.edu.tw/dictView.jsp?ID=14701

00270
00270
刀 18.7.5
UK-30032
TS 9 · IDS
Unification
[ Unresolved from v2.0 ]
Note: the link given in comment #6908 is broken, the new link is https://db.history.go.kr/unicode/getCodeDetailHtml.do?code=75462
03266
03266
艸 140.7.3
UTC-03353
TS 11 · IDS
Unification
[ Unresolved from v2.0 ]
U+2C73B
Given that there is other evidence of use, I suggest that this character doesn't need to be withdrawn. However, unification should still be on the table as I believe they (UTC-03353, U+83EF and U+2C73B) are variants.

Attributes

Showing 1 comments.

SnImage/SourceComment TypeDescription
02611
02611
目 109.8.4
VN-F200F
TS 13 · IDS
Residual Stroke Count
[ Unresolved from v2.0 ]
SC=9, TS=14.

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

Evidence

Showing 2 comments.

SnImage/SourceComment TypeDescription
03593
03593
貝 154.11.1
KC-10053
TS 18 · IDS
Evidence
Supplementary info to Tao Yang:

② is already encoded at 𧸅 U+27E05

U+27E05


① and ③ can be unified to it if they are submitted in the future.
04643
04643
黑 203.4.5
幺 52.13.2
VN-F0188
TS 16 · IDS
Evidence
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.

Glyph Design & Normalization

Showing 2 comments.

SnImage/SourceComment TypeDescription
00277
00277
刀 18.10.1
GZ-1852301
TS 12 · IDS
Normalization
Support normalization to ⿱艹剑 as the traditional form 𧁴 ⿱艹劍 is coded as U+27074.
03545
03545
言 149.25.2
SAT-09174
TS 32 · IDS
Glyph design
The evidence seems to show ⿱山六 (𡴆) instead of ⿱山大, of which 𡴆 is a common transliteration of 𧶠

Other

Showing 4 comments.

SnImage/SourceComment TypeDescription
03168
03168
肉 130.10.2
GCCPP-00019
TS 14 · IDS
Comment
[ Unresolved from v1.0 ]
The Traditional Variant needs to be checked as the Traditional Variant is currently under radical moon instead of expected meat.
00264
00264
刀 18.6.4
GXM-00436
TS 8 · IDS
Comment
[ Unresolved from v1.0 ]
Semantic Variant of 𣶒?
03593
03593
貝 154.11.1
KC-10053
TS 18 · IDS
Comment
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 ⿰貝㒼

02050
02050
毛 82.11.2
SAT-09392
TS 15 · IDS
Comment
[ Unresolved from v1.0 ]
See also: https://hc.jsecs.org/irg/ws2017/app/?id=01867
Another form of this character is ⿰睪毛.