INX extension descriptor format - Revision history

Joneuhauser: Move documentation

2022-03-10T20:12:53Z

Move documentation

Oskay: fix link

2021-11-18T21:31:30Z

fix link

← Older revision		Revision as of 21:31, 18 November 2021
Line 152:		Line 152:

	== See Also ==		== See Also ==
	*[[INX Parameters]]		*[[Extensions:_INX_widgets_and_parameters\|INX Parameters]]
	*[[ScriptingHOWTO]]		*[[ScriptingHOWTO]]

Oskay: Add savecopyonly attribute, remove some deprecated items, improve descriptions, clean up a bit

2021-11-18T21:01:26Z

Add savecopyonly attribute, remove some deprecated items, improve descriptions, clean up a bit

← Older revision		Revision as of 21:01, 18 November 2021
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	In order for Inkscape to make use of an external script or program, you must describe that script to inkscape using an INX file. ~~See the inkscape share directory for examples~~. The INX file allows the author to:		In order for Inkscape to make use of an external script or program, you must describe that script to inkscape using an INX file. The INX file is an XML file with Inkscape-specific content that can be edited in a plain-text editor.
	* ~~label strings~~ for ~~translation~~
	* ~~define parameters~~		The INX file allows the author to:
	* ~~chain~~ extensions		* Specify what type of extension it is, for example input, output, or effect
	* ~~etc~~		* Identify [[Extension_Interpreters\|which interpreter]] should be used to run the extension
	~~Be sure~~ to ~~read through~~ the ~~INX files that come with Inkscape.~~ Nothing beats a working example.		* List dependencies; files or other extensions required for operation
			* Define parameters that can be set in the extension
			* Create [[Extensions:_INX_widgets_and_parameters\|a GUI with control widgets]] for those parameters
			* Add a submenu to the Extensions menu for the extension to reside in
			* Label strings for translation
			* Chain extensions
			* Etc

			Nothing beats a working example, and Inkscape includes a great number of extensions with INX files that you can read. To find the location of your Inkscape extensions directory, where included extensions and their INX files are located, look in the System pane of Inkscape Preferences, under "Inkscape extensions".


	== Translation of extensions ==		== Translation of extensions ==

	Extension dialog windows, described in INX files, can be prepared for translation or localisation by adding an <code>_</code> (underscore) to the XML tags or attributes. Only add underscores when text ~~need~~ to be translated (not numeric values, for example!).		Extension dialog windows, described in INX files, can be prepared for translation or localisation by adding an <code>_</code> (underscore) to the XML tags or attributes. Only add underscores when text needs to be translated (not numeric values, for example!).

	Example:		Example:
Line 37:		Line 46:
	\| <code>implements-custom-gui</code> (''new in 1.0'')		\| <code>implements-custom-gui</code> (''new in 1.0'')
	\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> ''(default)''		\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> ''(default)''
	\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI.<br>''Implementation detail: The "extension is working" window is not shown for this kind of extensions. This means user interaction with the Inkscape interface is blocked until the extension returns, with no way for the user to abort the running extension! It is therefore '''absolutely essential''' that your extension provides the necessary visual feedback for the user and has proper error handling, to rule out any dead-locking behavior.''		\| If set to <code>true</code> '''requires''' an effect extension to implement custom GUI.<br>''Implementation detail: The "extension is working" window is not shown for this kind of extensions. This means user interaction with the Inkscape interface is blocked until the extension returns, with no way for the user to abort the running extension! It is therefore '''absolutely essential''' that your extension provides the necessary visual feedback for the user and has proper error handling, to rule out any dead-locking behavior.''
	\|-		\|-
	\| <code>needs-document</code>		\| <code>needs-document</code>
	\| <code>"true"</code> ''(default)'' <nowiki>\|</nowiki> <code>"false"</code>		\| <code>"true"</code> ''(default)'' <nowiki>\|</nowiki> <code>"false"</code>
	\| If set to <code>false</code> ~~the~~ effect extension will not be passed a document nor will a document be read back ("no-op" effect). This is currently a hack to make extension manager work and will likely be removed/replaced in future, so use at your '''own risk'''!		\| If set to <code>false</code> an effect extension will not be passed a document nor will a document be read back ("no-op" effect). This is currently a hack to make extension manager work and will likely be removed/replaced in future, so use at your '''own risk'''!
	\|-		\|-
	\| <code>needs-live-preview</code>		\| <code>needs-live-preview</code>
	\| <code>"true"</code> ''(default)'' <nowiki>\|</nowiki> <code>"false"</code> (default)		\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)
	\| '''''~~(please fill~~ in~~!)'''''~~		\| If set to <code>true</code> in an effect extension, it will offer a "Live preview" checkbox in its GUI. When the user checks that box, it will run the extension in a "preview mode", visually showing the effect of the extension, but not making any changes to the SVG document, unless the user clicks the Apply button. While "Live preview" is checked in the GUI, any changes that the user makes to parameters accessible in the GUI will generate an updated preview.
			\|-
			\| <code>savecopyonly</code> (''new in 1.2'')
			\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)
			\| If set to <code>true</code> in an '''output''' extension, it will limit the extension to being available only in the "Save a Copy" menu.
	\|-		\|-
	\|}		\|}
