
Making the transition to web design from print design was a welcomed change for me. Although the web is far more technical, print is much less forgiving. I do still design printed materials, but the days of eating the cost to reprint a job for having a one character typo are long gone.
After switching camps I quickly noticed that I wasn’t able to use all of my pretty (and expensive) fonts on the web pages I created. This is because a site visitor can not see the font you are using unless he has that font installed on his machine. So, for many years all we could do was specify the desired font and then set a few backups, like so (a generic CSS style):
.hope_and_pray_the_user_has_my_desired_font_choice {
font-family: "Bodoni", "Garamond", Georgia;
}
Referring to the CSS snippet above, if the visitor has the font Bodoni it will be used but if she doesn’t Garamond will be used. If she doesn’t have Garamond either, Georgia will be displayed as a last resort.
The next major breakthrough was sIFR, or Scalable Inman Flash Replacement. This technology allowed a very tech-savvy web developer to implement their font of choice by embedding it in a special Flash file. The chosen font could then be called into a web page to replace the default.
However, sIFR is not a perfect solution namely because it requires the use of Flash and it can be a royal pain in the ass to implement and style correctly. Flash is unsupported by most (if not all) mobile devices so using it for anything mission critical is a very BAD idea. Also, anyone familiar with Flash probably wouldn’t use it as their first choice for doing any kind of type setting. I have implemented sIFR on a few sites and although the result was pleasant, the hassle of doing so was not.
Next, designers discovered they could load fonts into web pages using the @font-face property. I could explain @font-face here, but Tjobbe Andrews of Milton Bayer has done such a nice job already. So check out his explanation of @font-face for a very thorough introduction. Just know that to use @font-face legally, you need a web license for the font.
Well, web designers everywhere now have a reason to rejoice. Google isn’t waiting around for the w3c to solve the font-licensing issues. They went ahead a created a repository of open-source web fonts for everyone to use. Here’s a simple way to use a font from the Google Web Fonts library:
- Include the web font as a stylesheet. We are using Buda here, but you can change it to whatever you want:
<link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Buda">
- Use the font in a CSS style. We are using it on the paragraph tag:
p {
font-family: 'Buda', serif;
font-size: 12px;
}
- That’s it! In our example, all paragraph tags will now use Buda! For more info on using Google Web Fonts read Getting Started (Google Fonts API).
Now there’s no excuse to keep kicking it old school. Most of the major font foundries are getting with the program. They are now making web versions of their fonts and usually include them free of charge when you purchase the standard font license. And many thanks to Google for extending our font repertoire!
Hopefully, we won’t see the likes of Verdana, Georgia, Times New Roman, Arial or Trebuchet until designers decades from now are looking to exhibit a retro feel in their work. I would have included Helvetica, but I don’t think designers will be dropping that one anytime soon.