The document discusses the history of web typography from 1996 when core fonts were developed by Microsoft to 2010 when services like Google Fonts, Fonts.com, and Typekit launched to provide font hosting and embedding. It examines reasons for the delay in widespread font embedding including issues with foundries, licensing, and pricing. Finally, it provides details on current services for font embedding and things to watch out for like inconsistent sizing across browsers and need for fall-back fonts.

1. WEB TYPOGRAPHY
beyond Arial, Verdana & Georgia

2. A SKETCHY HISTORY
1996 • Core Fonts Developed by Microsoft
1998 • CSS2 introduced the @font-face rule
2005 • sIFR (Scalable Inman Flash Replacement)
October 2008 • Font Squirrel goes live
2009 • Typekit goes live
May 19, 2010 • Google Introduces their Font API & Directory
May 2010 • Fonts.com Web Fonts goes live

3. WHAT TOOK SO LONG?
Three main reasons:
Foundries.
Licensing.
Pricing.

4. TODAY & YOU
Font Squirrel • Quality & Free for Commercial Use
@font-face kits and @font-face generator
Google Web Fonts • Reliability & Free
includes 436 Font Families & Growing as Google Funds
Fonts.com Web Fonts • Affordable & Quality
$10/month for 20,000 fonts & 250,000 page views/month
Typekit • Highest Quality & Affordable
$49.99/year 707 Font Families & 500,000 page views/month

5. TRIVIA QUESTION
Of the websites discussed in the past few slides,
which was acquired by Adobe last October?

6. ANSWER:
Typekit

7. THINGS TO WATCH FOR
TRUE OR FALSE: Embedded font sizes are
consistent across browsers. • FALSE
TRUE OR FALSE: When using embedded fonts,
font-families (fall-backs) are not necessary. • FALSE
Example:
WRONG: font-family:'Avenir LT W01 55 Roman';
RIGHT: font-family:'Avenir LT W01 55 Roman', "Helvetica Neue", Arial, Helvetica, sans-serif;
MOST IMPORTANT!
Avoid using font-weight with embedded fonts.

8. ONE MORE THING...
Lettering.js