Introducing Typekit « The Typekit Blog
http://blog.typekit.com/2009/05/27/introducing-typekit/

via windfucker

ウェブページでフォントをダンロードしやすくする仕組みっぽい。Javascript一行だってさ。どんな風になるのかな。

all browsers will soon support a wide range of fonts. but using fonts on the web (in most cases) is a direct violation of the font's copyright, as linking to a font gives the viewer a direct way to download the font . It's like using a font to print a book and then including the font with the printed book. Enter TypeKit, a web app that designers and developers subscribe to. The service has a collection of typefaces that the dev can link to in their jscript and TypeKit handles all the background witch's brew of delivering the font to the end user's screen, without that iser being able to download the font package. Interesting idea! I wonder what the tech looks like behind the service and the susbcription fees.

As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts. This really is going to change web design.

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.

As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts.

The Typekit solution That’s where Typekit comes in. 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.

The W3C recommendation for CSS web fonts will be 7 years old soon. Why, after all these years, has typography for the web not progressed further? Why haven’t designers embraced linked, downloadable fonts in their designs?

embed any font into your website, with the use of js

Platform and legal support for using linked fonts in CSS

May 27のblogの米欄は賛否両論ね。金払って@font-faceの薄いラッパーとか意味わからんという感じか。しかし、そもそも気になるのは、FF3.5+ではremote fontのsame-origin policyにひっかかって動かないんじゃねーの？という点だ。せっかくなので直接聞いてみる。

ThinkVitamin - Carsonified's blog about the web

By Elliot Jay Stocks When Johno first asked me to write about Typekit, I jumped at the chance. I’d received a beta invite to try out the service about a week before, but deadlines had got in the way of actually getting round to it. Now I had the

i love typography, the typography and fonts blog

Typekit

More: http://bit.ly/bckNoh and "I'm surprised that most of the stuff in the current Google font directory made the cut": http://typophile.com/node/70557#comment-412118

Better to work with, than against, a giant.

Typekit announces that it has teamed up with Google to build the Web Font Loader API, which more smoothly enables web designers to load custom fonts into their pages. Additionally, Typekit has added Goolgle’s new collection of free web fonts to it's own offering.