On Thu, 2014-11-27 at 21:54 -0700, Brynn wrote:
Hi Friends, And there's a 3rd item to clarify, if someone has a chance. and please note that these can all wait until after 0.91 is released! The faq item "Inkscape and renderer X show my SVGs differently. What to do?" mentions the Adobe SVG Plugin, which of course has been discontinued a few years ago. The text is below. Can "Adobe SVG plugin" just be deleted? If so, does the rest of the item need to be rewritten? I do see this question from time to time, in forums, so it's worth keeping the faq item. Just want to have a correct answer :-)
"That depends on X. We accept Batik and Adobe SVG plugin as authoritative SVG renderers because they are backed by some of the the authors of the SVG standard and really care about compliance. This may not be true for other renderers. So if you are having a problem with some renderer, please try the same file with either Batik or Adobe, or better yet, with both (they are free and cross-platform). If you still see a discrepancy with Inkscape rendering, we want to look into it. Please submit a bug; don't forget to attach a sample of the problem file to the bug report, and ideally include screenshots too"
The Adobe plug-in is dead dead dead. It has some quirks so no longer should be used as a point of reference. Batik is a much better implementation of SVG 1.1 but even it is beginning to show it's age.
For SVG 1.1 level stuff, I usually compare the rendering of Batik (squiggle), old Opera (Presto), Firefox, and Chrome. For more recent stuff (CSS3, SVG2) I pretty much rely on comparing the rendering of Firefox and Chrome. IE and Safari tend to be behind in the implementation curve.
Tav