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

[tkeo]

Hi DiapDealer,

Originally Posted by DiapDealer

Just out of curiosity, are you manufacturing the "linear=No" attribute for the created cover page's spine entry? Or is that something that unpacks "as is"?

I wrote "linear=No" on purpose. I thought it should be set to "No" for a cover page; from a few references:
http://blog.threepress.org/2009/11/2...-cover-images/
https://wiki.mobileread.com/wiki/Ebook_Covers
But, I am not confident so much.

Originally Posted by DiapDealer

I prefer the somewhat "standard" svg method of creating a cover page, but that's just a personal preference. Feel free to take a look at my hacked-up mobi_k8resc.py file if you're interested at all. I've added a 'borrowed' method to get the necessary dimensions of jpeg, gif, or png images (and removed the 'linear' attribute for my own selfish reasons). Don't feel any pressure to adopt my changes or anything. I don't mind adjusting the "official" codebase to suit my needs. That's how I get my practice.

Thanks for your input on the project, by the way. Much appreciated!

I am impressed by looking at the code you posted (though 'borrowed'). It's quite nice!
In oder to use svg wrapper, the size of an image is necessary; I thought it needs an extra library like PIL, (I don't hesitate to use the PIL if it was just for my private use.) To avoid using the extra library, I wrote that style.

Thanks,

[DiapDealer]

Originally Posted by tkeo

I wrote "linear=No" on purpose. I thought it should be set to "No" for a cover page; from a few references:
http://blog.threepress.org/2009/11/2...-cover-images/
https://wiki.mobileread.com/wiki/Ebook_Covers
But, I am not confident so much.

Yours is probably the best approach for source/epubs that are going to be edited and then run right back through kindlegen. That's what Amazon suggests, actually--to get around their no cover-page "rule" with epubs as the source. For those who may be using KindleUnpack simply to get a clean(er) epub from a KF8, that may not be in their best interest. But it can be easily changed in an editor in that case, too.

I would stick with your approach, though. I asked mainly because I couldn't find where that string was created, at first glance.

I thought it needs an extra library like PIL. To avoid using the extra library, I wrote that style.

I thought the same thing (PIL)! Then a search turned up that particular method. I guess in a perfect world, I'd like to see the dimensions stored in the same dictionary as the image names when the image data is first extracted--so there'd be no need to re-read that file in the cover-page creation routines--but that's for a future rainy day.

Of course, I quickly cobbled that together--I suspect it might break easily. Probably needs to be some basic error-handling to make it die a little more gracefully if that happens.

[m0ngr31]

How hard would it be to be able use this to update the meta information inside a mobi (like mobi2mobi) instead of unpacking it?

[DiapDealer]

Originally Posted by m0ngr31

How hard would it be to be able use this to update the meta information inside a mobi (like mobi2mobi) instead of unpacking it?

There's lots of code in Kindleunpack used for accessing the EXTH data. But with the exception of a few routines in the portion that splits hybrid mobi/kf8's, it's not really geared toward modifying existing binary kindlebooks "on the fly," so to speak.

[pdurrant]

Originally Posted by m0ngr31

How hard would it be to be able use this to update the meta information inside a mobi (like mobi2mobi) instead of unpacking it?

It would need a whole lot of new code, I think. Extracting to files, or stripping out sections is very different to re-writing (say) the EXTH section.

But this is probably you best place to start if you want to have a stand-alone modern python-based mobi2mobi kind of function.

The other alternative would be the calibre source code, which (obviously) already has code to create Mobipocket format files.

[shyamusingh]

Hi All,

Can any one suggest me how can I convert ePub format to kf8 format...

thanks in advance...

Shyamu Singh

[hosein]

Originally Posted by shyamusingh

Hi All,

Can any one suggest me how can I convert ePub format to kf8 format...

thanks in advance...

Shyamu Singh

Hi,
Use kindle previewer program.
Open the epub in the program.
The program automatically convert it to mobi.

[pdurrant]

Originally Posted by shyamusingh

Can any one suggest me how can I convert ePub format to kf8 format...

Calibre can also convert from ePub to KF8/AZW3. Provided the ePyb doens't have DRM of course. If that's the case, google for Apprentice Alf.

[shyamusingh]

Originally Posted by hosein

Hi,
Use kindle previewer program.
Open the epub in the program.
The program automatically convert it to mobi.

Thanks a lot for your support...

Basically I want to know what are changes required when we convert ePub to KF8..

rgds,
Shyamu

[shyamusingh]

thanks pdurrant for your support...

This is an automatic conversion by calibre but there are lots of correction required in ePub before convert to KF8.

So what are the changes required in ePub thats I want to know...

rgds,
Shyamu

[DaleDe]

Originally Posted by shyamusingh

thanks pdurrant for your support...

This is an automatic conversion by calibre but there are lots of correction required in ePub before convert to KF8.

So what are the changes required in ePub thats I want to know...

rgds,
Shyamu

Generally speaking there are no changes required to ePub in order to convert it to KF8. KF8 can be thought of as a compiled version of ePub where the ePub source is compiled into a KF8 binary in a mobi wrapper. Read about it on our wiki under KF8.

Dale

[pdurrant]

Originally Posted by shyamusingh

This is an automatic conversion by calibre but there are lots of correction required in ePub before convert to KF8.

So what are the changes required in ePub thats I want to know...

If using calibre, there are no specific changes required to the ePub.

If using Kindlegen or Kindle Previewer, there are some Amazon-specific changes you could make (see the Amazon documentation), but that's to turn the ePub into source for Kindlegen rather than changes to the ePub to make it a better ePub.

[DaleDe]

A recommended addition to the ePub is to ensure that it has a inline TOC. Some conversion techniques won't include the ePub TOC so you need on in the document itself.

Dale

[shyamusingh]

Thanks to all of you for your support..

[EbokJunkie]

Have a very limited expertize in Python but have a pressing need to edit some fields in exth of existing azw3.
Looking at mobi_split code I found all function needed for editing mobi file and saving result to azw3, that is read_exth, del_exth, and add_exth.
In my case I don't have mobi but have only azw3 file.
Could you give me some general ideas how can I apply the same tools that class mobi_split provides (sure only if they are applicable) to simple azw3 editing?
I just need to add 501, and modify 202 with content of 201.
Added:
Found this and understood that solution is not that easy nut to crack...