Hi roger64,
The serializer I wrote for Gumbo will always produce xhtml that can be parsed by an html5 parser (only void tags will ever self-close, any void tags with separate closing tags will be made self-closing, etc). Using gumbo as the heart of the parsing/repairing engine in Sigil will always see to that.
So call it .xhtml but for epub3, anytime we parse the file and serialize it we are effectively creating polyglot html5/xhtml using xhtml serialization rules that will always parse in a spec compliant html5 parser. I just think it is nuts to have 2 (3 if you count pure xml, 4 if you count xhtml5 as different to xhtml 1.1) different specs when proper serialization can generate code that is recognized the same way under html5, xhtml5, xhtml 1.1 and xml 1.0.
Thanks,
KevinH
|