Quote:
Originally Posted by thiago.eec
Maybe I wasn't clear. Image I already have a book with a linked resource. If I don't know about this and open the book on Sigil, do some changes and save, then the file would be deleted.
|
Not any more. That's what Kevin's fix is all about. This single spec compliant, unmanifested file (a properly referenced file in a metadata link element) will not be deleted any more. A plugin will (hopefully) be added so that Sigil users can add this file from within Sigil.
Quote:
Originally Posted by thiago.eec
Sigil should detect the linked resource and let it be, even without the plugin (altough it would be necessary for further actions, such as editing the file).
|
It will. In the next release of Sigil. However ...
Sigil is a long way from allowing user-defined archive structures. As such, there are no guarantees that unmanifested files which aren't specifically allowed by the EPUB specs will survive a Sigil save.
This was a one-off fix for your specific issue. Sigil won't delete this spec-compliant, non-manifested file any more (or others if we learn of them). But accommodations aren't going to be made for just any old files that might be included willy-nilly in an EPUB's archive. Sigil currently requires epubs to have a very strict structure. That's not going to change any time soon (even though we all might like it to). That type of functionality is going to require a
huge overhaul of Sigil's codebase: something neither of us has the time for right now.