-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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+7436) and 瑟 (U+745F) need adjustments for CN #383
Comments
Interesting. Neither of these need a new CN glyph because they both have CN glyphs, but they are 100% identical to the JP glyph. I think U+745F can just use uni745FuE0101-JP and we can drop the existing CN glyph. |
Well based on the previous reply, the CN glyphs were adjusted in v2, copying direct from the corresponding JP glyphs by mistake. But still, to unify the 心/必 component to the JP aesthetic I suggest to continue using uni745FuE0101-JP for CN, and remove the current uni745F-CN glyph (or orphan it if the CIDs cannot be changed). uni7436-CN (琶) can be reverted to the v1 glyph. But anyway I think those two characters were already fixed in the source a long time ago as indicated by the "fixed for next version" tag, so I suppose there will be no more changes because it would probably be a headache for the maintainer to keep checking. On another note, in Mainland China, there was a plan to change 44 glyphs to follow traditional calligraphy conventions which is closer to the current TW/HK forms, which included 琶 (U+7436) and 瑟 (U+745F), which would have followed JP/TW/HK forms for those two, but the plan did not go through because it would be too expensive to re-print everything with the new glyphs. Maybe the font designer must have thought the plan went through at that time. |
I reported on 琶 before as quoted above, but recently I also found out that 瑟 requires a new CN glyph, as explained before.
Accordingly, I will modify my previous post #374 to strike out the quoted text and make a note that this issue will supersede it.
The text was updated successfully, but these errors were encountered: