«
00020
00021
00022
»
00021
2.0 丨
SC=4, FS=1 TS=5

SAT-01303
IRGN2632WS2021v6.0Pending
Postponed for further discussion of encoding model, IRG 57.
Attributes:



Review Comments

Type
Description
Submitter
Evidence
UNCLEAR_EVIDENCE
WS2021 v1.0
[ Resolved ]
The shape can be ⿰卜云,according to the shape of the right one, the shape can be ⿸厂𠫔.
Xieyang WANG
Individual
2021-05-19 02:53:39 UTC
Evidence
UNCLEAR_EVIDENCE (Response)
WS2021 v1.0
[ Resolved ]
As a composite character, the structure ⿰丨云 is standard and ⿰卜云 is extremely rare if any.

cf. https://www.unicode.org/L2/L2019/19346-gongche-policy.pdf
WANG Yifan
SAT
2021-05-20 05:57:32 UTC
Other
COMMENT
WS2021 v1.0
[ Resolved ]
Doubtful that this kana-ideograph ligature for to-iu should be considered as a CJK unified ideograph. As the example shows that it is used in the same way as kana, it probably more appropriate to propose to encode it in one of the kana blocks.
Andrew WEST
UK
2021-05-21 11:02:51 UTC
Evidence
NEW_EVIDENCE
WS2021 v1.0
[ Resolved ]
There are a non-trivial number of ideographs that include jamo as components, and this hybrid katakana (ト) + ideograph (云) is really no different. This evidence is page 2 of 国字の字典 (1990).

Ken LUNDE
UTC
2021-05-21 12:41:23 UTC
Other
COMMENT
WS2021 v1.0
[ Resolved ]
The evidence image shows that the proposed character is used in the same way as kana and reading marks (written smaller than a CJK ideograph, and positioned to the bottom right of a CJK ideograph), so in order to properly support this sizing and positioning behaviour in fonts it would be best to treat this kana-ideograph hybrid as a kana letter, and encode it in one of the kana blocks. This is completely different to some of the other hybrid characters which do behave like CJK ideographs, so I do not think Korean hybrid characters are a good analogy. IMO it should not be encoded as a CJK unified ideograph without compelling evidence that it is treated as a CJK ideograph in running text.
Andrew WEST
UK
2021-06-08 23:43:23 UTC
Other
COMMENT
WS2021 v1.0
[ Resolved ]
This case is similar to U+2B9AB 𫦫. We can't get any useful semantic information from the face of U+2B9AB 𫦫, because it's not an ideograph as we know.



Please see https://moji.or.jp/mojikibansearch/info?MJ文字図形名=MJ057066 .

The reading for U+2B9AB 𫦫 is かたな (the above page shows the type of this Japanese reading is 訓読み, but I think it's not right). The top left component is U+30AB カ, the top right component is 万葉仮名 (まんようがな) ta which is used in 古事記 (こじき), 日本書紀 (にほんしょき) and 萬葉集 (まんようしゅう), please also see http://www1.kcn.ne.jp/~uehiro08/contents/kana/ta.htm, and the bottom component is U+30CA ナ.
Eiso CHAN
Individual
2021-06-09 01:31:49 UTC
Other
COMMENT
WS2021 v1.0
[ Resolved ]
As UTC withheld the decision on whether it is a CJK ideograph, we need to consult IRG whether to accept it as an ideograph. Any suggestion is welcome.
WANG Yifan
SAT
2021-07-26 08:01:18 UTC
Other
COMMENT
WS2021 v1.0
[ Resolved ]
I suggest other method on encoding this character in my feedback on IRGN2492.
Eiso CHAN
Individual
2021-09-13 14:06:12 UTC
Evidence
NEW_EVIDENCE
WS2021 v4.0
[ Unresolved ]
This one has been included in ISO/IEC TR 10036:2020, which the corresponding glyph identifier is 10065005.

https://www.iso.org/standard/79490.html
Eiso CHAN
Individual
2023-03-10 14:01:29 UTC
Other
COMMENT
WS2021 v5.0
[ Unresolved ]
Eiso CHAN
Individual
2023-04-26 02:02:01 UTC

Meeting Minutes

DateDescription
IRG #57
2021-09-17 (Fri)
9:29 am +0800
Recorded by CHEN Zhuang
Postponed for further investigation on encoding model.

Attribute Changes

VersionDescription
2.0
For 00021, add Discussion Record "Postponed for further discussion of encoding model, IRG 57."
2.0
For 00021, change Status to Postponed

Glyph Changes

Source ReferenceGlyph
SAT-01303
1.0

Raw Info
groupSAT
a) Source referenceSAT-01303
b) PUA Code of TTFF111
c) KangXi Radical Code(Primary)002.0
d) Stroke Count(Primary)4
e) First Stroke(Primary)1
g) Total Stroke Sount5
i) IDS (Ideographic Description Sequence)⿰丨云
j) Similar/ Variants N/A
k) Ref. to Evidence docSAT-01303-01.jpg
l) Optional infoN/A
m1)Previous IRG WSN/A
m2)Sequence No of Previous IRG WSN/A