This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5051 - hints on Inkscape/Sodipodi SVG
Summary: hints on Inkscape/Sodipodi SVG
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: Test Suite (show other bugs)
Version: HEAD
Hardware: All All
: P5 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-14 12:36 UTC by Ruud Steltenpool
Modified: 2007-10-27 11:29 UTC (History)
0 users

See Also:


Attachments

Description Ruud Steltenpool 2007-09-14 12:36:03 UTC
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.
Comment 1 Olivier Thereaux 2007-09-17 23:16:58 UTC
You may want to explain what the "situation" actually is...
Comment 2 Ruud Steltenpool 2007-09-18 11:01:10 UTC
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).
Comment 3 Olivier Thereaux 2007-10-09 10:01:50 UTC
(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
Comment 4 Ruud Steltenpool 2007-10-24 05:54:33 UTC
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.
Comment 5 Ruud Steltenpool 2007-10-27 11:29:53 UTC
maybe some Inkscape developers can help on this matter