Slashdot Mirror


User: bd-asc

bd-asc's activity in the archive.

Stories
0
Comments
3
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 3

  1. Re:what is the point? on Will W3C Accept DRM For Webfonts? · · Score: 1

    EOT is not DRM. Read the specs. EOT simply leverages the existing font embedding information built into TrueType and OpenType fonts.

  2. Re:Bogus on Will W3C Accept DRM For Webfonts? · · Score: 1

    Type designers and commercial font developers simply do not want their fonts posted to web sites in the native TrueType or OpenType formats. They would prefer an approach that makes it easy for honest people to do honest things - which is what EOT offers. So if web developers want additional fonts to use in formatting websites the only solution will be using free fonts. Sure there are thousands of free fonts out there, but you get what you pay for. Lousy quality when used at text sizes, incomplete character sets, etc. There are some nice open source fonts, but these are in the minority. Web designers and creative professionals would LOVE to be able to use the same fonts they buy to use for print and web graphics. EOT represents an approach that finally will solve the web fonts problem, with the support of the font developer community.

  3. Re:DRM doesn't make sense for any standard on Will W3C Accept DRM For Webfonts? · · Score: 1

    EOT (Embedded OpenType), as proposed by Microsoft and Monotype, is not DRM. Unfortunately this mis-perception has taken a life of its own. EOT has a lot of features to offer web designers & developers beyond native TrueType fonts including character set subsetting, file size compression, and font embedding permissions.