Quote:
Originally Posted by brontus
Hitch & Doitsu,
I was the one with the 6 programs. Prior to KF8, my workflow was:
1)OpenOffice to clean up formatting to be more ebook compatible & save as HTML
2)gEdit/Notepad++ to clean up HTML, inline TOC
3)GIMP to create or edit cover image
4)MobiPocket Creator to start process of creating mobi file
5)Back to Notepad to form toc.ncx file and edit opf file
6)Back to MPC to finish mobi file.
7)Kindle Previewer to validate.
8)Sigil with original html file of step 2, split chapters into separate files, validate epub.
6 programs. If I thought I was up to the task of extending Sigil, I would do it.
|
Hi, @brontu:
Well, counting GIMP is a bit much, as you'd have to use that for your cover no matter what you did.
I've no idea why you'd use MBPC-->NT or Notepad-->for the ncx and opf; we do it in Sigil when needed. Everybody has their own workflow, of course; but it seems really redundant to me. It seems that you're making the Kindle first, and the epub second--we always do the opposite, as I prefer to do the (relatively "upcoded") epub first, and then downcode for the MOBI, and add the necessary items (i.e., explicit sizing for images, etc.).
ETA: Actually...you're creating two books on two paths.
That's what threw me. We use the completed ePUB, so we don't have two editing paths. Of course, we're doing this commercially, so I have to be certain I have conformed books; I make the Kindle files, literally, from the final ePUB files.
@Doitsu:
You don't need a GUI. You can drop the completed ePUB file on the command-line KindleGen, as well. You don't even need to run it from the command-line, as someone with your skillset obviously knows.
Here's my question: is your entire desire for Sigil to simply make an inline TOC? Because really, there's not much else needed for KG; so I'm inferring from your post that what you really want is an inline-TOC-maker and an integration to the KG command-line tool. Is that correct? Do I understand you rightly?
Hitch