W3C home > Mailing lists > Public > public-html-diffs@w3.org > December 2008

spec/Overview.html 1.1779 2608 terminology consistency fixes (whatwg r2

From: poot <cvsmail@w3.org>
Date: Mon, 29 Dec 2008 19:46:36 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20081229104636.6E0242BC14@toro.w3.mag.keio.ac.jp>

terminology consistency fixes (whatwg r2608)

limited to only known values
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#limited-to-only-known-values
2.4.3.2 Signed integers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#signed-integers
2.4.3.5 Percentages and dimensions
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#percentages-and-dimensions
2.4.2 Boolean attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#boolean-attributes
limited to only positive non-zero numbers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#limited-to-only-positive-non-zero-numbers
rules for parsing dimension values
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#rules-for-parsing-dimension-values
4.8.17 Dimension attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#dimension-attributes
rules for parsing integers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#rules-for-parsing-integers
2.4.3.6 Lists of integers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#lists-of-integers
find a number
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#find-a-number
2.4.3 Numbers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#numbers
rules for parsing a list of integers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#rules-for-parsing-a-list-of-integers
rules for parsing non-negative integers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1779.html#rules-for-parsing-non-negative-integers

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1778&r2=1.1779&f=h
http://html5.org/tools/web-apps-tracker?from=2607&to=2608

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1778
retrieving revision 1.1779
diff -u -d -r1.1778 -r1.1779
--- Overview.html	29 Dec 2008 09:59:51 -0000	1.1778
+++ Overview.html	29 Dec 2008 10:43:59 -0000	1.1779
@@ -158,7 +158,7 @@
      <li><a href=#boolean-attributes><span class=secno>2.4.2 </span>Boolean attributes</a></li>
      <li><a href=#numbers><span class=secno>2.4.3 </span>Numbers</a>
       <ol>
-       <li><a href=#unsigned-integers><span class=secno>2.4.3.1 </span>Unsigned integers</a></li>
+       <li><a href=#non-negative-integers><span class=secno>2.4.3.1 </span>Non-negative integers</a></li>
        <li><a href=#signed-integers><span class=secno>2.4.3.2 </span>Signed integers</a></li>
        <li><a href=#real-numbers><span class=secno>2.4.3.3 </span>Real numbers</a></li>
        <li><a href=#ratios><span class=secno>2.4.3.4 </span>Ratios</a></li>
@@ -1652,7 +1652,7 @@
   of the attribute represents the false value.<p>If the attribute is present, its value must either be the empty
   string or a value that is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a>
   match for the attribute's canonical name, with no leading or
-  trailing whitespace.<h4 id=numbers><span class=secno>2.4.3 </span>Numbers</h4><h5 id=unsigned-integers><span class=secno>2.4.3.1 </span>Unsigned integers</h5><p>A string is a <dfn id=valid-non-negative-integer>valid non-negative integer</dfn> if it
+  trailing whitespace.<h4 id=numbers><span class=secno>2.4.3 </span>Numbers</h4><h5 id=non-negative-integers><span class=secno>2.4.3.1 </span>Non-negative integers</h5><p>A string is a <dfn id=valid-non-negative-integer>valid non-negative integer</dfn> if it
   consists of one of more characters in the range U+0030 DIGIT ZERO
   (0) to U+0039 DIGIT NINE (9).<p>The <dfn id=rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</dfn> are as
   given in the following algorithm. When invoked, the steps must be
@@ -1702,7 +1702,8 @@
   more characters in the range U+0030 DIGIT ZERO (0) to U+0039 DIGIT
   NINE (9), optionally prefixed with a U+002D HYPHEN-MINUS ("-")
   character.<p>The <dfn id=rules-for-parsing-integers>rules for parsing integers</dfn> are similar to the
-  rules for non-negative integers, and are as given in the following
+  <a href=#rules-for-parsing-non-negative-integers title="rules for parsing non-negative integers">rules for
+  non-negative integers</a>, and are as given in the following
   algorithm. When invoked, the steps must be followed in the order
   given, aborting at the first step that returns a value. This
   algorithm will either return an integer or an error. Leading spaces
@@ -2017,10 +2018,9 @@
 
    <li>Return <var title="">number</var>.</li>
 
-  </ol><h5 id=percentages-and-dimensions><span class=secno>2.4.3.5 </span>Percentages and dimensions</h5><p class=XXX><dfn id=valid-positive-non-zero-integers>valid positive non-zero integers</dfn>
-  <dfn id=rules-for-parsing-dimension-values>rules for parsing dimension values</dfn> (only used by
-  height/width on img, embed, object &mdash; lengths in css pixels or
-  percentages)<h5 id=lists-of-integers><span class=secno>2.4.3.6 </span>Lists of integers</h5><p>A <dfn id=valid-list-of-integers>valid list of integers</dfn> is a number of <a href=#valid-integer title="valid integer">valid integers</a> separated by U+002C
+  </ol><h5 id=percentages-and-dimensions><span class=secno>2.4.3.5 </span>Percentages and dimensions</h5><p class=XXX><dfn id=rules-for-parsing-dimension-values>rules for parsing dimension values</dfn> (only
+  used by height/width on img, embed, object &mdash; lengths in css
+  pixels or percentages)<h5 id=lists-of-integers><span class=secno>2.4.3.6 </span>Lists of integers</h5><p>A <dfn id=valid-list-of-integers>valid list of integers</dfn> is a number of <a href=#valid-integer title="valid integer">valid integers</a> separated by U+002C
   COMMA characters, with no other characters (e.g. no <a href=#space-character title="space character">space characters</a>). In addition, there
   might be restrictions on the number of integers that can be given,
   or on the range of values allowed.<p>The <dfn id=rules-for-parsing-a-list-of-integers>rules for parsing a list of integers</dfn> are as
@@ -4359,29 +4359,28 @@
   and then that string must be used as the new content attribute
   value.<p>If a reflecting DOM attribute is an <em>unsigned</em> integer
   type (<code>unsigned long</code>) then, on getting, the content
-  attribute must be parsed according to <a href=#rules-for-parsing-non-negative-integers title="rules for parsing
-  non-negative integers">the rules for parsing unsigned
-  integers</a>, and if that is successful, the resulting value must
-  be returned. If, on the other hand, it fails, or if the attribute is
-  absent, the default value must be returned instead, or 0 if there is
-  no default value. On setting, the given value must be converted to
-  the shortest possible string representing the number as a
-  <a href=#valid-non-negative-integer>valid non-negative integer</a> in base ten and then that
-  string must be used as the new content attribute value.<p>If a reflecting DOM attribute is an unsigned integer type
+  attribute must be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing
+  non-negative integers</a>, and if that is successful, the
+  resulting value must be returned. If, on the other hand, it fails,
+  or if the attribute is absent, the default value must be returned
+  instead, or 0 if there is no default value. On setting, the given
+  value must be converted to the shortest possible string representing
+  the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a> in base ten
+  and then that string must be used as the new content attribute
+  value.<p>If a reflecting DOM attribute is an unsigned integer type
   (<code>unsigned long</code>) that is <dfn id=limited-to-only-positive-non-zero-numbers>limited to only positive
   non-zero numbers</dfn>, then the behavior is similar to the previous
   case, but zero is not allowed. On getting, the content attribute
-  must first be parsed according to <a href=#rules-for-parsing-non-negative-integers title="rules for parsing
-  non-negative integers">the rules for parsing unsigned
-  integers</a>, and if that is successful, the resulting value must
-  be returned. If, on the other hand, it fails, or if the attribute is
-  absent, the default value must be returned instead, or 1 if there is
-  no default value. On setting, if the value is zero, the user agent
-  must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
-  given value must be converted to the shortest possible string
-  representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
-  in base ten and then that string must be used as the new content
-  attribute value.<p>If a reflecting DOM attribute is a floating point number type
+  must first be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing
+  non-negative integers</a>, and if that is successful, the
+  resulting value must be returned. If, on the other hand, it fails,
+  or if the attribute is absent, the default value must be returned
+  instead, or 1 if there is no default value. On setting, if the value
+  is zero, the user agent must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code>
+  exception. Otherwise, the given value must be converted to the
+  shortest possible string representing the number as a <a href=#valid-non-negative-integer>valid
+  non-negative integer</a> in base ten and then that string must be
+  used as the new content attribute value.<p>If a reflecting DOM attribute is a floating point number type
   (<code>float</code>) and it doesn't fall into one of the earlier
   categories, then, on getting, the content attribute must be parsed
   according to <a href=#rules-for-parsing-floating-point-number-values title="rules for parsing floating point number
@@ -17671,7 +17670,8 @@
   of the visual content of the element (the width and height
   respectively, relative to the nominal direction of the output
   medium), in CSS pixels. The attributes, if specified, must have
-  values that are <a href=#valid-positive-non-zero-integers>valid positive non-zero integers</a>.<p>The specified dimensions given may differ from the dimensions
+  values that are <a href=#valid-non-negative-integer title="valid non-negative integer">valid
+  non-negative integers</a> greater than zero.<p>The specified dimensions given may differ from the dimensions
   specified in the resource itself, since the resource may have a
   resolution that differs from the CSS pixel resolution. (On screens,
   CSS pixels have a resolution of 96ppi, but in general the CSS pixel
Received on Monday, 29 December 2008 10:47:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT