--- a/608toVTT/608toVTT.html	Tue Jan 22 16:35:51 2013 +1100
+++ b/608toVTT/608toVTT.html	Tue Jan 22 16:48:22 2013 +1100
@@ -968,6 +968,128 @@
         <p>
           WebVTT uses only unicode code points, rendered as UTF-8 characters. All of the CEA-608 and CEA-708 character codes - standard and extended character codes - are mapped to unicode.
         </p>
+
+        <p>
+          Single-byte codes 0x20-0x7f map to the same Unicode code point, except for:
+        </p>
+
+        <table border="1">
+          <tr>
+            <td>0x2a</td>
+            <td>U+00E1</td>
+          </tr>
+          <tr>
+            <td>0x5c</td>
+            <td>U+00E9</td>
+          </tr>
+          <tr>
+            <td>0x5e</td>
+            <td>U+00ED</td>
+          </tr>
+          <tr>
+            <td>0x5f</td>
+            <td>U+00F3</td>
+          </tr>
+          <tr>
+            <td>0x60</td>
+            <td>U+00FA</td>
+          </tr>
+          <tr>
+            <td>0x7b</td>
+            <td>U+00E7</td>
+          </tr>
+          <tr>
+            <td>0x7c</td>
+            <td>U+00F7</td>
+          </tr>
+          <tr>
+            <td>0x7d</td>
+            <td>U+00D1</td>
+          </tr>
+          <tr>
+            <td>0x7e</td>
+            <td>U+00F1</td>
+          </tr>
+          <tr>
+            <td>0x7f</td>
+            <td>U+2588</td>
+          </tr>
+        </table>
+
+        <p>
+          Two-byte special characters where the second byte maps as follows:
+        </p>
+
+        <table border="1">
+          <tr>
+            <td>0x30</td>
+            <td>U+00AE</td>
+          </tr>
+          <tr>
+            <td>0x31</td>
+            <td>U+00B0</td>
+          </tr>
+          <tr>
+            <td>0x32</td>
+            <td>U+00BD</td>
+          </tr>
+          <tr>
+            <td>0x33</td>
+            <td>U+00BF</td>
+          </tr>
+          <tr>
+            <td>0x34</td>
+            <td>U+2122</td>
+          </tr>
+          <tr>
+            <td>0x35</td>
+            <td>U+00A2</td>
+          </tr>
+          <tr>
+            <td>0x36</td>
+            <td>U+00A3</td>
+          </tr>
+          <tr>
+            <td>0x37</td>
+            <td>U+266A</td>
+          </tr>
+          <tr>
+            <td>0x38</td>
+            <td>U+00E0</td>
+          </tr>
+          <tr>
+            <td>0x39</td>
+            <td>transparent space</td>
+          </tr>
+          <tr>
+            <td>0x3a</td>
+            <td>U+00E8</td>
+          </tr>
+          <tr>
+            <td>0x3b</td>
+            <td>U+00E2</td>
+          </tr>
+          <tr>
+            <td>0x3c</td>
+            <td>U+00EA</td>
+          </tr>
+          <tr>
+            <td>0x3d</td>
+            <td>U+00EE</td>
+          </tr>
+          <tr>
+            <td>0x3e</td>
+            <td>U+00F4</td>
+          </tr>
+          <tr>
+            <td>0x3f</td>
+            <td>U+00FB</td>
+          </tr>
+        </table>
+
+        <p>
+          When multiple characters on-screen talk simultaneously, transparent space is sometimes used to position the text for each character in the same line. In these cases, use the transparent space as a cue break, and calculate the positioning for the next part in a new cue similar to the recommendation for converting mid-row PACs.
+        </p>
       </section>
 
       <section>