I’d like to self-host the fonts for
Right now it goes to
fonts.googleapis.com but I’d like to avoid that. Articles like this argue that there are performance benefits, but my personal motivation was concern that Google Fonts could be used as a tracking tool by Google. Maybe it is not, but hey, it may be faster to self-host anyway.
I was self-hosting fonts when the package website got updated recently, but it was leading to strange visual artifacts in some browsers, like in Chrome on Windows:
So I reverted to using
My approach was to download the file given by https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700,400italic,700italic|Source+Code+Pro and then download the subsequent links. It appears that the initial file varies by browser, so people in Chrome actually needed different font files for some reason.
Can someone figure out:
Why do the files vary by browser? I assume it is some trick to reduce asset size, but what is the nature of that trick?
What is the full range of
User-Agentfields that produce different files? Is it custom for each IE version or something wild?
What are our options for self-hosting in terms of asset sizes? What kind of savings can we get without detecting
This would be great for the Elm websites, but I suspect it’d be useful for lots of people in the community! So please blog about it and share in public spots if you end up looking into this!