-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add support for Literata #58
Comments
You mean, in docs (https://github.com/readium/readium-css/blob/master/docs/CSS10-libre_fonts.md) or in RCSS itself? → Right now, the only fonts we’re “embedding” are the a11y-specific fonts, see. https://github.com/readium/readium-css/tree/master/css/dist/fonts |
What's your take on this? I think it might be worth extending font embedding to a subset of fonts from various families that we could vouch for. |
I've just tried |
Hmmm as far as I can remember, there’s been 2 major factors “preventing” us from embedding fonts until now:
In any case I must test it with our own tool though, to make sure it is rendered properly on all platforms – it’s not yet available on Google Fonts so that’s quite a significant signal to take into account. So I’m definitely not against a subset of fonts we could vouch for but the 2 constraints are tricky to say the least – kerning, hinting, support, etc. can be improved dramatically on updates so we probably want to avoid updating the repo every time a font is updated. |
Hmmm interesting, I’m running into various issues at least on MacOS with the old deliverables (both OTF and TTF). Safari will simply refuse to render it, Chrome is OK, some glyphs are buggy in Firefox (esp. Cyrillic + Greek). All latest versions. I’d recommend we wait for google fonts to upload it as you must currently build latest from the repo’s src in order to check if those issues are resolved. Here’s the generated report from Chrome, looking good in terms of support and OT features though. And comparison with Georgia: |
So yeah it looks like I have a system-wide issue with user-installed local fonts in Mojave (MacOS 10.14.2). Those fonts appears OK everywhere, including word processors, DTP apps, etc., except Safari. So this is not about Literata. As every user-installed local font I’m testing fails. Those ones worked when I made the md doc, and they’re still working otherwise. I’ve tried a simple webpage and could get the same result. Preinstalled (system) local fonts are OK: User-installed local fonts are also OK in Chrome and Firefox: However, Firefox has an issue with some glyphs e.g. "ϐ" and "ϕ": Those are OK in Chrome: |
So research tells me Safari nuked user-installed local fonts because of fingerprinting (tracking). If you're using |
I stumbled across this issue by chance, but one solution might be to establish a local server that proxies requests for those user-installed fonts. |
@HadrienGardeur I’m postponing this a little more I’m afraid. They added a list of required changes to the GitHub repo yesterday: https://github.com/googlefonts/literata/blob/master/NOTES_JS.txt and there’s still no sign of it on Google Fonts, even on Early Access – so my assumption is that they don’t feel it can be distributed yet. |
Literata is now available on Google Fonts: https://fonts.google.com/specimen/Literata Might be worth revisiting this issue? |
Ah yes thanks for spotting the availability. I’ll add to docs first, but re.
I guess this is probably a good candidate for next week’s call? What do people think? |
I'm submitting a feature request.
Short description of the issue/suggestion:
Literata is a high quality font for long form reading designed initially for Google Play Books: https://github.com/googlefonts/literata
It was recently open sourced and would make a wonderful addition to Readium CSS and test apps.
The text was updated successfully, but these errors were encountered: