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

Misunification of U+5CB8 (岸) #169

Closed
3 tasks done
4b3 opened this issue Sep 10, 2022 · 3 comments
Closed
3 tasks done

Misunification of U+5CB8 (岸) #169

4b3 opened this issue Sep 10, 2022 · 3 comments

Comments

@4b3
Copy link

4b3 commented Sep 10, 2022

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, the JIS standards 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

U+5CB8 (岸) should be separated into JP/KR and CN/TW/HK forms by the shape of the break in the second stroke of 山.
The five letters shown here as an example, 岩, 岳, 岸, 島, and 崩, are screenshots from region-map.xlsx v2.001, and all meet the criteria for inclusion in the subset of five regions, but only 岸 is unified.

region-map-radical-mountain

@punchcutter
Copy link
Member

The JP glyph was mistakenly removed with all the big changes for 2.000 update. It will be back in the next update.

@Marcus98T
Copy link

Fix verified in Noto Serif v2.002. When Source Han Serif v2.002 is released, this issue will be closed.

Screenshot 2023-08-17 at 20 09 01

@punchcutter
Copy link
Member

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

3 participants