Out-of-scope remap suggestions for JP/KR to follow faux-traditional forms by using TW/HK glyphs instead of CN glyphs

[Marcus98T]

I know there’s an existing issue regarding this, but this issue is more than just requesting to use HK glyphs for JP, KR and CN, for which they only have a TW/HK glyph.

I’ve perused through the issues on the forks of Source Han Sans/Serif focusing on traditional orthography for Chinese (sometimes termed Inherited Glyphs, which I do mention in the tables for reference), and I have quite a lot of out-of-scope characters to suggest that they should at least follow the faux-traditional orthography of JP/KR by using TW/HK glyphs, which can look closer to the old traditional forms than CN glyphs.

I know that some characters may have radicals (e.g. 火) or components (e.g. 虍) which can look jarring for JP/KR because of the relatively ugly handwriting nature of the TW/HK glyphs, but unfortunately, because there is not enough glyph space, and that some characters only show TW/HK forms, I think there is no choice but to have those TW/HK components for JP/KR anyway because it’s more important that certain components follow hyōgaiji rules for Japan (and also follow the Korean K2 Unicode reference more closely) rather than to plainly use CN glyphs as a fallback (which can deviate from the so-called Kangxi forms). I even checked against v1 JP glyphs in Serif to make sure they are closely matched.

That is about most of the characters I could find in existence, however, I have not had the time to check component for component. I might add more characters in future edits to this issue page.

Also applies to Serif, which will have a separate set of tables soon.

However, I will like to note that there could have been unreleased/removed JP glyphs (those within Adobe-Japan1 designed by Adobe in-house, the extras designed by Iwata) for which they could have been safely used for TW/HK, instead of using TW/HK glyphs designed by Changzhou Sinotype (and later Arphic) as they are now. This I will also note in the tables.

And this issue does not take into account any possible major redesign of Sans, which means component merging, either by having JP and KR follow CN forms, or CN, TW and HK glyphs follow JP forms (which I prefer). If either scenario happens, then part of the tables may be invalid.

List of characters that would benefit from remapping

