limitations of font embeddings


Always try to avoid fancy fonts while developing websites. Try to stick with standard universal fonts such as Arial or Times new Roman. Sometimes user does not have a particular font installed on their computer. It may destroy the look and feel of your website for those particular user. It is possible to embed font in your site, it will help you to retain the look of your website regardless whether a visitor has that font or not.

There are two main file formats that are used when installing fonts: truedoc (.pfr) files and embedded opentype (.eot). These file types work in different ways and each has its limitations. Ultimately, truedoc files are superior as they have better cross-browser support and can support multiple fonts in a single file.

Unfortunately, neither truedoc nor opentype files offer a completely problem free solution. Although the purpose of embedding fonts is to make a rare font accessible to all users, the reality is that there will always be some users who cannot view it. If someone is using a particularly old browser such as Internet Explorer 3, for example, they will not be able to see your embedded fonts. Although this is a drawback, it is a problem that will reduce over time, and there is still benefit to be had from using embedded fonts. However, to be on the safe side, it is best to specify more common alternative fonts such as Verdana or Arial by using the font-family attribute in CSS.

Mircosfts font embedded system only works with IE but for open source browser like Mozilla Firefox it will not work at all.


One response to “limitations of font embeddings”

  1. Thanks for this nice post. I used this font embedding technique earlier. Got positive result in IE, but in Mozilla it was just horrible.

Leave a Reply