View Single Post
Old 10-29-2016, 08:31 AM   #10
JustinThought
Groupie
JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.JustinThought ought to be getting tired of karma fortunes by now.
 
JustinThought's Avatar
 
Posts: 171
Karma: 3517858
Join Date: May 2016
Location: Monterrey, Mexico
Device: Samsung Tab-3 7"
Quote:
Originally Posted by DiapDealer View Post

To tell the truth, I'd almost be in favor of removing the wellformedness check altogether. 1) People seem to want to rely on it for more than what it was intended for. And 2) The preview window tends to immediately inform someone (pink box) when entered/altered code is fatally incorrect anyway.
No! No! Sometimes I do something REALLY stupid (I'm very good at that!) with a search and replace, and somewhere in one of the many files that make up the book, there's a real problem. This function helps me to find which file contains the error without having to page through them one-by-one. I'm not real fond of the idea of letting Sigil correct the problem; once I know which page contains the error, I can then discover what I've done and correct future behavior.

Last edited by JustinThought; 10-29-2016 at 08:35 AM.
JustinThought is offline   Reply With Quote