Real fonts on the web, part 2

Introducing Typekit:

We’ve been working with foundries to develop a consistent web-only font linking license. We’ve built a technology platform that lets us to host both free and commercial fonts in a way that is incredibly fast, smoothes out differences in how browsers handle type, and offers the level of protection that type designers need without resorting to annoying and ineffective DRM.

See also: “Web Fonts Now: How We’re Doing With That” (23 May 2009) right here at

[tags]webdesign, webstandards, @font-face, typekit, realfonts[/tags]

6 thoughts on “Real fonts on the web, part 2

  1. Only one remaining rhetorical question here for me: Is Ascender/Microsoft, Adobe, and Monotype signed on for this? Let me know when they are, then there will be something to talk about. In the meantime, I see typekit as little more than a questionnaire posing as a blog for a new service.
    Nice to see a lot of foks interested, though.

  2. I’d love to see more real type on the web, but I think that the problem is primarily legal and not technical. We should be able to solve for that without adding third parties and another javascript library to the mix.

    Richard raises an interesting question. I was party to a conversation recently about just that: Register a domain and put up a splash page with a newsletter sign-up form to gauge interest in a concept before doing any actual work on it. It’s an interesting strategy from a maker’s standpoint but it seems to me like it would make people angry (and less likely to participate) once it became widely known. However, convincing font foundries that there is a real population of paying customers who want to solve this might be worth the fallout.

  3. Despite a lack of details, it’s now clear to me that Typekit is a real attempt at providing font-linking as a service.
    Kudos to those behind it for trying to take the bull by the horns. I’m eager to see how it pans out.

Comments are closed.