Quote:
Originally Posted by bobcdy
I noticed in marking italics with <i> I forgot to end an italic section with the </i>. OK, I expected that correcting that mistake would be the end of the problem of the entire text being in italics until the end of the .xhtml containing file. WRONG. Sigil had helped me by adding <i> at the beginning of every paragraph with a </i> at the end of every paragraph. Thus to correct my error, it was necessary to remove all those extra <i> and </i>
|
That Tidy "feature" is very nasty, yes.
Quote:
Originally Posted by bobcdy
Is it possible to COMPLETELY turn off error checking and substitute something such as a notice of an error, or a color change, or even letting the epub author find the error on his/her own?
|
This is the general idea and something I'm working towards, yes. FlightCrew has to be integrated first so that I have
something that can actually notice, locate and describe the errors. That can then be used to inform the user of errors when switching from CV to BV; the user could then either fix the errors by hand or let the "simplified" Tidy do its thing (the code
has to become valid XML before leaving CV).
OPF and NCX editing is more important so it will come sooner, but that too depends on FC getting into the Sigil core.
We're slowly getting there.
I keep telling people that Sigil's obvious shortcomings are not there because I'm too stupid to notice them, but because I just
don't have the time to iron them all out as fast as both you and I want me to
. Hell, university work has been so tight lately it has almost been a full month since my last commit in the repo. That's the longest dev pause I've had since I started this project.
I think I'll have a few days for Sigil a week from now, but we'll see.