Request to add variant: Traditional Kangxi glyph form

[ghost]

Could you please add variants of the traditional Kangxi glyph form?
Noto CJK KR is the most similar to it, but still differs in details.

This style is known as "旧字形 (old glyph form)" in mainland China. In Taiwan, it is called "傳統字形(traditional glyph form)". In Japan, it is called "旧字体(old glyph form)".

[ghost]

https://en.wikipedia.org/wiki/Jiu_zixing
https://en.wikipedia.org/wiki/Ky%C5%ABjitai

[ghost]

In Noto CJK KR, the vertical line of "告" does not protrude downward. On the other hand, in the traditional glyph form, it sticks out below.
https://www.zdic.net/hans/%E5%91%8A
https://img.zdic.net/kxzd/543F.svg

[ghost]

Umm...🤔
adobe-fonts/source-han-sans#6

[NightFurySL2001]

There was suggestion to introduce traditional orthography which had faced huge backlash. A more complete reference of traditional printing orthography/jiu zixing/inherited forms can be found on https://github.com/ichitenfont/inheritedglyphs/ which is a compilation of the best suggested orthography for modern usage.

[ghost]

I am not advocating for replacement. I am arguing for the addition of a new form. It's good to have more options.

[NightFurySL2001]

I believe adobe-fonts/source-han-sans#6 did not advocate for replacement, quote from original comment:

我不反對有台灣人想用台灣敎育部的寫法，但也應還其他Traditional Chinese使用者，使用眞正Tradition寫法的空間，分拆開「Taiwan」和「Traditional」兩體。而不是強迫其他正體使用者依從台灣那種以楷扭曲黑的寫法。

Translate:

I have no objection to Taiwanese who want to use the Taiwan MOE orthography, but [Source Han Sans] should also allow other Traditional Chinese users the space to use the Traditional orthography, and separate "Taiwan" and "Traditional", instead of forcing other traditional users to follow the Taiwan [MOE] way of distorting sans form with regular script form.

[tamcy]

I am arguing for the addition of a new form. It's good to have more options.

This was answered in the adobe-fonts/source-han-sans#6 issue. Scroll to the bottom to see the last message:

The substantial enhancements to the glyph repertoire of Source Han Sans as discussed in this thread are, unfortunately, beyond the scope of Adobe's current plans and capacity to investigate further. If we are able to revisit this in the future, we will reopen investigation into what would constitute an appropriate set of glyphs.

Also in #1 of this repo:

I'm closing this issue as it seems out of scope for this project. Feel free to rename and fork the project to organize development in that direction if you wish :)

[MY1L]

如果仅康熙部首区段使用康熙字形呢？这个应该很合理，统一码也有字形规范可参考：Kangxi Radicals

[tamcy]

如果仅康熙部首区段使用康熙字形呢？这个应该很合理，统一码也有字形规范可参考：Kangxi Radicals

The glyphs in this document are typesetted with CJK Radicals, a font derived from Source Han Serif/Noto Serif CJK.

文件中的參考字形是來自 CJK Radicals, 一款 Noto Serif CJK/思源宋體 的衍生字型。

[MY1L]

@tamcy 其实上面这个PDF，我先前已获知使用的字体了，并不是为了这个，而是，
实际上，我因为思源黑的康熙部首区段写法与康熙字典不符，困扰好久了。甚至为康熙部首区段专门画了一个黑体字形。是这样的。

[NightFurySL2001]

The main thread of this discussion focus on the CJK Unified Ideographs for Traditional Chinese, which the Taiwan region (mislabelled as TC in Noto) is not the de facto form used in Traditional Chinese communities. A region-agnostic form like Kangxi Dictionary or jiu zixing is better for Noto Sans TC, and moving the current mislabelled TC to Noto Sans TW.

The issue raised by @/MY1L about Kangxi Radicals block is a valid point too, but might face some issue as the Source Han/Noto Sans CJK replaces the orthography of Kangxi Radicals in locl too, meaning JP/KR/CN/TW/HK have their "standard" locale applied to the Kangxi Radicals block. Fixing all regions to use the same Kangxi Dictionary form is a good idea, but the CN locale will not be following requirements set by GB 18030 (especially the new -2022 version includes this block in Level 3 implementation).

Note that the repo here doesn't attract much discussion and suggestion by @/MY1L should be done with a new issue in https://github.com/adobe-fonts/source-han-sans .

[Marcus98T]

I'll repeat this here. This request will never be possible in the main branches of the Source Han/Noto CJK projects, unless there's new font technology which removes the 65K glyph limit, but even then that may be too much headache for all of us, because we have to get operating systems to support such technology if it ever exists, and then deal with the frustrations of having to upgrade the operating systems when some of us refuse to upgrade for various reasons. Or simply, this project is just an edge case of reaching the 65K glyph limit whereas 98% of all fonts won't ever need to reach that limit.

I can only hope that Adobe release all the unreleased JP overlapping sources that never made it to v1, along with detailed instructions on how to compile your own custom fork simply by adding, editing and removing glyphs, so that such a fork will become a reality.

Finally, I don't know if Google will close this issue as not planned, or keep it open so that Adobe can solve it with this aforementioned request of releasing all the overlapping sources that were never included in the main font, then it can be closed as completed.