3 ms·

The updates are specifically to improve the rendering at smaller font sizes.

• mnicole 14y ago
  Guess I'm confused then, because looking at them at the small sizes on the site itself, they have these issues.
  • ZeroGravitas 14y ago
    It's the old "fuzzy approximation of real shape vs sharp representation of a shape altered to look sharp at low pixel density" argument all over again, which last flared up when Apple released Safari for Windows. http://www.codinghorror.com/blog/2007/06/font-rendering-respecting-the-pixel-grid.html http://www.codinghorror.com/blog/2007/06/font-rendering-resp... If you assume the other side is simply "doing it wrong" then conversation rapidly goes downhill, it's an engineering trade-off. I personally like the fuzzy side of things, and I thought that they'd added hinting (possibly via ttfautohint) to make them sharp at small sizes on platforms than need hints (i.e. Windows basically). But, possibly to make it easier for people to contribute, they've conformed the icons to a grid at all sizes, and for all platforms, instead. It's possible this was done to appease the Bootstrap devs, who were very picky about small scale rendering being pixel perfect and gave that as a reason for sticking with glyphicon hand drawn pngs. But its seems those same devs have chosen to go with fuzzy vectors glyphicons for Bootstrap 3. I'll probably go with using those, which is a shame as I like the open contribution model and new license of Font-Awesome better. (Talking of which, how can it be openly licensed via SIL, but still allow glyph contributers to keep CC-BY-SA?)