Inkscape Wiki - User contributions [en]

Inkscape SVG vs. plain SVG

2006-01-31T15:08:58Z

Abel: /* Inkscape SVG vs. Plain SVG */

== Inkscape SVG vs. Plain SVG ==

Some notes about "Inkscape SVG" [http://sourceforge.net/mailarchive/forum.php?thread_id=7412326&forum_id=37513 ref]:
* the default mode of saving
* standards-conforming (the SVG standard permits these kinds of extensions)
* should render identically with or without the inkscape extensions
* 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
* seems to have a smaller filesize vs "Plain SVG" for some odd reason

"Saving document as 'plain SVG' actually invokes exporter. All objects will be reconstructed from parsed data, but overall object hierarchy will be preserved." -- quote from the documentation.

From my perspective,
* inkscape svg is basically the same as plain svg, just with a couple of extra commands (in seperate namespaces) added, which the inkscape tools use to keep track of their work
* 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 sophadia:, and just be left with the plain svg (?)
* 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.

-please correct as neccessary
Thomas

OK, a little table of the extentions that inkscape SVG uses:

<svg>
inkscape:output_extension
inkscape:version
(sodipodi:docbase)
(sodipodi:docname)
sodipodi:modified
sodipodi:version
<sodipodi:namedview>
bordercolor
borderopacity
id
inkscape:cx
inkscape:cy
inkscape:pageopacity
inkscape:pageshadow
inkscape:window-height
inkscape:window-width
inkscape:zoom
pagecolor
<svg:07:07, 31 January 2006 (PST)Gradients>
inkscape:collect
<svg:path (in patten defs)>
sodipodi:cx
sodipodi:cy
sodipodi:rx
sodipodi:ry
<svg :path (in spiral)>
sodipodi:argument
sodipodi:cx
sodipodi:cy
sodipodi:expansion
sodipodi:radius
sodipodi:revolution
sodipodi:t0
sodipodi:type

<svg:path (in star)>
inkscape:flatsided
inkscape:randomized
inkscape:rounded
sodipodi:arg1
sodipodi:arg2
sodipodi:cx
sodipodi:cy
sodipodi:r1
sodipodi:r2
sodipodi:sides
sodipodi:type
<tiled clones>
first tiled shape (clone)
inkscape:tile-cx
inkscape:tile-cy
inkscape:tile-h
inkscape:tile-w
<others>
inkscape:tiled-clone-of
sodipodi:nodetypes?

Inkscape SVG vs. plain SVG

2006-01-31T15:07:20Z

Abel: /* Inkscape SVG vs. Plain SVG */

== Inkscape SVG vs. Plain SVG ==

Some comments about "Inkscape SVG" [http://sourceforge.net/mailarchive/forum.php?thread_id=7412326&forum_id=37513 ref]:
* the default mode of saving
* standards-conforming (the SVG standard permits these kinds of extensions)
* should render identically with or without the inkscape extensions
* 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
* seems to have a smaller filesize vs "Plain SVG" for some odd reason

"Saving document as 'plain SVG' actually invokes exporter. All objects will be reconstructed from parsed data, but overall object hierarchy will be preserved." -- quote from the documentation.

From my perspective,
* inkscape svg is basically the same as plain svg, just with a couple of extra commands (in seperate namespaces) added, which the inkscape tools use to keep track of their work
* 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 sophadia:, and just be left with the plain svg (?)
* 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.

-please correct as neccessary
Thomas

OK, a little table of the extentions that inkscape SVG uses:

<svg>
inkscape:output_extension
inkscape:version
(sodipodi:docbase)
(sodipodi:docname)
sodipodi:modified
sodipodi:version
<sodipodi:namedview>
bordercolor
borderopacity
id
inkscape:cx
inkscape:cy
inkscape:pageopacity
inkscape:pageshadow
inkscape:window-height
inkscape:window-width
inkscape:zoom
pagecolor
<svg:07:07, 31 January 2006 (PST)Gradients>
inkscape:collect
<svg:path (in patten defs)>
sodipodi:cx
sodipodi:cy
sodipodi:rx
sodipodi:ry
<svg :path (in spiral)>
sodipodi:argument
sodipodi:cx
sodipodi:cy
sodipodi:expansion
sodipodi:radius
sodipodi:revolution
sodipodi:t0
sodipodi:type

<svg:path (in star)>
inkscape:flatsided
inkscape:randomized
inkscape:rounded
sodipodi:arg1
sodipodi:arg2
sodipodi:cx
sodipodi:cy
sodipodi:r1
sodipodi:r2
sodipodi:sides
sodipodi:type
<tiled clones>
first tiled shape (clone)
inkscape:tile-cx
inkscape:tile-cy
inkscape:tile-h
inkscape:tile-w
<others>
inkscape:tiled-clone-of
sodipodi:nodetypes?