3 ms·

Is it just me or have people stopped testing how the font renders on anything other than a Mac? Don't people believe in cross-platform readability anymore? The

Is it just me or have people stopped testing how the font renders on anything other than a Mac? Don't people believe in cross-platform readability anymore? The font being used looks terrible on a Windows machine (Win 7 with Chrome at 100% zoom). http://i.imgur.com/OmWJiyn.png http://i.imgur.com/OmWJiyn.png

Xymak1y 14y ago
Same here.
tferris 14y ago
Oh this looks really like living crap. But I'have to admit with everything non-commercial I develop I give a shit on Windows compatibility (it's so hard to test Windows' browsers, either you need some VM running or netbook).
- icebraining 14y ago
  Testing basic stuff like that is easy, just use one of those "website screenshot" services.
  - tferris 14y ago
    is there any free one around?
    - thaumaturgy 14y ago
      http://browsershots.org/ http://browsershots.org/
    - mwilcox 14y ago
      I recommend Adobe BrowserLab.
thekevan 14y ago
Looks fine for me on the latest FF in XP. Also looks good on Chrome 25 in Ubuntu--which I also bet it wasn't tested on.
- chc 14y ago
  I'm looking at it in Firefox on Windows 7, and while the headline looks OK, the body text is still atrocious. The tops of the capital letters are all fug beyond belief.
JacksonGariety 14y ago
We decided to go with .woff on the font cause it's the trendy, cross-browser thing to do. We now know Windows won't anti-alias .woff files. In the next commit I'll add fallback to .ttf or .otf for Windows machines.
- thaumaturgy 14y ago
  Oh! Oh! This is something I actually know something about! So, if you're willing to use something like FontSquirrel (http://www.fontsquirrel.com/fontface/generator http://www.fontsquirrel.com/fontface/generator) to convert a single font file into four different formats, and if you're willing to store all four formats on your site, then you can fix your font problem by loading the .eot version of it first in your stylesheet, followed by a "?". Like so: @font-face { font-family: 'Crimson Text'; src: url('/style/v6/fonts/crimsontext-regular.eot?') format('embedded-opentype'), url('/style/v6/fonts/crimsontext-regular.woff') format('woff'), url('/style/v6/fonts/crimsontext-regular.ttf') format('truetype'), url('/style/v6/fonts/crimsontext-regular.svg#svgFontName') format('svg'); } The browsers I've tested on so far will only load the file they're interested in, so it doesn't add much overhead in requests. There's a breakdown of the hows & whys of this method at http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax http://www.fontspring.com/blog/the-new-bulletproof-font-face...; I think that's the most current method in use. It seems to work well.

Xymak1y 14y ago

Same here.

tferris 14y ago

Oh this looks really like living crap. But I'have to admit with everything non-commercial I develop I give a shit on Windows compatibility (it's so hard to test Windows' browsers, either you need some VM running or netbook).

icebraining 14y ago
Testing basic stuff like that is easy, just use one of those "website screenshot" services.
- tferris 14y ago
  is there any free one around?
  - thaumaturgy 14y ago
    http://browsershots.org/ http://browsershots.org/
  - mwilcox 14y ago
    I recommend Adobe BrowserLab.

thekevan 14y ago

Looks fine for me on the latest FF in XP. Also looks good on Chrome 25 in Ubuntu--which I also bet it wasn't tested on.

chc 14y ago
I'm looking at it in Firefox on Windows 7, and while the headline looks OK, the body text is still atrocious. The tops of the capital letters are all fug beyond belief.

JacksonGariety 14y ago

We decided to go with .woff on the font cause it's the trendy, cross-browser thing to do. We now know Windows won't anti-alias .woff files. In the next commit I'll add fallback to .ttf or .otf for Windows machines.

thaumaturgy 14y ago
Oh! Oh! This is something I actually know something about! So, if you're willing to use something like FontSquirrel (http://www.fontsquirrel.com/fontface/generator http://www.fontsquirrel.com/fontface/generator) to convert a single font file into four different formats, and if you're willing to store all four formats on your site, then you can fix your font problem by loading the .eot version of it first in your stylesheet, followed by a "?". Like so: @font-face { font-family: 'Crimson Text'; src: url('/style/v6/fonts/crimsontext-regular.eot?') format('embedded-opentype'), url('/style/v6/fonts/crimsontext-regular.woff') format('woff'), url('/style/v6/fonts/crimsontext-regular.ttf') format('truetype'), url('/style/v6/fonts/crimsontext-regular.svg#svgFontName') format('svg'); } The browsers I've tested on so far will only load the file they're interested in, so it doesn't add much overhead in requests. There's a breakdown of the hows & whys of this method at http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax http://www.fontspring.com/blog/the-new-bulletproof-font-face...; I think that's the most current method in use. It seems to work well.