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

Design difference between Source Han Sans K and Source Han Serif K #59

Closed
KazunariTsuboi opened this issue May 11, 2017 · 5 comments
Closed
Assignees

Comments

@KazunariTsuboi
Copy link

KazunariTsuboi commented May 11, 2017

Thank you for your clear explanation on the KR glyph.
The CJK Type Blog was very helpful.
I noticed 15 characters that differ in character form concerning KS X 1001 and 1002 between Source han serif K and Source han sans K.
倂 U+5002, 剪 U+526A, 墁 U+5881, 栞 U+681E, 梏 U+688F, 櫝 U+6ADD, 汋 U+6C4B, 瀆 U+7006, 炷 U+70B7, 牘 U+7258, 犢 U+72A2, 犳 U+72B3, 猀 U+7300, 琱 U+7431, 瑤 U+7464

kr_diff

@kenlunde
Copy link
Contributor

U+526A 剪, U+5881 墁, U+681E 栞, U+688F 梏, U+6ADD 櫝, U+6C4B 汋, U+7006 瀆, U+70B7 炷, U+7258 牘, U+72A2 犢, U+72B3 犳, and U+7431 琱 are handled by mapping these characters to the corresponding CN glyphs in the KR CMap resource, and this is now recorded in Issue #37.

U+5002 倂, U+7300 猀 (outside the scope of KS X 1001 and KS X 1002), and U+7464 瑤 require slightly different treatment.

@kenlunde
Copy link
Contributor

For U+5002 倂, the difference can actually be traced back to differences in Kozuka Mincho and Kozuka Gothic, and the former, and therefore Source Han Serif, is correct. However, this means that the JP glyph for U+5002 倂 in Source Han Sans, uni5002-JP, needs to be corrected, and both Source Han Sans and Source Han Serif need a KR glyph for U+5002 倂, uni5002-KR, to be added.

For U+7300 猀, although this character is outside the scope of the two KS standards, I plan to remove its JP glyph in Version 2.000 (it's already a candidate for removal), and will map U+7300 猀 to the CN glyph, uni7300-CN, in the JP and KR CMap resources.

For U+7464 瑤, this looks like a Source Han Sans issue that affects its JP glyph, which is also used in the KR CMap resource. I made a note to check that glyph as part of its Version 2.000 update.

@KazunariTsuboi
Copy link
Author

Sorry to have duplicated a past issue. Thank you for your clear reply.

@kenlunde
Copy link
Contributor

@dadasutasudadas: Thank you for the report, which included several actionable items. When developing such a large and complex project, the presence of issues is expected. Luckily, open source projects have a good mechanism for reporting and tracking issues.

@kenlunde
Copy link
Contributor

For U+681E 栞, I determined that the correct course of action is to leave the current mapping as-is, meaning that the JP glyph, uni681E-JP, is used, and that the corresponding mapping needs to be fixed in Source Han Sans (see Source Han Sans Issue 177).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants