Inkscape SVG vs. plain SVG - Revision history

Skrapion: Documented -inkscape-stroke property

2020-11-23T04:17:08Z

Documented -inkscape-stroke property

← Older revision		Revision as of 04:17, 23 November 2020
Line 85:		Line 85:
	*(others)		*(others)
	** sodipodi:nodetypes?		** sodipodi:nodetypes?

			==Inkscape Properties==
			===Inkscape Stroke Extensions===
			This property houses any non-standard Inkscape specific extensions to the stroke property. Currently it's only used for defining hairlines.
			{\| class="wikitable"
			\|-
			\| ''Name:'' \|\| '''-inkscape-stroke'''
			\|-
			\| ''Value:'' \|\| none \| hairline
			\|-
			\| ''Initial:'' \|\| none
			\|-
			\| ''Applies to:'' \|\| graphics elements
			\|-
			\| ''Inherited:'' \|\| no
			\|-
			\| ''Percentages:'' \|\| N/A
			\|-
			\| ''Media:'' \|\| visual
			\|-
			\| ''Computed value:'' \|\| as specified
			\|-
			\| ''Animation type:'' \|\| not animatable
			\|}

			==== none ====

			Specifies that no vector effect shall be applied, i.e. the default rendering behaviour from SVG 1.1 is used.

			==== hairline ====

			Specifies that the stroke is always drawn with a visual width of 1 device unit, but has a zero-width logical size. For compatibility with other renderers, this should always be accompanied with stroke-width: 1px; vector-effect: non-scaling-stroke.

	[[Category:User Documentation]]		[[Category:User Documentation]]

Moini: /* Inkscape SVG vs. Plain SVG */ Fix missing word

2016-12-31T16:22:47Z

Inkscape SVG vs. Plain SVG: Fix missing word

