Traditional Chinese Character U+26C29 U+E0102 (KS068340) Not Supported

[patrickdark]

The traditional Chinese variant of 𦰩 (U+26C29 U+E0102 (KS068340)) doesn't seem to be supported; I can only get the Japanese glyph to display.

The glyph is displayed on page 230 at https://unicode.org/ivd/data/2017-12-12/IVD_Charts_Hanyo-Denshi.pdf. Both glyphs are supported for characters like 嘆 through Noto Sans CJK JP/TC Regular.

[kenlunde]

First and foremost, the only form of U+26C29 𦰩 that is claimed to be supported in the context of these Pan-CJK typeface families is the JP form as it appears in the JIS X 0213 standard. Any other context is out of their scope. U+26C29 𦰩 is also a single-source ideograph. In other words, this is as-designed.

Second, instead of referencing the effectively-deprecated Hanyo-Denshi IVD collection, you should instead be referencing the relevant page in the _MojiJoho IVD collection glyph charts, specifically page 200. As the IVD Registrar, I have been asking the Hanyo-Denshi IVD collection registrant to provide a non-stale URL for the collection, and have yet to receive anything, which is why I am treated it as deprecated. Furthermore, a large number of Hanyo-Denshi IVSes are shared with the newer _MojiJoho IVD collection, which supports the deprecataed treatment.

Lastly, the IVS you referenced, <26C29 E0102> (aka Moji_Joho MJ057282), is not Traditional Chinese, but rather the traditional form of the Japanese glyph. There is a subtle yet important difference.

@marekjez86 You can safely close this issue.

[marekjez86]

@kenlunde : Thank you Ken for a very thorough explanation. Closing

[patrickdark]

@kenlunde It may be helpful to know the primary rationale for submitting this bug report: there is currently no way to distinguish between traditional Chinese and Japanese forms without font support for the additional glyph in documents like https://en.wiktionary.org/wiki/%E5%98%86#Alternative_forms. The document is currently using inline SVG images as a workaround.

I'm not sure that the status of Hanyo‐Denshi is particularly relevant since U+26C29 U+E0102 is also a requirement of the document you mentioned. (My original source was the neutral https://unicode.org/ivd/data/2017-12-12/IVD_Sequences.txt and I arbitrarily picked one of the graphical documents listed for U+26C29 to cite here to make the bug report clear.) It would be possible to achieve the correct rendering for traditional Chinese using a CSS‐based, single‐character subset of the Japanese font; however, my testing indicates that the Japanese Noto font doesn't support the glyph either.

If it's been determined that this glyph is definitely out of scope of the entire project, I can't really argue with that, however.

[kenlunde]

@patrickdark When dealing with a Pan-CJK typeface design, you need to be very specific about requests. Using U+6F22 漢 as an example, whose right-side component is U+26C29 𦰩 that is the focus of your issue, the image below shows the standard Japanese, the traditional form for Japanese, and the Traditional Chinese (for Taiwan) form of the character:

The second and third glyphs are not exactly the same.

My point about referring to the _MojiJoho IVD collection rather than the Hanyo-Denshi one is unrelated to the issue at hand, and was mainly meant for your benefit when plucking IVSes out of the _IVDSequences.txt data file. In any case, neither IVD collection is within the scope of these Pan-CJK typeface designs.

For the far future, which means years and possibly a decade or more, we may end up covering this and other glyphs. For the near future—and to answer your question in what I hope is a definitive way—the glyph you are requesting is outside the current scope of the project.