Comments on: Multiple font weights via CSS 3 and more font fun http://ajaxian.com/archives/multiple-font-weights-via-css-3-and-more-font-fun Cleaning up the web with Ajax Thu, 17 May 2012 07:43:39 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: CaptainN http://ajaxian.com/archives/multiple-font-weights-via-css-3-and-more-font-fun/comment-page-1#comment-274670 CaptainN Fri, 24 Jul 2009 23:26:46 +0000 http://ajaxian.com/?p=7134#comment-274670 I wrote about a similar way to protect fonts a while back, talking about how you can really only protect against the casual pirate with these kinds of techniques. Someone could easily pirate a file from a server (like a font or an image), even if they don't posses the necessary knowledge to get an embedded font to install in the system, if it is encumbered in some way, like being in EOT or SVG format, encoded in a dataURL. That kind of protection is a lot more reasonable for font sellers to ask for, than something like heavy handed DRM. Other forms of content on the internet (video, graphics, music, etc.) posses the same kind of protection since they are generally heavily edited and compressed before they are used. http://www.unfocus.com/projects/2009/04/22/the-third-option-for-html-font-embedding/ I wrote about a similar way to protect fonts a while back, talking about how you can really only protect against the casual pirate with these kinds of techniques. Someone could easily pirate a file from a server (like a font or an image), even if they don’t posses the necessary knowledge to get an embedded font to install in the system, if it is encumbered in some way, like being in EOT or SVG format, encoded in a dataURL. That kind of protection is a lot more reasonable for font sellers to ask for, than something like heavy handed DRM. Other forms of content on the internet (video, graphics, music, etc.) posses the same kind of protection since they are generally heavily edited and compressed before they are used.

http://www.unfocus.com/projects/2009/04/22/the-third-option-for-html-font-embedding/

]]> By: Schill http://ajaxian.com/archives/multiple-font-weights-via-css-3-and-more-font-fun/comment-page-1#comment-274660 Schill Thu, 23 Jul 2009 16:19:10 +0000 http://ajaxian.com/?p=7134#comment-274660 I didn't realize it when poking around yesterday, but the Typekit guys had just written a nice post the day before on <a href="http://blog.typekit.com/2009/07/21/serving-and-protecting-fonts-on-the-web/" rel="nofollow">how their service works</a>, and their protection scheme (referrer checking, base64-encoded data URIs, and "segmenting"). Also, see <a href="http://forabeautifulweb.com/blog/about/first_impressions_of_typekit/" rel="nofollow">First impressions of Typekit</a>.   Given the "open" web nature, I think it's interesting to see companies trying to protect assets like fonts online on top of the @font-face standard. There is also a proposal for a <a href="http://ilovetypography.com/2009/07/20/web-fonts-%E2%80%94-where-are-we/" rel="nofollow">.webfont standard</a>, which would include another form of permission-based protection. Will be interesting to see where it all goes. I didn’t realize it when poking around yesterday, but the Typekit guys had just written a nice post the day before on how their service works, and their protection scheme (referrer checking, base64-encoded data URIs, and “segmenting”). Also, see First impressions of Typekit.
 
Given the “open” web nature, I think it’s interesting to see companies trying to protect assets like fonts online on top of the @font-face standard. There is also a proposal for a .webfont standard, which would include another form of permission-based protection. Will be interesting to see where it all goes.

]]>