View Single Post
Old 09-03-2021, 06:01 PM   #6
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,118
Karma: 92500001
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
As far as I can tell none of Amazon's documentation for publishers mentions font obfuscation. (If anyone knows differently I would appreciate a link.)

I do know that neither Amazon's Kindle Previewer or the older kindlegen support input files with obfuscated fonts. Kindlegen would include the fonts without the key needed to deobfuscate them resulting in unusable fonts. Kindle Previewer will just silently strip them out. Perhaps obfuscated fonts will be handled correctly if the EPUB is instead uploaded to Amazon, but I wouldn't count on it.

Font subsetting can be problematic if not done carefully. The book rendering process can introduce characters that were not present in the original content and problems will occur if those characters are not present in the font. Two examples are automatic list numbering and ligature substitution.
jhowell is offline   Reply With Quote