Skip to content

Enquiry about regional glyphs for U+9FD6..9FE9 #450

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

Open
NightFurySL2001 opened this issue Aug 1, 2023 · 1 comment
Open

Enquiry about regional glyphs for U+9FD6..9FE9 #450

NightFurySL2001 opened this issue Aug 1, 2023 · 1 comment

Comments

@NightFurySL2001
Copy link

NightFurySL2001 commented Aug 1, 2023

U+9FD6..9FE9 is not in any of the official documentation of all 5 regions supported by Source Han, and only GB18030 requires the presence of it (the glyph in GB18030 is not mandatory, only requiring the character codepoint to presence).

Thus, from the font's perspective, the character between U+9FD6..9FE9 should only have 1 CN glyph each to support GB18030.

However, there are some of the glyph that has a HK variant. My question is as follow

  1. Why are the HK glyphs present? Why not other region (like JP or TW)? Personally I would prefer JP to be present here instead of HK since Source Han original focus is Japanese. Five characters (U+9FD1-U+9FD5,鿑鿒鿓鿔鿕) in Unicode 8.0 should be added. #121 or Consolidation of Character/Glyph Addition Suggestions #180 does not mention why choosing the HK region specifically. Should HK glyphs be removed?
  2. If HK is definitely chosen as the alternative region to be supported for this block, should characters that does not match HK be added new glyph and be fixed (above point)?
    • U+9FDB 鿛 should fix 夂 since HK 夂 does not protude outwards.
    • U+9FDE 鿞 should have a HK glyph added for closed 夕
    • U+9FE9 鿩 should have a HK glyph added for 曰 魯
  3. If the HK glyphs are to stay, U+9FE2 鿢, U+9FE3 鿣, U+9FE4 鿤 and U+9FE6 鿦 (?) can have the HK glyph map to JP and KR.

nightfurysl2001 github io_shs-cid_

@CoolMarvel43
Copy link

CoolMarvel43 commented Aug 3, 2023

Since those characters from U+9FD6 to U+9FE9 only have UTC as a source, I suggest that only the CN glyphs be kept. The HK glyphs should be removed to free glyph space for something that matters more.

鿞 (U+9FDE) might need to be adjusted to the closed form, if the merging of the 夕 component to the JP forms is to go ahead, otherwise leave it alone if 夕 is to follow CN forms.

And finally, if the 人 component is to be merged to the JP forms, the CN glyphs for 鿖 (U+9FD6), 鿗 (U+9FD7), 鿘 (U+9FD8) and 鿢 (U+9FE2) will need to be adjusted, or if JP glyphs were already designed (does not apply to 鿢 (U+9FE2)), use them and remove the CN glyphs. As for 鿿 (U+9FFF), when it's finally added to the next release of Sans, should just have a JP-styled glyph.

Also there's no reason for 魯 (U+9B6F) to appear here, as this character is outside the issue scope, probably an error made while checking the glyphs for U+9FD6 to U+9FE9. EDIT: I didn't see that it was supposed to be a reference for a possible HK glyph for 鿩 (U+9FE9), but whatever the case, I think Adobe should not be making a HK glyph.

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

3 participants