No one file is enough

It turns out that if you want to serve up your own webfonts, no single file is ever enough to ensure that the font appears cleanly in every browser and operating system. Instead, generate ttf, eot, svg, and woff files and then define an exhaustive @font-face declaration block.

When I first added a webfont to test double's web site, I didn't realize that only hosting a ".woff" file was not enough to ensure sharp rendering across browsers and operating systems. The font looked fine in Safari on OS X, a little aliased on Chrome on OS X, a jagged mess on Chrome in Windows, and almost invisible Internet Explorer.

As it turns out, browser filetype support is all over the place. Some browsers will (apparently, my knowledge of this is limited to my own frustrations) attempt to degrade gracefully when only a non-preferred filetype is provided. What's really odd, however, is that even if you provide a browser's preferred font filetype, it will sometimes render the font more accurately (with better kerning and anti-aliasing) if you also provide font files it doesn't prefer. Who knows why that is. Browsers.

Anyway, here's how I recommend going about hosting your own fonts on the web.

  1. Find OTF or TTF files for the various weights and styles of your font.
  2. Visit Font Squirrel's webfont generator and upload each weight and style of your font that you'd like, selecting the Optimal option.
  3. Download your kit, then copy all the newly generated eog, .svg., .ttf, and .woff font files into any publicly available path of your web application
  4. Define your @font-face declarations (one per style & weight) to point at your new web font styles.

Here's the CSS declaration I'm currently finding success with:

@font-face {
  font-family: 'Source Sans Pro';
  src: url('..//cdn.testdouble.com/webfonts/sourcesanspro-regular-webfont-b2a134dfdef6ca93147e896c1a0d6e60.eot');
  src: url('..//cdn.testdouble.com/webfonts/sourcesanspro-regular-webfont-b2a134dfdef6ca93147e896c1a0d6e60.eot?#iefix') format('embedded-opentype'),
       url('..//cdn.testdouble.com/webfonts/sourcesanspro-regular-webfont-231c2f10fb1ecdc835471ac3c256cc5c.woff') format('woff'),
       url('..//cdn.testdouble.com/webfonts/sourcesanspro-regular-webfont-55a9ce05023eecff5fef42a6aba66a3b.ttf') format('truetype'),
       url('..//cdn.testdouble.com/webfonts/sourcesanspro-regular-webfont-7b39c122fb3d194b82385b2118a81031.svg#source_sans_proregular') format('svg');
  font-weight: 400;
  font-style: normal;
}

In the above, my CSS is being served from /app/css/fonts.css and my webfonts are in /app/webfonts.

It's also important to specify a font-weight and font-style in accordance with each font file. This step can be a little confusing, as each font creator seems to have their own nomenclature for font weights. But at the end of the day, all that matters is that the font-weight you assign matches whatever weight your CSS specifies.

If you enjoy this post, let us know by twitter or e-mail! If you'd like to discuss it, open an issue on our feedback repo!