Quote:
Originally Posted by jackie_w
Obviously I can't speak for anyone else's usage, but I've never needed or wanted to 'refine' any SVG code with this plugin. I only use it for <div> and <span>.
|
That's sort of where I am, too. I use the plugin for doing bulk edits that would otherwise be unwieldy and/or dangerous with regex. In the unlikely (or at least rare) event that there's something wrong with some SVG code in an epub, I'd find it pretty easy to manually fix it. It's not like there's divs or other inline elements in need of tweaking being used within SVG tags in the first place.
I think I'll proceed with my plan to "exempt" SVG from the plugin's parsing routine. That way it won't be making meaningless whitespace changes to svg code (which will then trigger a rather pointless diff to be verified).