While I agree that in this case, the character is a variant of U+8870 / U+2E571, it is also used as a variant of 襄, both as a component in U+2A48C and U+2C340 and standalone. I would argue for separation.
Oppose Unification
I don't currently have evidence of the standalone usage of this as U+8944 襄, but given the examples of component usage as 襄, it's certainly possible that we would find this as a standalone form.
In the 30 plus years of experience with encoding Nôm we have come up with exactly 5 pairs of characters which distinguish 𦥷 and 興. With the exception of V0-3962 and VN-232F1, all are already encoded: e.g U+2C2D9 and U+2444D. I don't see this as a big win, it would just add another difficult to explain unification rule.
As Eiso points out, these two characters were addressed by the IRG during the discussion of IRGN2429. They different in shape, non-cognate, and should not be unified.
For extension H, the IRG previously debated unification U+31E22 𱷥 with 籠 and U+31DE5 𱷥 with variants of 龍. Unification was rejected. There is no new information here and I see no reason to change.
For extension H, the IRG previously debated unification U+31E22 𱷥 with 籠 and U=31DE5 𱷥 with variants of 龍. Unification was rejected. There is no new information here and I see no reason to change.
U+31DE5 is less common than 竜. For extension H, the IRG previously debated unification U+31E22 𱷥 with 籠 and U+31DE5 𱷥 with variants of 龍. Unification was rejected. There is no new information here and I see no reason to change.
My understanding is that for IRG work we count 及 as 4 strokes (different from Unihan data). 盍 is 10, so SC = 14. This is consistent with the simplified form: U+28E0D
Looking at all of the encoded Vietnamese characters with 娄 on the left side, since 娄 is the phonetic, with the exception of U+21890, which uses # 38, the radicals used are based on the right side semantic element. Since we we have now changed the basis for determining the radical, we might want to go back and the change previously encoded characters at some time.
I would be careful about assuming that this is an error form. In Vietnamese, this form has a specific meaning, for example, U+2015C 𠅜 (⿱亠例) is thought to be an abbreviation of ⿱麻例 (ma+lệ) where the reduced form 亠 for "ma" indicates an initial "*ml-" in spoken Vietnamese when the character was first used. We need more information.
Agree with #12638, this seems to be a simplification of the the form 褱, similar to the the way 坏 is used for 壞. Modern Chinese editions typically use simplified forms for classical texts, but that does not invalidate the form or the edition.
This is and the character next to it, are arguably not transcriptions of Sanskrit, but attempts to reproduce forms of the Siddham characters "ni" and "svā" Variants of this script can be found throughout East Asia. We should consider whether to encode the complete alphabet and combinations in a separate block.
This is arguably not a transcription of Sanskrit, but an attempt to reproduce a form of the Siddham character "ha". Variants of this script can be found throughout East Asia. Here is an example from Vietnam:
It might be better to collect the whole alphabet and combined forms as a separate script rather than encode piecemeal in the Ideographic blocks.
It is important to note that the Vietnamese is not a misprint. 茶 (Sino-Vietnamese, "trà") is clearly the desired phonetic for "chà". 荼 (SV: đồ) is more commonly used for "dưa", "giưa", etc.
The Vietnamese means "to split lengthwise". It's unlikely that this is cognate with the Chinese usage, but since the shapes are identical we can treat both usages as a single character. This is similar to other separately created characters, such as 畑: Vietnamese "đèn" = lamp, Japanese はたけ = dry field.
The dictionary, Giúp Đọc, just explains the structure: "thủ" = 手 and the phonetic, "sùng" 崇. The final, 'ung' of 崇 is an exact match, so I guess the question is about the initial "s-". There are certainly many cases where the phonetic is not an exact match, but the use of "s-" here to represent a velar does seem to be an outlier. Possibly this is a borrowing from an older stage of Chinese that contained a velar (at least according to Baxter-Sagart reconstructions). For example, "sen" (lotus) is thought to be derived from 蓮, which they reconstruct as *k.[r]ˤe[n]. Similarly, the word river, "sông" is thought to be derived from an earlier Austroasiatic word similar to Mon "kruŋ". Perhaps in some circumstances, the velar was retained.
In the Vietnamese source, this is a stand-alone character, read "rông" (from "rồng" = "dragon"), meaning "unrestrained, dissolute". The new evidence shows that it can also be used as a component.
I agree with the comment. Structurally, 淫 (dâm) is a better phonetic than 滛 (phonetic "dao"), but if you see here (https://hvdic.thivien.net/whv/滛), many Vietnamese dictionaries consider the two to be equivalent. Here is another example where phonetic 滛 has a reading based on 淫
Evidence
Prof. Hồng, the author of the source, explains that the character is written with 滛. His intent in the structural analysis is to show that the intended phonetic was 淫. So, the font is correct.
According to Prof Hồng, the compiler of the dictionary, both forms are in use and the analysis is a short way to indicate that 速 can be abbreviated to 束.
It might be premature to change the shape. ⿱⿹⺄夕一 and ⿹⺄𢆰 possibly represent different Sanskrit syllables. The original evidence only explains ⿱⿹⺄夕一 as 尼. However, 尼 is used to write both dental "ni" (e.g 釋迦牟尼 śākyamuni) and retroflex "ṇi" (摩尼 maṇi). If these are attempts to represent some Brahmic script (梵書), it's possible that the difference in shape reflects the different sounds. The evidence for ⿹⺄𢆰 shows it the context of a dhāraṇī that is clearly "ṇi" in "maṇi". It would be safer to see ⿱⿹⺄夕一 in context to determine whether they are the same or different.
I checked other glyphs that have the same element, 善. Almost all of the characters with 善 on the right use the same design as VN-F00EC, many with 善 on the left do too. Since this includes many encoded characters it's not a trivial effort, requiring a proposal and review.
This could possibly be 攵, but I don't have access to the source text cited by Prof. Hồng. Most of the glyphs with the component 嫩 have 攵, but U+21128 / V2-7259 "non: 𡄨 has 女. But, as you can see in the 2nd character of line 1369 of Kiều, the glyph is clearly 攵.
It would be reasonable to normalize VN-F170F and V2-7259 to 攵
Glyph design
We have updated the font to reflect the proposed change.
This form is similar to many others, such as V2-6E38 𠂫. The form that looks more like 乃 would also be acceptable, but there is no point to do this unless we change the 50 odd glyphs, mostly encoded, to use it.
While some manuscripts show a dot, most have a longer stroke for this element, so in our normalized form, it looks more like 丨 than a "dot". Here is another character with the same element on the left;
VN-F1DE1 is a Nôm Tày character meaning stale, spoiled and it is read "nẩu" from the phonetic 𱜢 < 鬧 (nháo). While the left side is similar, as the radical suggests, there is no relationship semantically to U+2DC59, a variant of U+3D11 㴑, (which in turn is a variant of 逆) meaning "against, opposite". The Shuowen cited here uses U+2DC59 to explain the meaning of 洄 as "against the current". This is very different from VN-F1DE1
Japanese reading shown is さむし, which is the classical Japanese form. In modern Japanese this would be さむい. The latter might be preferred for the value of kJapanese.
IRG Working Set 2021v5.0
Source: Lee COLLINS
Date: Generated on 2024-12-14
Unification
Attributes
Evidence
It might be better to collect the whole alphabet and combined forms as a separate script rather than encode piecemeal in the Ideographic blocks.
Glyph Design & Normalization
It would be reasonable to normalize VN-F170F and V2-7259 to 攵
Other
Data for Unihan