This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As a significant bit of SVG on the web is created with these programs, through "save" instead of the "save As plain SVG", i think it would be very useful to provide some helpful feedback to improve the situation.
You may want to explain what the "situation" actually is...
Inkscape/Sodipodi save SVG with lots of stuff in their custom namespaces, which the validator complains about. With loads of these 'complaints' it's rather difficult to notice the actual SVG-errors (especially if you're not an XML expert).
(In reply to comment #2) > Inkscape/Sodipodi save SVG with lots of stuff in their custom namespaces, which > the validator complains about. Understood. I am however unsure what a good solution for this would be, short of finding a good way to make the parser understand or ignore foreign-namespace stuff
If an error contains "sodipodi:" or "inkscape:" -> "your SVG is likely to have Inkscape-specific (ignored by SVG viewers) information in it, which because of limitations in the current version of this validator, would then result in error reports on content that could very well be actually valid". If you want to get rid of these 'errors' you can open the file with Inkscape and save (a version) as "plain SVG". Not nearly a perfect solution, but better than the current situation i think.
maybe some Inkscape developers can help on this matter