Quote:
Originally Posted by Hitch
Which is why I said, in my post: just build an OPF and an NCX, for your superclean HTML. Then drop the OPF onto Kindlegen or KindlePreviewer, and it will build a dual-MOBI file. Voila, no ePUB and you have what you need.
|
Kind of figured that as well, reading the
Kindle Publishing Guidelines.
Quote:
Originally Posted by Hitch
I will say this--I've used LO and OO and Word and Pages and all kinds of word processors, over the last decades. If OO or LO works for you, great, but the cruft output by any of them is pretty much the same. What needs cleaning is always pretty much the same, if, like most of us, you have utterly untrained (and untrainable, typically) authors. I can clean Word the fastest, of all the word-processing solutions. Just offered FWIW.
|
Oh, how I miss that feature of WordPerfect to view the source!
I haven't looked at MSWord since I was no longer required to provide user support for it, but LibreOffice has really worked on their regular expression engine the past few updates. Not perfect, but pretty good. I also like the feature to search for applied styles, fonts, etc.
Quote:
Originally Posted by Hitch
So: just build an OPF and an NCX. From what you've said, that's obviously well within the scope of your abilities. Place it in the correct relative position, with your HTML files directory, and drop that OPF on Kindlegen or Kindle Previewer. You'll have a dual mobi without any problems--and without an ePUB.
|
Certainly will give this a bash, instead of a whole ePub.
Quote:
Originally Posted by Hitch
BTW: you do know that your authors could send ePUB format to their Kindle email addresses, and get a formatted MOBI in their personal docs section of their Kindle, right?)
|
Whilst I do, for (most of) them this is akin to designing a returnable Mars rover.