Unicode	Character	Current Mapping (JP)	Current Mapping (KR)	Remap to	Notes	(Reference only) Is there a JP glyph in Serif (removed v1 glyphs or otherwise) for which an unreleased JP Sans glyph could have been safely used for TW/HK?
U+3597	㖗	CN	CN	HK
U+361A	㘚	CN	CN	HK
U+4B90	䮐	CN	CN	HK
U+4F62	佢	CN	CN	TW	See this issue on Serif, also Serif is using the TW forms for JP and KR
U+505D	偝	TW	TW	HK	In issue #443
U+50CB	僋	CN	CN	TW	Serif is using the TW forms for JP and KR	Yes, but the 人 component is different in Sans.
U+50E0	僠	TW	TW	HK	In issue #443
U+51B9	冹	CN	CN	TW	Serif is using the TW forms for JP and KR
U+537C	卼	CN	CN	TW	Serif is using the TW forms for JP and KR
U+539E	厞	CN	CN	TW		Yes, could have been used for TW/HK.
U+5526	唦	CN	CN	HK
U+555F	啟	CN	CN	TW	In issue #458	Yes, but the 戶 component is different in Sans.
U+55D6	嗖	CN	CN	TW
U+580E	堎	CN	CN	HK
U+5814	堔	CN	CN	TW
U+5863	塣	CN	CN	TW		Yes, could have been used for TW/HK.
U+58CF	壏	CN	CN	TW		Yes, could have been used for TW/HK.
U+58FE	壾	CN	CN	TW	See this issue on Serif	Yes, could have been used for TW/HK.
U+5DB5	嶵	CN	CN	TW
U+5DB6	嶶	CN	CN	HK
U+5F05	弅	CN	CN	TW	In issue #414	Yes, could have been used for TW.
U+609C	悜	CN	CN	TW		Yes, could have been used for TW/HK.
U+60FE	惾	CN	CN	HK
U+618C	憌	CN	CN	TW		Yes, but the 金 component is different in Sans.
U+623A	戺	CN	CN	TW	Related to issue #458	Yes, but the 戶 component is different in Sans.
U+6331	挱	CN	CN	HK		Yes, could have been used for HK.
U+63D9	揙	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+63DD	揝	JP	JP	TW (KR only?)	The JP glyph is out-of-scope (not in Adobe-Japan1). Seems like the traditional forms prefer that the top part of the 昝 component is ⿺夂人 rather than ⿺夂卜, but the JP glyph shows ⿺夂卜 which is closer to the shape found in the Kangxi Dictionary. However, the Unicode Korean K2 reference shows ⿺夂人, so remap only for KR?
U+6718	朘	CN	CN	HK
U+6779	杹	TW	TW	HK	In issue #443
U+6820	栠	TW	TW	HK	In issue #443
U+68CE	棎	CN	CN	TW
U+6944	楄	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+6997	榗	CN	CN	TW
U+6A8C	檌	CN	CN	TW		Yes, could have been used for TW/HK.
U+6A93	檓	CN	CN	TW
U+6AA8	檨	CN	CN	TW		Yes, could have been used for TW/HK, because it seems the 欠 component is joined at the bottom right for both CN and TW glyphs.
U+6B76	歶	TW	TW	HK	In issue #443
U+6C8E	沎	TW	TW	HK	In issue #443
U+6E9E	溞	CN	CN	TW		Yes, could have been used for TW/HK.
U+6EA6	溦	CN	CN	TW
U+6EBE	溾	CN	CN	TW
U+6FBF	澿	TW	TW	HK	In issue #443 and #368, also Serif is using the HK forms for JP and KR and CN
U+7029	瀩	CN	CN	TW	Serif is using the TW forms for JP and KR
U+7128	焨	TW	TW	HK	In issue #443
U+715F	煟	TW	TW	HK	In issue #443, and also see this issue in Serif
U+7181	熁	TW	TW	HK	In issue #443
U+7182	熂	TW	TW	HK	In issue #443
U+7203	爃	TW	TW	HK	In issue #443
U+752E	甮	CN	CN	HK	Unsure for JP. The Unicode Korean K2 reference shows a form closer to HK.
U+7705	眅	CN	CN	TW		Yes, could have been used for TW.
U+7743	睃	CN	CN	HK
U+7759	睙	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+7828	砨	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+78A5	碥	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+7A04	稄	CN	CN	HK
U+7A28	稨	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+7A68	穨	CN	CN	TW
U+7BFB	篻	TW	TW	HK	In issue #443
U+7CD0	糐	TW	TW	HK	In issue #443
U+7F92	羒	CN	CN	TW	In issue #414
U+7FA7	羧	CN	CN	HK
U+801B	耛	CN	CN	TW	Serif is using the TW forms for JP and KR
U+8029	耩	CN	CN	TW	Serif is using the TW forms for JP and KR
U+815C	腜	TW	TW	HK	In issue #443
U+8215	舕	TW	TW	HK	In issue #443
U+86C2	蛂	CN	CN	TW		Yes, could have been used for TW/HK.
U+8727	蜧	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+8746	蝆	CN	CN	TW?	Unsure, seems like the v1 JP glyph in Serif showed ⿰虫𦬒 (as appeared in Guangyun (廣韻)), however, a similar variant exists as U+45B9 (䖹), but with the 卝 component on the top right rather than 艹.
U+876C	蝬	CN	CN	HK
U+8779	蝹	CN	CN	TW	Serif is using the TW forms for JP and KR
U+87A5	螥	CN	CN	HK		Yes, but the 人 component is different in Sans.
U+87A9	螩	CN	CN	HK
U+87B6	螶	CN	CN	TW	See this issue on Serif
U+89B9	覹	CN	CN	TW	Serif is using the TW forms for JP and KR
U+89D3	觓	CN	CN	TW	Serif is using the TW forms for JP and KR
U+8AF2	諲	CN	TW	TW (JP only)	The JP glyph in Serif is similar to the TW glyph in Sans (right side only), so might as well remap to TW for JP.
U+8C43	豃	CN	TW	TW (JP only)		Yes, but the 人 component is different in Sans.
U+8C5F	豟	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+8C71	豱	CN	CN	TW	Serif is using the TW forms for JP and KR
U+8C7D	豽	CN	CN	TW	Serif is using the TW forms for JP and KR	Yes, could have been used for TW/HK.
U+8CBE	貾	CN	CN	TW	Serif is using the TW forms for JP and KR
U+8DBF	趿	CN	TW	TW (JP only)		Yes, could have been used for TW.
U+8E02	踂	CN	CN	TW	Serif is using the TW forms for JP and KR
U+8E1C	踜	CN	CN	HK
U+8EB9	躹	CN	CN	HK		Yes, could have been used for TW/HK.
U+8EE1	軡	CN	CN	TW	Serif is using the TW forms for JP and KR	Yes, but the 今 component is different in Sans.
U+8EE7	軧	CN	CN	TW	Serif is using the TW forms for JP and KR
U+8EF6	軶	CN	TW	TW (JP only)		Yes, but the 戶 component is different in Sans.
U+910B	鄋	CN	CN	TW
U+9111	鄑	CN	CN	TW	Serif is using the TW forms for JP and KR
U+9287	銇	CN	CN	TW		Yes, but the 金 component is different in Sans.
U+9313	錓	CN	CN	TW		Yes, but the 金 component is different in Sans.
U+9389	鎉	CN	TW	TW (JP only)
U+93AA	鎪	CN	CN	TW		Yes, probably, but the 金 component is different in Sans.
U+93CF	鏏	CN	CN	TW	Serif is using the TW forms for JP and KR	Yes, but the 金 component is different in Sans.
U+95B7	閷	CN	CN	TW
U+966B	陫	CN	CN	TW		Yes, could have been used for TW/HK.
U+981B	頛	CN	CN	TW		Yes, could have been used for TW/HK.
U+985D	顝	TW	TW	HK	Serif is using the HK forms for JP and KR	Yes, could have been used for HK.
U+99A7	馧	CN	CN	TW		Yes, could have been used for TW.
U+99CF	駏	CN	CN	TW	See this issue on Serif
U+9A48	驈	CN	CN	TW	Serif is using the TW forms for JP and KR	Yes, probably could have been used for TW/HK.
U+9A68	驨	CN	CN	TW	Serif is using the TW forms for JP and KR
U+9AAB	骫	TW	TW	HK	Serif is using the HK forms for JP and KR	Yes, could have been used for HK.
U+9AB1	骱	CN	CN	HK	Serif is using the HK forms for JP and KR	Yes, but the 人 component is different in Sans.
U+9AB3	骳	TW	TW	HK	Serif is using the HK forms for JP and KR	Yes, could have been used for HK.
U+9ABA	骺	CN	CN	HK		Yes, could have been used for HK.
U+9AC7	髇	CN	CN	HK
U+9ACA	髊	TW	TW	HK		Yes, could have been used for HK.
U+9ACD	髍	CN	CN	HK	While TW 麻 is closer to traditional forms, the 骨 radical looks jarring. HK would look better for stability.
U+9B3E	鬾	CN	CN	TW
U+9B3F	鬿	CN	CN	TW
U+9B40	魀	CN	CN	HK
U+9B4A	魊	CN	CN	TW
U+9B59	魙	CN	CN	TW	Serif is using the TW forms for JP and KR
U+9BDE	鯞	CN	TW	TW (JP only)	Serif is using the TW forms for JP and KR
U+9BE6	鯦	CN	CN	TW	Serif is using the TW forms for JP and KR
U+9D5A	鵚	CN	CN	TW	Serif is using the TW forms for JP and KR
U+9DA3	鶣	CN	CN	TW		Yes, but the 戶 component is different in Sans.
U+9DEC	鷬	CN	CN	HK	Serif is using the HK forms for JP and KR	Yes, could have been used for HK.
U+9EB1	麱	CN	CN	HK?	Seems like the JP glyph in Serif is close to the CN form in Sans. Turns out the JP glyph does not normally use the ⿺ composition for the 麥 radical for 麱 (U+9EB1), instead choosing to use the ⿰ composition as seen in the Kangxi Dictionary. KIV for now.
U+9EC7	黇	CN	CN	HK		Yes, could have been used for HK.
U+9EE2	黢	CN	CN	HK
U+9EEB	黫	CN	CN	TW
U+9F74	齴	CN	CN	TW	Serif is using the TW forms for JP and KR

List of characters that would show TW/HK educational forms inappropriate for JP/KR traditional forms after remapping

Unicode	Character	Current Mapping (JP)	Current Mapping (KR)	Remap to	Notes about the Taiwan Ministry of Education (MOE)/HK Educational forms that are incompatible with traditional orthography	Why remap anyway?
U+3D32	㴲	CN	CN	HK	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+44DF	䓟	CN	CN	HK (JP only)	The split 艹 component, while acknowledged in Inherited Glyphs, is not normally seen in Japanese and Korean fonts, instead preferring 艹.	Japanese traditional forms usually have the upper-middle component connect with the lower-middle 口 component.
U+4504	䔄	CN	CN	HK	The split 艹 component, while acknowledged in Inherited Glyphs, is not normally seen in Japanese and Korean fonts, instead preferring 艹.	Traditional forms usually go for ⿱𱼀缶, not ⿱爫缶 as per PRC conventions.
U+4561	䕡	CN	HK	HK (JP only)	The split 艹 component, while acknowledged in Inherited Glyphs, is not normally seen in Japanese and Korean fonts, instead preferring 艹.	It's better to show 呂 rather than simplified 吕 for traditional forms. Also, if the KR locale has the HK glyph, then JP should also remap to the HK glyph.
U+4B19	䬙	CN	CN	HK	There is a horizontal stroke rather than a left throw stroke in 風. While Inherited Glyphs recommend the horizontal stroke, Japanese and Korean fonts prefer the left throw stroke.	Traditional forms usually go for ⿱𱼀缶, not ⿱爫缶 as per PRC conventions.
U+5061	偡	CN	CN	TW	The bottom 匸 component is ⿱一㇄ rather than ⿱一𠃊 preferred by Japanese and Korean fonts.	It's better to have 儿 rather than 八 in the bottom of the 甚 component for traditional forms.
U+595C	奜	CN	TW	TW (JP only)	The bottom 大 component is a drop stroke rather than a throw.	It's better to have the top 非 component follow the faux-traditional orthography. Also, if the KR locale has the TW glyph, then JP should also remap to the TW glyph.
U+5AF9	嫹	CN	CN	HK	The left 女 radical looks jarring.	It's better to have traditional 黃 rather than simplified 黄 as preferred in PRC conventions.
U+5CFC	峼	CN	CN	HK (JP only)	The 牛 touches the 口 in 吿 (referring to HK educational forms), whereas Japanese kyūjitai forms do not have two parts touch.	It's better to show 吿 rather than 告 for Japanese traditional forms. Does not apply to the KR locale.
U+640B	搋	CN	CN	TW	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+64D9	擙	CN	CN	HK	The bottom-right 大 component is a drop stroke rather than a throw.	It's better to show 奧 for traditional forms rather than the simplified 奥 as per PRC conventions.
U+64E8	擨	CN	CN	TW	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+6825	栥	CN	CN	TW	The bottom 木 component is showing ホ. Also, slight difference in the way 次 is being written between TW and KR forms. On the left side, TW has a straight 二, while the second stroke in KR is a pickup stroke.	It's still better for 次 to follow traditional forms of ⿰二欠 rather than ⿰冫欠 as per PRC conventions.
U+6902	椂	CN	CN	HK	The way 氺 in 彔 is being written. In Japanese and Korean fonts, it ends with a throw stroke, not a drop stroke.	It's better to show 彔 rather than simplified 录 for traditional forms.
U+6976	楶	CN	CN	TW	The bottom 木 component is showing ホ. Also, slight difference in the way 次 is being written between TW and KR forms. On the left side, TW has a straight 二, while the second stroke in KR is a pickup stroke.	It's still better for 次 to follow traditional forms of ⿰二欠 rather than ⿰冫欠 as per PRC conventions.
U+69B9	榹	CN	CN	TW	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+6C2F	氯	CN	CN	TW	The way 氺 in 彔 is being written. In Japanese and Korean fonts, it ends with a throw stroke, not a drop stroke.	It's better to show 彔 rather than simplified 录 for traditional forms.
U+718E	熎	CN	CN	HK	The left 火 radical looks jarring.	Traditional forms usually go for ⿱𱼀缶, not ⿱爫缶 as per PRC conventions.
U+7769	睩	CN	CN	TW	The way 氺 in 彔 is being written. In Japanese and Korean fonts, it ends with a throw stroke, not a drop stroke.	It's better to show 彔 rather than simplified 录 for traditional forms.
U+7BCE	篎	CN	CN	HK	The disconnected ⺮ component, however, it might be unified in the next major version as per issue #398	The 少 component must have a hook as per traditional forms.
U+7BEB	篫	CN	CN	TW	The disconnected ⺮ component, however, it might be unified in the next major version as per issue #398	Traditional forms usually go for ⿰工卂, not ⿰工凡 as per PRC conventions.
U+7BEC	篬	CN	CN	HK	The disconnected ⺮ component, however, it might be unified in the next major version as per issue #398	It's better to show 亼 rather than 亽 for the 倉 component for traditional forms.
U+7C05	簅	CN	CN	TW	The disconnected ⺮ component, however, it might be unified in the next major version as per issue #398	It's better to have tradtional 產 rather than simplified 産 (which is actually Japanese shinjitai) as per PRC conventions.
U+7C48	籈	CN	CN	TW	The disconnected ⺮ component, however, it might be unified in the next major version as per issue #398	Traditional forms usually show ⿱西土 rather than ⿱覀土 for the 垔 component.
U+8623	蘣	CN	CN	HK	The split 艹 component, while acknowledged in Inherited Glyphs, is not normally seen in Japanese and Korean fonts, instead preferring 艹.	It's better to have traditional 黃 rather than simplified 黄 as preferred in PRC conventions.
U+8628	蘨	CN	CN	HK	The split 艹 component, while acknowledged in Inherited Glyphs, is not normally seen in Japanese and Korean fonts, instead preferring 艹. Also note the unbalanced 系 component.	Traditional forms usually go for ⿱𱼀缶, not ⿱爫缶 as per PRC conventions.
U+8633	蘳	CN	CN	HK	The split 艹 component, while acknowledged in Inherited Glyphs, is not normally seen in Japanese and Korean fonts, instead preferring 艹.	It's better to have traditional 黃 rather than simplified 黄 as preferred in PRC conventions.
U+8742	蝂	CN	CN	TW	The 片 component, rendered as ⿰丿⿱𠃎𠃍  in the Taiwan MOE forms rather than the ⿰丿⿱丄𠃍 preferred by Japanese and Korean fonts.	It's better to show ⿸厂又 rather than ⿸𠂆又 for traditional forms.
U+8794	螔	CN	CN	TW	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+8800	蠀	CN	CN	TW	Slight difference in the way 次 is being written between TW and KR forms. On the left side, TW has a straight 二, while the second stroke in KR is a pickup stroke.	It's better for 次 to follow traditional forms of ⿰二欠 rather than ⿰冫欠 as per PRC conventions.
U+89A4	覤	CN	CN	TW	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+8D19	贙	CN	CN	TW	The lack of a hook in the middle 七 part of the 虎 component.	It's better to have 儿 for the bottom part rather than 几 for the 虎 component for traditional forms.
U+9199	醙	CN	CN	TW	The bottom inner horizontal stroke is disconnected from the enclosure in the left 酉 radical.	Traditional forms prefer a disconnected 臼 component in 叟.
U+942D	鐭	CN	CN	HK	The bottom-right 大 component is a drop stroke rather than a throw.	It's better to show 奧 for traditional forms rather than the simplified 奥 as per PRC conventions.
U+9C4B	鱋	CN	CN	TW	The lack of a hook in the middle 七 part of the 虛 component.	Traditional forms prefer 虛 rather than simplified 虚 as per PRC conventions.
U+9F2D	鼭	CN	CN	HK	Japanese standards are inconsistent in their dealing with the 鼠 component, most of the time it's ⿱臼⿲𠄌⺀⿲𠄌⺀㇂, but sometimes it's ⿱臼⿲𠄌二⿲𠄌二㇂. Taiwan MOE forms, however, prefer ⿱臼⿲𠄌二⿲𠄌二㇂.	Traditional forms prefer a ⿺ composition for the 鼠 component rather than the ⿰ composition as per PRC conventions.

Miscellaneous remappings from other issues

夗 although kind of out of scope, can map the TW glyph to JP/KR for the 夕 component.

Originally posted by @/NightFurySL2001 in #443 (comment)

---

As far as I know, there are two characters currently using TW/HK forms in Sans for JP and KR, 觺 (U+89FA) and 觾 (U+89FE), for which a separate CN glyph exists for both.

Because of this, we should remap more glyphs to TW/HK forms for JP and KR, so as to make them look a bit closer to traditional forms.