remove text that is already covered

Author: annevk

cssom/Overview.html

@@ -3572,19 +3572,6 @@ <h4 id=serializing-css-values><span class=secno>6.6.2. </span>Serializing
    href="#escape-a-string" title="escape a string">escaped</a> value of the
    given string, followed by '<code>")</code>'.</p>
   <!--
-  <ol>
-   <li><p>Relative lengths (<code>em</code>, <code>ex</code>, <code>px</code>,
-   all the font-size keywords and <code>%</code>) do not have their units
-   changed. However, absolute lengths must be given in millimeters. For example,
-   the canonical version of <code>+012.0pt</code> is <code>4.2333mm</code> (give
-   or take a few significant figures). <span class="note"><em>Computed</em>
-   values may well be in different units than the specified value. User agents
-   are to use <code>px</code> as their final units for computed length
-   values.</span></p></li>
-
-   <li><p>When a <code>&lt;length></code> of zero is given change it to
-   "<code>0px</code>"</p></li>
-   
    <li>
     <p>A <code>&lt;color></code> value is canonicalized as follows:</p>
 
@@ -3622,29 +3609,6 @@ <h4 id=serializing-css-values><span class=secno>6.6.2. </span>Serializing
     </dl>
    </li>
 
-   <li><p>Angles are canonicalized to <code>deg</code> and normalized to the
-   range of their property. For example, <code>azimuth: 700grad</code> would be
-   canonicalized to <code>azimuth: 270deg</code>. This also applies to angle
-   keywords as used in the <code>elevation</code> and <code>azimuth</code>
-   properties, they are canonicalized to their value in degrees.</p></li>
-   
-   <li><p>Times are canonicalized to seconds (<code>s</code>).</p></li>
-   
-   <li><p>Frequencies are canonicalized to Hertz (<code>Hz</code>).</p></li>
-   
-   <li><p>For all integers and real numbers, including those with units, these
-   canonicalization steps <em class="ct">must</em> be followed: If the number
-   is <code>0</code>, the canonical result is the literal string <code>0</code>
-   plus any units (for lengths, the unit identifier will have been removed
-   before this step). Otherwise, leading <!- -and trailing - ->zeros
-   <em class="ct">must</em> be omitted, any leading <code>+</code>
-   <em class="ct">must</em> be omitted, the decimal point in a real number
-   <em class="ct">must</em> be omitted unless there is a fractional part, and if
-   the number is in the range <code>-1 &lt; <var title="">x</var> &lt; 1</code>, then one
-   leading <code>0</code> <em class="ct">must</em> be inserted before the
-   decimal point. The number of given significant figures is completely user
-   agent dependent.</p></li>
-   
    <li><p>Where multiple values may appear in any order without changing the
    meaning of the value (typically represented by a double bar <code>||</code>
    in the value syntax), user agents are to use the canonical order as given in
@@ -3660,21 +3624,7 @@ <h4 id=serializing-css-values><span class=secno>6.6.2. </span>Serializing
    
    <li><p><code>&lt;specific-voice></code> and <code>&lt;family-name</code>
    values are to be quoted.</p></li>
-   
-   <li><p>Double quotes (rather than single quotes) <em class="ct">shall</em> be
-   used for string quotation. (When changing from single quotes to double
-   quotes, double quotes already in the string are escaped.)</p></li>
-   
-   <li><p>The quotes in the <code>&lt;uri></code> form should be removed.
-   (Parenthesises that were in the string, along with any other characters not
-   legal when the string is not quoted (such as commas), must be
-   escaped.)</p></li>
-   
-   <li><p>Unnecessary escapes should be removed. (For example, <code>\z</code>
-   should be represented as <code>z</code>. This extends to unescaping UNICODE
-   escapes, except, of course, if the encoding cannot contain those
-   characters!)</p></li>
-   
+
    <li><p>Where components of the value may be dropped without changing the
    meaning of the value (for example, initial values in shorthand properties),
    then they should be removed. If this would remove all the values, then the
@@ -3683,7 +3633,7 @@ <h4 id=serializing-css-values><span class=secno>6.6.2. </span>Serializing
    <code>background-color</code> is the first component of the value; for
    <code>border</code> it would be <code>0</code> since the first component of
    that value is <code>border-width</code>).</p></li>
-   
+
    <li>
     <p>A single space should be added after each comma that is not part of a
      string, except where that would change the meaning of the value. For
@@ -3696,20 +3646,6 @@ <h4 id=serializing-css-values><span class=secno>6.6.2. </span>Serializing
     <pre>foo, bar, baz</pre>
    </li>
    
-   <li>
-    <p>Whenever case is insensitive, for example in property or counter names,
-     the text should be changed to the canonical case as given in the syntax
-     definition. For example, the canonical value of:</p>
-    
-    <pre>COUNTER( PAR-NUM,UPPER-ROMAN ) DISC</pre>
-    
-    <p>is:</p>
-    
-    <pre>counter(par-num, upper-roman) disc</pre>
-    
-    <p>but the color <code>WINDOWTEXT</code> becomes
-    <code>WindowText</code>.</p>
-   </li>
   </ol>
   -->
 

