4 ms·

I am baffled. OpenSans renders fine in IE and Firefox, but Chrome doesn't do it. Here is what I get on the WP page: http://imgur.com/XgmEN9P http://imgur.com/

by pgrote 14y ago

I am baffled. OpenSans renders fine in IE and Firefox, but Chrome doesn't do it. Here is what I get on the WP page: http://imgur.com/XgmEN9P http://imgur.com/XgmEN9P It is the same for every other site that uses opensans. Windows 7, Chrome 26.0.1410.64 m, Font Size: Medium, Page Zoom, 100%. Any ideas?

pgrote 14y ago
I did fine a bug for Chrome. https://code.google.com/p/chromium/issues/detail?id=137692 https://code.google.com/p/chromium/issues/detail?id=137692 Looks like the workaround is to turn off ClearType.
mmahemoff 14y ago
Seems fine on Chrome 26 in OSX (10.7.5). http://i.imgur.com/RTARq61.png http://i.imgur.com/RTARq61.png
- pgrote 14y ago
  Thanks for the comparison ... and the feelings of envy. lol It really is a gorgeous looking font. For the longest time I just though trendy designers were picking the worst looking font.
  - mattengi 14y ago
    http://imgur.com/j7TGaA9.png http://imgur.com/j7TGaA9.png from ubuntu with infinality freetype patch.
    - tasuki 14y ago
      That doesn't look right. The font-weight of the heading is supposed to be 300 and is at least 400 in your screenshot. Chromium on out-of-the-box ubuntu seems better: http://i.imgur.com/0WIO2t6.png http://i.imgur.com/0WIO2t6.png
Bezvezenator 14y ago
> Any ideas? Chrome uses GDI for font rendering while Firefox and IE use DirectWrite.
- iaskwhy 14y ago
  Is there any relation between the font rendering engine and the font being hinted for Windows? When I saw the title of the article on the page my first thought was the font not being properly hinted for Windows.
  - Bezvezenator 14y ago
    You're right, it most likely means font is not hinted for windows. That looks horrible when rendered with GDI at smaller sizes because GDI hammers everything into pixel grid and doesn't do vertical anti-aliasing. DirectWrite features anti-aliasing in both directions and doesn't try to fit everything into pixel grid. Because of that non-hinted fonts look much better, although blurrier, with DW than with GDI.

by pgrote 14y ago

pgrote 14y ago

I did fine a bug for Chrome. https://code.google.com/p/chromium/issues/detail?id=137692 https://code.google.com/p/chromium/issues/detail?id=137692 Looks like the workaround is to turn off ClearType.

mmahemoff 14y ago

Seems fine on Chrome 26 in OSX (10.7.5). http://i.imgur.com/RTARq61.png http://i.imgur.com/RTARq61.png

pgrote 14y ago
Thanks for the comparison ... and the feelings of envy. lol It really is a gorgeous looking font. For the longest time I just though trendy designers were picking the worst looking font.
- mattengi 14y ago
  http://imgur.com/j7TGaA9.png http://imgur.com/j7TGaA9.png from ubuntu with infinality freetype patch.
  - tasuki 14y ago
    That doesn't look right. The font-weight of the heading is supposed to be 300 and is at least 400 in your screenshot. Chromium on out-of-the-box ubuntu seems better: http://i.imgur.com/0WIO2t6.png http://i.imgur.com/0WIO2t6.png

Bezvezenator 14y ago

> Any ideas? Chrome uses GDI for font rendering while Firefox and IE use DirectWrite.

iaskwhy 14y ago
Is there any relation between the font rendering engine and the font being hinted for Windows? When I saw the title of the article on the page my first thought was the font not being properly hinted for Windows.
- Bezvezenator 14y ago
  You're right, it most likely means font is not hinted for windows. That looks horrible when rendered with GDI at smaller sizes because GDI hammers everything into pixel grid and doesn't do vertical anti-aliasing. DirectWrite features anti-aliasing in both directions and doesn't try to fit everything into pixel grid. Because of that non-hinted fonts look much better, although blurrier, with DW than with GDI.