View Single Post
Old 10-29-2016, 09:00 AM   #11
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JustinThought View Post
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.
Fair enough. We just have to find a way for people to understand that it's NOT any kind of validator (neither for xhtml nor epubs). It's a quick and dirty test to make sure that all existing tags have been properly closed and that there's been no improper nesting of tags. Nothing more.

It's an "at a quick glance, nothing seems to have gone terribly wrong" tool. Not an "everything in your epub is absolutely perfect" tool.
DiapDealer is offline   Reply With Quote