Will W3C Accept DRM For Webfonts?
dotne writes "Microsoft has submitted Embedded OpenType (EOT) to W3C and a slimy campaign for EOT has been launched. EOT is a DRM layer on top of normal TrueType/Opentype files; EOT ties a font file to a certain web page or site and prevents reuse by other pages/sites. Microsoft's IE has supported EOT for years, but it has largely been ignored due to the clumsiness of having to regenerate font files when a page changes. Now that other browsers are moving to support normal TrueType and OpenType on the web (Safari, Opera, Mozilla, Prince), W3C is faced with a question: should they bless Microsoft's EOT for use on the web? Or, should they encourage normal font files on the web and help break Microsoft's forgotten monopoly?"
"Or, should they encourage normal font files on the web and help break Microsoft's forgotten monopoly?"
/. will think...
Gee, I wonder what
If there's one thing that I wake up every morning with a deep desire to have, it's more random, cutesy, difficult to read fonts on websites.
ZuluPad, the wiki notepad on crack
Pantone would love that!
I call #FFFFFF, #000000 and everything inbetween!
Just because a standard exists ^[1mdoesn't^[0m mean it has to be supported.
It will depend on how "slimy" the campaign for EOT is. If something is slimy enough, /. actually thinks it's cool.
/. will never get tired of watching "Ghostbusters".
Knowledge is the small part of ignorance that we arrange and classify. (Ambrose Bierce)
Just not every time someone wants to see their work.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft