View Single Post
Old 09-19-2014, 02:05 PM   #18
JimmyG
Zealot
JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.JimmyG solves Fermat’s last theorem while doing the crossword.
 
Posts: 119
Karma: 28454
Join Date: Apr 2011
Location: Yuma, AZ
Device: Kindle Touch, Voyage
Used preview on a file and it told me there was an error just before the </body> tag (where most Sigil errors occur,) had to upload the file to W3C to find it. Missing </p>, nowhere near the </body>. As I said, not that helpful.

I've discovered that the p button won't work until I've closed the enclosing blockquote tag. Even the smarty quotes plugin does error checking. That's just obsessive.

Lurking somewhere in all that error checking is a routine that tries to fix the error without asking the user first, and that is what is truncating files. And that is a BUG. To destroy hours, days, or even weeks of work without notice either before or after is simply inexcusable, and I don't care what anyone says about structure, design, blah, blah, blah.

Hopefully, I can finish this one book, and then Sigil goes back on the shelf. Perhaps some can write error-free html on the first pass, but I can't. I leave the error checking to the end (EpubCheck on idpf) just before and after the final proofread.
JimmyG is offline   Reply With Quote