cssom/Overview.src.html

@@ -1902,7 +1902,7 @@ <h3>CSS Declaration Blocks</h3>
 
   <p class="XXX">To
   <dfn id="serialize-a-css-declaration-block">serialize a CSS declaration block</dfn>
-  ...</p> 
+  ...</p>
 
 
 
@@ -2236,19 +2236,6 @@ <h4>Serializing CSS Values</h4>
   followed by '<code>")</code>'.</p>
 
   <!--
-  <ol>
-   <li><p>Relative lengths (<code>em</code>, <code>ex</code>, <code>px</code>,
-   all the font-size keywords and <code>%</code>) do not have their units
-   changed. However, absolute lengths must be given in millimeters. For example,
-   the canonical version of <code>+012.0pt</code> is <code>4.2333mm</code> (give
-   or take a few significant figures). <span class="note"><em>Computed</em>
-   values may well be in different units than the specified value. User agents
-   are to use <code>px</code> as their final units for computed length
-   values.</span></p></li>
-
-   <li><p>When a <code>&lt;length></code> of zero is given change it to
-   "<code>0px</code>"</p></li>
-   
    <li>
     <p>A <code>&lt;color></code> value is canonicalized as follows:</p>
 
@@ -2286,29 +2273,6 @@ <h4>Serializing CSS Values</h4>
     </dl>
    </li>
 
-   <li><p>Angles are canonicalized to <code>deg</code> and normalized to the
-   range of their property. For example, <code>azimuth: 700grad</code> would be
-   canonicalized to <code>azimuth: 270deg</code>. This also applies to angle
-   keywords as used in the <code>elevation</code> and <code>azimuth</code>
-   properties, they are canonicalized to their value in degrees.</p></li>
-   
-   <li><p>Times are canonicalized to seconds (<code>s</code>).</p></li>
-   
-   <li><p>Frequencies are canonicalized to Hertz (<code>Hz</code>).</p></li>
-   
-   <li><p>For all integers and real numbers, including those with units, these
-   canonicalization steps <em class="ct">must</em> be followed: If the number
-   is <code>0</code>, the canonical result is the literal string <code>0</code>
-   plus any units (for lengths, the unit identifier will have been removed
-   before this step). Otherwise, leading <!- -and trailing - ->zeros
-   <em class="ct">must</em> be omitted, any leading <code>+</code>
-   <em class="ct">must</em> be omitted, the decimal point in a real number
-   <em class="ct">must</em> be omitted unless there is a fractional part, and if
-   the number is in the range <code>-1 &lt; <var title="">x</var> &lt; 1</code>, then one
-   leading <code>0</code> <em class="ct">must</em> be inserted before the
-   decimal point. The number of given significant figures is completely user
-   agent dependent.</p></li>
-   
    <li><p>Where multiple values may appear in any order without changing the
    meaning of the value (typically represented by a double bar <code>||</code>
    in the value syntax), user agents are to use the canonical order as given in
@@ -2324,21 +2288,7 @@ <h4>Serializing CSS Values</h4>
    
    <li><p><code>&lt;specific-voice></code> and <code>&lt;family-name</code>
    values are to be quoted.</p></li>
-   
-   <li><p>Double quotes (rather than single quotes) <em class="ct">shall</em> be
-   used for string quotation. (When changing from single quotes to double
-   quotes, double quotes already in the string are escaped.)</p></li>
-   
-   <li><p>The quotes in the <code>&lt;uri></code> form should be removed.
-   (Parenthesises that were in the string, along with any other characters not
-   legal when the string is not quoted (such as commas), must be
-   escaped.)</p></li>
-   
-   <li><p>Unnecessary escapes should be removed. (For example, <code>\z</code>
-   should be represented as <code>z</code>. This extends to unescaping UNICODE
-   escapes, except, of course, if the encoding cannot contain those
-   characters!)</p></li>
-   
+
    <li><p>Where components of the value may be dropped without changing the
    meaning of the value (for example, initial values in shorthand properties),
    then they should be removed. If this would remove all the values, then the
@@ -2347,7 +2297,7 @@ <h4>Serializing CSS Values</h4>
    <code>background-color</code> is the first component of the value; for
    <code>border</code> it would be <code>0</code> since the first component of
    that value is <code>border-width</code>).</p></li>
-   
+
    <li>
     <p>A single space should be added after each comma that is not part of a
      string, except where that would change the meaning of the value. For
@@ -2360,20 +2310,6 @@ <h4>Serializing CSS Values</h4>
     <pre>foo, bar, baz</pre>
    </li>
    
-   <li>
-    <p>Whenever case is insensitive, for example in property or counter names,
-     the text should be changed to the canonical case as given in the syntax
-     definition. For example, the canonical value of:</p>
-    
-    <pre>COUNTER( PAR-NUM,UPPER-ROMAN ) DISC</pre>
-    
-    <p>is:</p>
-    
-    <pre>counter(par-num, upper-roman) disc</pre>
-    
-    <p>but the color <code>WINDOWTEXT</code> becomes
-    <code>WindowText</code>.</p>
-   </li>
   </ol>
   -->