Quote:
Originally Posted by DiapDealer
There really wouldn't be much point in having Sigil give you an option to build the KF8 with kindlegen (by configuring kindlegen's location in Sigil).
|
I beg to differ.
Quote:
Originally Posted by DiapDealer
Building the MOBI/KF8 file is already as simple as dragging the ePub onto the Kindlepreviewer app from a file browser. The latest kindlegen is built into the KindlePreviewer app.
|
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?
Quote:
Originally Posted by DiapDealer
Sigil is an ePub editor. I think it's best if they focus on that and not muddy the waters with features for other formats.
|
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.
Quote:
Originally Posted by Perkin
Why not e-mail kidlegen makers and ask them to auto add TOC into their build pipeline.
|
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.