adobe-fonts / source-han-serif

Source Han Serif | 思源宋体 | 思源宋體 | 思源宋體 香港 | 源ノ明朝 | 본명조
https://adobe.ly/SourceHanSerif
Other
8.17k stars 644 forks source link

[Unnecessary] Proportional Kana and the fluency of horizontal reading. #22

Closed ShikiSuen closed 7 years ago

ShikiSuen commented 7 years ago

I am wondering whether the kana of SHSerif is mostly optimized for vertical texts (looks really beautiful to me). However, I couldn't find a way (like that in SHSans) to enable proportional kana for SHSerif at this moment. I am afraid it is not fair to the designer for leaving such question here or giving my opinions to this question until there is an approach to enable proportional kana.

kenlunde commented 7 years ago

Applying the 'palt' (H) or 'vpal' (V) GPOS features will enable proportional kana, and further enabling 'kern' (H) or 'vkrn' (V) will enable kerning, which mainly covers kana and punctuation. Actually, enabling 'kern' (H) or 'vkrn' (V) should automatically enable 'palt' (H) or 'vpal' (V), because the values specified in 'kern' (H) or 'vkrn' (V) assume that 'palt' (H) or 'vpal' (V) are enabled. Making the glyphs for kana proportional by default, or via separate glyphs, is a nonstarter for this project. Oh, and like Source Han Sans, all kana have separate horizontal and vertical forms, and not just the small kana.

ShikiSuen commented 7 years ago

@kenlunde Thanks for your confirmation. I finally found that it is the bug in Apple Pages 6.1 (4328) that its "typography options" does not show any access to those OpenType features you addressed just now. The TextEdit.app shipped with macOS 10.12.4 could do this, and I found that it looks consistent under horizontal mode with proportional kana enabled.

image

This makes this issue topic unnecessary to me anymore. You may think of closing this case if you feel necessary.

ShikiSuen commented 7 years ago

Oh. My current point (hope that it is right): The horizontal kana in SHSans is optimized for proportional kana only and does not look consistant on occasions without access to east-asian OpenType features. However, similar to SHSans, SHSerif has insufficient CID slots for horizontal kana glyphs under default monospace mode (with no east-asian OpenType features enabled).

Maybe this issue needs to be marked as "as designed".

ShikiSuen commented 7 years ago

@kenlunde Here comes another question (which I'm afraid that it is not important enough to post as another single issue):

Most computer users in Japan uses Microsoft Windows. It ships "MS P 明朝" as default serif font for Microsoft Office and Windows. There is no doubt that this is the most famous computer Mincho font in Japan. This font uses proportional kana as default. Does this lead to the essense of enabling proportional kana as default in SHSerif? Or do you think further marketing research / survey needs to be done to see whether more people prefer the monospaced "MS 明朝" instead?

P.S.: I am afraid that monospaced kana only makes horizontal Japanese text look inconsistent (with unnecessary spaces between kana glyphs) for most east-asian users who read texts mixed with Japanese, especially that serif fonts are not the primary choice of UI fonts of operating systems in these days. For those people who prefer monospaced kana (and usually also monospaced latin and numeric character glyphs), they could simply enable the "tnum" or "fwid" feature (if the font supports showing monospaced kana specifically through these features).