Slashdot Mirror


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?"

2 of 315 comments (clear)

  1. what is the point? by FunkyELF · · Score: 1, Redundant

    I can't believe that today people think DRM actually works. You make it part of some standard, it is cracked 2 days later, then for decades we still have to deal with it.

    Why not just assume that it will get cracked, then not implement DRM in the first place?

  2. Re:Loaded question by X0563511 · · Score: 0, Redundant

    That has everything to do with nothing. Congratulations, you almost won the "most useless post" award! Unfortunately for you, I just won it, with this one.

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...