Quote:
Originally Posted by HarryT
Not so. As I've already pointed out earlier in the thread, Amazon's freely downloadable "Kindle Previewer" app will allow you to see exactly what your book will look like on any Kindle device or app. It uses exactly the same rendering engine that the actual device or app does, and will precisely reproduce all the "quirks" that each one has.
It's a free download for both Windows and Mac from:
http://www.amazon.com/gp/feature.html?docId=1000234621 |
That's a great suggestion, and certainly worth pursuing, but I wonder if Amazon has bothered to keep this tool up to date now that they actually have several platforms.
As you know, the original Kindles used a proprietary embedded Linux implementation, where the new Kindle Fire is Android based.
Most Linux code is programed in "C", and though there are other options, all Linux compilers comply with basic Linux POSIX API standards.
Nearly all Android code is written in Googles simplified variant of Open Java with Androids unique API and Libraries.
I am sure that in both the Kindle Fire and original K3, the 'rendering engine' code is written to the same internal Amazon spec, but there are LOTS of EPUB devices which implement the same 'open standard', which none the less show some differences when rendering the exact same EPUB document.
Do you know for a fact that Amazon has updated the Kindle Previewer to include a separate Java based rendering engine which is an exact representation of their Android based rendering used in the Kindle Fire? (along with their older presumably 'C' coded Kindle engine)
If not, one work around would be to use the Kindle for Android app on a 16:9 Android Tablet (or a real Kindle Fire) to preview the current and future Android based Kindles, and rely on their PC Kindle Preview App to approximate the older 4:3 proprietary coded Kindles.