adobe-fonts / adobe-fonts/source-han-sans
Some CN glyphs are showing inappropriate JP forms for GB 18030
- 主要语言
- Python
- 星标
- 17.2k
- 派生
- 1.4k
- PR 合并指标
- 30 天内没有已合并 PR
描述
As a supplement to [this two-year-old issue about some CN glyphs having only TW/HK forms](https://github.com/adobe-fonts/source-han-sans/issues/313), I found out that several GB18030 hanzi are showing only Japanese traditional print forms which are inappropriate for CN use. All of them listed had v1 CN glyphs, although some of them might not need to be restored if merging of components like 人 and 子 favours JP forms in the next release.
Yes, [I raised the issue before briefly](https://github.com/adobe-fonts/source-han-sans/issues/412), and it's mentioned before that GB 18030 does not define glyph standards, but it will be jarring to see what Mainland Chinese users will find as inappropriate traditional print forms (alongside Taiwan Ministry of Education forms) for rare/occasional use Chinese characters, especially if they're on a device that has Source Han Sans/Noto Sans CJK as the only UI font and cannot install custom fonts to replace the default UI font (at least without a difficult and hacky workaround).
This is due to the 65,535 glyph limit and the practicality of having to restrict the scope of PRC glyph conventions to only basic Simplified/Traditional characters as defined in the G0-G8 GB standards according to Unicode, and the Table of General Standard Chinese Characters (通用规范汉字表, Tongyong), with extra CN-style characters for other rare/occasional use characters if there's space. But if we still cannot fit them all even after merging the non-essential regional components, might as well limit the PRC glyph scope to only G0-G8 (roughly), forget about GE and have thousands of unreleased JP glyphs to replace all CN glyphs that are not part of G0-G8, but obviously this means a lot more glyphs will no longer follow PRC glyph conventions and it might raise more complaints from mainland Chinese users, so it's not going to happen either.
Granted about 95% of them are GE sources (GB Extension, which means rare characters not reflecting real world usage), but a few of them are within the basic Chinese standards which means CN glyphs absolutely must be restored or new ones created, with the highest priority. This will be noted in the tables if I decide the v1 CN glyph must be restored.
The following tables are mostly correct as of version 2.004 and they are for reference only. I might have to do this again for the next version whenever it comes.
The tables contain all the removed CN glyphs [as documented in this issue](https://github.com/adobe-fonts/source-han-sans/issues/259#issuecomment-891759931) (may not be entirely accurate due to some glyph renaming, etc.), and are sorted according to Japanese JIS Levels 1-4, with the rest on another table. About half of them need not be restored because they are practically identical to the JP glyphs.
Also applies to Serif, which can be seen [here](https://github.com/adobe-fonts/source-han-serif/issues/202).
## JIS Level 1
Unicode | Character | GB Source | Restore v1 CN glyph? | Comments
-- | -- | -- | -- | --
U+4E38 | 丸 | | No |
U+4E5D | 九 | | No |
U+4E7E | 乾 | | No |
U+4E80 | 亀 | | No |
U+4E98 | 亘 | | No |
U+4E9C | 亜 | GB Extension | Depends | This is regarding the feet removal issue at #293.
U+4F34 | 伴 | | No |
U+4F38 | 伸 | | No |
U+4F50 | 佐 | | No |
U+501F | 借 | | No |
U+5024 | 値 | GB Extension | Yes |
U+5039 | 倹 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+5149 | 光 | | No |
U+514E | 兎 | | No |
U+5177 | 具 | | No |
U+51CB | 凋 | | No |
U+51DD | 凝 | | No |
U+51F8 | 凸 | | No |
U+51F9 | 凹 | | No |
U+5203 | 刃 | | No |
U+5229 | 利 | | No |
U+5237 | 刷 | | No |
U+523A | 刺 | | No |
U+5263 | 剣 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+52A0 | 加 | | No |
U+52C9 | 勉 | | No |
U+52E4 | 勤 | | No |
U+5351 | 卑 | | No |
U+535A | 博 | | No |
U+5371 | 危 | | No |
U+53E9 | 叩 | | No |
U+53F6 | 叶 | | No |
U+5420 | 吠 | | No |
U+5448 | 呈 | | No |
U+5449 | 呉 | GB Extension | Depends | This is regarding the feet removal issue at #293.
U+5606 | 嘆 | | No |
U+5642 | 噂 | | No |
U+565B | 噛 | GB Extension | Yes |
U+5668 | 器 | | No |
U+570F | 圏 | GB Extension | Yes |
U+5766 | 坦 | | No |
U+57A3 | 垣 | | No |
U+5835 | 堵 | | No |
U+5841 | 塁 | | No |
U+5869 | 塩 | | No |
U+5897 | 増 | GB Extension | Depends | The strokes are not very obvious. So that will depend on the merging of the 丷 components to the JP forms.
U+58A8 | 墨 | | No |
U+58EE | 壮 | | No |
U+5A2F | 娯 | GB Extension | Yes |
U+5C3B | 尻 | | No |
U+5C4A | 届 | | No |
U+5C60 | 屠 | | No |
U+5CE0 | 峠 | GB Extension | Yes |
U+5D16 | 崖 | | No |
U+5DFB | 巻 | GB Extension | Yes |
U+5DFD | 巽 | | No |
U+5E30 | 帰 | GB Extension | No | Related issue: #374 (see section Remapping of 帰 (U+5E30)). The v1 CN glyph is structurally identical to the v2 JP variant glyph.
U+5E3D | 帽 | | No |
U+5E4C | 幌 | | No |
U+5E55 | 幕 | | No |
U+5F3E | 弾 | GB Extension | Yes |
U+5FA1 | 御 | | No |
U+5FB3 | 徳 | GB Extension | Yes |
U+60A9 | 悩 | GB Extension | Yes, and adjust | The v1 CN glyph has a problem with the bottom part being slanted, see [this comment on another unrelated issue](https://github.com/adobe-fonts/source-han-sans/issues/361#issuecomment-1448374732).
U+60AA | 悪 | | No |
U+6163 | 慣 | | No |
U+621A | 戚 | | No |
U+62B1 | 抱 | | No |
U+62D0 | 拐 | | No |
U+62E0 | 拠 | | No |
U+63FA | 揺 | GB Extension | Yes |
U+656C | 敬 | | No |
U+65ED | 旭 | | No |
U+660E | 明 | | No |
U+6643 | 晃 | | No |
U+66F3 | 曳 | | No |
U+671D | 朝 | | No |
U+673A | 机 | | No |
U+6751 | 村 | | No |
U+676F | 杯 | G0, GB 2312 | Adjust JP glyph instead | See issue #308.
U+67FE | 柾 | | No |
U+683C | 格 | | No |
U+683D | 栽 | | No |
U+685C | 桜 | GB Extension | Yes |
U+68EE | 森 | | No |
U+691C | 検 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+697D | 楽 | | No |
U+69D8 | 様 | GB Extension | Probably no | Slightly different strokes at the bottom right of the v1 CN glyph, probably not an issue.
U+69FB | 槻 | | No |
U+69FD | 槽 | | No |
U+6A2A | 横 | | No |
U+6A3D | 樽 | | No |
U+6B69 | 歩 | GB Extension | Yes |
U+6BCE | 毎 | GB Extension | Yes |
U+6CC9 | 泉 | | No |
U+6CE1 | 泡 | | No |
U+6D1B | 洛 | | No |
U+6DAF | 涯 | | No |
U+6DEB | 淫 | | No |
U+6DFB | 添 | | No |
U+6E09 | 渉 | GB Extension | Yes |
U+6E20 | 渠 | | No |
U+6E2F | 港 | | No |
U+6E80 | 満 | GB Extension | Yes |
U+6F22 | 漢 | | No |
U+6F5C | 潜 | | No |
U+701E | 瀞 | | No |
U+7026 | 瀦 | | No |
U+7114 | 焔 | | No |
U+724C | 牌 | | No |
U+731F | 猟 | | No |
U+73ED | 班 | | No |
U+7433 | 琳 | | No |
U+7554 | 畔 | | No |
U+7565 | 略 | | No |
U+756A | 番 | | No |
U+77A5 | 瞥 | | No |
U+7832 | 砲 | | No |
U+7872 | 硲 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+7891 | 碑 | | No |
U+79A6 | 禦 | | No |
U+79E4 | 秤 | | No |
U+7A0B | 程 | | No |
U+7A17 | 稗 | | No |
U+7A3D | 稽 | | No |
U+7A42 | 穂 | | No |
U+7B95 | 箕 | | No |
U+7BB8 | 箸 | | No |
U+7C82 | 粂 | GB Extension | Yes |
U+7F6B | 罫 | | No |
U+7FA4 | 群 | | No | v1 CN looks identical to the JP glyph, so it was an exact duplicate glyph that was removed in v2.
U+8036 | 耶 | | No |
U+8074 | 聴 | GB Extension | Yes |
U+80BA | 肺 | | No |
U+80DE | 胞 | | No |
U+8133 | 脳 | GB Extension | Yes, and adjust | The v1 CN glyph has a problem with the bottom part being slanted, see [this comment on another unrelated issue](https://github.com/adobe-fonts/source-han-sans/issues/361#issuecomment-1448374732).
U+817A | 腺 | | No |
U+81D3 | 臓 | GB Extension | Yes |
U+820E | 舎 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+8217 | 舗 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+8304 | 茄 | | No |
U+831C | 茜 | | No |
U+8358 | 荘 | | No |
U+8461 | 葡 | | No |
U+84B2 | 蒲 | | No |
U+8511 | 蔑 | | No |
U+853D | 蔽 | | No |
U+85AF | 薯 | | No |
U+86FE | 蛾 | | No |
U+898F | 規 | | No |
U+8CCA | 賊 | | No |
U+8CCE | 賎 | | No |
U+8CED | 賭 | | No |
U+8D77 | 起 | G0, GB 2312 | No | I would rather remove the feet from the JP glyph as per issue #293.
U+8ECD | 軍 | | No |
U+8F09 | 載 | | No |
U+916A | 酪 | | No |
U+9192 | 醒 | | No |
U+91A4 | 醤 | | No |
U+92AD | 銭 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+967A | 険 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+9686 | 隆 | | No |
U+96B7 | 隷 | | No |
U+96EA | 雪 | | No |
U+96F7 | 雷 | | No |
U+9759 | 静 | | No |
U+976D | 靭 | | No |
U+981A | 頚 | GB Extension | Yes |
U+99C1 | 駁 | | No |
U+99C5 | 駅 | | No |
U+99C6 | 駆 | GB Extension | Yes |
U+99C8 | 駈 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+99D2 | 駒 | | No |
U+9A12 | 騒 | | No |
U+9A13 | 験 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+9A28 | 騨 | | No |
U+9A5A | 驚 | | No |
U+9C52 | 鱒 | | No |
U+9CF6 | 鳶 | | No |
U+9D0E | 鴎 | GB Extension | Yes |
U+9D60 | 鵠 | | No |
U+9E78 | 鹸 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+9EDB | 黛 | | No |
## JIS Level 2
Unicode | Character | GB Source | Restore v1 CN glyph? | Comments
-- | -- | -- | -- | --
U+4E17 | 丗 | | No |
U+4E55 | 乕 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+4E62 | 乢 | GB Extension | Yes |
U+4FFE | 俾 | | No |
U+5056 | 偖 | | No |
U+50D6 | 僖 | | No |
U+5116 | 儖 | GB Extension | Yes |
U+51A4 | 冤 | | No |
U+51A9 | 冩 | GB Extension | Depends | If merging of the 臼 component favours JP forms, no need to restore.
U+51AA | 冪 | | No |
U+51B2 | 冲 | | No |
U+51B5 | 况 | | No |
U+51C5 | 凅 | | No |
U+51E9 | 凩 | GB Extension | Yes |
U+5271 | 剱 | GB Extension | Yes, and adjust if possible | In v1 CN, the right side follows 刃, not 刄. But because of a possible component merger for the 人 component in the left side, restore and adjust the left side to keep JP forms.
U+5292 | 劒 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+5306 | 匆 | | No |
U+54AF | 咯 | | No |
U+54E2 | 哢 | | No |
U+5540 | 啀 | | No |
U+5556 | 啖 | | No |
U+5632 | 嘲 | | No |
U+56A0 | 嚠 | GB Extension | Yes | Also in issue #374, under the section Missing Glyphs.
U+5738 | 圸 | GB Extension | Yes |
U+574F | 坏 | G0, GB 2312 | Adjust JP glyph instead | See issue #308.
U+57D3 | 埓 | | No |
U+57D6 | 埖 | | No |
U+583D | 堽 | | No |
U+5870 | 塰 | GB Extension | Yes |
U+58EF | 壯 | | No |
U+5918 | 夘 | GB Extension | Depends | If merging of the 夕 component favours JP forms, no need to restore.
U+591B | 夛 | GB Extension | Depends | If merging of the 夕 component favours JP forms, no need to restore.
U+594E | 奎 | | No |
U+5962 | 奢 | | No |
U+599B | 妛 | GB Extension | Yes |
U+5AD0 | 嫐 | GB Extension | Yes |
U+5B36 | 嬶 | GB Extension | Yes |
U+5E36 | 帶 | | No |
U+5F09 | 弉 | GB Extension | Depends | This is regarding the feet removal issue at #293. Also see [this comment](https://github.com/adobe-fonts/source-han-sans/issues/421#issuecomment-1558458021).
U+5F16 | 弖 | GB Extension | Yes |
U+5F41 | 彁 | GB Extension | Yes |
U+5F99 | 徙 | | No |
U+5FDD | 忝 | | No |
U+5FE4 | 忤 | | No |
U+5FF1 | 忱 | | No |
U+6042 | 恂 | | No |
U+606A | 恪 | | No |
U+60F1 | 惱 | | No |
U+613C | 愼 | | No |
U+615F | 慟 | | No |
U+625E | 扞 | | No |
U+6289 | 抉 | | No |
U+62CC | 拌 | | No |
U+62D4 | 拔 | | No |
U+63A3 | 掣 | | No |
U+63B5 | 掵 | GB Extension | Yes |
U+6500 | 攀 | | No |
U+6538 | 攸 | | No |
U+655E | 敞 | | No |
U+6746 | 杆 | | No |
U+6763 | 杣 | GB Extension | Yes |
U+6785 | 枅 | | No |
U+67B3 | 枳 | | No |
U+67B4 | 枴 | | No |
U+67B7 | 枷 | | No |
U+67B9 | 枹 | | No |
U+67CE | 柎 | | No |
U+68D8 | 棘 | | No |
U+69C7 | 槇 | | No |
U+69DD | 槝 | GB Extension | Yes |
U+6A0C | 樌 | | No |
U+6A2E | 樮 | | No |
U+6A72 | 橲 | | No |
**U+6AA0** | **檠** | G0, GB 2312 | **Better to create a new CN glyph instead** | See issue #426.
U+6AAA | 檪 | | No |
U+6BB1 | 殱 | GB Extension | Depends | If merging of the 夕 component favours JP forms, no need to restore.
U+6BDF | 毟 | GB Extension | Yes |
U+6C5E | 汞 | G0, GB 2312 | Adjust JP glyph instead | See issue #431.
U+6CAE | 沮 | | No |
U+6D85 | 涅 | | No |
U+6E23 | 渣 | | No |
U+6EEF | 滯 | | No |
U+6F74 | 潴 | | No |
U+70AE | 炮 | | No |
U+70FD | 烽 | | No |
U+718F | 熏 | | No |
U+7199 | 熙 | | No |
U+71D4 | 燔 | | No |
U+71F9 | 燹 | | No |
U+7246 | 牆 | | No |
U+7329 | 猩 | | No |
U+73CE | 珎 | GB Extension | No, create a new CN glyph instead | See issue #352. v1 CN glyph shows the two parts as connected. Would likely need a new CN glyph instead based off the JP variant glyph, uni73CEuE0101-JP. Do not modify the JP variant glyph directly as it is required for Adobe-Japan1 support.
U+73DE | 珞 | | No |
U+73F1 | 珱 | GB Extension | Yes |
U+7459 | 瑙 | | No |
U+775A | 睚 | | No |
U+7765 | 睥 | | No |
U+78AF | 碯 | | No |
U+79B9 | 禹 | | No |
U+7B18 | 笘 | G3 GB/T 13131 (unpublished GB/T 7589-1987 unsimplified forms) | No | I asked to redesign the JP glyph instead as per issue #408.
U+7B7A | 筺 | GB Extension | Yes |
U+7BDD | 篝 | | No |
U+7BE5 | 篥 | | No |
U+7BF3 | 篳 | | No |
U+7BF6 | 篶 | GB Extension | Yes |
U+7CAD | 粭 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+7F83 | 羃 | | No |
U+7F88 | 羈 | G1, GB 12345 | No | This is regarding the feet removal issue at #293 and #386.
U+80D6 | 胖 | | No |
U+8129 | 脩 | | No |
U+813E | 脾 | | No |
U+81A4 | 膤 | GB Extension | Yes |
U+838A | 莊 | | No |
U+83B5 | 莵 | | No |
U+83BD | 莽 | | No |
U+83EB | 菫 | | No |
U+8420 | 萠 | | No |
U+8422 | 萢 | | No |
U+84F4 | 蓴 | | No |
U+8591 | 薑 | | No |
**U+85CF** | **藏** | G0, GB 2312 | **Yes*** | In issue #342.
U+8602 | 蘂 | | No |
U+8655 | 處 | | No |
U+868C | 蚌 | | No |
U+870A | 蜊 | | No |
U+876E | 蝮 | | No |
U+87B3 | 螳 | | No |
U+87D2 | 蟒 | | No |
U+8827 | 蠧 | | No |
U+8842 | 衂 | | No |
U+8CC1 | 賁 | | No |
U+8D05 | 贅 | | No |
U+8D71 | 赱 | GB Extension | Yes | Also in issue #374, under the section Missing Glyphs.
U+8DDA | 跚 | | No |
U+8E34 | 踴 | | No |
U+8EB1 | 躱 | GB Extension | Yes |
U+8EBE | 躾 | GB Extension | Yes |
U+8EC6 | 軆 | GB Extension | Yes |
U+8F0C | 輌 | GB Extension | Yes |
U+8F4C | 轌 | GB Extension | Yes |
U+91DB | 釛 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+91E1 | 釡 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+91FC | 釼 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+922C | 鈬 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+933B | 錻 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+941A | 鐚 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9421 | 鐡 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+945A | 鑚 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9587 | 閇 | | No |
U+958A | 閊 | GB Extension | Yes |
U+95A8 | 閨 | | No |
U+95CD | 闍 | | No |
U+968D | 隍 | | No |
U+96B2 | 隲 | GB Extension | Yes |
U+9730 | 霰 | | No |
U+98AA | 颪 | | No |
U+98C4 | 飄 | | No |
U+98DC | 飜 | | No |
U+98EE | 飮 | GB Extension | Yes, and adjust | If the top left 人 component follows JP forms, restore and adjust glyph.
U+9920 | 餠 | GB Extension | Yes, and adjust | If the top left 人 component follows JP forms, restore and adjust glyph.
U+99AE | 馮 | | No |
U+99F1 | 駱 | | No |
U+99F2 | 駲 | | No |
U+9A65 | 驥 | | No |
U+9BF1 | 鯱 | | No |
U+9C04 | 鰄 | GB Extension | Yes |
U+9CEC | 鳬 | | No |
U+9D48 | 鵈 | | No |
U+9D50 | 鵐 | | No |
U+9D6F | 鵯 | | No |
U+9DA4 | 鶤 | | No |
## JIS Level 3
Unicode | Character | GB Source | Restore v1 CN glyph? | Comments
-- | -- | -- | -- | --
U+34B5 | 㒵 | | No |
U+37E2 | 㟢 | | No |
U+4E2F | 丯 | | No |
U+5002 | 倂 | GB Extension | Depends | Slightly different strokes at the top of the v1 CN glyph. Unsure if this is an issue or not.
U+51DE | 凞 | | No |
U+52C8 | 勈 | | No |
U+5307 | 匇 | GB Extension | Depends | Suggest to use uni5307uE0101-JP instead, if the merging of the 夕 component favours JP forms.
U+5393 | 厓 | | No |
U+539D | 厝 | | No |
U+560E | 嘎 | | No |
U+57E4 | 埤 | | No |
U+5861 | 塡 | | No |
U+5C5B | 屛 | GB Extension | Yes |
U+5E77 | 幷 | GB Extension | Yes |
U+5F45 | 彅 | GB Extension | Yes |
U+6451 | 摑 | | No |
U+659D | 斝 | | No |
U+665A | 晚 | | No |
U+6678 | 晸 | | No |
U+66FB | 曻 | GB Extension | Yes |
U+679B | 枛 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+6A73 | 橳 | GB Extension | Yes |
U+6B1B | 欛 | | No |
U+6C5C | 汜 | | No |
U+6D39 | 洹 | | No |
U+704E | 灎 | GB Extension | Yes |
U+710F | 焏 | GB Extension | Yes |
U+769D | 皝 | | No |
U+76CE | 盎 | | No |
U+76F1 | 盱 | | No |
U+784F | 硏 | GB Extension | Yes |
U+7A5D | 穝 | GB Extension | Yes |
U+7B6D | 筭 | | No |
U+80F3 | 胳 | | No |
U+82C6 | 苆 | GB Extension | Yes |
U+85AD | 薭 | | No |
U+8612 | 蘒 | | No |
U+8657 | 虗 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+865B | 虛 | | No |
U+8D12 | 贒 | | No |
U+91FB | 釻 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9243 | 鉃 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+95DA | 闚 | | No |
U+974E | 靎 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9856 | 顖 | | No |
U+9BCE | 鯎 | GB Extension | Yes |
## JIS Level 4
Unicode | Character | GB Source | Restore v1 CN glyph? | Comments
-- | -- | -- | -- | --
U+34C7 | 㓇 | | No |
U+3B77 | 㭷 | | No |
U+3DC0 | 㷀 | | No |
U+4508 | 䔈 | | No |
**U+4D77** | **䵷** | G5 GB/T 13132 (unpublished GB/T 7590-1987 unsimplified forms) | **Yes** | Minor stroke difference is likely a regional difference. Maybe restore for consistency sake.
U+4E12 | 丒 | GB Extension | Yes |
U+4E2E | 丮 | | No |
U+4E40 | 乀 | GB Extension | Yes |
U+4E47 | 乇 | | No |
U+4E51 | 乑 | GB Extension | Probably no | This was addressed [previously](https://github.com/adobe-fonts/source-han-serif/issues/56) to make the right two strokes consistent between Sans and Serif, but I'm honestly not sure if it breaks PRC glyph conventions and whether they are related to similar characters like 豕. However, being a GB Extension character it might probably not matter. Even the commercial Chinese fonts show that the right part of 乑 is unrelated to that of 豕.
U+4E5A | 乚 | | No |
U+4ED0 | 仐 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+4FBE | 侾 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+5010 | 倐 | GB Extension | Yes |
U+51A3 | 冣 | GB Extension | Yes |
U+51AD | 冭 | GB Extension | Yes |
U+51BC | 冼 | | No |
U+5500 | 唀 | GB Extension | Yes |
U+5560 | 啠 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+5564 | 啤 | | No |
U+56AD | 嚭 | | No |
U+56CD | 囍 | | No |
U+57F8 | 埸 | | No |
U+5906 | 夆 | | No |
U+5B52 | 孒 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+5B6F | 孯 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+5CC9 | 峉 | | No |
U+5E6C | 幬 | | No |
U+5EFD | 廽 | GB Extension | Yes, and adjust if possible | The restored v1 CN glyph should follow the v2 design of 廴, and no feet on the top right part (also applies to JP glyph as well).
U+5F8F | 徏 | GB Extension | Yes |
U+604C | 恌 | | No |
U+6197 | 憗 | | No |
U+6215 | 戕 | | No |
U+63F7 | 揷 | GB Extension | Depends | If merging of the 臼 component favours JP forms, no need to restore.
U+674C | 杌 | | No |
U+675D | 杝 | | No |
U+6844 | 桄 | | No |
U+6857 | 桗 | GB Extension | Yes |
U+6896 | 梖 | | No |
U+68BB | 梻 | GB Extension | Yes |
U+68CF | 棏 | | No |
U+697F | 楿 | | No |
U+6A30 | 樰 | GB Extension | Yes |
U+6A91 | 檑 | | No |
U+6BEE | 毮 | GB Extension | Yes |
U+6C95 | 沕 | | No |
U+6C97 | 沗 | GB Extension | Probably no | Slightly different strokes at the bottom of the v1 CN glyph, probably not an issue.
U+6E57 | 湗 | | No |
U+7047 | 灇 | GB Extension | Yes |
U+71AF | 熯 | | No |
U+722B | 爫 | | No |
U+7234 | 爴 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+728E | 犎 | | No |
U+72B1 | 犱 | GB Extension | Yes |
U+7695 | 皕 | | No |
U+76EC | 盬 | | No |
U+77A2 | 瞢 | | No |
U+77EA | 矪 | GB Extension | Yes |
U+7847 | 硇 | | No |
U+78E0 | 磠 | | No |
U+79C2 | 秂 | GB Extension | No, create a new CN glyph instead | The v1 CN glyph is only slightly adjusted from JP, but the top part is a throw stroke but it's not supposed to be that due to the 避重捺 (no repeated throw strokes) policy for Chinese handwriting standards. Need a new CN glyph.
U+79C7 | 秇 | GB Extension | Yes |
**U+7BD6** | **篖** | G3 GB/T 13131 (unpublished GB/T 7589-1987 unsimplified forms) | **Yes** |
U+7C5E | 籞 | | No |
U+7C61 | 籡 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+7F3C | 缼 | GB Extension | Yes |
U+7F63 | 罣 | | No |
U+7F64 | 罤 | GB Extension | Yes |
U+8451 | 葑 | | No |
U+84DC | 蓜 | | No |
U+84F0 | 蓰 | | No |
U+8551 | 蕑 | | No |
U+867A | 虺 | | No |
U+8731 | 蜱 | | No |
U+87E6 | 蟦 | | No |
U+8990 | 覐 | GB Extension | Yes |
U+8E22 | 踢 | | No |
U+8E6F | 蹯 | | No |
U+8EB5 | 躵 | GB Extension | Yes |
U+90EB | 郫 | | No |
U+90FF | 郿 | | No |
U+9137 | 鄷 | GB Extension | Yes |
U+9247 | 鉇 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9259 | 鉙 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9268 | 鉨 | GB Extension | No, create a new CN glyph instead | See issue #352. v1 CN glyph shows the two parts as connected. Would likely need a new CN glyph instead based off the JP glyph.
U+929F | 銟 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+97F1 | 韱 | | No |
U+9825 | 頥 | GB Extension | Yes |
U+98AB | 颫 | GB Extension | Yes |
U+98B7 | 颷 | | No |
U+9D11 | 鴑 | GB Extension | Yes |
U+9D5F | 鵟 | | No |
U+9D62 | 鵢 | GB Extension | Yes |
U+9F3D | 鼽 | | No |
## Other Non-JIS Characters
_Most of them are part of Adobe-Japan1-6_
Unicode | Character | GB Source | Restore v1 CN glyph? | Comments
-- | -- | -- | -- | --
U+3405 | 㐅 | | No |
U+3427 | 㐧 | | No |
U+39B3 | 㦳 | | No | Glyph looks the same in v1 and v2
**U+3ADA** | **㫚** | G3 GB/T 13131 (unpublished GB/T 7589-1987 unsimplified forms) | **No** | Make a new CN glyph instead as the bottom part is 曰 (with the middle stroke not touching the right box), not 日.
U+3B35 | 㬵 | | No | Still showing CN forms, glyph must be shared with 胶 (U+80F6)
U+3B3A | 㬺 | | No | Glyph looks the same in v1 and v2
U+3B3B | 㬻 | | No | Glyph looks the same in v1 and v2
U+3BA3 | 㮣 | | No | Still showing CN forms, was adjusted in v2
U+439B | 䎛 | | No | Glyph looks the same in v1 and v2
U+4B7E | 䭾 | | No |
U+4E41 | 乁 | | No |
U+4E74 | 乴 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+4E77 | 乷 | GB Extension | Yes |
U+4E90 | 亐 | GB Extension | Yes |
U+4EFE | 仾 | GB Extension | Yes |
U+4F2E | 伮 | GB Extension | Yes |
U+4F31 | 伱 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+4F71 | 佱 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+4FBD | 侽 | | No |
U+4FE2 | 俢 | GB Extension | Yes |
U+5035 | 倵 | | No |
U+5071 | 偱 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+50C0 | 僀 | | No |
U+5128 | 儨 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+514F | 兏 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+51BF | 冿 | | No |
U+51C2 | 凂 | | No |
**U+51D2** | **凒** | G5 GB/T 13132 (unpublished GB/T 7590-1987 unsimplified forms) | **Depends** | If merging of the 丷 (豆) component favours JP forms, no need to restore.
U+51F2 | 凲 | GB Extension | Yes |
U+5231 | 刱 | | No |
U+5266 | 剦 | GB Extension | Yes |
U+52B0 | 劰 | | No |
U+52B6 | 劶 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+52B7 | 劷 | GB Extension | Yes |
U+52C4 | 勄 | GB Extension | Yes |
U+5303 | 匃 | GB Extension | Yes |
U+531B | 匛 | GB Extension | Yes |
U+531E | 匞 | GB Extension | Yes |
U+5328 | 匨 | GB Extension | Yes |
U+5329 | 匩 | GB Extension | Yes |
U+5365 | 卥 | | No |
U+53E0 | 叠 | | No |
U+53E6 | 另 | | No |
U+543F | 吿 | GB Extension | Depends | JP looks better and the character does not look obvious when seen in small sizes, but Chinese standards dictate that the 牛 must touch the 口, so unsure for now.
U+5444 | 呄 | GB Extension | Yes |
U+54F6 | 哶 | | No |
U+55E0 | 嗠 | GB Extension | Yes |
U+560A | 嘊 | | No |
U+5619 | 嘙 | GB Extension | Yes |
U+5620 | 嘠 | | No |
U+5641 | 噁 | | No |
U+56CF | 囏 | | No |
U+58E1 | 壡 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+58FF | 壿 | | No |
U+5936 | 夶 | GB Extension | Yes |
U+5995 | 妕 | GB Extension | Yes |
U+5A3F | 娿 | GB Extension | Yes |
U+5A72 | 婲 | GB Extension | Yes |
U+5A8D | 媍 | GB Extension | Yes |
U+5B5E | 孞 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+5B7E | 孾 | GB Extension | Yes, and adjust if possible | The left 子 radical could be modified to the JP form if the JP forms are preferred for all regions.
U+5BF9 | 对 | G0, GB 2312 | No | JP looks better.
**U+5C14** | **尔** | G0, GB 2312 | **Yes** | See issue #352. Likely the v1 CN glyph will be restored as part of a regional difference. There's nothing I can do to force JP to use CN forms.
U+5C2E | 尮 | GB Extension | Yes |
U+5C36 | 尶 | GB Extension | Yes |
U+5CB2 | 岲 | GB Extension | Yes |
U+5D44 | 嵄 | GB Extension | Yes |
U+5D83 | 嶃 | GB Extension | Yes |
U+5DD9 | 巙 | GB Extension | Yes |
U+5E32 | 帲 | GB Extension | Yes |
U+5F2B | 弫 | GB Extension | Yes |
U+5F2C | 弬 | GB Extension | Yes |
U+6056 | 恖 | | No |
U+60E5 | 惥 | GB Extension | Depends | If merging of the 臼 component favours JP forms, no need to restore.
U+6102 | 愂 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+61A0 | 憠 | GB Extension | Yes |
U+636D | 捭 | | No |
U+6371 | 捱 | | No |
U+63C5 | 揅 | | No |
U+645C | 摜 | | No |
U+64EA | 擪 | | No |
U+654E | 敎 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+6598 | 斘 | GB Extension | Depends | If merging of the 夕 component favours JP forms, no need to restore.
U+65A3 | 斣 | | No |
U+65FE | 旾 | GB Extension | Yes |
U+661B | 昛 | GB Extension | Yes |
U+66E3 | 曣 | | No |
U+6707 | 朇 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+6710 | 朐 | | No |
U+67A4 | 枤 | | No |
U+67BE | 枾 | | No |
U+67FA | 柺 | | No |
U+682E | 栮 | | No |
U+6858 | 桘 | | No |
U+6A37 | 樷 | GB Extension | Yes |
U+6B2B | 欫 | GB Extension | Yes |
U+6B5A | 歚 | GB Extension | Yes |
U+6B7D | 歽 | GB Extension | Depends | If merging of the 夕 and 斤 components favours JP forms, no need to restore.
U+6BAC | 殬 | GB Extension | Depends | If 歹 favours JP forms, create a new CN glyph by adjusting from the JP glyph. Also, see issue #388.
U+6E42 | 湂 | GB Extension | Yes |
U+6E95 | 溕 | GB Extension | Yes |
U+6F04 | 漄 | | No |
U+7013 | 瀓 | GB Extension | Yes |
U+7179 | 煹 | GB Extension | Yes |
U+7241 | 牁 | | No |
U+724E | 牎 | | No |
U+7343 | 獃 | | No |
U+7360 | 獠 | | No |
U+7527 | 甧 | GB Extension | Yes |
U+7575 | 畵 | GB Extension | Yes |
U+7682 | 皂 | | No |
U+76C1 | 盁 | GB Extension | Yes |
U+7773 | 睳 | | No |
U+7796 | 瞖 | GB Extension | Yes |
U+784C | 硌 | | No |
U+7863 | 硣 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+7916 | 礖 | GB Extension | Depends | If merging of the 臼 component favours JP forms, no need to restore.
U+791F | 礟 | | No |
U+7B40 | 筀 | | No |
U+7B53 | 筓 | GB Extension | Yes |
U+7B6A | 筪 | GB Extension | Yes |
U+7BBA | 箺 | GB Extension | Yes |
U+7BC8 | 篈 | | No |
U+7BFE | 篾 | | No |
U+7CDA | 糚 | GB Extension | Yes |
U+7CE9 | 糩 | GB Extension | Depends | If merging of the 人 component favours JP forms, no need to restore.
U+8009 | 耉 | GB Extension | Yes |
U+8013 | 耓 | GB Extension | Yes |
U+8040 | 聀 | GB Extension | Yes |
U+8060 | 聠 | GB Extension | Yes |
U+809E | 肞 | GLK 《龍龕手鑑》(續古逸叢書) | Adjust JP variant glyph instead | **UPDATE 2023-07-30:** The JP variant glyph, uni809EuE0101-JP, is much closer to the latest China GB standard, although the right 叉 component is an open loop which may not fully comply with the closed-loop form favoured by the PRC glyph conventions. However, I suggest instead to make an adjustment to the JP variant glyph to reduce the gap in the 叉 component so it will look a bit more compliant.
Also see [this comment](https://github.com/adobe-fonts/source-han-sans/issues/180#issuecomment-366722429).
U+80F7 | 胷 | GB Extension | Yes |
U+8141 | 腁 | GB Extension | Yes |
U+8152 | 腒 | | No |
U+81CB | 臋 | GB Extension | Yes |
U+830A | 茊 | GB Extension | Depends | If merging of the 𠂆 component favours JP forms, no need to restore.
U+832E | 茮 | | No |
U+8550 | 蕐 | GB Extension | Yes |
U+8552 | 蕒 | | No |
U+85B8 | 薸 | | No |
U+8642 | 虂 | | No |
U+865D | 虝 | GB Extension | Yes |
U+8745 | 蝅 | GB Extension | Yes |
U+87CA | 蟊 | | No |
U+87F8 | 蟸 | GB Extension | Yes |
U+89A8 | 覨 | GB Extension | Yes |
U+8C63 | 豣 | GB Extension | Yes |
U+8CC9 | 賉 | | No |
U+8CEF | 賯 | GB Extension | Depends | If merging of the 子 component favours JP forms, no need to restore.
U+8D82 | 趂 | GB Extension | Yes | See issue #352. Likely the v1 CN glyph will be restored as part of a regional difference. There's nothing I can do to force JP to use CN forms.
U+8D9E | 趞 | | No |
U+8DE5 | 跥 | GB Extension | Yes |
U+8EC7 | 軇 | GB Extension | Yes |
U+8F27 | 輧 | | No |
U+90C9 | 郉 | GB Extension | Yes |
U+90CC | 郌 | | No |
U+913C | 鄼 | GB Extension | Yes |
U+921D | 鈝 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+921F | 鈟 | GB Extension | Maybe create a new CN glyph instead | It would be better to create a new CN glyph by basing it off the JP glyph if the 金 component can be merged to the JP forms.
U+9292 | 銒 | GB Extension | Maybe create a new CN glyph instead | It would be better to create a new CN glyph by basing it off the JP glyph if the 金 component can be merged to the JP forms.
U+9337 | 錷 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+936F | 鍯 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+937F | 鍿 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9402 | 鐂 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+941F | 鐟 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9459 | 鑙 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+945C | 鑜 | GB Extension | Depends | If merging of the 金 component favours JP forms, no need to restore.
U+9484 | 钄 | GB Extension | Maybe create a new CN glyph instead | It would be better to create a new CN glyph by basing it off the JP glyph, because the 柬 part in the bottom right must be a drop stroke (點), not a throw stroke (捺), and that is if the 金 component can be merged to the JP forms.
U+95C9 | 闉 | | No |
U+9625 | 阥 | | No |
U+9631 | 阱 | | No |
U+9674 | 陴 | | No |
U+967B | 陻 | | No |
U+967F | 陿 | GB Extension | Yes |
U+9775 | 靵 | GB Extension | Yes |
U+99F5 | 駵 | | No |
U+9A08 | 騈 | GB Extension | Yes |
U+9A0B | 騋 | | No |
U+9A51 | 驑 | | No |
U+9A56 | 驖 | | No |
U+9B94 | 鮔 | GB Extension | Yes |
U+9BBC | 鮼 | GB Extension | Yes |
U+9D2F | 鴯 | | No |
U+9F0F | 鼏 | | No |
U+9F11 | 鼑 | GB Extension | Yes |
U+9F47 | 齇 | | No |
U+9FB4 | 龴 | | No |
**UPDATE 2023-07-23:** The v1 CN glyphs for 妕 (U+5995), 娿 (U+5A3F), 婲 (U+5A72) and 媍 (U+5A8D) must be restored, instead of "should not be restored", because previously I failed to notice the regional difference in the 女 component. Ironically for Serif, [the JP glyphs for 娿 (U+5A3F) and 婲 (U+5A72) were mistakenly removed which is required for Korean KSX support](https://github.com/adobe-fonts/source-han-serif/issues/174#issuecomment-1465270749).
**UPDATE 2023-07-30:** Added more info about 肞 (U+809E) which I didn't check properly, so Adobe should not restore the v1 CN glyph, and instead adjust the JP variant glyph, uni809EuE0101-JP, so that it matches the JP glyph of 叉 (U+53C9).
**UPDATE 2023-08-03:** Changed entry for 圸 (U+5738) to "restore v1 CN glyph" instead of "do not restore v1 CN glyph", missed that one out.
贡献指南
这个仓库没有索引到贡献指南
评估
这个 Issue 还没有评估数据。