-
Notifications
You must be signed in to change notification settings - Fork 644
-
Notifications
You must be signed in to change notification settings - Fork 644
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
HK & TW glyph issue for U+9ED5 黕 and U+9EE0 黠 #136
Comments
As I am not a typeface designer I am not in a good position to comment on this, but also I agree that the TW glyph looks better, mainly because of the placement of the four dots 灬. But it would still be fine to use the current JP glyph if the designer doesn't agree to replace it with the TW one. I say this because the stroke above that 灬 isn't consistent in JP, and it seems to me that the JP glyph designer tends to preserve the same flow of the four dots (灬) no matter which stroke type is used above that 灬: And it doesn't seem to worth allocating a new CID just for this difference 😄. |
Definitely not saying we should add both the TW and JP. Just using one is fine. Easiest right now is to map TW/HK to the existing JP. |
Fix to U+9ED5 黕 and U+9EE0 黠 confirmed in v2.001 release, thanks! |
I am closing this as @Marcus98T has his own issue about this in #148. |
Version: 2.000
The circled region indicates a stroke type difference between CN and HK/TW.
For U+9ED5 黕, the JP glyph could be used.
For U+9EE0 黠, a new glyph would be needed.
The text was updated successfully, but these errors were encountered: