Why do I need to see the ePub code?
Once the odt has been cleaned and properly styled, one of the things that gets done to it, is it gets exported to HTML. This HTML file is cleaned (by a little script that heavily uses regular expressions), eye-balled and uploaded to the website. Thus I already have super-clean HTML in my possession.
Please understand that the authors do not understand HTML, the ePub format or for the most part anything beyond the basics of their word processing program. Any revision of the text is done by them using their word processor. So editing the HTML or an ePub as a source document is seriously out.
The readers are asking for mobi files, because they have Kindles. I was therefor looking for a way to generate the mobi from what I already had, namely HTML, odt or PDF (derived from the odt). But it seems I need to package the HTML into an ePub before I can create a mobi. Silly, but an expected reality in this age of lazy, point-&-click computing.
So I'm writing a program that will package the HTML in a valid ePub, along with added metadata, without trying to be intelligent and messing up my neat HTML files.
|