[html5] r5822 - [e] (0) s/codepoint/code point/ for consistency Fixing http://www.w3.org/Bugs/Pu [...]

whatwg at whatwg.org whatwg at whatwg.org
Thu Feb 3 12:59:20 PST 2011


Author: ianh
Date: 2011-02-03 12:59:18 -0800 (Thu, 03 Feb 2011)
New Revision: 5822

Modified:
   complete.html
   index
   source
Log:
[e] (0) s/codepoint/code point/ for consistency
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11644

Modified: complete.html
===================================================================
--- complete.html	2011-02-03 20:57:51 UTC (rev 5821)
+++ complete.html	2011-02-03 20:59:18 UTC (rev 5822)
@@ -3698,8 +3698,8 @@
    <dd>Each byte must be replaced with a U+FFFD REPLACEMENT CHARACTER.</dd>
 
   </dl><p>For the purposes of the above requirements, an <dfn id=overlong-form>overlong
-  form</dfn> in UTF-8 is a sequence that encodes a codepoint using
-  more bytes than the minimum needed to encode that codepoint in
+  form</dfn> in UTF-8 is a sequence that encodes a code point using
+  more bytes than the minimum needed to encode that code point in
   UTF-8.</p>
 
   <p class=example>For example, the byte string "41 98 BA 42 E2 98
@@ -48971,7 +48971,7 @@
            0x30 to 0x39, 0x41 to 0x5A, 0x5F, 0x61 to 0x7A</dt>
 
            <dd><p>Append to <var title="">s</var> the Unicode
-           character with the codepoint equal to the byte.</dd>
+           character with the code point equal to the byte.</dd>
 
            <dt>Otherwise</dt>
 
@@ -77549,7 +77549,7 @@
 
   <p>Code points in the range U+D800 to U+DFFF<!-- surrogates are not
   allowed e.g. in UTF-8, and we don't want them to suddenly turn into
-  codepoints when they go through a UTF-16 pipe --> in the input must
+  code points when they go through a UTF-16 pipe --> in the input must
   be replaced by U+FFFD REPLACEMENT CHARACTERs. Any occurrences of
   such characters and code points are <a href=#parse-error title="parse error">parse
   errors</a>.</p>

Modified: index
===================================================================
--- index	2011-02-03 20:57:51 UTC (rev 5821)
+++ index	2011-02-03 20:59:18 UTC (rev 5822)
@@ -3677,8 +3677,8 @@
    <dd>Each byte must be replaced with a U+FFFD REPLACEMENT CHARACTER.</dd>
 
   </dl><p>For the purposes of the above requirements, an <dfn id=overlong-form>overlong
-  form</dfn> in UTF-8 is a sequence that encodes a codepoint using
-  more bytes than the minimum needed to encode that codepoint in
+  form</dfn> in UTF-8 is a sequence that encodes a code point using
+  more bytes than the minimum needed to encode that code point in
   UTF-8.</p>
 
   <p class=example>For example, the byte string "41 98 BA 42 E2 98
@@ -48953,7 +48953,7 @@
            0x30 to 0x39, 0x41 to 0x5A, 0x5F, 0x61 to 0x7A</dt>
 
            <dd><p>Append to <var title="">s</var> the Unicode
-           character with the codepoint equal to the byte.</dd>
+           character with the code point equal to the byte.</dd>
 
            <dt>Otherwise</dt>
 
@@ -73525,7 +73525,7 @@
 
   <p>Code points in the range U+D800 to U+DFFF<!-- surrogates are not
   allowed e.g. in UTF-8, and we don't want them to suddenly turn into
-  codepoints when they go through a UTF-16 pipe --> in the input must
+  code points when they go through a UTF-16 pipe --> in the input must
   be replaced by U+FFFD REPLACEMENT CHARACTERs. Any occurrences of
   such characters and code points are <a href=#parse-error title="parse error">parse
   errors</a>.</p>

Modified: source
===================================================================
--- source	2011-02-03 20:57:51 UTC (rev 5821)
+++ source	2011-02-03 20:59:18 UTC (rev 5822)
@@ -2667,8 +2667,8 @@
   </dl>
 
   <p>For the purposes of the above requirements, an <dfn>overlong
-  form</dfn> in UTF-8 is a sequence that encodes a codepoint using
-  more bytes than the minimum needed to encode that codepoint in
+  form</dfn> in UTF-8 is a sequence that encodes a code point using
+  more bytes than the minimum needed to encode that code point in
   UTF-8.</p>
 
   <p class="example">For example, the byte string "41 98 BA 42 E2 98
@@ -55059,7 +55059,7 @@
            0x30 to 0x39, 0x41 to 0x5A, 0x5F, 0x61 to 0x7A</dt>
 
            <dd><p>Append to <var title="">s</var> the Unicode
-           character with the codepoint equal to the byte.</p></dd>
+           character with the code point equal to the byte.</p></dd>
 
            <dt>Otherwise</dt>
 
@@ -87815,7 +87815,7 @@
 
   <p>Code points in the range U+D800 to U+DFFF<!-- surrogates are not
   allowed e.g. in UTF-8, and we don't want them to suddenly turn into
-  codepoints when they go through a UTF-16 pipe --> in the input must
+  code points when they go through a UTF-16 pipe --> in the input must
   be replaced by U+FFFD REPLACEMENT CHARACTERs. Any occurrences of
   such characters and code points are <span title="parse error">parse
   errors</span>.</p>




More information about the Commit-Watchers mailing list