.SVG files made are not W3C valid

[Clay Smalley]

Example: http://validator.w3.org/check?uri=http%3A%2F%2Fwiibrew.org%2Fw%2Fimages%2F1%2F19%2FWiimote_Aim.svg&charset=(detect+automatically)&doctype=Inline&group=0

My idea:
* Make the default save file something like .IVG (Inkscape Vector Graphic). The file itself should have the same data as if it were saved as a .SVG in the current version of Inkscape.
* Make an option "File->Export as .SVG". It should make a well-formed, valid .SVG that doesn't have the attributes like "id", "sodipodi:xyz", and "inkscape:xyz".
* I guess the first time a user tries to save it as .SVG, the program should warn them loss of Inkscape-specific data (but if you do this, please make a "do not show this again" checkbox).

I remember making a topic about this a while back, and people responded, but I didn't get quite the response I needed. So I'm making a new bug topic, with more details and an example.

[Thomas Hicks (hicks-kingtom)]

The file that you link to should actually validate as it is valid xml. The problem is is that the validator does not seem to be namespace aware (or at least cannot coupe with multiple namespaces in svg documents see: http://www.w3schools.com/XML/xml_namespaces.asp for info on namespaces.

Inkscape svg's have an inkscape: namespace to help with editing the file in inkscape, as allowed by the xml specification. If you want to save files from inkscape without the extra namespaces, then you need to save as Plain SVG. This only contains the SVG namespaced elements, and validates according to the w3g validator.

Use: File -> Save AS -> Plain SVG

For more information see this FAQ:
http://wiki.inkscape.org/wiki/index.php/FAQ#Are_Inkscape.27s_SVG_documents_valid_SVG.3F

[nightrow (jb-benoit)]

Can you please confirm or invalidate this bug ?
Thanks

[Niko Kiirala (kiirala)]

As noted by Thomas Hicks, this is not an Inkscape bug, but a problem in the w3c online validator. Note that not validating external namespaces is most likely an informed decision made by the validator developers, due to security considerations. Then again, it shouldn't flag them as errors, either...