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

Mapping error in CN for U+5141 (允) and U+535A (博) #162

Closed
NightFurySL2001 opened this issue May 7, 2022 · 5 comments
Closed

Mapping error in CN for U+5141 (允) and U+535A (博) #162

NightFurySL2001 opened this issue May 7, 2022 · 5 comments

Comments

@NightFurySL2001
Copy link

Affects 允 and 博.
image

@Pal3love
Copy link

Pal3love commented May 15, 2022

To provide more context, the affected characters are uni5141 (允) and uni535A (博), which have different shapes in SC/CN, TC/TW, HC/HK, J/JP and K/KR.

Expected mappings should be:

uni5141 (允)

  • cid10832 -> J, K
  • cid10833 -> SC, TC, HC

uni535A (博)

  • cid11682 -> J
  • cid11683 -> TC, HC
  • cid62034 -> SC, K, codepoint U+E0101 of J

Current mappings in SHSerif 2.001, which needs to fix, are:

uni5141 (允)

  • cid10832 -> J, K, SC
  • cid10833 -> TC, HC

uni535A (博)

  • cid11682 -> J, K, SC
  • cid11683 -> TC, HC
  • cid62034 -> K, codepoint U+E0101 of J

The following are the detailed differences among the characters:

允博 in J:
允博 in J

允博 in HC, TC:
允博 in HC, TC

博 in SC, K
博 in SC, K

If possible, please prioritize this issue as it impacts daily Chinese (and Japanese) words, such as 允许 (allow) and 博士 (doctor).

Thanks!

@NightFurySL2001
Copy link
Author

NightFurySL2001 commented May 16, 2022 via email

@NightFurySL2001 NightFurySL2001 changed the title Mapping error in CN Mapping error in CN for U+5141 (允) and U+535A (博) May 16, 2022
@punchcutter
Copy link
Member

Fixed mapping for next release

@Marcus98T
Copy link

Fix verified in Noto Serif v2.002. CN is using the TW glyph for 允 (U+5141) and the KR glyph (uni535AuE0101-JP) for 博 (U+535A). I think this is good enough.

Screenshot 2023-08-17 at 20 29 23

@NightFurySL2001
Copy link
Author

Verified fix in v2.002.

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

4 participants