Our great sponsors
-
Google Fonts
Font files available from Google Fonts, and a public issue tracker for all things Google Fonts
-
google-webfonts-helper
A Hassle-Free Way to Self-Host Google Fonts. Get eot, ttf, svg, woff and woff2 files + CSS snippets
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Even worse than what you mentioned, they sometimes update the fonts and refuse to offer any way to version lock them. Really. Check out this issue for more details: https://github.com/google/fonts/issues/1307. It's all a lot of magic for very little gain.
I wrote https://github.com/mmastrac/webfont-dl for this purpose a few years back (although it was designed more for the command line). It still works, though I probably should change the defaults to be a little more modernized.
Apparently the issue with Exo 2 is an upstream issue in Exo 2 that mostly affects macOS Browsers: https://github.com/NDISCOVER/Exo-2.0/issues/11
(Possibly Google Fonts is serving different CSS specific to macOS user agents as a current workaround.)
Fontsource (which is similar to this tool but packaged as npm packages and I found mentioned in another thread here) is similarly aware of the issue and suggests the current macOS workaround is to enable it as a Variable Font with slightly different CSS: https://github.com/fontsource/fontsource/issues/243
(They don't enable fonts as variable fonts in their default CSS because of different browser issues with variable fonts.)
Apparently the issue with Exo 2 is an upstream issue in Exo 2 that mostly affects macOS Browsers: https://github.com/NDISCOVER/Exo-2.0/issues/11
(Possibly Google Fonts is serving different CSS specific to macOS user agents as a current workaround.)
Fontsource (which is similar to this tool but packaged as npm packages and I found mentioned in another thread here) is similarly aware of the issue and suggests the current macOS workaround is to enable it as a Variable Font with slightly different CSS: https://github.com/fontsource/fontsource/issues/243
(They don't enable fonts as variable fonts in their default CSS because of different browser issues with variable fonts.)
Related posts
- Just launched my first svelte project! An opensource alternative to Google Fonts, with a focus on variable fonts. Coming from a React background Svelte has been absolutely amazing to work with.
- Variable Fonts
- Fontsource
- Font Source – a privacy-friendly Google Fonts alternative
- justFoundOutGoogleFontsCollectsUserIPs