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

The HK mapping of 蜻 (U+873B) refers to CN, however CN uses the IVS of JP, resulting in duplicate glyphs #522

Open
3 tasks done
lakejason0 opened this issue Dec 9, 2024 · 2 comments

Comments

@lakejason0
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, 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

image
image

For Sans, CN maps to the IVS, which is fine, but HK then maps to the CN glyph that should be unused since CN now uses the IVS glyph. Both CN and HK should map to the IVS.

Source Han Serif use CN glyph for both, maybe should also sync it to map both to use IVS as well.

@tamcy
Copy link

tamcy commented Dec 15, 2024

FWIW, in Serif the CN glyph is used for the IVS. There is no JP glyph.

@NightFurySL2001
Copy link

NightFurySL2001 commented Dec 15, 2024

In Sans the JP IVD glyph is more balanced than CN. The CN glyph in Serif is also the IVD glyph for JP, so there is no problem mapping the Sans JP to CN region. Similar mapping to JP IVDs have been done in CN before.

It would be better to map HK to JP IVD glyph on Sans.

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