Line 60:		Line 73:
	<param name="tab" type="notebook">		<param name="tab" type="notebook">
	<page name="controls" _gui-text="Controls">		<page name="controls" _gui-text="Controls">
	<param name="{argumentName}" type="[int\|float\|string\|~~boolean\|description~~]" min="{number}" max="{number}"		<param name="{argumentName}" type="[int\|float\|string\|bool]" min="{number}" max="{number}"
	_gui-text="{Friendly Argument Name}">{default value}</param>		_gui-text="{Friendly Argument Name}">{default value}</param>
	</page>		</page>
Line 117:		Line 130:
	<!ATTLIST effect needs-live-preview (true\|false) #REQUIRED>		<!ATTLIST effect needs-live-preview (true\|false) #REQUIRED>
	<!ATTLIST effect implements-custom-gui (true\|false) #IMPLIED>		<!ATTLIST effect implements-custom-gui (true\|false) #IMPLIED>
			<!ATTLIST effect needs-document (true\|false) #IMPLIED>
	<!ATTLIST page name CDATA #REQUIRED>		<!ATTLIST page name CDATA #REQUIRED>
	<!ATTLIST page gui-text CDATA #IMPLIED>		<!ATTLIST page gui-text CDATA #IMPLIED>
	<!ATTLIST param name CDATA #REQUIRED>		<!ATTLIST param name CDATA #REQUIRED>
	<!ATTLIST param type (int\|float\|string\|~~boolean\|enum~~\|notebook\|~~description~~\|optiongroup\|color) #REQUIRED>		<!ATTLIST param type (int\|float\|string\|bool\|notebook\|path\|optiongroup\|color) #REQUIRED>
	<!ATTLIST param min CDATA #IMPLIED>		<!ATTLIST param min CDATA #IMPLIED>
	<!ATTLIST param max CDATA #IMPLIED>		<!ATTLIST param max CDATA #IMPLIED>

Leyghis: added missing menu-tip element; fixed typo

2021-04-27T09:37:06Z

added missing menu-tip element; fixed typo