← Older revision		Revision as of 16:22, 31 December 2016
Line 6:		Line 6:
	* Inkscape's default mode when saving		* Inkscape's default mode when saving
	* conforms to the SVG standard which permits extensions like those outlined [[Inkscape SVG vs. plain SVG#list of inkscape: and sodipodi: namespaces (incomplete)\|here]]		* conforms to the SVG standard which permits extensions like those outlined [[Inkscape SVG vs. plain SVG#list of inkscape: and sodipodi: namespaces (incomplete)\|here]]
	* Inkscape should render identically with or without the Inkscape extensions		* Inkscape SVG 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		* 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 "[[PlainSVG]]" for some odd reason		* seems to have a smaller filesize vs "[[PlainSVG]]" for some odd reason

Arlo James Barnes: /* Inkscape SVG vs. Plain SVG */ wiki documents are collective

2016-12-31T10:09:03Z

Inkscape SVG vs. Plain SVG: wiki documents are collective

← Older revision		Revision as of 10:09, 31 December 2016
Line 12:		Line 12:
	"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.		"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,		From one perspective,
	* 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		* 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
	* 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		* 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

Arlo James Barnes: /* Inkscape SVG vs. Plain SVG */ Started removing the freedom2surfer's personal opinions

2016-12-31T10:07:41Z

Inkscape SVG vs. Plain SVG: Started removing the freedom2surfer's personal opinions

← Older revision		Revision as of 10:07, 31 December 2016
Line 4:		Line 4:

	Some notes about "Inkscape SVG" [http://sourceforge.net/mailarchive/forum.php?thread_id=7412326&forum_id=37513 ref]:		Some notes about "Inkscape SVG" [http://sourceforge.net/mailarchive/forum.php?thread_id=7412326&forum_id=37513 ref]:
	* ~~the~~ default mode of saving		* Inkscape's default mode when saving
	* ~~standards-conforming (~~the SVG standard permits ~~these kinds~~ of ~~extensions~~)		* conforms to the SVG standard which permits extensions like those outlined [[Inkscape SVG vs. plain SVG#list of inkscape: and sodipodi: namespaces (incomplete)\|here]]
	* should render identically with or without the ~~inkscape~~ extensions		* Inkscape 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		* 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 "[[PlainSVG]]" for some odd reason		* seems to have a smaller filesize vs "[[PlainSVG]]" for some odd reason
Line 13:		Line 13:

	From my perspective,		From my perspective,
	* 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		* 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
	* 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~~		* 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
	* 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.		* 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.

	~~Below is an incomplete~~ list of ~~what is contained in the~~ inkscape: and sodipodi: (preserved for backwards compatibility with its functions) ~~namespaces~~		== list of inkscape: and sodipodi: namespaces (incomplete) ==

			(preserved for backwards compatibility with its functions)

	*<svg>		*<svg>
Line 41:		Line 43:
	*<svg:Gradients>		*<svg:Gradients>
	** inkscape:collect		** inkscape:collect
	*<svg:path >(in ~~patten~~ defs)		*<svg:path >(in pattern defs)
	** sodipodi:cx		** sodipodi:cx
	** sodipodi:cy		** sodipodi:cy
Line 75:		Line 77:
	*<svg:g> (id=layer)		*<svg:g> (id=layer)
	**inkscape:groupmode		**inkscape:groupmode
	**inkscape:~~lable~~		**inkscape:label
	*(connectors)		*(connectors)
	**inkscape:connector-avoid:		**inkscape:connector-avoid:

Marko: + languages

2012-05-07T15:20:33Z

+ languages

← Older revision		Revision as of 15:20, 7 May 2012
Line 1:		Line 1:
			{{Other languages\|en=Inkscape SVG vs. plain SVG}}

	== Inkscape SVG vs. Plain SVG ==		== Inkscape SVG vs. Plain SVG ==

Legio noctis: /* Inkscape SVG vs. Plain SVG */

2010-01-10T21:13:00Z

Inkscape SVG vs. Plain SVG

← Older revision		Revision as of 21:13, 10 January 2010
Line 11:		Line 11:

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

	Below is an incomplete list of what is contained in the inkscape: and sodipodi: (preserved for backwards compatibility with its functions) namespaces		Below is an incomplete list of what is contained in the inkscape: and sodipodi: (preserved for backwards compatibility with its functions) namespaces

Richardink: Fix typo

2010-01-03T16:03:29Z

Fix typo

← Older revision		Revision as of 16:03, 3 January 2010
Line 11:		Line 11:

	From my perspective,		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		* inkscape svg is basically the same as plain svg, just with a couple of extra commands (in separate 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 sodipodi:, and just be left with the plain svg		* 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
	* 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.		* 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.

Tweenk: moved InkscapeSVG to Inkscape SVG vs. plain SVG: kill wikiwords

2009-06-19T15:02:52Z

moved InkscapeSVG to Inkscape SVG vs. plain SVG: kill wikiwords

← Older revision	Revision as of 15:02, 19 June 2009
(No difference)

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

2008-03-05T21:16:57Z

Inkscape SVG vs. Plain SVG

← Older revision		Revision as of 21:16, 5 March 2008
Line 74:		Line 74:
	**inkscape:groupmode		**inkscape:groupmode
	**inkscape:lable		**inkscape:lable
	*(~~conectors~~)		*(connectors)
	**inkscape:connector-avoid:		**inkscape:connector-avoid:
	**inkscape:connector-type		**inkscape:connector-type
	**~~inkscpae~~:connector-start		**inkscape:connector-start
	**inkscape:connector-end		**inkscape:connector-end
	*(others)		*(others)

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

2006-08-21T17:26:44Z

Inkscape SVG vs. Plain SVG

← Older revision		Revision as of 17:26, 21 August 2006
Line 6:		Line 6:
	* should render identically with or without the inkscape 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		* 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		* seems to have a smaller filesize vs "[[PlainSVG]]" 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.		"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.
Line 12:		Line 12:
	From my perspective,		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		* 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		* 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
	* 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.		* 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.

	Below is an ~~incompleate~~ list of what is contained in the inkscape: and sodipodi: (preserved for backwards compatibility with its functions) namespaces		Below is an incomplete list of what is contained in the inkscape: and sodipodi: (preserved for backwards compatibility with its functions) namespaces

	*<svg>		*<svg>