-
Notifications
You must be signed in to change notification settings - Fork 62
Translations: fonts that support other languages (specifically Japanese) #504
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
Comments
Here is a sample of the Warnings that appear during building:
|
@tkoyama010 do you happen to know which fonts might be ideal to support Japanese characters? We can vendor another font to support what is missing, potentially. 🙌🏻 |
Our current font config in CSS:
Since Poppins does not support Japanese and we don't specify any other option, the browser is selecting a font from the sans-serif family. That would explain why the fonts in Linux, Mac and the font picked during the build in sphinx are all different. |
I've posted about this issue on Slack. Let's give it a few days, and if no one replies there or knows, I can then post on social. surely someone else can help! OR we can try what i found below: This font (Noto Sans Japanese) - https://fonts.google.com/noto/specimen/Noto+Sans+JP?preview.text=noto |
i figure the technology wizards in this group can figure out how to embed the font, but also just sharing a cool tool i like - this thing makes it very easy to embed a google font without leaking information to google on every page load :) generates the download for you and the css to just copy/paste : https://gwfh.mranftl.com/fonts omg font decisions are so hard to make especially when u don't read the language, i have no idea what looks good in a Japanese font! that Noto Sans looks good to me but also i have no frame of reference. |
Someone reached out to me because I'm learning Japanese at the moment asking for me to provide my opinion here between Noto Sans JP and M Plus. For me as a learner, Noto Sans JP is better because it's more simple. The M Plus has a few extra accents that make it trickier for a learner to understand. Granted, I doubt they're an issue for native speakers. I also asked a Japanese friend and they said they prefer Noto Sans as well. From the few times I've worked with Japanese computers in my IT roles, most windows users just use the default font that comes with the Windows IME keyboard/language pack. But that's my 2 cents as a foreigner so take my comments with a grain of salt, hopefully more native speakers can provide better feedback |
@all-contributors please add @ZacWarham for idea, review @ZacWarham thank you so much for this. It seems like we might have a consensus here around trying Noto Sans JP! Also @sneakers-the-rat - that site is awesome! It will make the vendoring part a lot easier. I am going to create a subissue here to vendor and use Noto Sans JP as a fall back!! And link to that helper site too!! |
I've put up a pull request to add @ZacWarham! 🎉 |
Comment from my Japanese friend who does Japanese <> English translations
|
https://mplusfonts.github.io/ is awesome! |
During our sprint today, @flpm noticed that an error popping up with the packaging guide build (specific to Japanese translation) might be a font / missing character issue.
By default we are using the Google Font Poppins which does NOT have a Japanese character base. We might want to vendor another font, that supports Japanese and add it as an fallback to our css styles
font-family: "Poppins", san-serif
and maybe instead we vendor another font and do
font-family: "Poppins", "another-font", san-serif
The text was updated successfully, but these errors were encountered: