Quote:
Originally Posted by Ahmad Samir
Turning off the check for well-formed errors doesn't do what you think it does; actually turning that one off means that Sigil will auto-fix any errors without asking you ... generally, not a good idea. (see the tooltip of that button).
FWIW, when you do a "Replace All" in "All HTML files" any well-formed errors are auto fixed without asking you regardless of the state of "check for well-formed errors" option.
|
Thanks! I didn't know this. I unchecked it, because I didn't read the tooltip carefully
I tried to repeat this with the button enabled (checked) with the same results; too much automation deleted contents from my files. As you say, the state of this switch probably doesn't matter.
But I really do not understand why automatic error-correction is done after each search and replace? When you choose to do something in code view, the programmers of Sigil must assume that the user knows what he/she is doing and allow the user to shoot oneself in the foot if he/she whishes to do so? I'm sure there are scenarios where you could want to do a search and replace in two stages, and auto-correct errors after the second stage, but not after the first