Thread: Embedded fonts
View Single Post
Old 08-08-2015, 02:21 PM   #8
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by bphil00 View Post
Hey guys,

HarryT,
Thanks for your feedback. I disagree that no one is going to appreciate the embedding of a body text font. I'm not disabling the ability to change fonts within the eReader, they are still free to do that as with any ebook.
Phil:

While I don't disagree with you about embedding fonts, you should know that about 99% of the time, embedding a font means that the end-reader cannot change it on the device. In fact, very few of the devices allow a reader override of the fonts, and some do it in such an obscure way that a reader can rarely find the "how." Just advising, here.

Quote:
Doitsu,
Thank you as well. I found that un-obfuscating/subsetting/encrypting the fonts by replacing the fonts within the .epub and deleting the encryption.xml file led to the fonts working on the ipad. Of course the font foundries, probably wouldn't be happy to hear that.

Adding the xml file that you mentioned also worked! Thank you!
Of course, when running thru FlightDeck, Kobo and Amazon didn't like the file.

You had some weird issue in your obfuscation file, then, for, as mattmc states, above, it shouldn't have caused you an issue, not in an ePUB that you are sideloading.

About the encryption: No, the font foundries WON'T be happy to hear it--you ought to at least subset the fonts, assuming that they are all licensed for eBook use, rather than simply "for commercial" use, or for "personal" use. I find that a lot of print designers (not saying that's what YOU are, or do; I don't know anything about you; I'm posting this for folks who come along and read this as part of their research) don't realize that simple "commercial" licensing doesn't cover eBook or App use. Check for the fonts you're using, and in any event, subset them.

Font Encryption is NOT a substitute for correct font-licensing for eBooks, just so this is clear for anyone coming along later and reading this.

Amazon's Kindlegen won't like that file, no. You may also find that when you upload an ePUB or MOBI at Amazon that the fonts are stripped right out of the file--I strongly recommend that you check it by doing a test upload at the KDP, to see if that happens to you.

Hitch
Hitch is offline   Reply With Quote