3 ms·
Thanks for the heads-up, we'll fix this asap. We've run into this issue before, and it seems to have something to do with the font's Unicode values being "out
by matm 14y ago
Thanks for the heads-up, we'll fix this asap.
We've run into this issue before, and it seems to have something to do with the font's Unicode values being "out of range" on Windows, whatever that means.
- mattl 14y agoYour move from self-hosted WordPress assets to S3 left some weird stray URLs on your blog that you could fix too... http://blog.heapanalytics.com/wp-content/uploads/2013/03/blog_2-26-13_2.png/ http://blog.heapanalytics.com/wp-content/uploads/2013/03/blo... for example. Now can I have an invite? ;) mattl [at] gnu org
- crazygringo 14y agoFWIW, I've worked on projects where we "blacklist" embedded fonts on certain combinations of OS+Browser -- particularly chrome on older versions of windows. Based on the user string, we would serve up a version of the HTML that didn't request the embedded font, and then those users would see Arial instead of, for example, Proxima Nova. Super-annoying to have to deal with. But it works.