Thanks so much for the responses, but...
As much as I appreciate the number of them, none of you have really answered my question (that I probably asked badly).
My question:
With respect to eBooks ONLY, what can XHTML do that HTML cannot?
I would not consider myself an expert at HTML, but I've been editing my Sigil eBooks successfully for almost a decade now, and many of the cautions you made, I do watch out for, closing tags, proper syntax, etc.
I also realize that it is what is *in* the file that makes it HTML. But because of that fact that for all the eBooks I edit, (and I do edit any Kindle eBooks I buy to combine individual stories together when it's a series), it seems like nothing outside the realm of HTML seems to occur. Thus the question.
Most of what I do when I'm editing eBooks, (or rarely, writing an eBook), seems pretty straightforward. Occasionally, I will wish that there was a way to have a picture in the text with the text wrapped around it, but aside from that, I am fine. (and there probably is, but I don't know how)
But with all the push for Sigil to be able to do things with XHTML (and it did handle it pretty well before), I'm wondering if there are things in my eBooks that I can do with XHTML that I CAN'T do with HTML. Is there anything that people do in eBooks that XHTML can do that HTML cannot?
Once again, thank you for giving me much to think about, but I hope I can get some information to set my question to rest.
FDWojo
|