If I were you, I'd view the process in 2 stages1. Convert to HTML
2. Compiler to eBook.
Step 1, seems to be your problem area, and I'll divide this into two further sub-stages:
(a) Convert Quark to HTML
(b) Fix up the HTML
The better you can do (a), the less work is required for (b).
I would try (a) several ways and compare the results of each approach
- Use Quark's own conversion process to HTML (if it has one - I think it probably does)
- Load your Quark file in other programs that support the file format, and convert to HTML in the,
The results of the conversion may vary between different programs - more than you might think.
Once I had the best possible conversion for (a), I'd then edit the HTML code to fix the stuff up.
I am "code" type of guy, so tend not to use visual editors. However Storyman seems to love Adobe GoLIve, so that may be good for your if you like WYSIWYG.
Finally once you have the HTML out, converting to an eBook (step 2) should be relatively straight forward, including using our own compiler -- although you might want to do some fine-tuning of things like menus, toolbar appearances in the ebook settings, etc.