View Single Post
Old 01-06-2013, 08:24 PM   #3
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 8,772
Karma: 39540023
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Being listed as "embeddable and/or "editable" and/or "installable" has nothing to do with whether or not the font can work (functionality-wise) when embedded in an ePub. Those various labels only deal with the legalities of doing so.

There's at least one font property (OS2 version) that if set improperly can cause the embedded font to not work in ADE renderers, but other than that ... you can get most any font (ttf or otf) to function properly when embedded. It's just a matter of whether you can legally distribute it with your ebook or not.

I do know you can't just grab any font-file and slap a random encryption.xml file in the ePub and expect it to work. The encryption file is created at the same time the font-file is obfuscated and there are very specific urn id requirements in the opf file in order for ADE based readers to properly use encrypted fonts.

Last edited by DiapDealer; 01-07-2013 at 09:43 AM.
DiapDealer is online now   Reply With Quote