Currently there are a few cross-platform compatible fonts that designers can use with the certainty that users have them installed on their system.
Over the years, several alternatives have appeared to let designers add specific fonts to their pages; for example, techniques such as sIFR and Cufón rely on methods that work well in certain situations. These techniques only represent a temporary solution.
The growth of HTML5 and CSS3 have led to the expansion and need for more innovative and thorough website designs. With rapid advancement in web development options, it is time for web typography and font selection to keep pace. Font replacement methods can be an integral element in a designer’s arsenal to fully achieve the desired look and feel of their website.
CSS3 uses a technique called @font-face supported by designers and by the companies that make and license fonts. @font-face lets you embed fonts within a page by declaring the font you want and placing this font on your web server. When a user visits your site, the browser renders the page using this font where specified. This technique is an excellent solution to the problem of uninstalled fonts, but there are complications that require some work. The following sections explain the complications and their solutions.
The initial CSS syntax for @font-face is straightforward. HTML tags currently inherit the font-family properties that are assigned to them in the designers HTML document and CSS style sheet.
@Font-face in a CSS Style sheet looks like this:
@font-face { font-family: Sigmar; }
If you want to display the Sigma font on as many browsers as possible, you need another method to display the font.
@font-face { font-family: Sigmar, Georgia, Palatino, Times New Roman, serif; }
Sigmar is first in the list, but you need to provide alternative fonts in case the user’s browser cannot render Sigmar which is an OpenType font. In this case, Georgia is the first alternative that will show up in browsers if they cannot read Sigmar.
The following table lists the various levels of support for the different font-types:
BROWSER | OTF & TTF | SVG | WOFF | EOT |
IE | IE9 | — | IE9 | IE5+ |
Firefox | FF3.5 | FF3.5 | FF3.6 | — |
Chrome | Chrome 4 | Chrome 0.3 | Chrome 5 | — |
Safari | 3.1 | 3.1 | — | — |
Opera | Opera 10.00 | Opera 9 | — | — |
iOS | — | iOS 1 | — | — |
Android | 2.2 | — | — | — |
OpenType (OTF): a widespread font format heavily supported by the industry and developed as collaboration between Adobe and Microsoft; one of its primary advantages is cross-platform support. Other typesetting features, such as glyph support, make OpenType fonts the primary font choice for professional font designers.
TrueType (TTF): originally developed by Apple computer and later adopted by Microsoft, TrueType fonts are widely used because they are cross-platform compatible and offer sophisticated typesetting controls, such as hinting, a technique that improves the quality of the font in low resolution screens.
SVG: a vector-based format currently supported only by Apple’s iOS for iPod and iPod devices. SVG fonts are text documents that define the font outlines as vector objects within the Scalable Vector Graphic language (SVG).
Web Open Font Format (WOFF): the latest addition to web fonts that can potentially become a standard since it is in the final stages of approval by the World Wide Web Consortium (W3C). WOFF includes the ability to heavily compress font files and optimize them for distribution over an Internet connection.
Embedded OpenType (EOT): a variation on OpenType created by Microsoft and largely supported by Internet Explorer. EOT has several copy protection features built in to prevent copying of fonts.
The Solution? Using a web service to generate multiple fonts.
The @font-face technique requires you to declare multiple font alternatives for maximum compatibility; for example, you need to declare OpenType fonts, Embedded Open Type for Internet Explorer, and SVG for the iOS. If you fail to declare multiple fonts, your website will not be able to be viewed on all browsers. There are web services available that allow you access to fonts in all of the different font types.
Font Squirrel is a popular web service that provides web designers’access to hundreds of fonts. Font Squirrel was created in 2009 and is still active today. New fonts are constantly being added to the website. All the fonts on Font Squirrel are Commercial Free and can be used with the @font-face property. This means that designers do not need to worry about misreading a web font license or picking a font not compatible with @font-face.
The strengths of Font Squirrel.
The cons of Font Squirrel.
There are a few other issues that may make user use complicated.
The Typekit web service has several licensed web fonts available for use from well-known type manufacturers, such as Adobe, Bitstream, Chank, FontFont, and others. Typekitunlike Font Squirrel is not a free service. Interested designers will have to pay a yearly fee for the use of the fonts.
The Strengths of Typekit.
There are a few other issues that may make user use complicated.
Google has a similar system to Typekit called the Google Font API. Like Typekit, all the fonts are hosted on the Google servers. Add references to these in your style sheet, and then use them as needed. Unlike Typekit, these fonts are currently free to use and there are several options in different styles.
The Strengths of Google Font API.
There are a few other issues that may make user use complicated.
Cufón is a website that provides a font replacement technique using a font generator and a rendering engine. It uses JavaScript and vector graphics to convert TTF, OTF, and PFB and postscript fonts to SVG. The conversion process also creates a JavaScript file for you to reference in your HTML.
The Strengths of Cufón.
There are a few other issues that may make user use complicated.
Despite the wonder of Font Squirrel, Typekit, GoogleFont API,Cufón and various other web services, they do not fix all the browser problem presented by @Font face. None of the web services provide a font that can be used across all browsers without a fall back font. Instead these web services work within @Fontface by providing multiple fonts that provide both the right aesthetic appeal and font type that the web owner desires. For web designers who have vision, but lack technical skill and knowledge, you might want to consider enrolling in some local or internet based HTML classes that will allow you to fully utilize the HTML and CSS web sources available to us today.
Nice article, but why didn’t you considered the new H&FJ service named Cloud.Typography (http://www.typography.com/cloud/welcome/)?
It seems a little bit more expensive, but with amazing fonts.
You have old information about WOFF: https://en.wikipedia.org/wiki/Web_Open_Font_Format
Opera & Safari as well as other actual webkit-based browsers supports it.
I’m using WOFF as the only font format because of small size and wide support (who cares about IE <= 8, right?:))
Our exact process, its technically not font replacement but just calling a font locally from the web server instead of accessing the local font file on a users computer to render in browser when specified in the css.
Thank you for your thoughts on css fonts. There also some other tools like WhatFont extension for Chorme browser that can help you find and replace fonts on the fly on your website … :)