Kindle Previewer 3.0 Fail
I had an interesting experience today with a MOBI. In a book with lots of images, many were out of place. They were correctly placed in the EPUB edition, but somehow moved around in the conversion to MOBI. Sleuth time.
Here are the main characters:
- Valid EPUB3 file
- Kindle Previewer 3.17.1
Here is the workflow:
- Drag valid EPUB3’s content.opf onto Kindle Previewer 3
- Wait a while
- View result in KP3, different views, make adjustments, repeat
- Load onto Kindle Fire, scroll through looking for presentation issues, make adjustments, repeat
- Send file to client for content check
Here is what client said:
- Why are many images in the wrong places?
- Did you use the correct EPUB?
*Actually, client was not aggravated. This is just my transference.
Here is what I did to diagnose/solve the problem:
- Ascertained that yes, I used the correct file.
- Looked at locations in HTML where images were wrong in the MOBI.
- Ascertained that correct images were in place in the HTML.
- Scratched my head.
Then I went back over my process for the entire job:
- I created this job in 2 distinct sections due to client needs.
- I exported some grouped images from InDesign using Object Export Options — Rasterize Container
- InDesign exported these groups and named them sequentially: 1.jpg, 2.jpg, etc.
- Because I created the project in 2 sections, I had 2 sets of identically named images.
- To combine the 2 sections of the job, I created image folders for each set (imagesONE and imagesTWO).
- The paths were correct in HTML:
<img src="imagesONE/16.jpg" alt=""> <img src="imagesTWO/16.jpg" alt="">
- I validated the EPUB, client reviewed, approved.
And finally, to get to the MOBI:
- I opened Kindle Previewer 3.17.1 and dragged the content.opf over the window (my usual way of creating a MOBI).
Here’s what I tried after going over my process:
- I opened Kindle Previewer 2.9 and placed content.opf
Images are all in correct places.
So, it’s a Kindle Previewer 3 issue. Then I tried this:
- I dragged the valid EPUB itself over KP3.
And there it was, everything in place.
So it’s a Kindle Previewer 3 issue, but only when content.opf is used as the source.
What I learned:
- Kindle Previewer 3.17.1 can’t be trusted.
- KP3 didn’t follow the paths as written in the HTML; it used “imagesONE/16.jpg” in place of “imagesTWO/16.jpg”
- Using content.opf as source may produce different result than using complete EPUB.
- I should explore uploading EPUB to Amazon instead of creating my own MOBI
- I should avoid using duplicate names for images, even if kept in separate folders.
- I should remember that there’s always ice cream.