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

IBM Plex Sans JP: Initial reactions #387

Open
johnnyshields opened this issue Jul 24, 2021 · 10 comments
Open

IBM Plex Sans JP: Initial reactions #387

johnnyshields opened this issue Jul 24, 2021 · 10 comments

Comments

@johnnyshields
Copy link

johnnyshields commented Jul 24, 2021

Overall, I'm blown away by how good IBM Plex Sans JP is--it's an instant classic.

If I had to make criticisms:

  • the hiragana characters (あいうえお etc.) feel slightly too small (relative to kanji) and it gives the feeling of broken/disjointed kerning in some places. Some of the ascents/descents don't feel correctly aligned between neighboring characters. Compare vs TBUD Gothic, the latter just feels more snug:
    image

  • in katakana, consider adding clear/more even separation on the diacritic marks. Compare vs TBUD Gothic:
    image

  • is easier to read with the 2nd stroke intersecting the 1st stroke
    image

  • , etc. the stroke serifs feel a bit too sharp. I get that these are "plex-ish" but would experiment with a softer angle / shorter stroke. Would recommend to omit it on
    image

  • The kanji feels too wide and hard to read.
    image

  • The kanji is easier to read with a steeper oriented accent stroke.
    image

Text comparison:
image

(raw text)
日本語専攻学科や教師養成課程、修士課程などの立ち上げ支援や、中等教育段階での日本語導入支援のほか、現地の日本語教師への助言・指導、カリキュラム編成や教材作成等について支援を行う。また、派遣先国あるいは周辺国、地域の日本語教師を対象とした研修会の実施、教師間のネットワーク形成、日本語教授法や日本語教材作成に関する助言・指導等を行う。
利便性向上、利用分析および広告配信等のためにクッキーを利用してアクセスデータを取得しています。詳しくは「データ利用について」をご覧ください。オプトアウトもこちらから可能です。
@mjabbink
Copy link
Contributor

FYI @sandoll-inc

@sandoll-inc
Copy link

Relatively, JP is designed so that dots and strokes fill character face frames compared to other JP fonts.
This is to keep the letters homogeneous in size and to use small spaces efficiently. Of course, we also thought it was important to reflect IBM Plex's legacy, "Engineering Respecting the trajectory of Writing.”
Thank you for your detailed response to Plex JP’s design. We will collect your opinions on the design for the time being.

@johnnyshields
Copy link
Author

johnnyshields commented Aug 2, 2021

@sandoll-inc thank you for your comments:

Relatively, JP is designed so that dots and strokes fill character face frames compared to other JP fonts.

Specifically regarding hiragana, the two examples above (TBUD Gothic Std R and MPlus 2) both do a better job filling the frame, and the stokes are better aligned between neighboring characters. I particularly encourage you to study TBUD Gothic from Morisawa, I feel it is a good model for Plex.

@mjabbink
Copy link
Contributor

Top: IBM Plex Sans JP
Middle: Hiragino Kaku gothic(MacOS bundle font)
Bottom: Kozuka gothic(Adobe bundle font)

M2

Still looking into some other feedback mentioned above.

@mjabbink
Copy link
Contributor

and are more a concern and I think in future updates we could address these.

@johnnyshields
Copy link
Author

@mjabbink In your examples of katakana it still feels like Plex "fills the frame" less than the other fonts.

@mjabbink
Copy link
Contributor

mjabbink commented Aug 19, 2021

In reviewing some of the feedback the Sandoll designers and I feel the current Plex JP designs are very valid as they are. We have documented this feedback and will revisit as we collect more feedback and assess again in the near future but for now we will maintain these designs. We are limited in budget and have Chines to complete and also will prioritize adding a CJK JP and KR set with shared baseline eights and the same scale Latin.

We will wait and collect a larger sum of glyphs to refine so the above feedback may be included at that time.

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

4 participants
@johnnyshields @mjabbink @sandoll-inc and others