mobi2oeb

[kovidgoyal]

After an 8-hour hackathon I'm happy to announce mobi2oeb. Converts (non DRMed) .mobi/.prc files to an exploded OEBPS ebook. Supports all three levels of compression in .mobi files. Part of libprs500 v0.4.37. To use

mobi2oeb book.mobi

This is an initial release, so expect bugs. Thanks to darkninja for the HUFF/CDIC decompression code.

[HarryT]

Great! Thanks, Kovid; this will make it very easy to edit a MobiPocket book. Use your tool to explode to OEB, make the edits, then use Mobi Creator to rebuild it.

[Ortep]

Originally Posted by kovidgoyal

After an 8-hour hackathon I'm happy to announce mobi2oeb. Converts (non DRMed) .mobi/.prc files to an exploded OEBPS ebook. Supports all three levels of compression in .mobi files. Part of libprs500 v0.4.37.

Sounds great, But look what I got when I clicked on the link:

There is a problem with this website's security certificate. 
 
   
 The security certificate presented by this website was not issued by a trusted certificate authority.

Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.  
  We recommend that you close this webpage and do not continue to this website.  
  Click here to close this webpage.  
  Continue to this website (not recommended).  
     More information 


If you arrived at this page by clicking a link, check the website address in the address bar to be sure that it is the address you were expecting. 
When going to a website with an address such as https://example.com, try adding the 'www' to the address, https://www.example.com. 
If you choose to ignore this error and continue, do not enter private information into the website. 

For more information, see "Certificate Errors" in Internet Explorer Help.

[Nate the great]

That's because he doesn't have the money to pay for a security certificate. His site has alway been that way. I just checked again; his site is still there. I canvouch for him.

[Ortep]

Ok, thanks

We can't be to carefull these days

[FixB]

Thanks kovidgoyal !
Once again, your work helps us all so much !!

[nrapallo]

Originally Posted by kovidgoyal

After an 8-hour hackathon I'm happy to announce mobi2oeb. Converts (non DRMed) .mobi/.prc files to an exploded OEBPS ebook. Supports all three levels of compression in .mobi files. Part of libprs500 v0.4.37. To use

mobi2oeb book.mobi

This is an initial release, so expect bugs. Thanks to darkninja for the HUFF/CDIC decompression code.

I used my 'mobi2imp' (version 5) to output 'SpaceEncyclopedia.mobi' into OEBFF (.oeb) output. I use:

mobi2imp --oeb 'SpaceEncyclopedia.mobi' Space

Can you check it against the output of mobi2oeb? Can you load my .oeb in mobicreator or use it with libprs500 utils?

Our (ebook format) worlds are crossing...

-Nick

[kovidgoyal]

There are really only a handful of things to do in mobi->oeb conversion so I see no reason why your OEB output should be wrong. THey are
1) Read metadata from the EXTH header to create the .opf file
2) Decompress the text using the three possible compression chemes
3) Replace the filepos attributes
4) Replace the mobi specific tags like <mbpagebreak>
5) Extract the images and replace the <img recindex> tags

At the moment, the only not fullly implemented step is 4). The only mobi specific markup that mobi2oeb replaces is <mbpagebreak>

[nrapallo]

Originally Posted by kovidgoyal

There are really only a handful of things to do in mobi->oeb conversion so I see no reason why your OEB output should be wrong. THey are
1) Read metadata from the EXTH header to create the .opf file
2) Decompress the text using the three possible compression chemes
3) Replace the filepos attributes
4) Replace the mobi specific tags like <mbpagebreak>
5) Extract the images and replace the <img recindex> tags

At the moment, the only not fullly implemented step is 4). The only mobi specific markup that mobi2oeb replaces is <mbpagebreak>

Hey, this reads like psuedo-code and would be a great guide to 'rolling-your-own' program.

However, for me, this was all accomplished by using tompe's 'mobi2html' and making my .IMP specific changes to get 'mobi2imp'.

So, in the end, it appears we get the same result.

Cool!

-Nick

[brecklundin]

kovid....kovid...kovid....awesome...thanks!!

here is the best I can offer in return:



She is yours...

[kovidgoyal]

I appreciate the gesture, but I have to say I like 'em with a leetle more meat on the bones

[brecklundin]

your wish is our command oh great code breaker...

[IceHand]

Nice work, thanks! One question though: is it normal that the exploded html file has only three lines? Line one is always "<html><head>" line two is "<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />" and line three is the rest. It's no problem to make some breaks with par, but the resulting html code is not very cleary arranged for manual editing.

[llasram]

Originally Posted by IceHand

Nice work, thanks! One question though: is it normal that the exploded html file has only three lines? Line one is always "<html><head>" line two is "<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />" and line three is the rest. It's no problem to make some breaks with par, but the resulting html code is not very cleary arranged for manual editing.

All of the pre-.epub HTML-based e-book formats seems to do this – strip out all “unnecessary” whitespace to save space. ConvertLIT tries to fix this for LIT files by adding whitespace to the generated HTML, but it gets it wrong often enough to be troublesome. For adding whitespace and otherwise cleaning up grody HTML check out HTML Tidy.

[IceHand]

Thanks for the tip, but I already knew of HTML Tidy and it won't generate a cleaned up version if the source file has errors – which includes most exploded Mobipocket html files.

Anyway, I had a closer look at the html code and it seems that running a search and replace for "> <" with ">\n<" does the trick. Maybe an idea for the next mobi2oeb version?