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 #38

Open
kenlunde opened this issue Apr 11, 2017 · 21 comments
Open

Consolidation of Glyph Sharing Suggestions #38

kenlunde opened this issue Apr 11, 2017 · 21 comments
Assignees
@kenlunde
Labels
suggestion

Comments

@kenlunde
Copy link
Contributor

kenlunde commented Apr 11, 2017 •
edited
Loading

This issue is meant for tracking and submitting suggestions for glyph sharing changes that result in glyphs no longer being necessary. Any such changes in Version 1.xxx will be implemented via mapping changes, and the unused glyphs will be targeted for removal as part of the Version 2.000 update. Issues that were submitted before this consolidation issue was opened are referenced by issue number.

Note To Self: I have not yet checked this report and after.
@kenlunde kenlunde self-assigned this Apr 11, 2017
This was referenced Apr 11, 2017
Open
Closed
Closed
@hfhchan
Copy link

hfhchan commented Apr 12, 2017

image

U+81EC CID 34088 is nearly the equivalent to CID 34089.

@hfhchan
Copy link

hfhchan commented Apr 14, 2017

image
U+6DE6 24166 === 24165

@hfhchan
Copy link

hfhchan commented Apr 14, 2017

image
U+6DFC 24211 = 24212

@hfhchan
Copy link

hfhchan commented Apr 14, 2017

image
U+6E23 (JP) 24272 === 61621

@kenlunde
Copy link
Contributor Author

@hfhchan: uni6E23-JP (CID+61621) and uni6E23uE0101-JP (CID+24272) are intentional duplicate glyphs that shall remain for Adobe-Japan1 IVD collection compatibility.

@hfhchan
Copy link

hfhchan commented Apr 14, 2017

@kenlunde should they be mapped to the same CID though? as they look nearly identical

@hfhchan
Copy link

hfhchan commented Apr 14, 2017

image
U+6EA3 24499 === 24498 (latter of which is likely to be going away as it is outside the scope of JP subset)

@kenlunde
Copy link
Contributor Author

@hfhchan: About U+6E23 渣, the duplicate glyph shall remain for reasons already stated. Derivative implementations are free to do what they choose.

@hfhchan
Copy link

hfhchan commented Apr 14, 2017

image
U+6EB4 24531 === 24530

@hfhchan
Copy link

hfhchan commented Apr 15, 2017 •
edited
Loading

@kenlunde: Ah, sorry I had not realized (until just now) that since GSUBs are done on a glyph basis, separate glyph IDs have to be maintained to make sure glyphs for IVD don't get substituted away. Sorry for the churn

This was referenced Apr 16, 2017
Open
Open
@hfhchan
Copy link

hfhchan commented Apr 21, 2017

image
No observable difference exists for the JP and CN variants of U+62FF and U+6301.

@kenlunde
Copy link
Contributor Author

@hfhchan: Noted. The CN glyphs for U+62FF 拿 and U+6301 持, uni62FF-CN and uni6301-CN, respectively, will be removed in Version 2.000.

@kenlunde kenlunde mentioned this issue Apr 22, 2017
Closed
@jimmymasaru
Copy link

Glyphs for 猪, uni732A-CN and uni732A-JP can be shared.

@tamcy
Copy link

tamcy commented May 11, 2017 •
edited
Loading

In this report, CN implies TW unless explicitly mentioned.

View image

sharable1

旦 (U+65E6) : CN = JP
昧 (U+6627) : CN = JP
暖 (U+6696) : CN = JP
暴 (U+66B4) : CN = JP
曝 (U+66DD) : CN = JP
本 (U+672C) : CN = JP
杖 (U+6756) : CN = JP
枳 (U+67B3) : CN = JP
桓 (U+6853) : CN = JP
橙 (U+6A59) : CN = JP
沁 (U+6C81) : CN = JP
淪 (U+6DEA) : CN = JP
瀑 (U+7011) : CN = JP
異 (U+7570) : CN = JP
的 (U+7684) : CN = JP
瞠 (U+77A0) : CN = JP
秘 (U+79D8) : CN = JP
而 (U+800C) : CN = JP
蜀 (U+8700) : CN = JP
鴆 (U+9D06) : CN = JP
黴 (U+9EF4) : CN = TW

Some entries are with doubts:

  • 的 (U+7684): it seems that it's confirmed that the designer intentionally make the width of the two components (白 & 勺) different for CN and JP - CN has a wider 白. Please ignore this one.
  • 鴆 (U+9D06): in ancient writing, the last two strokes of 冘 are connected. Now they are disconnected, and IMHO their distance should be up to the style of the typeface, not a region-specific issue. For instance, "耽 (U+803D)" uses the same glyph for TW and JP, and looks completely fine. But this looks like the exception. Other glyphs, like 沈 and 枕, are separated.
  • 沁 (U+6C81) , 秘 (U+79D8): the discrimination seems intentional - the designer seems to believe that the degree of rotation of the last to dots of 心 is a regional difference, not a typeface design discretion.

As a side note, I found that the KR version of the typeface (which serves a more traditional form of Traditional Chinese characters) more "smooth" to read than the TW version. Despite the glyph difference to comply with regional standard, I found that a number of CN-glyphs tend to push the glyph's 重心 (weight center?) downwards, which I suspect is one of the causes. Refer to 昧,曝,瀑,瞠,秘 in the this reported issue for some obvious examples. But I'm not in the position to comment on this professional matter, I believe it worth further investigation by a more authorized entity.

@tamcy
Copy link

tamcy commented May 11, 2017 

徒 (U+5F92) : CN = JP
走 (U+8D70) : CN = JP
赴 (U+8D74) : CN = JP
起 (U+8D77) : CN = JP (*TW ≠ CN)
超 (U+8D85) : CN = JP
趖 (U+8D96) : CN = JP
View image

sharable2

Notes:

  • 趁 (U+8D81) and 陡 (U+9661) included in the image for reference.
  • For the JP glyph of 趖, vertical strokes of the 走 component are connected, making it inconsistent with other design. 樾 U+6A3E is another example.

u 6a3e

@tamcy
Copy link

tamcy commented May 11, 2017

sharable3

挑 (U+6311) : CN = JP
桃 (U+6843) : CN = JP
矽 (U+77FD) : CN = JP

@hfhchan
Copy link

hfhchan commented May 11, 2017

For 矽 (U+77FD), the TW glyph can be replaced with the JP glyph, while the CN glyph kept for CN only.

It is typical design that the 夕 is widened at the top in CN locales. This is similar to the problem with 多 I reported earlier.

@Explorer09
Copy link

Explorer09 commented May 17, 2017 •
edited
Loading

U+4E0D (不): Two glyphs have identical strokes. Can consider merging. (Or is there any reason to have this minor positioning difference?)
U+574F (坏): Likewise.
U+4E15 (丕): If Source Han wishes to follow the TW MoE glyph (note 1), just like in U+4F3E (伾) and U+576F (坯), then at least be consistent. Let the vertical stroke barely touch the horizontal base.
note 1: http://language.moe.gov.tw/001/Upload/files/SITE_CONTENT/M0001/SUNGTI/as1.htm (丕 Number 100013)

selection_308
)

@Marcus98T
Copy link

Marcus98T commented Oct 29, 2018 •
edited
Loading

Remove the JP glyph for U+6EA3 溣, uni6EA3-JP.

I suggest you remove the CN glyph instead because the JP looks aesthetically better, then map the JP glyph to the CN, TW and HK locale.

Edited my comment because I was a bit rude earlier, but my suggestion remains intact. My apologies.

@kenlunde
Copy link
Contributor Author

@Marcus98T Thank you. We'll take this under advisement.

@lapomme
Copy link

lapomme commented Jan 20, 2020

The CN glyph for 博 can be replaced with the KR glyph.
image
(KR left, CN right)

@Marcus98T Marcus98T mentioned this issue Nov 15, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kenlunde kenlunde

Labels
suggestion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@tamcy @Explorer09 @kenlunde @hfhchan @Marcus98T @jimmymasaru @lapomme