Index: 07_devmap.html
===================================================================
--- 07_devmap.html	(revision 277)
+++ 07_devmap.html	(revision 278)
@@ -13,7 +13,7 @@
 	     footprint or simulation model (problem known as "slotting")
 </ul>
 
-<p>{des7:0}
+<p>{des7:1}
 These goals are achieved by using symbolic terminal names (instead
 of "pin numbers") in the schematic symbols and auxiliary data to translate
 the terminal names into port numbers. The following diagram demonstrates
@@ -21,7 +21,7 @@
 
 <p><img src="07_diag.svg">
 
-<p>{des7:0}
+<p>{des7:2}
 The device mapper has three major features: slotting name translation
 (red), device mapping (green) and pin mapping (blue). The slotting translation
 makes sure the resulting abstract component has the right amount of ports;
@@ -29,7 +29,7 @@
 attributes from a database; the pin mapper applies a pin numbers from
 a table (the table typically set up by the device mapper).
 
-<p>{des7:0}
+<p>{des7:3}
 The device mapper is an optional mechanism implemented in a plugin. The
 user may choose to use it or to:
 <ul>
@@ -43,17 +43,17 @@
 	     that would introduce a <i>pinmap</i> attribute
 </ul>
 
-<p>{des7:0}
+<p>{des7:4}
 It is possible to use features of this plugin selectively and/or replace
 some or all features using another plugin.
 
 <h2> 7.1. Slot prefixing </h2>
 
-<p>{des7:0}
+<p>{des7:5}
 Devmap registers for the <a href="02_data#des2:77">terminal-name-to-port-name
 translation</a>.
 
-<p>{des7:0}
+<p>{des7:6}
 If the <i>slot</i> attribute presents in a symbol, and the terminal does
 not have the "noslot" attribute, the translation is activated. The slot
 name is taken directly from the concrete symbol's <i>slot</i> attribute.
@@ -61,11 +61,11 @@
 attribute is then removed from the abstract component to avoid
 collisions.
 
-<p>{des7:0}
+<p>{des7:7}
 Typical example: common opamp symbol:
-<p>{des7:0}
+<p>{des7:8}
 <p><table border=1 cellspacing=0>
-<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:0} example opamp terminal attributes
+<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:9} example opamp terminal attributes
 <tr><th> name       <th> noslot                <th> terminal description
 <tr><td> in_plus    <td> (not present)         <td> positive input pin
 <tr><td> in_minus   <td> (not present)         <td> negative input pin
@@ -74,7 +74,7 @@
 <tr><td> v_minus    <td> "yes"                 <td> negative power rail
 </table>
 
-<p>{des7:0}
+<p>{des7:10}
 In the above example v_plus and v_minus are never prefixed with "slot/" because
 of their noslot attribute. In case the symbol is used with the slot attribute
 set, this means:
@@ -85,7 +85,7 @@
 	     exist in the abstract component
 </ul>
 
-<p>{des7:0}
+<p>{des7:11}
 Note: when the same symbol is used in a non-slotted use case, the symbol will
 not have the "slot" attribute; in this case no terminal name translation
 applied and the resulting abstract component will have the same port names
@@ -94,7 +94,7 @@
 
 <h2> 7.2. Pin mapping </h2>
 
-<p>{des7:0}
+<p>{des7:12}
 Pin mapping takes a map between the symbolic description  and emits the
 physical description (port numbers for a footprint or sim model). There
 shall be one such mapping per abstract component. If multiple symbols
@@ -102,7 +102,7 @@
 keep only one of the arrays.
 
 
-<p>{des7:0}
+<p>{des7:13}
 The input is a array is an unordered list of (terminal name + slot name)
 -&gt; (attribute_name + value) pairs, each specified in the following syntax:
 <pre>
@@ -109,17 +109,17 @@
 slot/termname -&gt; attribkey=value
 </pre>
 
-<p>{des7:0} E.g. "A/out -&gt; pcb/pin=1" means "terminal with 
+<p>{des7:14} E.g. "A/out -&gt; pcb/pin=1" means "terminal with 
 <i>name=out</i> in symbol tagged as <i>slot=A</i> shall get attribute
 <i>pcb/pin</i> set to <i>1</i>".
 
 
-<p>{des7:0}
+<p>{des7:15}
 If a slot/terminal pair is not found in the map, an error message is
 emitted. This happens when the schematics symbol uses a terminal that
 has no physical pin with the given device.
 
-<p>{des7:0}
+<p>{des7:16}
 If a slot/terminal pair of the map is not used in the mapping, no error
 is generated. A typical example when this happens is when a logic circuit
 has 4 identical slots but the schematics uses only 3. If this is considered
@@ -126,9 +126,9 @@
 an error, a DRC plugin shall check for it.
 
 
-<p>{des7:0}
+<p>{des7:17}
 <p><table border=1 cellspacing=0>
-<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:0} pin mapping related symbol attributes
+<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:18} pin mapping related symbol attributes
 <tr><th> attribute <th> value                <th> description
 <tr><td> pinmap    <td> array of map entries <td> the actual map, as described in TODO
 <tr><td> slot      <td> slot name            <td> textual name of the slot the symbol provides
@@ -136,24 +136,24 @@
 
 <h2> 7.3. Device mapping </h2>
 
-<p>{des7:0}
+<p>{des7:19}
 The device mapper takes the <i>devmap</i> attribute of a symbol and looks it up
 in a database for finding a device map file. If the devmap attribute is an
 array, each devmap file is looked up and applied, in order of appearance.
 
-<p>{des7:0}
+<p>{des7:20}
 A device map file is a simple list of cschem attributes. The device mapper
 takes each attribute from the device map file and apply it on the symbol that
 had the devmap attribute.
 
-<p>{des7:0}
+<p>{des7:21}
 A common device map file will usually have a pinmap attribute that will
 set at least one attributes on each terminal.
 
 
-<p>{des7:0}
+<p>{des7:22}
 <p><table border=1 cellspacing=0>
-<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:0} device mapping related symbol attributes
+<tr><th colspan=3 bgcolor="#aaaaaa"> {des7:23} device mapping related symbol attributes
 <tr><th> attribute <th> value  <th> description
 <tr><td> devmap    <td> name   <td> name of the devmap file to use
 </table>