There are just 2 ways to do it: You either give the customers the webfonts, or you give them a code and everything else is handled on the server of the webfonts provider. There is no other way to do it. So I was a little bit surprised about the hype around the "revolutionary idea" called Typekit. Richard and I (among others) are proposing this model for quite some time now.
About the "real fonts on Web sites without piracy": It's just not possible! Sure, all these webfont services will use some sort of obfuscating, both for the download URLs and the font files itself, but in the end there is always a working font delivered to the browser. And any obfuscating can easily be bypassed or reversed. So as foundries we shouldn't fall for any promises about a "secure webfont service".
We should either accept the risk, or not take part in this development. But we shouln't wait for a magical solution to secure the fonts. It's not gonna happen.
ralf said:
> There is no other way to do it. So I was a little bit surprised
> about the hype around the “revolutionary idea” called Typekit.
well, typekit has gotten a lot of attention, that's for sure...
veen usually does.
but i'm not sure even typekit describes itself as "revolutionary".
i seem to remember them saying something that is more like
"well, the browsers will support it now, so we're gonna try it."
-bowerbird
Seems the "webfont" story is getting some attention from Monotype Imaging. The company introduced a non-commercial end user license agreement, or EULA, that permits the use of fonts in the Embedded OpenType format on the Web. Intended to extend font choice for Web page design, the EULA requires no additional fee for use on a non-commercial Web site when licensing products from the company’s Monotype, Linotype, ITC and Image Club typeface collections from Monotype Imaging’s e-commerce sites: Fonts.com, Linotype.com, ITCFonts.com and Faces.co.uk. http://www.communitype.co.uk/archives/category/webtype
Captured from web.archive.org on 22 Aug 2013. view this capture