Quote:
Originally Posted by DNSB
The latest version (I think) shows in the E.2 Manifest item Properties in section E.2.6.
A minor nit but if it can be fixed, would be much appreciated.
|
Not so minor, to do it properly:
Quote:
This property MUST be set when SVG markup is included directly in the resource and MAY be set when the SVG is referenced from the resource (e.g., from an [HTML] img, object or iframe element).
|
In other words, while the cover document is the most common place this would be found, it’s not at all the only one. A proper implementation of this feature would have to scan every file in the ebook for SVG markup and flag all of them appropriately. That’s a significantly nastier can of worms.
I mean, there’s nothing conceptually wrong with saying, in effect, “I’m changing the cover and specifying SVG markup, therefore I should check the EPUB version and see if I need to slap the properties attribute on it in the OPF” – but that still leaves the rest of the ebook unchecked, just waiting to generate those validation errors you want to avoid.
And then, on top of all that, the code has to deal with the possibility that a properties attribute already exists, meaning it has to be checked and correctly modified…