View Single Post
Old 06-22-2022, 07:25 PM   #7
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,394
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by mazdaspeed View Post
As for Encryption with Adobe Fonts. Per Adobe's EULA, encryption is not required when the font is properly subset. In order to even get Kindle Previewer to read the "Publisher Font" you must scrap the encryption.xml file that is generated by InDesign. Simply include a blank (header-only) encryption.xml file.
May I ask how you are removing the encryption from the font files themselves? My preferred method is to open the epub in Sigil, right-click each font file and set the encryption to none. When you remove the encryption from all the font files, Sigil will remove the unneeded encryption.xml file.
DNSB is offline   Reply With Quote