Suggestions for Sigil Improvements or New Features

[KevinH]

And this thread is effectively closed as the time for our 2.7.0 release is approaching. Please save any future feature requests until after Sigil 2.7.0 has been released and a new suggestion thread has been created.

Thank you.

[un_pogaz]

Originally Posted by KevinH

[...] and all the possible crap that would need to be fixed if the file selected does not meet the epub standard (i.e. no nav, no spine, broken spine without xhtml included in it, missing manifest items, missing metadata, etc).

Oh it not even that, just that if the file is not recognized, assume that it a epub and import as it. And if Sigil fail to open it as epub (with the regular already existing auto-fix eature), well, too bad but you shouldn't have tried to open a file that wasn't an epub.
But that a very low request.

EDIT: My philosophy is that if you open a file with specific software in a command line, the software should not check the extension and should always try to open the file at least in a default format. And if the file is invalid (in it content), the file is invalid, end.

[JSWolf]

Originally Posted by DiapDealer

Kepub should be considered proprietary in my mind. Only Kobo uses it. I have no idea if it's spec compliant or not (I tend to doubt it), but I'm not on board with adding it as an extension that Sigil can handle inherently.

A KePub is an ePub (2 or 3) that has added spans and maybe some.js code. to work with the KePub renderer Kobo uses. I don't think the .js code is used any more.

You can remove all of the code that makes it a KePub with the Modify ePub plugin for calibre and then when you send it to the Kobo, you can have all of the code put back in by the Kobo Touch driver.

IMHO, it can be a lot more difficult to edit with all of the spans then a plain ePub depending on what you are editing.

[KevinH]

Since the concept of a thread being closed seems to have been lost, I will repeat it here.