Quote:
Originally Posted by mrmikel
If the option to turn off well-formed correction will not come back, then maybe introduce auto save to save us from ourselves.
|
Yeah, I know user_none has some ideas about this. They won't happen for the 0.6 release. But longer term, certainly. It should be possible to "undo" a Replace All operation for instance or roll back to some checkpoint be it time based or whatever. A simple "auto save" is not going to be enough - what if you screwed up half an hour ago and only just noticed? What if you keep Sigil open overnight, is it going to fill your hard disk with a new copy of the file every five minutes? It is a solvable problem, but not one that is trivial to implement.
As I've tried to explain above and diapdealer has mentioned, there are just too many parts of Sigil that depend on well formed xhtml. The Xerces component chokes on invalid html very badly - it is one of the causes of a number of the crashes that have plagued Sigil in the past.
In the meantime, treat Sigil like you would pretty much any other editor - if you are about to do something "dodgy", save first. You can also use the new Save A Copy feature in order not to overwrite your starting ePub, just to be sure you don't overwrite with some invalid changes you haven't noticed yet...