Thread: mobi2oeb
View Single Post
Old 02-17-2008, 12:03 PM   #8
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 26,432
Karma: 5383257
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
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>
kovidgoyal is offline   Reply With Quote