(preserved for backwards compatibility with its functions) List of inkscape: and sodipodi: namespaces (incomplete)
however, if you then re-edit the SVG in Inkscape (after hand editing, for example) 'without' removing the references to inkscape in the object that has been edited (for an example if you edit a path created using the inkscape star tool), then inkscape will re-generate the SVG path d="" attributes using the information that 'it' has stored under its namespace, and therefore getting rid of any editing to the path of that you, the user have done. if you edit an inkscape SVG in any other SVG editor, then it should appear as any other plain SVG, if not, then you can safely remove all references to inkscape: or sodipodi:, and just be left with the plain SVG. Inkscape SVG is basically the same as plain SVG, just with a few extra commands (in separate namespaces) added, which the Inkscape tools use to keep track of their work. All objects will be reconstructed from parsed data, but overall object hierarchy will be preserved." - quote from the documentation. 
"Saving document as 'plain SVG' actually invokes exporter.
seems to have a smaller filesize vs " PlainSVG" for some odd reason. gives Inkscape hints how to treat things in the UI - for example, whether to treat a given group as a layer, or whether path nodes are cusp/flat/whatever. Inkscape SVG should render identically with or without the Inkscape extensions. conforms to the SVG standard which permits extensions like those outlined here. 2 list of inkscape: and sodipodi: namespaces (incomplete).
0 kommentar(er)
