3 ms·
Completely unrelated, but how does that Museo Sans render so nicely on Win/Chrome? Usually font rendering on Chrome is horrible. Now, checking Typekit, it seems
by Geee 15y ago
Completely unrelated, but how does that Museo Sans render so nicely on Win/Chrome? Usually font rendering on Chrome is horrible. Now, checking Typekit, it seems some fonts have nice anti-alias, while some not. Where's the difference?
- dpcan 15y agoYou may want to consider asking this on Stackoverlfow.com
- karipatila 15y agoI think it's in the TrueType hinting: http://blog.typekit.com/2011/03/16/skolar-web-hinted-for-better-screen-rendering/ http://blog.typekit.com/2011/03/16/skolar-web-hinted-for-bet...
- joshuacc 15y agoI believe that is due to the work they explain in this blog post: http://blog.typekit.com/2011/07/26/new-from-typekit-improved-font-rendering-on-windows/ http://blog.typekit.com/2011/07/26/new-from-typekit-improved...
- eps 15y agoThis and the fact that Jos, the Museo designer, has always been very web-oriented and paid a lot of attention to the rasterization issues. His fonts are all really well hinted to begin with, and then there is Typekit's conditional .ps serving on top of that.
- Geee 15y agoThanks a lot, I think that's exactly what's happening here.