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

Adjust 韃 (U+97C3, CN only) and 韆 (U+97C6, CN only) to improve balance #178

Open
Marcus98T opened this issue Mar 3, 2023 · 5 comments

Comments

@Marcus98T
Copy link

Marcus98T commented Mar 3, 2023

The 辶 radical looks weird and off-balanced. Please adjust to match TW/HK/JP/KR proportions, which are fine.

Screenshot 2023-03-03 at 14 26 29

@Marcus98T
Copy link
Author

Not fixed in Noto Serif v2.002. This issue will remain open.

Screenshot 2023-08-17 at 20 02 12

@Wenti-D
Copy link

Wenti-D commented Jan 9, 2024

Well, in Unicode Standard, these two glyphs are just like current in SHS.
image
image

@Marcus98T
Copy link
Author

Marcus98T commented Jan 9, 2024

Well, in Unicode Standard, these two glyphs are just like current in SHS. image image

Yes, as of v2.002, those two CN glyphs follow the Unicode reference exactly, but I feel that this typeface can be better designed, which is why I am asking Adobe to adjust them.

@Wenti-D
Copy link

Wenti-D commented Jan 11, 2024

Yes, as of v2.002, those two CN glyphs follow the Unicode reference exactly, but I feel that this typeface can be better designed, which is why I am asking Adobe to adjust them.

I mean, that's true, but glyph designs usually follow the Unicode Standard. Maybe Unicode should adjust them first.🤨

@Marcus98T
Copy link
Author

I mean, that's true, but glyph designs usually follow the Unicode Standard. Maybe Unicode should adjust them first.🤨

That is the problem with the type foundries designing references for the Unicode standard. On the other hand, open-source typefaces like Source Han Serif can be made to look better than the Unicode reference while following glyph guidelines. I don't wish to debate this anymore.

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

2 participants