![]() (If it makes a difference, the issue where I noticed the discrepancy is image size. I'm using Kindle Previewer 3 and Kindle 1.25.2 on a Mac.īoth appear to be up to date (I just downloaded Previewer yesterday). Or is each maybe useful in a different way (and if so, what is each program's strong point?)? Or, should I keep fiddling until I get happy results in both? So I'm wondering, should I even be using Kindle Previewer? Sometimes even when something seems to work in Kindle Previewer, it's still problematic in Kindle. I'm editing an azw3 file in Calibre and looking at the results in Kindle Previewer and Kindle. Professional e-book formatters will also test the book in a variety of formats using multiple devices/apps to get at least an acceptable quality of rendering on all of them. For books with simple formatting the results shown by the Kindle Previewer are pretty close to what readers with newer Kindle devices will see. Publishers mostly provide either EPUB or DOCX to Amazon and Amazon then produces the various Kindle formats from that. Amazon does not accept that format from publishers. ![]() If you are instead producing a book for sale on Amazon then you are taking a wrong approach by editing an AZW3 file. If you are producing a book for personal reading on your own devices then I suggest making it look good there and not worrying about how the Kindle Previewer shows it. Use of unsupported features is more likely to result in a book that renders inconsistently. See the Amazon Kindle Publishing Guidelines for information about what HTML/CSS is supported. There are also differences between renderers for the same format across different apps and devices. Amazon supports multiple Kindle formats (mainly MOBI7, KF8, and KFX) and there are significant differences in how these are rendered. There is no one true way that a book will be rendered. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |