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 SC and Source Han Serif SC 2 #56

Closed
KazunariTsuboi opened this issue May 4, 2017 · 3 comments
Assignees

Comments

@KazunariTsuboi
Copy link

21 characters were found in Source Han Serif SC that have different design with Source Han Sans SC.
They are ⻁ (U+2EC1), ⻪ (U+2EEA), 懲 (U+61F2), 乑 (U+4E51), 堩 (U+5829), ⼬ (U+2F2C), 巆 (U+5DC6), 濹 (U+6FF9), 衋 (U+884B), 贗 (U+8D17), ⿋ (U+2FCB), 㗴 (U+35F4), 䙶 (U+4676), 䜛 (U+471B), 䞅 (U+4785), 䟡 (U+47E1), 𩻄 (U+29EC4), 㧤 (U+39E4), 㵮 (U+3D6E), 䎉 (U+4389), 䕎 (U+454E)
170504_22glyphsquestion_1
170504_22glyphsquestion_2
170504_22glyphsquestion_3
170504_22glyphsquestion_4

@kenlunde kenlunde self-assigned this May 4, 2017
@kenlunde
Copy link
Contributor

kenlunde commented May 4, 2017

Thank you. A small number of these issues have been fixed for the forthcoming dot release, and some of them are Source Han Sans issues, not Source Han Serif ones. Also, some of them are intentional typeface design differences.

I will go through this list in the next few days to determine their dispositions.

@kenlunde
Copy link
Contributor

kenlunde commented May 4, 2017

Here's my analysis of the 21 glyph pairs that you identified:

Characters Serif Sans
⻁ U+2EC1 Fixed for Version 1.001 OK
⻪ U+2EEA Fixed for Version 1.001 OK
懲 U+61F2 OK Known issue (fix CN glyph)
乑 U+4E51 OK Remove CN glyph; Use JP glyph for CN/TW
堩 U+5829 OK Known issue (fix CN glyph). See U+21377 𡍷
⼬ U+2F2C Fixed for Version 1.001 OK
巆 U+5DC6 Add CN glyph OK
濹 U+6FF9 OK Known issue (change mapping to JP variant)
衋 U+884B OK Known issue (for both JP and CN glyphs)
贗 U+8D17 Rename TW glyph to be CN glyph OK
⿋ U+2FCB OK CN glyph for U+9EF9 needs to be adjusted
㗴 U+35F4 OK Known issue (add CN glyph)
䙶 U+4676 Fix CN glyph OK
䜛 U+471B Fix CN glyph OK
䞅 U+4785 Fix CN glyph OK
䟡 U+47E1 OK Fix CN glyph
𩻄 U+29EC4 OK (typeface design difference) OK (typeface design difference)
㧤 U+39E4 OK (typeface design difference) OK (typeface design difference)
㵮 U+3D6E OK Remove CN glyph (it also has a subtle interpolation issue)
䎉 U+4389 OK Fix CN glyph
䕎 U+454E OK Known issue (fix CN glyph)

In other words, you found five Source Han Serif issues (one new CN glyph needs to be added, three CN glyphs need to be fixed, and one TW glyph needs to be changed to a CN glyph) and five Source Han Sans ones (two CN glyphs need to be removed, and three CN glyphs need to be fixed). The rest are either addressed in the forthcoming Source Han Serif update, or are already known Source Han Sans issues.

I will update the appropriate issues within the next day or two to consolidate the above, and then will close this issue.

@kenlunde
Copy link
Contributor

kenlunde commented May 5, 2017

(Thank you, @miguelsousa, for turning my data above into a easy-to-read table.)

The above changes are now either reflected in the appropriate issues (Source Han Serif) or in my own notes (Source Han Sans Version 2.000), and therefore consolidated.

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