[Hitch]

Originally Posted by Doitsu

I beg to differ.


I'm aware of that option, but why force users to open another full blown GUI application, when this functionality could be easily added by a programmer in a couple of minutes?

Why screw up Sigil, a smashingly good epub tool, when it takes 30 seconds to drag a properly-crafted ePUB onto Previewer, which you'll have to use anyway to test the book on multiple devices, assuming you don't have an iPad, a Kindle, a K-3, a Fire, a Droid tablet, and iPhone, etc.?

Based on your post history you didn't strike me as a stickler for protocol who insists on doing everything by the book. Isn't adding useful features always something that adds value to a program? IMHO, simply insisting on blindly following the "pure doctrine" doesn't make much sense.

I think everyone's entitled to their opinions, heavens know, but part of the problem here, IMHO, is the (repeating) sense that Sigil's an authoring tool. It isn't. It's a tool for people who regularly work in html, xhtml, css and regex. For WYSIWYG insta-ebook-creation, authors and small imprints can use Scrivener, JUTOH, Atlantis Word Processor, etc. My personal opinion is that this belief is fostered by the language that Sigil is a "WYSIWYG editor," which is, truth be told, pure nonsense (no offense, @user_none or @V). Just bollocks, as we see here every day in the myriad questions we get that can't be "fixed" from any WYSIWYG perspective. for that matter, take one look at the new Search and Replace functions--not exactly WYSIWYG-"author"-friendly, in any sense.

I don't understand why anyone would (routinely and repetitively) need 6 programs, but, hey--to each their own. We use a wide number, but primarily, if you're using Word, your path invariably is Word-->good html editor (like NoteTab Pro, my own fave)-->Sigil. From Sigil, if you want a MOBI, you can use Calibre if you wish, or KindleGen. Not sure what the other two programs would be, but those four pretty much cover the gamut. OO has the same path; even WordPerfect goes that way.

I agree that Amazon should add an automatically generated inline TOC to their Kindlegen ePub conversion code. However, given Amazon's track record when it comes to responding to customer requests, this is not very likely to happen anytime soon.
However, the current Sigil maintainer user_none is not bound by these limitations and could easily implement this feature.

Well, for that matter, if someone doesn't want to make their own inline TOC's, they can either use Calibre, again, or use "epubfixer," altho I find the latter very unintuitive. We have a clip that makes our inline TOC's for KindleGen, as given the Guide architecture, we don't foresee that changing anytime soon--if it were to change, I should have thought we'd see it in the Fire, (not via adding an inline TOC, but by using the ncx as does ePUB) and we didn't.

I can virtually guarantee that user_none certainly won't implement a Magic KindleGen Maker Bullet into Sigil anytime soon, and certainly not while Amazon holds mobi as proprietary. It's just not his bag, as we oldsters used to say.

Just my $.02,
Hitch