Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unifying CN and JP 辶 component #300

Open
NightFurySL2001 opened this issue May 8, 2021 · 4 comments
Open

Unifying CN and JP 辶 component #300

NightFurySL2001 opened this issue May 8, 2021 · 4 comments

Comments

@NightFurySL2001
Copy link

NightFurySL2001 commented May 8, 2021

Prerequisites

  • [/] If you are reporting an issue that affects glyphs for characters for a particular region or regions, did you verify that the characters are within the supported scope of the region or regions? This generally means GB 18030 or Tōngyòng Guīfàn Hànzìbiǎo (通用规范汉字表) for China, Big Five or CNS 11643 Planes 1 & 2 for Taiwan, HKSCS-2016 for Hong Kong, JIS X 0208, JIS X 0212, and JIS X 0213 for Japan, and KS X 1001 and KS X 1002 for Korea.
  • [/] Did you thoroughly search the open and closed issues to avoid reporting a duplicate issue?
  • [/] Did you go through the official font readme file to better understand the scope of the project, to include the Known Issues section at the very end?

Description

I would like to raise the 辶 component from this discussion again. I think that the CN and JP glyphs for 辶 component should be unified in Source Han Sans (and to Source Han Serif).
image

I do know that this was rejected by Ken Lunde after consultation with the designer team (probably from Changzhou Sinotype at the time) but there is now a new team from Arphic Technology working with Adobe and thus I would suggest consulting this decision with both Changzhou Sinotype and Arphic Technology.

The points are as follow:

  1. There are no official documentation or mentions of 辶 to be designed as a single stroke in any of the official documents from Tōngyòng Guīfàn Hànzìbiǎo, or any of its predecessors. Similar decisions with official documentation in say, Standard Form of National Characters, which mentioned that the two strokes in 立 and 豆 should be touching both top and bottom line, are not even implemented in Source Han Sans.
  2. 辶 is designed similar to JP in some SC fonts, such as Microsoft YaHei (Windows default system font). The current design of 辶 is mainly a relic from the Shanghai Song style.
    image
  3. Sharing of 辶 glyph between CN and JP can reduce a significant amount of CIDs to be used for expanding the character set.

This suggestion should be considered by both Changzhou Sinotype and Arphic Technology as they may have better knowledge on this issue.

@NightFurySL2001
Copy link
Author

P/S: If this is to be viewed as a regional difference, then the requirement of two dots in 立 and 豆 to be connected to the top and bottom stroke should be implemented for TW and HK as this is a written requirement in Taiwan's 國字標準字體教師手冊, unlike this differentiation of 辶 component which is not specified anywhere in any of China's official document.

立: https://language.moe.gov.tw/001/Upload/files/SITE_CONTENT/M0001/STD/p173.htm?open
image

豆: https://language.moe.gov.tw/001/Upload/files/SITE_CONTENT/M0001/STD/p203.htm?open
image

@SyaoranHinata
Copy link

I couldn't agree more, NightFurySL2001 made a very good point. I strongly hope that NightFurySL2001's suggestion will be accepted.

@fatloong
Copy link

fatloong commented Mar 9, 2023

Strongly support this point.

@tjw123hh
Copy link

Strongly support this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants