Index: 07_io/export_spice/raw.html
===================================================================
--- 07_io/export_spice/raw.html	(revision 7540)
+++ 07_io/export_spice/raw.html	(revision 7541)
@@ -29,3 +29,39 @@
 	     it is exported after the value attribute.
 
 </table>
+
+<p>
+The final spice <i>instance line</i>is built by appending the following sections
+in order, in a single line:
+<ul>
+	<li> <b>name of the component</b>, perhaps prefixed with the value of attribute
+	     spice/prefix; e.g. M_Q45
+	<li> <b>one netname for each port</b> of the component; ports are first ordered
+	     numerically by their display/name (or display/pinnum or name or pinnum)
+	     attribute, then iterated from 1; ports must form a continous list from
+	     1 to the number of ports the component has; each port must be connected
+	     to a network. TODO: maybe auto-resistor to 0?
+	<li> <b>optionally the value</b>, if there is one specified in
+	     the display/value (or value) attribute;
+	     this is useful for passives (e.g. resistors)
+	<li> <b>optionally the spice model name</b>, if there is one specified in
+	     the spice/model attribute;
+	     this is useful for non-passives (e.g. transistors, diodes)
+	<li> <b>optionally extra spice parameters</b>, if specified in
+	     the display/spice/params (or spice/params) attribute if it
+	     exists and is not empty;
+	     this is useful if the model has extra parameters that should be
+	     printed after the model name; generally preferred instead of value
+	     for non-passives.
+</ul>
+<p>
+For example the following is a spice diode instance line, split up and
+annotated with source fields in the table below:
+<pre>
+D15 gnd sck 1n4148 T=35
+</pre>
+<p>
+<table border=1 cellspacing=0>
+	<tr><th>output  <td>D15  <td>gnd sck   <td>&nbsp;  <td>1n4148                  <td>T=35
+	<tr><th>section <td>name <td>netnames  <td>(value) <td>attribute: spice/model  <td>attribute: spice/params
+</table>