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.

Sign up for GitHub

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

Jump to bottom

Consolidation of Glyph Sharing Suggestions (See Issue #38) #28

Closed
hfhchan opened this issue Apr 9, 2017 · 4 comments
Closed

Consolidation of Glyph Sharing Suggestions (See Issue #38) #28

hfhchan opened this issue Apr 9, 2017 · 4 comments
Assignees
@kenlunde
Labels
consolidated suggestion

Comments

@hfhchan
Copy link

hfhchan commented Apr 9, 2017

U+6641: There is no practical difference between the two different forms by the CN and JP glyph.

image
Legend: CN, TW, JP, KR, CN/JP overlaid
@hfhchan
Copy link
Author

hfhchan commented Apr 10, 2017

U+4F8D: There is no practical difference between the two different forms by the CN and JP glyph.
image

@hfhchan
Copy link
Author

hfhchan commented Apr 10, 2017 •
edited
Loading

U+504F (偏): There is no practical difference between the two different forms by the TW and KR glyph.
image

Attached are the design of the glyphs in the Unicode Code Charts:
image
which indicates that the touching of the top right and bottom right components are also acceptable for Taiwan.

The counter for the top right hand component of the KR glyph is narrower and more in-line with the overall design of Source Han Serif. Thus, the glyph for KR could replace the one used for TW.

For U+6241(扁), U+8759 (蝙) and U+9A19 (騙), the TW glyph is already shared with KR. In all other cases, stroke differences cause them to be disunified.

@kenlunde kenlunde self-assigned this Apr 11, 2017
@hfhchan
Copy link
Author

hfhchan commented Apr 11, 2017 •
edited
Loading

image
No practical difference for U+6C35 (氵) -- exact same glyph offset by a few pixels only.

@kenlunde kenlunde changed the title Consolidation of Glyph Sharing Suggestions Consolidation of Glyph Sharing Suggestions (TO BE CLOSED) Apr 11, 2017
@kenlunde kenlunde mentioned this issue Apr 11, 2017
Open
@kenlunde kenlunde changed the title Consolidation of Glyph Sharing Suggestions (TO BE CLOSED) Consolidation of Glyph Sharing Suggestions (See Issue #38) Apr 11, 2017
@kenlunde
Copy link
Contributor

Consolidated with Issue #38 (so that I can better track and respond to such issues).

@kenlunde kenlunde mentioned this issue Apr 29, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kenlunde kenlunde

Labels
consolidated suggestion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kenlunde @hfhchan