HK & TW glyph issue for U+50F0 僰 and U+68D7 棗 #135
Comments
tamcy
changed the title
|
While this isn't related to the HK/TW mapping issue, I also want to point out the KR mapping for U+68D7 棗 should be the same as the JP version. Please fix this as well. While some major Korean fonts like (from left to right) Adobe Gothic Std, Apple Myungjo Std, Apple SD Gothic Neo (based off Nanum Gothic) and Apple Gothic have the CN form, this I think is inconsistent. Apple Myungjo (far right) has the JP form.
And yes, while the Korean Unicode reference is not consistent in some ways, I think 棗 needs to be more consistent with the other glyphs that have 朿 as the component.
|
|
Fix to U+68D7 and U+50F0 confirmed in v2.001. Thanks! |
|
|
|
Removed the mistaken line from the README. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Source Han Serif Version: v2.000
This one is easy to get overlooked. I just spot this by accident.
The CN glyphs for U+50F0 僰 and U+68D7 棗 cannot be used for HK or TW because of the difference in the 朿 component.
For U+68D7 棗, suggest to remap TW and HK to JP.
For U+50F0 僰, unfortunately (?) the JP glyph cannot be directly used because of the stroke form difference in the last stroke of 朿 on the right.
If allocating a new glyph isn't possible right now, I think the JP glyph is preferable for this case.
The text was updated successfully, but these errors were encountered: