Quote:
Originally Posted by Sella174
Obviously.
And that is why how to get to the mobi and KF8 without first making a redundant ePub was the original question.
|
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.
This has nothing to do with Gutenberg. It's simply what happened, when various groups had differing opinions about the "best" format, when eBooks were uber-young. Just as Betamax and VHS were the battling formats, in the early days of video. {shrug}.
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.
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.
Good luck to you. I don't disagree with you, btw, about the era of lazy point and click computing, but after working with thousands of authors, in the last decade--of which we've received, MAYBE, 20 files in which the author actually used Styles or Headings--which obviously translate pretty perfectly to HTML and thus to ePUB/MOBI--I don't believe that you can train them. I used to think I could--but the truth is, you can't. Right-brainers in particular are resistant to learning things like Heading and Styles, even though it would be to their own massive benefit to use them. Even our repeat clients--nope. (n.b.: most of ours can't even use Track Changes right. So...)
So, I understand--somewhat--why you've taken the path you have, in importing their content to OO/LO, cleaning it up, etc. I'd do it in Word, but that's all a matter of preference. Don't ignore what I said about building the OPF, though. If you want to go direct-to-mobi, that's probably your best path. (Although, again, to me, they're much of a sameness. Yeah, verily, there are a few differences in the formats, but....{shrug}, not enough to really think about. 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?)
Hitch