← Older revision		Revision as of 09:37, 27 April 2021
Line 82:		Line 82:

	== DTD XML schema==		== DTD XML schema==
	The following XML schema may not fully describe the current ~~ING~~ file structure. The actual XML schema used is described in the [[INX extension descriptor format#RELAX NG XML schema\|next paragraph]].		The following XML schema may not fully describe the current INX file structure. The actual XML schema used is described in the [[INX extension descriptor format#RELAX NG XML schema\|next paragraph]].
	<small><pre>		<small><pre>
	<!ELEMENT inkscape-extension (name, id, dependency, param,(input\|output\|effect),(script\|plugin))>		<!ELEMENT inkscape-extension (name, id, dependency, param,(input\|output\|effect),(script\|plugin))>
Line 107:		Line 107:
	<!ELEMENT helper_extension (#PCDATA)>		<!ELEMENT helper_extension (#PCDATA)>
	<!ELEMENT output_extension (#PCDATA)>		<!ELEMENT output_extension (#PCDATA)>
			<!ELEMENT menu-tip (#PCDATA)>

	<!ATTLIST check reldir (absolute\|path\|extensions\|plugins) #REQUIRED>		<!ATTLIST check reldir (absolute\|path\|extensions\|plugins) #REQUIRED>

Patrick87: /* Attributes description */ highlight dangers of "implements-custom-gui"

2021-03-28T16:00:04Z

Attributes description: highlight dangers of "implements-custom-gui"

← Older revision		Revision as of 16:00, 28 March 2021
Line 37:		Line 37:
	\| <code>implements-custom-gui</code> (''new in 1.0'')		\| <code>implements-custom-gui</code> (''new in 1.0'')
	\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> ''(default)''		\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> ''(default)''
	\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI. Implementation detail: "extension is working" window is not ~~show~~ for this kind of extensions.		\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI.<br>''Implementation detail: The "extension is working" window is not shown for this kind of extensions. This means user interaction with the Inkscape interface is blocked until the extension returns, with no way for the user to abort the running extension! It is therefore '''absolutely essential''' that your extension provides the necessary visual feedback for the user and has proper error handling, to rule out any dead-locking behavior.''
	\|-		\|-
	\| <code>needs-document</code>		\| <code>needs-document</code>

Patrick87: /* Attributes description */ clarify "needs-document" (can likely be dropped in future as it was only important for help menu extensions which were dropped for 1.0

2021-03-18T14:29:52Z

Attributes description: clarify "needs-document" (can likely be dropped in future as it was only important for help menu extensions which were dropped for 1.0

← Older revision		Revision as of 14:29, 18 March 2021
Line 36:		Line 36:
	\|-		\|-
	\| <code>implements-custom-gui</code> (''new in 1.0'')		\| <code>implements-custom-gui</code> (''new in 1.0'')
	\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)		\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> ''(default)''
	\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI. Implementation detail: "extension is working" window is not show for this kind of extensions.		\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI. Implementation detail: "extension is working" window is not show for this kind of extensions.
	\|-		\|-
	\| <code>needs-document</code>		\| <code>needs-document</code>
	\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> ~~(default)~~		\| <code>"true"</code> ''(default)'' <nowiki>\|</nowiki> <code>"false"</code>
	\| ~~'''''~~(~~please fill~~ in!)'''''		\| If set to <code>false</code> the effect extension will not be passed a document nor will a document be read back ("no-op" effect). This is currently a hack to make extension manager work and will likely be removed/replaced in future, so use at your '''own risk'''!
	\|-		\|-
	\| <code>needs-live-preview</code>		\| <code>needs-live-preview</code>
	\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)		\| <code>"true"</code> ''(default)'' <nowiki>\|</nowiki> <code>"false"</code> (default)
	\| '''''(please fill in!)'''''		\| '''''(please fill in!)'''''
	\|-		\|-

Mgmax: change outdated links to Gitlab

2020-05-02T08:55:12Z

change outdated links to Gitlab

← Older revision		Revision as of 08:55, 2 May 2020
Line 22:		Line 22:
	</pre>		</pre>

	When extensions are included in the [~~http~~://~~bazaar~~.~~launchpad.net/~inkscape.dev~~/inkscape~~/trunk/files/head%3A/share~~/extensions/ Inkscape ~~BZR~~ Repository], various scripts will scan each INX file for translatable text and prepare [~~http~~://~~bazaar.launchpad~~.~~net~~/~inkscape~~.dev~~/inkscape/~~trunk~~/~~files~~/~~head%3A~~/po/ translation files] for others to translate.		When extensions are included in the [https://gitlab.com/inkscape/extensions Inkscape Extensions Repository], various scripts will scan each INX file for translatable text and prepare [https://gitlab.com/inkscape/inkscape/-/tree/master/po translation files] for others to translate.

	See also: [http://gould.cx/ted/blog/Translating_Custom_XML Ted's blog].		See also: [http://gould.cx/ted/blog/Translating_Custom_XML Ted's blog].
Line 50:		Line 50:

	== Example ==		== Example ==
	More example INX files are available in the Inkscape distribution ~~or in~~ the ~~Inkscape~~ [~~http~~://~~bazaar.launchpad~~.~~net~~/~inkscape~~.dev/inkscape/trunk/files/head%3A/share~~/extensions~~/ BZR repository~~].		More example INX files are available in the Inkscape distribution, which takes its files from the [https://gitlab.com/inkscape/extensions Inkscape Extensions Repository].

	<small><pre>		<small><pre>
Line 134:		Line 134:

	== RELAX NG XML schema ==		== RELAX NG XML schema ==
	The XML schema for ~~ING~~ files is available in the [~~http~~://~~bazaar~~.~~launchpad.net~~/~inkscape~~.dev~~/~~inkscape~~/~~trunk/annotate~~/~~head%3A~~/~~share/extensions~~/inkscape.extension.rng Inkscape ~~BZR~~ repository]. This is a [http://www.relaxng.org/ RELAX NG schema].		The XML schema for INX files is available in the [https://gitlab.com/inkscape/extensions/-/blob/master/inkscape.extension.rng Inkscape extensions Git repository]. This is a [http://www.relaxng.org/ RELAX NG schema].

	~~A compactly formatted version of the schema (created on 2 November 2010 using [http://www.thaiopensource.com/relaxng/trang.html Trang]):~~
	~~<small><pre>~~
	~~default namespace =~~
	~~"http://www.inkscape.org/namespace/inkscape/extension"~~

	~~start =~~
	~~element inkscape-extension {~~
	~~element _name { text },~~
	~~element id { text },~~
	~~element dependency {~~
	~~attribute type { inx.dependency-type.values },~~
	~~attribute location { inx.location.values }?,~~
	~~attribute _description { text }?,~~
	~~text~~
	~~}*,~~
	~~(inx.parameters~~
	~~\| element param {~~
	~~attribute name { text },~~
	~~attribute type { "notebook" },~~
	~~element page {~~
	~~attribute name { text },~~
	~~attribute _gui-text { text },~~
	~~inx.parameters+~~
	}+
	~~})*,~~
	~~(element input {~~
	~~inx.io.common,~~
	~~element output_extension { text }?~~
	}
	~~\| element output {~~
	~~inx.io.common,~~
	~~element dataloss { xsd:boolean }?~~
	}
	~~\| element effect {~~
	~~attribute needs-document { xsd:boolean }?,~~
	~~attribute needs-live-preview { xsd:boolean }?,~~
	~~element object-type {~~
	~~xsd:token "all" \| xsd:token "path" \| xsd:token "rect"~~
	},
	~~element effects-menu {~~
	~~attribute hidden { xsd:boolean "true" }~~
	~~\| element submenu {~~
	~~attribute _name { text },~~
	~~empty~~
	}
	}
	}
	~~\| element path-effect { empty }~~
	~~\| element print { empty }),~~
	~~(element script {~~
	~~element command {~~
	~~inx.reldir.attr,~~
	~~attribute interpreter { "python" \| "perl" }?,~~
	~~text~~
	},
	~~element helper_extension { xsd:NMTOKEN }?,~~
	element check { inx.reldir.attr, text }*
	}
	~~\| element xslt {~~
	~~element file { inx.reldir.attr, text }~~
	}
	~~\| element plugin {~~
	~~element name { text }~~
	})
	}
	~~inx.reldir.attr = attribute reldir { inx.location.values }~~
	~~inx.location.values = "extensions" \| "path" \| "plugins"~~
	~~inx.dependency-type.values = "extension" \| "executable" \| "plugin"~~
	~~inx.io.common =~~
	~~element extension { text },~~
	~~element mimetype { text },~~
	~~element _filetypename { text }?,~~
	~~element _filetypetooltip { text }?~~
	~~inx.parameter =~~
	~~attribute name { xsd:token },~~
	~~attribute gui-hidden { xsd:boolean }?,~~
	~~attribute _gui-text { text }?,~~
	~~((attribute type { "int" },~~
	~~attribute min { xsd:integer }?,~~
	~~attribute max { xsd:integer }?,~~
	~~(empty \| xsd:integer))~~
	~~\| (attribute type { "float" },~~
	~~attribute precision { xsd:integer }?,~~
	~~attribute min { xsd:float }?,~~
	~~attribute max { xsd:float }?,~~
	~~xsd:float)~~
	~~\| (attribute type { "boolean" },~~
	~~xsd:boolean)~~
	~~\| (attribute type { "string" },~~
	~~attribute max_length { xsd:integer }?,~~
	~~(empty \| text))~~
	~~\| (attribute type { "description" },~~
	~~text)~~
	~~\| (attribute type { "enum" },~~
	~~(element _item { inx.parameter.enum.item }~~
	~~\| element item { inx.parameter.enum.item })+)~~
	~~\| (attribute type { "optiongroup" },~~
	~~attribute appearance { "minimal" }?,~~
	~~(element option { inx.parameter.optiongroup.option }~~
	~~\| element _option { inx.parameter.optiongroup.option })+))~~
	~~inx.parameters =~~
	~~element param { inx.parameter }~~
	~~\| element _param { inx.parameter }~~
	~~inx.parameter.enum.item =~~
	~~attribute value { text },~~
	~~xsd:token~~
	~~inx.parameter.optiongroup.option =~~
	~~attribute value { text }?,~~
	~~text~~
	~~</pre></small>~~

	== See Also ==		== See Also ==

Patrick87: /* Attributes description */ add missing needs-document and needs-live-preview attributes

2019-06-19T21:02:59Z

Attributes description: add missing needs-document and needs-live-preview attributes

← Older revision		Revision as of 21:02, 19 June 2019
Line 38:		Line 38:
	\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)		\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)
	\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI. Implementation detail: "extension is working" window is not show for this kind of extensions.		\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI. Implementation detail: "extension is working" window is not show for this kind of extensions.
			\|-
			\| <code>needs-document</code>
			\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)
			\| '''''(please fill in!)'''''
			\|-
			\| <code>needs-live-preview</code>
			\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)
			\| '''''(please fill in!)'''''
	\|-		\|-
	\|}		\|}


	== Example ==		== Example ==

Sizmailov: Add description for `implements-custom-gui` effect attribute

2019-05-29T21:07:14Z

Add description for `implements-custom-gui` effect attribute

← Older revision		Revision as of 21:07, 29 May 2019
Line 25:		Line 25:

	See also: [http://gould.cx/ted/blog/Translating_Custom_XML Ted's blog].		See also: [http://gould.cx/ted/blog/Translating_Custom_XML Ted's blog].


			== Attributes description ==

			{\| class="wikitable"
			\|-
			! Attribute name
			! Allowed values
			! Comment
			\|-
			\| <code>implements-custom-gui</code> (''new in 1.0'')
			\| <code>"true"</code> <nowiki>\|</nowiki> <code>"false"</code> (default)
			\| If set to <code>true</code> '''requires''' effect extension to implement custom GUI. Implementation detail: "extension is working" window is not show for this kind of extensions.
			\|-
			\|}


	== Example ==		== Example ==
Line 92:		Line 108:
	<!ATTLIST dependency description CDATA #IMPLIED>		<!ATTLIST dependency description CDATA #IMPLIED>
	<!ATTLIST effect needs-live-preview (true\|false) #REQUIRED>		<!ATTLIST effect needs-live-preview (true\|false) #REQUIRED>
			<!ATTLIST effect implements-custom-gui (true\|false) #IMPLIED>
	<!ATTLIST page name CDATA #REQUIRED>		<!ATTLIST page name CDATA #REQUIRED>
	<!ATTLIST page gui-text CDATA #IMPLIED>		<!ATTLIST page gui-text CDATA #IMPLIED>

Moini: fix layout of code blocks

2017-03-19T15:38:16Z

fix layout of code blocks

← Older revision		Revision as of 15:38, 19 March 2017
Line 13:		Line 13:

	Example:		Example:
	~~<code>~~<pre>		<pre>
	<_name>Some translatable extension name</_name>		<_name>Some translatable extension name</_name>
	</pre~~></code~~>		</pre>

	Or:		Or:
	~~<code>~~<pre>		<pre>
	<param name="..." type="..." _gui-text="Some translatable label text">		<param name="..." type="..." _gui-text="Some translatable label text">
	</pre~~></code~~>		</pre>

	When extensions are included in the [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/share/extensions/ Inkscape BZR Repository], various scripts will scan each INX file for translatable text and prepare [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/po/ translation files] for others to translate.		When extensions are included in the [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/share/extensions/ Inkscape BZR Repository], various scripts will scan each INX file for translatable text and prepare [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/po/ translation files] for others to translate.
Line 29:		Line 29:
	More example INX files are available in the Inkscape distribution or in the Inkscape [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/share/extensions/ BZR repository].		More example INX files are available in the Inkscape distribution or in the Inkscape [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/share/extensions/ BZR repository].

	<small~~><code~~><pre>		<small><pre>
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<inkscape-extension xmlns="http://www.inkscape.org/namespace/inkscape/extension">		<inkscape-extension xmlns="http://www.inkscape.org/namespace/inkscape/extension">
Line 54:		Line 54:
	</script>		</script>
	</inkscape-extension>		</inkscape-extension>
	</pre~~></code~~></small>		</pre></small>

	For a full list of currently supported interpreters, please see [[Extension Interpreters]].		For a full list of currently supported interpreters, please see [[Extension Interpreters]].
Line 60:		Line 60:
	== DTD XML schema==		== DTD XML schema==
	The following XML schema may not fully describe the current ING file structure. The actual XML schema used is described in the [[INX extension descriptor format#RELAX NG XML schema\|next paragraph]].		The following XML schema may not fully describe the current ING file structure. The actual XML schema used is described in the [[INX extension descriptor format#RELAX NG XML schema\|next paragraph]].
	<small~~><code~~><pre>		<small><pre>
	<!ELEMENT inkscape-extension (name, id, dependency, param,(input\|output\|effect),(script\|plugin))>		<!ELEMENT inkscape-extension (name, id, dependency, param,(input\|output\|effect),(script\|plugin))>
	<!ELEMENT input (extension, mimetype, filetype, filetypetooltip, output_extension?)>		<!ELEMENT input (extension, mimetype, filetype, filetypetooltip, output_extension?)>
Line 107:		Line 107:
	<!ATTLIST param appearance (minimal\|) "">		<!ATTLIST param appearance (minimal\|) "">
	<!ATTLIST submenu name CDATA #REQUIRED>		<!ATTLIST submenu name CDATA #REQUIRED>
	</pre~~></code~~></small>		</pre></small>

	== RELAX NG XML schema ==		== RELAX NG XML schema ==
Line 113:		Line 113:

	A compactly formatted version of the schema (created on 2 November 2010 using [http://www.thaiopensource.com/relaxng/trang.html Trang]):		A compactly formatted version of the schema (created on 2 November 2010 using [http://www.thaiopensource.com/relaxng/trang.html Trang]):
	<small~~><code~~><pre>		<small><pre>
	default namespace =		default namespace =
	"http://www.inkscape.org/namespace/inkscape/extension"		"http://www.inkscape.org/namespace/inkscape/extension"
Line 221:		Line 221:
	attribute value { text }?,		attribute value { text }?,
	text		text
	</pre~~></code~~></small>		</pre></small>

	== See Also ==		== See Also ==