View Single Post
Old 04-11-2010, 08:57 AM   #12
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
Quote:
Originally Posted by HarryT View Post
Will a licence that is adequate to cover embedding a font in a PDF therefore be sufficient to cover its use with an ePub, where it's more a case of packaging the font in the file rather than making it in any way inaccessible to the user?
If the licence only addresses embedding in a PDF, then that's all it covers. The licence we're talking about here specifically allows css @font-face embedding, so there's no problem using it in an epub.

ePub is designed as a delivery format. Sure, someone can jump through a couple of hoops and extract the font, but ereaders don't come with a menu option to extract the font. In exactly the same way, a webpage that uses @font-face is designed solely for the delivery of content, and browsers don't offer the option of extracting the underlying font file. But a skilled user can extract the font with ease, if they feel inclined to do so.

BTW, it is possible to extract fonts from a PDF (though some features may be missing from the result). Obviously I'm not going to explain how to do so here.
charleski is offline   Reply With Quote