Recent Tweets

  • The Ultimate Hipster Irony
  • Why You Can’t Work at Work | Jason Fried | Big Think:
  • Seeing too many ultra-minimal/undesigned blogs labeled “beautiful” cuz they use a @typekit font or two. Uh-uh.
  • I love what @typekit is doing for the web, how it’s shaping the agenda *and* delivering the needed tools.
  • In other news, I’ve come up with a title for my book of short stories. KAFKA FOR BEGINNERS.
  • Selection pseudo-element. Choose text color/BG color when user selects text! Try it at . (Not supported in IE).
  • “IRS bomber Joe Stack captured the news for days, but his African American, Vietnam vet victim has gone unheralded”
  • Must-read column, NYTimes: I Cost More, but I’m a Specialist
  • It’s probably a good thing that I didn’t get that XHTML2 tattoo. Probably.
  • I just received a lovely “Happy New Year” card from the W3C. Repeat, I just received it.
  • Watch Happy Cog’aoke 2 / Lesson Two: Solo-tunities on Vimeo!

Follow me on Twitter: @zeldman

5 thoughts on “Recent Tweets

  1. Outside of design blogs why aren’t we seeing more embedded fonts on sites? technologically its been around for ages. Is it just that the particular fonts that corporate sites would want to match their branding cannot be licensed?

  2. technologically its been around for ages.

    You are correct, sir.

    It has been around for over ten years.

    However, only IE supported it, and IE didn’t support it with standard fonts, only with a proprietary font format that Netscape and Opera (and later Firefox, Safari, Chrome, etc.) did not support. The usual browser compatibility stuff; the usual lack of support for standards.


    The ALA article stimulated renewed interest in @font-face. Webkit and Mozilla supported it. But there were issues with type designers, IP protection, and formatting … continued browser and OS compatibility issues … and so on.

    Typekit resolves many of these problems; that makes it attractive to many designers. Hence the renewed interest.

Comments are closed.