Quote:
Originally Posted by Hitch
At the end of the day, I've found the simplest thing to do is to run a hand-crafted (Sigil) epub through Calibre thus: my epub->.mobi in Calibre; then that same .mobi->epub, again in Calibre, and then use that second, Calibre-generated epub, drag-n-drop it on KindleGen and get a Kindle-ready .mobi file which will withstand the rigors of K4PC second layer of encryption. The entire "problem" is not really anything more than the fact that the toc is named differently by the two different formats.
Hitch
|
Doesn't that process end up stripping out the extra <guide> elements that crutlidge was concerned about originally, though?
OTOH, you do get a kindlegen-created mobi with an inline toc that way.
ETA: Aha! But, I see you can edit the second epub in sigil, add back the semantics, edit the content.opf and change the "text" semantic to "start-reading," re-zip, and then kindlegen -> mobi and hey, presto! TOC and semantic index, both working!
A bit convoluted, but not TOO bad. And that's why they pay us the big bucks, no?
