Please wait while loading

IRG Working Set 2021v5.0

Source: John Knightley
Date: Generated on 2026-01-14

Show Deleted | Show comments from version: 1.0 2.0 3.0 4.0 5.0 6.0 7.0
The Image/Source column is displayed as it was in WS2021 v5.0. The character may have a different status in the latest working set.

Unification

SnImage/SourceComment TypeDescription
01878
01878
木 75.16.3
GKJ-00298
TS 20 · IDS
Unification
The proposed "liding" rule has yet to be discussed during a meeting, let alone accepted. A central question to be debated is whether or not it is possible to have a rule that just applies to shouwen, and if that was the case does it not mean that the decision to unify is ad hoc and therefore should not result in a new UCV since if the a character of exactly the same shape but unconnected to shouwen was submitted then it would not be unified.
Oppose Unification
Disagree with unification. Unification in this case would be inconsistent with established unification rules, clearly a case of different components therefore abstract shape is different. The abstract shape of a character must be determined by it's regular, aka kaishu, shape it can be determined by the shape of a character in another script.
04782
04782
鳥 196.14.1
GKJ-00303
TS 25 · IDS 𠪨
UCV
This character was moved to pending as there was no agreement at the time on whether or not to unify. There do not seem to be any UCS unification examples and, as noted above, there are at least 4 UCS disunification UCS examples. As it stands looks insufficient of a new UCV.
03191
03191
耳 128.1.5
GKJ-00727
TS 7 · IDS 𡿨
Oppose Unification
Disagree on unification as a character. The abstract shapes are different because of having different right hand components.
02963
02963
竹 118.12.2
SAT-04240
TS 18 · IDS 𠝣
Unification
The question to answer is should these be unified without using the "liding" rule.
00870
00870
土 32.11.1
SAT-04244
TS 14 · IDS
UCV
If unified any new UCV should be properly discussed and limited to at most the scope of the new unification,
03165
03165
羊 123.11.1
SAT-06015
TS 17 · IDS
Unification
U+6BB8
Disagree, should not unify. The current UCV 312d should be changed by removing the middle variant containing 殸 because it is not consistent with established UCS precedent to unify ⿱殸 and ⿱𣪊 as the examples below illustrate:

U+78EC 磬 ids ⿱殸石 vs U+2553C 𥔼 ids ⿱𣪊石
U+6480 撀 ids ⿱殸手 vs U+30515 𰔕 ids ⿱𣪊手
U+417D 䅽 ids ⿱殸禾 vs U+2585B 𥡛 ids ⿱𣪊禾
U+2A879 𪡹 ids ⿱殸口 vs U+23AA5 𣪥 ids ⿱𣪊口
U+2A371 𪍱 ids ⿱殸麥 vs U+2A360 𪍠 ids ⿱𣪊麥$(GT)
U+288A4 𨢤 ids ⿱殸酉 vs U+2888B 𨢋 ids ⿱𣪊酉
U+27421 𧐡 ids ⿱殸虫 vs U+879C 螜 ids ⿱𣪊虫
U+246D7 𤛗 ids ⿱殸牛 vs U+246BC 𤚼 ids ⿱𣪊牛
UCV
The two comments together list 22 disunification examples, comment #14276 8 examples and #14290 14 examples. Also that GHZR42524.09 was withdrawn. Withdrawing a character can be because the submitter does not agree to unification. The quote that says unifiable was not made by the submitter. The case for removing 殸 is very strong.
01069
01069
寸 41.9.4
SAT-06468
TS 12 · IDS
Oppose Unification
The disunification of 首 and is so deep routed in UCS there is even a main block example U+885C 衜 vs U+885F 衟 . If the "liding" rule entails that these be unified, then this is further proof that the "liding" rule should not be adopted.
02345
02345
犬 94.5.1
SAT-06646
TS 8 · IDS
UCV
Is this what is intended by UCV #305? (see below) I think not. Also the question of 火 vs 大 suggests this might be a misprint, and if so better be withdrawn and dealt with by IVD by the submitter, and not suitable to use as the basis of a UCV.

