zach's changes to unicode-range

Author: John Daggett

css3-fonts/Fonts.html

@@ -116,7 +116,7 @@
 
    <h1>CSS Fonts Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=editors>Editor's Draft 18 May 2009</h2>
+   <h2 class="no-num no-toc" id=editors>Editor's Draft 19 May 2009</h2>
 
    <dl id=authors>
     <dt>This version:
@@ -2258,33 +2258,37 @@ <h3 id=character><span class=secno>4.5 </span>Character range: the ‘<code
    range has three basic forms:
 
   <ul>
-   <li>a single codepoint (e.g. U+416)
+   <li>a single code point (e.g. U+416)
 
    <li>an interval value range (e.g. U+400-4ff)
 
    <li>a range where trailing ‘<code class=css>?</code>’ characters imply
     ‘<code class=css>any digit value</code>’ (e.g. U+4??)
   </ul>
 
-  <p>Interval ranges consisting of a single codepoint are valid, as are
-   ranges specified with ‘<code class=css>?</code>’ that lack an initial
-   digit. Ranges can overlap but interval ranges that descend (e.g.
-   U+400-32f) are invalid and omitted rather than treated as parse errors,
-   they have no effect on other ranges in a list of ranges. Ranges containing
-   values greater than 10FFFF are also omitted. Without any valid ranges, the
-   descriptor is omitted. Ranges that do not fit any of the above three forms
-   are considered to be parse errors and the descriptor is omitted. User
-   agents may normalize the list of ranges into a list that is different but
-   represents the equivalent set of character code points.
+  <p>Ranges that do not fit any of the above three forms are considered to be
+   parse errors and the descriptor is omitted. Interval ranges consisting of
+   a single code point are valid. Ranges specified with ‘?’ that lack an
+   initial digit (e.g. "U+???") are also valid, and are treated as if there
+   was a single 0 before the question marks (thus, "U+???" = "U+0???" =
+   "U+0000-0FFF"). "U+??????" is not a syntax error, even though "U+0??????"
+   would be. Ranges can overlap but interval ranges that descend (e.g.
+   U+400-32f) are invalid and omitted rather than treated as parse errors;
+   they have no effect on other ranges in a list of ranges. Ranges are
+   clipped to the domain of Unicode code points (currently 0 - 10FFFF
+   inclusive); a range entirely outside the domain is omitted. Without any
+   valid ranges, the descriptor is omitted. User agents may normalize the
+   list of ranges into a list that is different but represents the equivalent
+   set of character code points.
 
   <p>The character range can be a subset of the full character map of the
    underlying font. The effective unicode-range used when mapping characters
    to fonts is the intersection of the unicode range specified and the
    underlying character map of the font. This means that authors do not need
    to define the unicode-range of a font precisely, broad ranges for which a
-   sparse set of codepoints are defined in the font can be used. Codepoints
+   sparse set of code points are defined in the font can be used. Code points
    outside of the defined unicode-range are ignored, irregardless of whether
-   the font contains a glyph for that codepoint or not. User agents that
+   the font contains a glyph for that code point or not. User agents that
    download fonts for characters outside the defined unicode-range are
    considered non-conformant. Likewise, user agents that render a character
    using a font resource for which the defined unicode-range does not include
@@ -2295,7 +2299,7 @@ <h3 id=character><span class=secno>4.5 </span>Character range: the ‘<code
   <dl>
    <dt>unicode-range: U+A5;
 
-   <dd>a single codepoint, the yen/yuan symbol
+   <dd>a single code point, the yen/yuan symbol
 
    <dt>unicode-range: U+0-7F;
 
@@ -2427,16 +2431,16 @@ <h3 id=character><span class=secno>4.5 </span>Character range: the ‘<code
 </pre>
 
    <p>The user agent again first checks the unicode-range of the font
-    containing Latin characters. Since U+2000-2300 includes the arrow
-    codepoint (U+21E8), the user agent downloads the font. For this character
+    containing Latin characters. Since U+2000-2300 includes the arrow code
+    point (U+21E8), the user agent downloads the font. For this character
     however the Latin font does not have a matching glyph, so the effective
-    unicode-range used for font matching excludes this codepoint. Next, the
+    unicode-range used for font matching excludes this code point. Next, the
     user agent evaluates the Japanese font. The unicode-range for the
     Japanese font, U+3000-9FFF and U+ff??, does not include U+21E8, so the
     user agent does <strong>not</strong> download the Japanese font. Next the
     fallback font is considered. The @font-face rule for the fallback font
     does not define unicode-range so it's value defaults to the range of all
-    Unicode codepoints. The fallback font is downloaded and used to render
+    Unicode code points. The fallback font is downloaded and used to render
     the arrow character.</p>
   </div>
   <!-- Tools to create subsetted fonts a problem.  Also, combining diacritics
@@ -2631,7 +2635,7 @@ <h3>Examples of font matching</h3>
   <div class=example>
    <p>It's useful to note that the CSS selector syntax may be used to create
     language-sensitive typography. For example, some Chinese and Japanese
-    characters are unified to have the same Unicode codepoint, although the
+    characters are unified to have the same Unicode code point, although the
     abstract glyphs are not the same in the two languages.
 
    <pre>*:lang(ja-jp) { font: 900 14pt/16pt &quot;Heisei Mincho W9&quot;, serif; }