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

莁(U+8381) and 菄(U+83C4) has wrong radical 艹 for CN #200

Closed
CrotchBurnt opened this issue Aug 25, 2023 · 3 comments
Closed

莁(U+8381) and 菄(U+83C4) has wrong radical 艹 for CN #200

CrotchBurnt opened this issue Aug 25, 2023 · 3 comments

Comments

@CrotchBurnt
Copy link

image

@Marcus98T
Copy link

A similar issue has been reported for Sans in 2021.

Unfortunately due to limited glyph space, some CN glyphs will show JP or TW/HK forms as the only glyph shape for CN, although most of them are rare-use characters which may not reflect actual usage in China. Most of those affected glyphs are GB Extension characters, although some of them, in the case of showing TW/HK forms, are G3 or G5 characters according to the Unicode charts.

When I'm free, I will list down all the CN glyphs showing JP forms and TW/HK forms for Serif in a separate issue.

@punchcutter
Copy link
Member

These glyphs only have a TW form right now and no current plan to add a CN glyph without some compelling argument.

@punchcutter punchcutter closed this as not planned Won't fix, can't repro, duplicate, stale Sep 8, 2023
@Marcus98T
Copy link

and no current plan to add a CN glyph without some compelling argument.

@punchcutter I see.

Which is why I suggest that the Sans and Serif readmes should add a note that not all GB 18030 characters are CN-compliant. That way people at least can know that Adobe is aware of this issue and may probably address it with a major redesign, or will not be addressing it due to technical limitations.

Sorry to bring it up again and again.

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