Quote:
Originally Posted by dgatwood
Adobe used a different font obfuscation technique than Apple for EPUB 2 books, so you couldn't embed obfuscated fonts in an EPUB 2 book and expect ADE and iBooks to both be able to read them.
EPUB 3 resolved that by providing a single obfuscation standard in the spec, and now everybody is on the same page. I'd imagine that's what she meant when she said that font embedding wasn't supported—specifically that font embedding of commercial fonts was dubious in EPUB 2.  |
Ah, interesting. Yes, I remember that vaguely. Well, in the more recent InDesign versions (CS6 forward, I think) Adobe switched to just using the standard IDPF obfuscation techniques, and they added the right metadata file in, so their EPUB2s with obfuscated fonts can be read just fine by iBooks.
Anyway, you're probably right--thanks!
Quote:
Originally Posted by JSWolf
I would not bother to obfuscate fonts. The best way to handle fonts is to subset them. Not only do you get fonts that cannot be used for anything other than that book, you get smaller fonts for a small size for the book.
|
I don't disagree with your point that subsetting is more effective than obfuscation at deterring theft, but I feel compelled to point out that your comment is only vaguely, tangentially related to this thread.