Hi,
Again, please provide a repeatable set of steps and a sample file, and I would be happy to look into this and try to fix it if it is really eating text. And I agree ... No matter how poor the tags are, text node information should never be lost. So if it is losing text, I too consider that a bug.
That said, I have never lost any text using Sigil. So I need some help tracking down where and how this is happening. That is why I need a sample file and sequence of steps to find the true cause of your issue.
I do agree that sometimes Sigil description of where to look for the issue leaves a lot to be desired. Finding and fixing single missing tags could be done in a plugin if we find out the issue is in Tidy someplace.
So if you can recreate any of your "eating text" bugs repeatable I would be happy to try and fix it.
KevinH
Quote:
Originally Posted by JimmyG
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.
|