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

Wrong mappings for U+2E569 U+E0100 and U+884B #126

Closed
3 tasks done
trueroad opened this issue Oct 31, 2021 · 2 comments
Closed
3 tasks done

Wrong mappings for U+2E569 U+E0100 and U+884B #126

trueroad opened this issue Oct 31, 2021 · 2 comments

Comments

@trueroad
Copy link

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

source-han-serif-2 000-wrong-mapping

If I understand correctly, SourceHanSerif version 2.000 has wrong mappings for U+2E569 U+E0100 and U+884B.

U+2E569 U+E0100 is a completely different letter from U+2E569.
I would like U+2E569 U+E0100 to be the same glyph as U+2E569.

U+884B is the same glyph as U+884B U+E0101 instead of U+884B U+E0100.
I would like U+884B to be the same glyph as U+884B U+E0100 instead of U+884B U+E0101.

@punchcutter
Copy link
Member

U+2E569 U+E0100 must have had a copy/paste error and got the CID from the previous line in the IVS file. Fixed now.

The mappings for U+884B are currently the same as in Source Han Sans, but that's also a mistake that needs to be corrected there. Fixed in Serif now.

@punchcutter
Copy link
Member

Fixed in 2.001.

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

No branches or pull requests

2 participants