KindleUnpack (MobiUnpack): Extracts text, images and metadata from Kindle/Mobi files
Quote kovidgoyal
I doubt that's very accurate. python is hardly exclusive to the computer language (while c++ and perl are).
Granted. How about this one?
http://www.google.co.uk/trends?q=perl%2C+python+-snake+-monty+-animal+-reptile+-skin+-petwhich I think removes most other meanings of python.
Much better I'm happy to see Python usage rising. Another useful comparison is with Ruby.
Quote pdurrant
By taking code from other sources and tweaking it, Version 0.17 (above) now creates an opf file, a folder of images, and an html file that are ready for use with Mobipocket Creator.
Version 0.20, now uploaded above, improves the opf file and the HTML file.
Quote pdurrant
Version 0.20, now uploaded above, improves the opf file and the HTML file.
Oh, it's really v0.21!
Thank you.
Quote quocsan
Oh, it's really v0.21!
Thank you.
So it is - I got it right in one message, and forgot the version number by the time I wrote the second! :-)
Quote pdurrant
[Bug fix so that it works right with Mobipocket files containing more than 9 images]
Now here's version 22.
Another update, to fix a silly bug that got the image links wrong if there were more than nine images.
I have to admit I kind of dropped this on the floor after my initial flurry. Thanks for the additional work, pdurrant.
One of the things that has always been a little irritating about Mobipocket (compared with ePub) is that it hard-codes file offsets in links, making it problematic to fix errors in an eBook if you don't have good tools. It's clearly seen as a display format (like PostScript) rather than a source format.
Thankfully, ePub is a lot more sane.
Quote adamselene
I have to admit I kind of dropped this on the floor after my initial flurry. Thanks for the additional work, pdurrant.
One of the things that has always been a little irritating about Mobipocket (compared with ePub) is that it hard-codes file offsets in links, making it problematic to fix errors in an eBook if you don't have good tools. It's clearly seen as a display format (like PostScript) rather than a source format.
Thankfully, ePub is a lot more sane.
Without your initial work, I couldn't have done anything. Tweaking python fine, I can do that. Writing this from scratch? No way...
I think that mobiunpack now allows unpacking, editing and re-packing (with KindleGen) without any problems. If anyone does come across any problems doing this, I'd love to hear about them so that they can be fixed.
What's nice with ePub is that (with careful choice of attributes in the opf file), it's possible to create a valid ePub
and use the ePub source folder to create a well-formed Mobipocket ebook using KindleGen.
Quote pdurrant
[Enhancement: Now includes Start guide item in the opf]
Now here's version 23.
Just uploaded version 23. Mobipocket books can include a pointer to where the book should open to when first opened (often the first page of the first chapter, skipping all the prelims).
Version 23 of MobiUnpack now writes this info out in the .opf file, so that it's preserved if the Mobipocket file is re-built from mobiunpack's output using Kindlegen.
Good job, thank you
pdurrant!
