«
UK-20697
UK-20698
UK-20699
»
04563
194.0 鬼
SC=9, FS=2 TS=19

UK-20698
Kept in Main Set, pending further discussion of the encoding model for Taoist characters, IRG 57.
Attributes:



Review Comments

Type
Description
Submitter
Evidence
UNCLEAR_EVIDENCE
WS2021 v1.0
[ Resolved ]
It seems that the evidence does not satisfy IRG PnP 2.1.1.c, so it should be rejected.
IRG PnP 2.1.1.c says: characters must be used in script as characters in text. Logos and images used separately from running text are not acceptable.
Xieyang WANG
Individual
2021-05-23 02:05:11 UTC
Evidence
UNCLEAR_EVIDENCE (Response)
WS2021 v1.0
[ Resolved ]
We utterly reject the nonsensical comment made here and for many other UK characters by Wang Xieyang. A logo is "a small design used as the symbol of an organization, etc." (Chambers Dictionary, 1998), and quite obviously none of the characters proposed by the UK are either logos representing an organization or embedded images. The examples clearly show that the proposed characters are used in running text in exactly the same context as other encoded CJK unified ideographs.
Andrew WEST
UK
2021-08-12 09:47:40 UTC
Evidence
UNCLEAR_EVIDENCE
WS2021 v1.0
[ Resolved ]
I am really tired of seeing the act of pretending "I don't know". The fact that the structure of this character seems normal doesn't prove it's not a logo or picture kind of thing. What's more, I must classify that I won't oppose to encode 符咒字 if real running text can be found, for example:
https://hc.jsecs.org/irg/ws2021/app/?find=UK-20700
https://hc.jsecs.org/irg/ws2021/app/?find=UK-20701
https://hc.jsecs.org/irg/ws2021/app/?find=UK-20702
https://hc.jsecs.org/irg/ws2021/app/?find=UK-20703
等等.
Here are my questions to UK:
1. What does UK take 符箓? Is 符箓 a character?
2. If a character is used only as a part of 符箓, does UK think it is a normal CJKUI?
3. Why this comment is not under these characters?
a) https://hc.jsecs.org/irg/ws2021/app/?find=UK-20710
In the evidence, it says 若因治病,上加"XXXX", it is very obvious saying how to write/draw a 符箓. It's not a running text.
What's more, the structure on the right bottom is not the claimed ⿰三三 but a 坤卦(☷, U+2637).
b) https://hc.jsecs.org/irg/ws2021/app/?find=UK-20796
You must be kidding me that this is running text.
c) https://hc.jsecs.org/irg/ws2021/app/?find=UK-20752
This actually an example of 符箓, the one on the left contains a weired character on the bottom and four character seems normal. If this can be running text, then why won't the one on the bottom encoded?
I'd like UK to answer my question direcly and clearly in a sensical way.

One more thing to clarify, I don't oppose to encode 符咒字, but I do oppose to encode them this way. The reasons are as follows:
1. It's not every 符咒字, even the ones used very frequently have an evidence that satisfys IRG PnP. It's meaningless that we encode them seperately and unprofessionally.
2. According to the comments in todays meeting, some experts still don't realize the complexity and the large quantity of 符咒字. We should discuss the ways of encoding them and unifying them thoroughly and change our PnP. It's better that we face the problems of 符咒字 and encode them as 符咒字 than pretend them as normal characters and make others belive this.
Xieyang WANG
Individual
2021-09-13 05:11:22 UTC
Evidence
EVIDENCE
WS2021 v1.0
[ Resolved ]
辞海 第六版(彩图本)P642:


p1459

现代汉语词典 第7版,P402
Xieyang WANG
Individual
2021-09-15 14:12:42 UTC
Evidence
UNCLEAR_EVIDENCE
WS2021 v5.0
[ Unresolved ]
Should be postponed according to experts' opinion in IRGN2579.
Xieyang WANG
Individual
2023-10-17 14:32:11 UTC
Evidence
UNCLEAR_EVIDENCE (Response)
WS2021 v6.0
[ Resolved ]
No reason to postpone as the evidence is clear, and the character is required for digitization of the source text.
Andrew WEST
UK
2024-02-20 17:20:05 UTC
Evidence
UNCLEAR_EVIDENCE
WS2021 v7.0
[ New ]
Potentially be nonce.
The evidence UK provided is from a book named "梵音斗科". ⿺鬼咢 is only found in this book, which is written and published by Mr. Lou Jinyuan(娄近垣) in the Qing Dynasty.
Considering that:
• ⿺鬼咢 is seen only in a song for a special ceremony to communicate with a God. Meanwhile, the ceremony was recorded only in the book "梵音斗科". The book has not been reorganized and published again since its initial publication, and the ideographs have not been quoted by anyone.
• Mr. Lou Jinyuan(娄近垣) should be famous at least among the Daoists in the Qing Dynasty. But we don't know if he is still well-known nowadays. The submitter didn't provide any related illustrations.
• The submitter didn't explain the meanings and rationale of ⿺鬼咢 is. For self-published books, ideographs used in them can be created very freely.
So:

After analysis, we can find that there are one or two factors that argue for encoding, but two or three factors that argue against encoding. Since it is not required for use in government databases, I think it is reasonable to ask for further investigation.
Xieyang WANG
Individual
2024-09-13 06:23:31 UTC
Evidence
NEW_EVIDENCE
WS2021 v7.0
[ New ]
正统道藏·法海遗珠·卷八
Xieyang WANG
Individual
2024-09-15 07:06:15 UTC

Meeting Minutes

DateDescription
IRG #57
2021-09-17 (Fri)
11:00 am +0800
Recorded by Henry CHAN
Kept pending further discussion of the encoding model for Taoist characters (automatically processed by IRG ORT Manager)
IRG #57
2021-09-17 (Fri)
11:01 am +0800
Recorded by Henry CHAN
Kept in Main Set, pending further discussion of the encoding model for Taoist characters (automatically processed by IRG ORT Manager)

Attribute Changes

VersionDescription
2.0
For 04563, add Discussion Record "Kept in Main Set, pending further discussion of the encoding model for Taoist characters, IRG 57."

Glyph Changes

Source ReferenceGlyph
UK-20698
1.0

Raw Info
groupUK
a) Source referenceUK-20698
b) PUA Code of TTFE0E0
c) KangXi Radical Code (Primary)194.0
d) Stroke Count (Primary)9
e) First Stroke (Primary)2
f) Secondary KX Radical CodeN/A
f) a. Secondary Stroke CountN/A
f) b. Secondary First StrokeN/A
g) Total Stroke Count19
i) IDS⿺鬼咢
j) Similar/ Variants N/A
k1) References to evidence documents《梵音斗科》(清雍正初刊本)卷上 folio 57
k2) Images FilenamesUK-20698-001.jpg
l) Other InformationN/A
m1) Previous IRG WSN/A
m2) Sequence No.N/A