03698
03698
衣 145.4.1
SAT-06753
TS 10 · IDS 𧘇
Unification
U+2E571
Agree to unification of SAT-06753 and U+2E571 𮕱 as the same abstract shape and cognate based on the evidence presented so far. Where is there evidence of standalone usage with a different meaning?
02287
02287
爿 90.2.2
SAT-06795
TS 6 · IDS
Unification
U+725B
U+723F
No response as yet form the submitter and the sources for the evidence not is clearly identified. Does this only appear in one printed edition or many? Conversely what examples are there where 牛 and 爿 have been mixed up, and have this been encoded separately?
02323
02323
牛 93.13.3
SAT-06926
TS 17 · IDS
Oppose Unification
Disagree with unification. It would be counter productive to have at UCV of 扌 and 牜. If there are texts that confuse 扌 and 牜 better simply to consider the text unreliable and look to other texts for confirmation or rejection of a character.
03902
03902
足 157.10.1
SAT-07000
TS 17 · IDS 𧾷𱣎
Unification
U+318CE
U+6840
Agree to unification. The only UCS occurrence 𱣎 is 𱣎 itself, therefore unification as a component would not create a UCS inconsistency and since the graphical difference between 𱣎 and 桀 is so slight they have the same abstract shape. There are many characters that whilst suitable for separate encoding but are best unified when a component.
01523
01523
手 64.10.1
SAT-08367
TS 13 · IDS 𱣎
Unification
Agree to unification, see comment on 03902.
01715
01715
日 72.15.2
SAT-08386
TS 19 · IDS 𰰜
UCV
Since U+83EF 華 and U+8550 蕐 are both main block characters not covered by the source separation rule so they have different abstract shapes.
02901
02901
穴 116.8.3
SAT-08609
TS 13 · IDS
UCV
Everyone agrees with the unification (Comment #13326). To answer comment #14594:

No need for 瓜 and 爪 as a UCV. Would be sufficient just to add 㼌 and ⿰爪爪 as a UCV.

Note:
1) ⿰爪爪 is only found in two UCS characters U+24519 𤔙 ⿱爪⿰爪爪 and U+2D4F9 𭓹 ⿱宀⿰爪爪, SAT-06305 (cognate to 寙 U+5bd9?)
2) 㼌 is a component in 16 ucs characters 㺠, 㼌, 寙, 攨, 窳, 蓏, 𠆁, 𢸖, 𤂜, 𤣛, 𤬑, 𦋯, 𨰆, 𪴒, 𫾞, and 𮊏.
02061
02061
水 85.10.2
SAT-08812
TS 13 · IDS
UCV
It seems inappropriate to draw inferences from UCV #454a in this case. Suggest changing UCV #454a to level 2 to better clarify the scope of the UCV.
01799
01799
木 75.8.5
UK-20573
TS 12 · IDS 𠃛𠃛
Oppose Unification
Disagree with unification. To use this different unification because it is a transposition from Shouwen is not consistent existent UCS precedent or Annex S.
00036
00036
丿 4.11.5
VN-F0BE9
TS 12 · IDS 𠂊丿𰀁
Oppose Unification
Disagree with unification as multiple differences. It should also be noted the even if unified this would not be justification for the 9 part UCV suggested.
00880
00880
土 32.11.4
VN-F1779
TS 14 · IDS 𱷥
Oppose Unification
Disagree with unification because different abstract shapes. The bottom half of right hand component is 兆 which is totally different to 电 therefore they have different abstract shape by virtue of having a different component.
02595
02595
田 102.11.4
VN-F1C41
TS 16 · IDS 𱷥
Oppose Unification
Diagree as different abstract shapes see
00880
土 32.11.4
VN-F1779
TS 14 · IDS 𱷥
IDS=⿰土𱷥, 2023-04.
.


Attributes

SnImage/SourceComment TypeDescription
02664
02664
鳥 196.5.5
GKJ-00348
TS 16 · IDS
Radical
Yes when 'niuj' 107.0 (皮), is the radical,

(Loan words are used for new ideas and things, but already a word for bird so not surprisingly, the Chinese word for bird can only rarely be found if ever in most Zhuang languages as an ancient loan, where of course the standard spelling is indeed ''niux". It should be noted the standard spelling for modern loans would be "niuj", however since the word "niuj (scar)" is not, according to various published sources, used in Wuming which the standard spelling is based on, so this is a conjecture. Not to mention that, in many places the actually pronunciation of loan words whilst reasonably predictable, differs from the standard spelling and the most common difference is of tone.)


Evidence

SnImage/SourceComment TypeDescription
01878
01878
木 75.16.3
GKJ-00298
TS 20 · IDS
Evidence
As comment #14400 point 3 illustrates, if there was a 'liding' rule, or an IRGN2612 might be called, the result would be long debates about whether or a character was IRGN2612 enough to be applied to.
04732
04732
鳥 196.9.2
GKJ-00386
TS 20 · IDS
Evidence
Without more information hard to say if this is a stable variant or not. What more information about the evidence or further evidence is there?


Glyph Design & Normalization

SnImage/SourceComment TypeDescription
04069
04069
金 167.6.1
GKJ-00504
TS 14 · IDS
Normalization
UCV 442 is level 2, the discussion leading to it was {{ws2021-04702}}, it did not include an analysis of UCS disunification and unification examples.


Other

SnImage/SourceComment TypeDescription
01878
01878
木 75.16.3
GKJ-00298
TS 20 · IDS
Comment
Reply #14398 Yes, here saying "different abstract components" would be clearer than "different components". In the sentence above, that the components are abstract is implied by context . In this case it seems we both agree the abstract shape of the upper part right hand components have different abstract shape and therefore that the two characters have different abstract shapes by usual Annex S and UCS usage of the words. The "liding" rule uses different criteria. We can say that by Annex S conventions the two characters have different abstract shape therefore by that convention should not be unifie, but that the "liding" rule to say they can be unified.
04782
04782
鳥 196.14.1
GKJ-00303
TS 25 · IDS 𠪨
Comment
Reply to #14350,

thank you for the clarification of your notation, because of your liberal use of ~ elsewhere, I was under the impression that by ~ you simply meant to indicate variant.
02963
02963
竹 118.12.2
SAT-04240
TS 18 · IDS 𠝣
Comment
Note on English terminology. The word 'transliteration' can be used for alphabetical scripts to refer to the result of systematically replacing letters from one script with those of another. When talking about changing from one ideographic script to anther the word 'transposition' can be used to refer to the result the replacement of one character by another.