Quote:
Originally Posted by KevinH
Those tools don't actually impact the input ( just decrypt ) so unless you are using a really old out of date version, or the book is Topaz and not azw3, I really doubt they are the issue.
Try unpacking your azw3 using KindleUnpack ( there is a standalone version - see the Mobi forum here and a calibre plugin version - you can load it as an official plugin ) and check the box to save the raw format to see exactly what is inside your azw3 file. It will also generate an epub for you from the azw3 contents that can be unzipped and checked as well.
I have found some poorly made official azw3 files where the fragment table start locations are wrong because the input was not in utf-8 and many smart-quotes were used all throughout the text messing up the byte counts.
You could also try calibre in debug mode to see if it generates any warnings about incorrect offsets when trying to convert your azw3.
Hope something here helps.
KevinH
|
Thanks. I've given up on these particular two files--as I mentioned, I returned the books. But I will keep the info for future reference.
The last version of the tools I downloaded was 5.1, but I have no idea if the plug-in was from an earlier version--it could well have been. I use Calibre only to convert Kindle books, and not very often. I did the first conversion attempt with Calibre 8.65, I think it was, and then downloaded and used the current version, and got the same screwy results both times.
I had a few Amazon mobi files that I converted at the same time, and those seem to look all right.
I think I'll just let it go and see what happens the next time I need to convert an azw3 file. Thanks.