Quote:
Originally Posted by impasto
Thank. Unless I missunderstood, it appears you guys are telling me any form of sideloading will NOT give me correct representation of a final published ebook. Im having a hard time believing there is no way of proper testing before final upload to Amazon. There is no form of a sandbox environment, or test uploading to Amazon, but available ONLY for me to preview?
|
Actually, that's NOT what I meant as the takeaway.
You can, absolutely, take your MOBI file (or ePUB or HTML or whatever) and using KP3, export an AZK file.
You can then sideload that AZK file, via a wired connection between your computer and an iPhone or iPad, through iTunes into Kindle4iOS, and then, yes, the result that you see will be reasonably close to what you can expect from the final published ebook. But doing that is a major PITA.
If you are seeing problems on a Kindle ereader, then you may have problems that need addressing, regardless of the iOS.
Even if you mean that your associate has, say, a K2 or early K3/K4, which are KF7 devices, you'll still need to clean that up. (I find a lot of source files that are ePUB3 completely and utterly ignore the existence of KF7.)
If you mean that the eInk is a more-recent eInk, but still KF8, then you do have issues and you need to address those.
Do you know exactly what device this older eink was?
Hitch