Not a problem and not in any way related to the bug. The bug also had nothing to do with splitting. It happens when anything invokes the parser (such as extracting subsets of xhtml as splitting does) when separate svg closing tags are used.
The bug is actually in some code that has existed since the time of Tidy way back in the Sigil-0.6 days. Tidy used to only support one xmlns prefix per tag, So there was code that someone wrote to Preprocess the code to remove the svg: prefix and fix the namespace. Only they did not use a real parser to do it and they did not properly handle prefixed end tags ala "/svg:text" and so the preprocessor ended up mangling your code. Very few people use much SVG and of course when they do it is typically embedding svg image tags for covers which are void tags (so no need for a separate end tag) so it seemed to work especially as the new gumbo autocorrecting parser fixed almost of of the broken cases. It took a more complex example like yours in order to see the bug at all. Even gumbo could not fix the damage done by the poorly written PreProcessSpoecialCases code.
I now work mostly in epub3 and of course the prefix is removed since svg is now part of html5 and it therefore completely avoids this messed up preprocessing code.
Either way the bug will be fixed for the next release. I realize you are not a heavy user of Sigil but dropping a line in any Sigil thread in MR would help when and if you run into other bugs.
All of the behind the scenes changes, happen because Sigil moves things to the structure it wants. This requires parsing and of course an auto-correcting parser (just like a browser uses) is needed. When I get support for fixed format epub3 done, I plan on spending some time changing Sigil to not relocate things (leaving the relocation code as a user option). That way the user can control if the parser is run or not if they do not use any of Sigil's more advanced tools.
KevinH
Quote:
Originally Posted by fbrzvnrnd
Yes, my fault, I make a copy & paste from the PDF version. If you like I could attach the ePub version, but there are only cosmetic differences.
|