-
Notifications
You must be signed in to change notification settings - Fork 92
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
Missing Google font subsets #21
Comments
Yes, please add support for latin-ext or other character sets! |
PRs welcome! Won't have time to work on this anytime soon. |
Latin only :( I wish it was mentioned in the README of corresponding npm packages, since they look genuinely useful (I discovered this project using the npm package search). Then again, doing a pull request stating "This here npm package is for use in 1985 and earlier, when everything was set in One True Americanski Language" in every README is kinda passive-aggressive. What an unfortunate turn of events. I hope you resume the development of this project eventually, since there is clearly a demand for it. |
Hey, I can see stagnation here, maybe some brainstorm is needed? What about adding additional entrypoints like |
@erykpiast Adding additional entry points has been my main idea as well. @mvasilkov happy to take a PR adding a less passive-aggressive notice that the packages are latin only. |
@KyleAMathews To be honest I cannot find any other idea, this one seems straightforward. Shall we go on with this? |
Yes please, we need Latin Extended and the Cyrillic and/or Cyrillic Extended |
Guys, I've made PR for this: #45. It's very dirty but works. I guess it'd be nice to have some tests, I didn't write any though, as there was no infrastructure prepared for this so far and I didn't want to make it too big. |
Hello all. |
CSS unicode-range could be used to optimize download size. |
There is a fork of typefaces project which supports different character sets: https://github.com/bedlaj/openfonts @koutsenko You can use @openfonts/roboto_cyrillic or @openfonts/roboto_all packages as a substitutes to |
Absolutely, here's how Google Fonts splits glyph ranges up in separate small files:
Browser will lazy-load the required woff2 file only on demand. I.e., if a website doesn't use greek letters, the greek woff2 files will not be requested at all. These few additional bytes of CSS are no problem bandwidth wide. The benefit of supporting more glyphs than latin only are on the other hand tremendous. |
typefaces-*
packages only support Latin while Google fonts support many different subsets. The project relies onhttps://google-webfonts-helper.herokuapp.com/api/fonts/
which only downloads Latin fonts by default.The text was updated successfully, but these errors were encountered: