Web Open Font Format for Firefox 3.6

By

This article was written by John Daggett. John is a Mozilla contributor and has been working hard with font creators and web developers to improve the state of fonts on the web. This article is a high-level overview of whats different and shows some examples of WOFF in use. A full list of other supporting organizations can be found at the official Mozilla Blog.

The WOFF format originated from a collabaration between the font designers Erik van Blokland and Tal Leming with help from Mozilla’s Jonathan Kew. Each had proposed their own format and WOFF represents a melding of these different proposals. The format itself is intended to be a simple repackaging of OpenType or TrueType font data, it doesn’t introduce any new behavior, alter the @font-face linking mechanism or affect the way fonts are rendered. Many font vendors have expressed support for this new format so the hope is this will open up a wider range of font options for web designers.

Details on Differences between TrueType, OpenType and WOFF

First, compression is part of the WOFF format so web authors can optimize the size of fonts used on their pages. The compression format is lossless, the uncompressed font data will match that of the original OpenType or TrueType font, so the way the font renders will be the same as the original. Similar compression can be achieved using general HTTP compression but because compression is part of the WOFF format, it’s simpler for authors to use, especially in situations where access to server configuration is not possible.

Second, the format includes optional metadata so that a font vendor can tag their fonts with information related to font usage. This metadata doesn’t affect how fonts are loaded but tools can use this information to identify the source of a given font, so that those interested in the design of a given page can track down the fonts used on that page. Fonts in WOFF format are compressed but are not encrypted, the format should not be viewed as a secure format by those looking for a mechanism to strictly regulate and control font use.

Note: until Firefox 3.6 ships, users can test the use of WOFF fonts with Firefox nightly builds.

Examples

Below is a simple example that shows how to construct an @font-face rule that links to a WOFF font. To support browsers that only support direct linking to OpenType and TrueType fonts, the ‘src’ descriptor lists the WOFF font first along with a format hint (“woff”), followed by the TrueType version:

Structured this way, browsers that support the WOFF format will download the WOFF file. Other browsers that support @font-face but don’t yet support the WOFF format will use the TrueType version. (Note: IE support is a bit trickier, as discussed below). As WOFF is adopted more widely the need to include links to multiple font formats will diminish.

Other examples below demostrate the use of WOFF formatted fonts but each example has been constructed so that it will work in any browser that supports @font-face, including Internet Explorer.

A font family with multiple faces

Using a Postscript CFF font

African Language Display

Below is an example of how downloadable fonts can be used to render languages for which font support is usually lacking. The example shows the UN Declaration of Human Rights, translated into two African languages, and how these render with default browser fonts vs. with a downloadable font suited for rendering these languages.

Note that in one of these examples that the font size goes from a 3.1MB TTF to a 1MB WOFF font and in the other from a 172KB TTF to an 80KB WOFF file.

Another Postscript CFF font

An example in Japanese

Working With Other Browsers

Firefox 3.6 will be the first shipping browser to support the WOFF format so it’s important to construct @font-face rules that work with browsers lacking WOFF support. One thing that helps greatly with this is the use of format hints to indicate the format of font data before it’s downloaded; browsers that don’t recognize a given format simply skip data in a format they don’t support.

Internet Explorer, including IE8, only supports the EOT font format and only implements a subset of the @font-face rule descriptors. This makes creating cross-platform @font-face rules that work with IE especially tricky. One solution is to make different rules for IE:

One minor downside of this is that IE doesn’t understand format hints and doesn’t parse @font-face URL’s correctly, it treats format hints as part of the URL, so web authors using the @font-face rules above will see the following in their access logs:

IE successfully pulls down and uses the EOT version of the font but also tries to pull down the WOFF font with the format hint included in the URL. This fails and doesn’t affecting page rendering but it wastes valuable server resources. For more discussion, see Paul Irish’s blog post for one interesting workaround.

Another problem is that IE currently tries to download all fonts on the page, whether they are used or not. That makes site-wide stylesheets containing all fonts used on site pages difficult, since IE will always try to download all fonts defined in @font-face rules, wasting lots of server bandwidth.

255 comments

[…] official endoresement and supporting organizations can be found below. Hacks.mozilla.org also has a full post about WOFF implementation for Firefox 3.6 and beyond. We endorse the WOFF specification, with default same-origin loading […]

Using the mentioned Firefox nightly builds you can see what WOFF could look like on a sample page FSI FontShop International designed together with the guys from Edenspiekermann using both FF Meta and FF Meta Serif to endorse the WOFF specification: edenspiekermann.com/woff.

[…] Mozilla has now made a formal statement regarding support for the Web Open Font Format. Plus a nice writeup on the whys and wherefores of WOFF by Firefox font honcho John Daggett. Kudos to all who helped […]

For fonts with a large number of glyphs, it is important to have random access to glyph data, so that you don’t spend the time and memory reading in, say, the 32,000 glyphs of a CJK font of which you only use 100. The Deflate compression is stream based, so if you kept the glyph data compressed and read each glyph as needed, as is common and efficient practice with TrueType and OpenType fonts, then on average you would have to decompress half of the glyph data for each glyph.

Alternatively, upon downloading the font the client could decompress all tables (if you’re uncompressing the glyph data you may as well uncompress everything since for most fonts the glyph data is by far the largest table). But if you uncompress, you may as well rely on the server’s HTTP compression and have a simpler specification. (And if there is no internal compression, the metadata could be put into a new table and WOFF fonts could be compatible with existing TrueType and OpenType.)

What is the recommended or Mozilla way to handle fonts with large glyph data that is compressed internally?

Why no EOT support? Doesn’t that mean that cross-browser font support will be a pipe-dream for the foreseeable future (until IE6, IE7 AND IE8 dies, let alone the other browsers catching up)?

What sort of file format is WOFF? Are Google/Opera/Apple/Microsoft all happy with WOFF, or is it Mozilla proprietary? Does it require dedicated tools or can it be made by hand? Has a spec been published anywhere? Is Mozilla planning making the tools to allow people to convert to and from other font formats? Are the font foundries signed up? What about the font software manufacturers?

@Tom Phelps
Right now the format is relatively simple, tables are either compressed or not, there’s no way to do partial decompression on a given table. CJK fonts are an interesting example, you probably don’t want to send 32,000 glyphs in any form, compressed or not. A format for the future would be one that allowed separate chunks containing sets of glyphs to be downloaded and dynamically linked to the original font when needed. But that’s a very, very tricky problem. Another approach would be to consider a stroke-based format, taking advantage of the common elements in CJK glyphs. But I don’t know of any open format for stroke-based glyphs.

No mentioning of svg fonts is kind of a drawback.
Open and TrueType fonts all good but svgfonts provide a step forward because they’re vector based.
Why doesn’t Firefox support svgfonts, they exist for a while and Opera 10 supports them.

[…] you to upload any font file and convert it not only to EOT, but SVG as well. Then a few days later, Mozilla announces support for the WOFF format in the next release of Firefox, which had only just been announced as a draft. Only days later Font Squirrel added WOFF […]

Followed a link on Lifehacker.com here…why is it that BROWSER DESIGNERS can’t design a website with FLUID WIDTH PAGES? I’ve got a 1680×1050 screen, and the main body of the site barely takes up 50% of the width of my screen. Get a clue, designers!

[…] November 4th, 2009 (3:00pm) Simon Mackie No CommentsTweet This The browser war continues to rage unabated, with the end result being better products for us, the users. This past week has seen significant beta updates to my two favorite browsers: Chrome and Firefox. I’ve been playing with beta 1 of Mozilla’s Firefox 3.6. This new version of Firefox boasts improved performance, personas (the ability to easily switch between different skins for your browser), and updated support for web standards, including support for the Web Open Font Format (WOFF). […]

[…] native video can now be displayed full screen, and supports poster frames.Support for the WOFF font format.Improved JavaScript performance, overall browser responsiveness and startup time.Support for new […]

[…] in their latest versions, support the more common .TTF and .OTF files. Firefox 3.6 will support .WOFF which hopes to be the new standard in web font filetypes. Chrome supports .TTF and .OTF as well, […]