So I even tried removing the encryption.xml file and replacing these fonts with full original versions. I read somewhere that kindle doesn’t like the encrypted fonts ID generates.
In the css file (in both the epub and mobi files), all fonts are correctly listed as and the css font-families look good and set to fall back onto a generic sans-serif style.
This has no effect on the font type, but it is being assigned as I also set the titles to be pink (as a test) and that worked. I even output an additional css file with the epub that targets amzn-kf8, amzn-mobi and (monochrome) to just display a sans-serif font. I’ve tried everything in my power to try and preserve the fonts. When I upload the e-pub to the Amazon KDP store and let it convert it, the same is happening. All other formatting settings are preserved though (page breaks, spacing, images). But when I pop the generated mobi file into dropbox and open it in the Kindle app on the ipad, all fonts are stripped away to some generic serif font. When I open it in Kindle Previewer on my mac it looks good too (even if some title fonts have defaulted to sans-serif). I slide it over to dropbox and open it in iBooks on my ipad and it is exactly the same as what I see in ADE on my mac.īut, it’s final destination is as a kindle book on the Amazon store. I even managed to amend the existing ID print file to output for e-pub without making a new version or damaging the existing print version. I can now output it as an e-pub and it is exactly as I want it. I used an earlier book I had designed for print to experiment with. I recently completed Anne-Marie Concepción’s “Indesign CS6 to EPUB” course on ( )Īs an experienced ID CC user it was great.
0 kommentar(er)
