KindleUnpack (MobiUnpack): Extracts text, images and metadata from Kindle/Mobi files

[sbwtxj]

I have a mobi format dictionary, can you help to convert to Kobo format?

thanks.

[Julius Caesar]

Does Kindle Unpack support azw6 files? I tried to unpack it but it didn't work. I got error message.

[KevinH]

Hi,
No. azw6 files are not ebooks. They are just a container for high res images.

I do have an experimental python script to try and dump these images but have found that some contain Windows only image media-types instead of jpegs which makes them pretty worthless unless you have access to a Windows machine and are willing to convert them one by one to something useable.
Let me know if you want me to post the experimental command line python script.

KevinH

Originally Posted by Julius Caesar

Does Kindle Unpack support azw6 files? I tried to unpack it but it didn't work. I got error message.

[KevinH]

hi,

No. KindleUnpack does understand a subset of mobi dictionary formats and can unpack some of them to html. I have no idea what a Kobo dictionary format looks like so you are on your own converting from html to that format.

KevinH

Originally Posted by sbwtxj

I have a mobi format dictionary, can you help to convert to Kobo format?

thanks.

[KevinH]

Hi All,

Just in case there was any interest in seeing/using the images in AZW6 files, I have attached a quick and dirty python command line program to unpack the contents of an non-drm azw6 file to a folder of images. I have added no smarts for using full unicode at the command line in python 2, so be careful to change paths/filenames to be pure ascii if running under python 2.

Hope this helps,

KevinH

[kyzcreig]

Question, I want to use Amazon's "location" information to extract text from a mobi. Can these scripts help with that?

To get more specific, "location" supposedly corresponds to 128 byte chunks of data and my plan is to just grab the chunks that went missing from my annotations due to DRM. But maybe I will be messing up some metadata with this approach? Otherwise can these scripts help me decode the location chunks?

Thanks !

[pdurrant]

Originally Posted by kyzcreig

Question, I want to use Amazon's "location" information to extract text from a mobi. Can these scripts help with that?

To get more specific, "location" supposedly corresponds to 128 byte chunks of data and my plan is to just grab the chunks that went missing from my annotations due to DRM. But maybe I will be messing up some metadata with this approach? Otherwise can these scripts help me decode the location chunks?

Thanks !

Turn on the option to output raw MobiML, so that changes to generate valid HTML don't mess up the file position info you're trying to use.

Good luck.

[odamizu]

Not to be pushy, Applescript Master The Grand Mouse pdurrant, but might you consider updating the first post in this thread with the latest KindleUnpack and an updated Applescript?

I am content running the python script if you don't have time, but if so, your Applescripts are so nifty and much appreciated Merci.

[pdurrant]

The first post is now updated with version 0.80 of the KindleUnpack code, and I've updated the AppleScript to include that code, and also modified it so that it works correctly on Mac OS X 10.10 (Yosemite).

[odamizu]

Thank you muchly kind sir! You and all the other programmer/developers here at MobileRead totally ROCK!

[kyzcreig]

Originally Posted by pdurrant

Turn on the option to output raw MobiML, so that changes to generate valid HTML don't mess up the file position info you're trying to use.

Good luck.

So I've been working on a script for this and I'm finding the offsets are all off. It doesn't appear to be a constant offset so my guess is that this raw HTML somehow doesn't correspond to the location data. Is that likely to happen?

[pdurrant]

Originally Posted by kyzcreig

So I've been working on a script for this and I'm finding the offsets are all off. It doesn't appear to be a constant offset so my guess is that this raw HTML somehow doesn't correspond to the location data. Is that likely to happen?

No idea. Are you certain you're looking at the RAWML, before it's processed to change links to proper HTML?

Or perhaps locations are calculated off some derivation of the RAWML. Or you're looking at different versions of the book. (Some devices will receive the KF8 version (if available) and some will receive the MOBI version.)

I suspect you'll need to dig into the details of formats and how they're interpreted to be able to make sense of this. And even then, Amazon locations may have some other fiddle-factor applied to them. Perhaps they only relate to visible displayed characters or something?

[DiapDealer]

I believe a location is 150 bytes of data (markup and all) instead of 128. I can't remember if that's compressed or uncompressed, but the total number of locations in a book is bytes/150+1. Perhaps that's why your offsets seem "off."

The 128 bytes is an ADE "page."

[eschwartz]

The details on Kindle pagenumber offsets should be in calibre's Kindle device driver code.

[kyzcreig]

Originally Posted by DiapDealer

I believe a location is 150 bytes of data (markup and all) instead of 128. I can't remember if that's compressed or uncompressed, but the total number of locations in a book is bytes/150+1. Perhaps that's why your offsets seem "off."

The 128 bytes is an ADE "page."

Well I'll be. This did the trick. Now the main obstacle is how I parse this jumble of HTML. It seems like some tags are cut off so I'll need a solution for that as well. So far this is turning out very nicely though!