Quote:
Originally Posted by Moonraker
I have used ebook Publisher (v2.2.3) for many years to create .imp files from my own XHTML code.
I could not get Mobi2Imp working at first because it could not find Publisher but after I updated it to v2.2.5 all worked well.
I was surprised that Publisher had been updated because I understood it was not being supported any more.
Mobi2Imp is a great and useful tool.
I have only one gripe - why does it replace a closing </p> with <div height="0em"></div> <div height="0em"></div>?
This makes for a larger than necessary file and also it is difficult to edit the html code to correct it. |
Mobi2IMP does not parse the HTML code; it just does some (global) search and replaces to "fix" things that are "broken" when used with eBook Publisher.
The </p> endings are being stripped/altered BEFORE the .prc is used by Mobi2IMP. I'm not sure if it is tompe's Mobiperl code or the use of BookDesigner. I think BookDesigner may be the culprit of the '<div height="0em"></div> <div height="0em"></div>' construct. Either way it's not Mobi2IMP's doing.
BTW, if you can read perl, check the source, mobi2imp.pl, for items replaced by Mobi2IMP.
I've used eBook Publisher for years and have come to respect its power and usefulness. It also doubles as great "validator" of HTML v3.2 code since it gives detailed error messages and points to the error in the source file.
Sure, it has a few shortcomings (image re-sizing fails to honour bottom margin; missing fraction HTML numeric codes; ...) but it has seen some improvements over the years (margin indents work better now; new default 'small' font size for eBookwise 1150; ...).
If you have any more specific Mobi2IMP questions/comments, please be sure to post in the thread
Mobi2IMP 9.4 with new Windows GUI released! Here, we discuss the current (and future) version of Mobi2IMP.
p.s. drool... How do you like the iLiad vs. the eBookwise 1150?