Adobe, Web fonts and EOT
Adobe is strongly supportive of the effort to make Microsoft’s EOT web font format an open standard. Indeed, Adobe pays for Steve Zilles’ time, and he will be chairing the EOT standardization effort, should the W3C accept the proposal in principle. We will be updating our licensing FAQ to make it clear that our existing font license terms allow EOT usage, and do not allow linking to original fonts placed on web servers.
Why do we support EOT? Our surveys of web designers and font developers have made it clear to us that users want an HTML/CSS font solution that allows them to use any font they want, and most of them would like to do so legally. In particular, they want to be able to use regular retail and OS-bundled fonts. With original fonts on web servers, hardly any retail or commonly-used fonts could legally be used; only freeware and open source fonts, some shareware, and a handful of retail fonts.
Some open source advocates argue that there are enough and good enough free/libre and open source fonts available that retail/commercial fonts are unnecessary. Whether they are right in principle or not (and I think not, given how few such fonts are decently made and come in even a basic set of four styles with bold, italic and bold italic), it doesn’t matter: the web designers who make web sites want to be able to use a vastly wider variety of fonts, and companies and organizations that have a web presence want to use their existing visual identity online, or at least a close adaptation. Being able to use 50% of the world’s fonts instead of 5% comes a lot closer to meeting these needs.
Why is it so? EOT comes vastly closer because many more type foundries and type designers are comfortable with EOT than are comfortable with original fonts on Web servers. And that includes Adobe.
One aspect of EOT is often misunderstood. As an open standard, EOT is not a DRM format in the usual sense. Yes, back when Microsoft had a proprietary and secret specification, EOT was a DRM font format. But as an open specification, anyone who wants to program the tools to do so will be able to create or convert fonts to and from the EOT format. What it does instead is give us a format that is not directly usable in common operating systems. If an end user wants to take an EOT file and convert it, there won’t be anything physically stopping them. But it will be difficult for them to be unaware that what they’re doing is usually wrong and illegal (dependent on the copyright and licensing status of the font in question).
As far as protection of the fonts (something type designers and font vendors care about), the situation is not that much different from fonts embedded in PDF or SWF (Flash) files. The fonts are there, the specs are public, and in principle somebody can rip off the font. Doubtless a few people will. But I honestly expect the same thing will happen with EOT as with these other formats: even a mild barrier is enough to keep most people honest. Think of it as equivalent to a traffic signal: most people will stop at the red light. That’s good enough for us, and for many other font designers/vendors as well, it seems.
Another way in which EOT is not a DRM format is that it is not the sole or even the primary format an end user can license. Although some font vendors may see an interesting opportunity to license fonts directly in the EOT format, customized for each user and web site, I don’t see this possibility as eliminating sale of licenses for “regular” fonts. Certainly at Adobe we intend to continue to license OpenType CFF fonts, from which users can then derive EOT fonts for their HTML/CSS projects, just as they do various embedding operations with those fonts.
If you’re a web designer wanting to use fonts in HTML/CSS, let’s compare this to the music DRM situation. This is not like you buying a protected music file that you can’t move to another machine and can’t copy freely. This is instead like providing an interchange format for your music files that gives you a new option for letting your friends listen to about half your music files legally and legitimately… while you still have the original unprotected file as well! Sweet! It doesn’t stop you from copying your original files and giving those to your friends (likely illegally), but it does give you an additional option that lets you share your music. (I can already hear some of you saying, “okay–and this is a bad thing why? Which is of course exactly my point.)
So that’s why calling EOT a DRM format as a pejorative or as a scare tactic is misleading at best: it implies a bunch of things that are not true of EOT, at least not any more.
* * * * *
On August 28th, an absurd post went up on Slashdot, which is in many ways typical of the kind of FUD going around about EOT. Here are my comments on that piece:
– There is no requirement to subset in EOT, and hence no requirement to regenerate EOT files when a page changes. However, subsetting may be a good idea for download size reasons! The availability of subsetting as an option is an advantage of EOT over unprocessed original font files. Microsoft’s existing WEFT implementation may subset by default, but users can override that as they wish, or customize the subsetting (hmm, not going to need all that Greek and Cyrillic support on my web page!). Of course, if the font license allows, one could do subsetting of native fonts as well, but that has complications because of the fact that you’re spinning off incompatible fonts into the wild. Keeping web fonts separated from general-use fonts is a Good Idea if you want to have the option of subsetting.
– Although the original incarnation of EOT required the EOT font be tied to some particular URL/domain, the spec submitted to the W3C specifically removes this requirement. EOT fonts which omit this informationa are still compatible with Microsoft’s existing EOT support.
– The primary reason EOT has been “largely ignored” is because it was a Microsoft-only “standard”; making it an open spec avoids this problem. Nothing to do with subsetting.
– Having a public spec (already available now) EOT is no longer a DRM format in the traditional sense, as described earlier.
– EOT can do a much better job of “breaking Microsoft’s forgotten monopoly” (on web fonts) than original font files; many times more fonts are or will be legally usable with EOT than as OS-native fonts on web servers.
My previous web font posts on web fonts and EOT:
– First comments on the Web fonts problem (March 2006)
– Comments on original fonts vs EOT format for Web fonts, and survey (November 2007)
– Initial results of my end user survey (November 2007)