Quote:
Originally Posted by mazdaspeed
Adobe, for all their hyped inclusiveness for EPUB, doesn't specify precisely how to encrypt or obfuscate to their satisfaction -- as though there's any difference in that terminology. What I do know is that Adobe InDesign subsets and "encrypts" the fonts when exporting EPUBs, and it packages an encryption.xml into the EPUB file that KDP won't process to my satisfaction.
|
Adobe has their own Adept DRM scheme used by some book sellers that encrypts the important files within an EPUB. That is different from font obfuscation.
In my opinion font obfuscation is silly because it offers no actual protection of font files. The de-obfuscation algorithms are widely published and the key needed for it is present in plain text in the OPF file. The only thing it accomplishes is indicating which fonts have license restrictions.
Quote:
Originally Posted by mazdaspeed
If I strip the encryption.xml file of everything but its header, then it does work for KDP. If this is not satisfactory to Adobe, then they need to speak up. I've done my part by paying the monthly subscription and following directions as closely as I can.
|
The encryption.xml file shows which files within the EPUB are encrypted and the encryption algorithm used for each. If you remove it then the obfuscated fonts will become unusable and the software rendering the EPUB will use a fallback font instead.
Also, publishing for Kindle based on an EPUB with obfuscated fonts will cause those fonts to be garbled and ignored as far as I know. Amazon applies their own encryption to Kindle books as long as you select the DRM option when publishing (and in some cases even if you don't.)