Quote:
Originally Posted by JSWolf
You don't happen to work for Phoenix Pick do you? Their ePub code looks just like the code was pulled from an unpacked Mobi.
Do you really unpack Mobi to make ePub? How do you deal with cleaning out the HTML and then making the CSS?
|
Hi JSWolf;
Some .mobi books -especially if they were generated with Kindlegen 2.x- have a .kf8 version AND an old .mobi version inside (all the more, files generated by the service of Kindle Direct Publishing, are .mobi files). When we use KindleUnpack to unpack that kind of files, then the KindleUnpack produces an .epub book -for the .kf8 part of the original mobi- and others files for the .mobi7 part. We must work in Sigil with the .epub generated from the .kf8 part. Of course, if the book is an old one (previous to .kf8/azw3) then things are more difficult. Still we can build an epub with the .html, .ncx and .opf generated by KindleUnpack and the epub will work in ADE but won't validate at Epubcheck. If we want to be more prolix, then as you say, we have to use a lot of regex to clean de .html and after that to write a css stylesheet.
But still in the case that we have an old mobi and we make an epub with Calibre, also will have to work with it, because the .epub generated by Calibre is not the best one that we can build and have.
Regards