View Single Post
Old 03-22-2013, 02:27 AM   #9
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by DaleDe View Post
Pretty much everyone uses the same obfuscation method for fonts and it is the one supported by Adobe for all devices using the Mobile ADE API. It is generally what is meant by "not trivially extractable"
Most of those terms of use were written before EPUB existed, and mostly referred to embedding in a PDF file, which is a lot harder to extract fonts from than an EPUB. This is the sort of situation where if there's any question about it, I'd want to get clarification from the foundry's legal department before including the font.

As an aside, I've recently been playing (not in an EPUB) with embedding fonts as a data URL programmatically inlined into a CSS file, which is, in turn, programmatically inlined as a data URL in a link element (along with images, etc.). Now that is obfuscation on the same order as what PDF does.
dgatwood is offline   Reply With Quote