«
02322
02323
02324
»
02323
93.0 牛
SC=13, FS=3 TS=17

SAT-06926
Not unified to 撿 (U+64BF), non-cognate, IRG 61.
Similar To: Similar: 檢 (U+6AA2)/
U+64BFU+64BF
U+6AA2U+6AA2
Attributes:



Review Comments

Type
Description
Submitter
Data for Unihan
UNIHAN_DATA
WS2021 v3.0
kFanqie 力冉反
Eiso CHAN
Individual
2022-07-07 00:43:57 UTC
Modified
Evidence
UNCLEAR_EVIDENCE
WS2021 v4.0
[ Resolved ]
It says similar to 檢 (U+6AA2), but it's not clear how they are related from the evidence. Is there some other evidence?
Lee COLLINS
Vietnam
2023-02-08 22:10:47 UTC
Evidence
UNCLEAR_EVIDENCE (Response)
WS2021 v4.0
[ Resolved ]
Our "similar" includes those whose relationship is neither confidently affirmed nor denied, which does not necessarily mean they are variants. Sorry for the confusion.
WANG Yifan
SAT
2023-03-14 07:12:34 UTC
Other
COMMENT
WS2021 v5.0
[ Resolved ]
Per the submission rules for WS2021, IRG has requested that similar looking characters without being confirmed variants should also be included in the "Similar" field.
Henry CHAN
Individual
2023-04-08 10:52:26 UTC
Unification
UNIFICATION
WS2021 v5.0
[ Resolved ]
U+64BF
Potentially unifiable to 撿.

Based on the text it seems this is a variant of 撿. It is common for the 扌 and 牜 components to be mixed up, and it is probably not worth disunifying them into separate characters as it does not help in indexing or searching. I am unsure if IRG may prefer to add this to the UCV as level 2.
Henry CHAN
Individual
2023-04-08 10:54:39 UTC
Unification
NO_UNIFICATION
WS2021 v5.0
[ Resolved ]
It is too confusing to unify Components 扌 and 牜. The submitted evidence shows it is the variant of 𣫍 (U+23ACD), and 𣫍 (U+23ACD) must be the variant of 歛 (U+6582). There is one fanqie of 歛 (U+6582) as 良冉切 in 廣韻, and the fanqie of 撿 (U+64BF) is also 良冉切. The initial shengmu of 良 and 力 are both 來母, that means 良冉切 and 良冉切 mean the same pronunciation. However, the most common pronunciation of 撿 (U+64BF) now is jiǎn in Putonghua, gim2 in Cantonese, 검 in Korean and so on, which means “to pick up”. 來母 would not become [k] (>[ʨ]) commonly, that means the variant of 撿 (U+64BF) is different from the current most common definition of 撿 (U+64BF). If we unify this character with 撿 (U+64BF), that will be hard for the information processing on semantic meaning.
Eiso CHAN
Individual
2023-09-27 05:49:35 UTC
Unification
NO_UNIFICATION
WS2021 v5.0
[ Resolved ]
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.
John Knightley
Individual
2023-10-11 06:12:55 UTC

Meeting Minutes

DateDescription
IRG #61
2023-10-16 (Mon)
12:44 pm -0400
Recorded by CHEN Zhuang
no change, non cognate to 撿.

Attribute Changes

VersionDescription
6.0
For 02323, add Discussion Record "Not unified to 撿 (U+64BF), non-cognate, IRG 61."

Glyph Changes

Source ReferenceGlyph
SAT-06926
1.0

Raw Info
groupSAT
a) Source referenceSAT-06926
b) PUA Code of TTFF1DB
c) KangXi Radical Code(Primary)093.0
d) Stroke Count(Primary)13
e) First Stroke(Primary)3
g) Total Stroke Sount17
i) IDS (Ideographic Description Sequence)⿰牛僉
j) Similar/ Variants Similar: 檢/
k) Ref. to Evidence docSAT-06926-01.jpg;SAT-06926-02.jpg;SAT-06926-03.jpg
l) Optional infoN/A
m1)Previous IRG WSN/A
m2)Sequence No of Previous IRG WSN/A