As mentioned in previous posts, there is an arsenal of methods to implement fonts outside of the ‘web safe’  list into website design. All have their advantages and disadvantages. In particular, the @font-face method is common, simple and somewhat standardized, so why all the other options? Because commercially licensed fonts are copyrighted just like any other media such as music, stock photography, etc., and the current way fonts are included with the @font-face method, the file source is easily discoverable, giving open access to download the installable font or directly link to that server through another domain. And typically having large price tags, temptation to ‘borrow’ a font from an online neighbor would be strong (and unlawful), but those hosting the font file could be held responsible.adoption of this new format has been high among many major foundries, such as Adobe and Linotype. Now we wait for cross-browser support. Currently, Firefox 3.6 supports the WOFF format and is attempting to pave the way with a good overview, documentation and resources.

Now comes in the web-based Web Open Font Format (WOFF). For the user, the highlight of this new format is in its HTTP compression. Compared to TrueType/OpenType, the end user has a shorter lag time rendering the font onscreen. But there is also a highlight for type foundries; WOFF fonts include XML metadata which can include information such as copyrights and where the fonts can be purchased. Although the fonts are still not considered ‘secure’, this data gives more legal strength to foundries that discover anyone breaking those copyrights.

With these features, adoption of this new format has been high among many major foundries, such as Adobe and Linotype. Now we wait for cross-browser support. Currently, Firefox 3.6 supports the WOFF format and is attempting to pave the way with a good overview, documentation and resources.