[html5] r3161 - [e] (0) Try to be a little more consistent about typographical use. (bug 6770)

whatwg at whatwg.org whatwg at whatwg.org
Mon Jun 1 13:09:37 PDT 2009


Author: ianh
Date: 2009-06-01 13:09:35 -0700 (Mon, 01 Jun 2009)
New Revision: 3161

Modified:
   index
   source
Log:
[e] (0) Try to be a little more consistent about typographical use. (bug 6770)

Modified: index
===================================================================
--- index	2009-06-01 19:49:10 UTC (rev 3160)
+++ index	2009-06-01 20:09:35 UTC (rev 3161)
@@ -1477,12 +1477,12 @@
 
   <p>This specification refers to both HTML and XML attributes and DOM
   attributes, often in the same context. When it is not clear which is
-  being referred to, they are referred to as <dfn id=content-attributes>content
-  attributes</dfn> for HTML and XML attributes, and <dfn id=dom-attributes>DOM
+  being referred to, they are referred to as <dfn title="">content
+  attributes</dfn> for HTML and XML attributes, and <dfn title="">DOM
   attributes</dfn> for those from the DOM. Similarly, the term
   "properties" is used for both JavaScript object properties and CSS
-  properties. When these are ambiguous they are qualified as object
-  properties and CSS properties respectively.</p>
+  properties. When these are ambiguous they are qualified as <dfn title="">object properties</dfn> and <dfn title="">CSS properties
+  respectively</dfn>.</p>
 
   <p>The term <a href=#html-documents>HTML documents</a> is sometimes used in
   contrast with <a href=#xml-documents>XML documents</a> to specifically mean
@@ -1496,16 +1496,16 @@
   out by explicitly stating that it does not apply to the other
   format, as in "for HTML, ... (this does not apply to XHTML)".</p>
 
-  <p>This specification uses the term <i>document</i> to
+  <p>This specification uses the term <dfn title="">document</dfn> to
   refer to any use of HTML, ranging from short static documents to
   long essays or reports with rich multimedia, as well as to
   fully-fledged interactive applications.</p>
 
-  <p>For simplicity, terms such as <i>shown</i>, <i>displayed</i>,
-  and <i>visible</i> might sometimes be used when referring to the
-  way a document is rendered to the user. These terms are not meant to
-  imply a visual medium; they must be considered to apply to other
-  media in equivalent ways.</p>
+  <p>For simplicity, terms such as <dfn title="">shown</dfn>, <dfn title="">displayed</dfn>, and <dfn title="">visible</dfn> might
+  sometimes be used when referring to the way a document is rendered
+  to the user. These terms are not meant to imply a visual medium;
+  they must be considered to apply to other media in equivalent
+  ways.</p>
 
   <p>When an algorithm B says to return to another algorithm A, it
   implies that A called B. Upon returning to A, the implementation
@@ -1593,9 +1593,9 @@
   of the more accurate "an object implementing the interface
   <code>Foo</code>".</p>
 
-  <p>A DOM attribute is said to be <i>getting</i> when its value is
+  <p>A DOM attribute is said to be <dfn title="">getting</dfn> when its value is
   being retrieved (e.g. by author script), and is said to be
-  <i>setting</i> when a new value is assigned to it.</p>
+  <dfn title="">setting</dfn> when a new value is assigned to it.</p>
 
   <p>If a DOM object is said to be <dfn id=live>live</dfn>, then that means
   that any attributes returning that object <span class=impl>must</span> always return the same object (not a new
@@ -1603,7 +1603,7 @@
   <span class=impl>must</span> operate on the actual underlying
   data, not a snapshot of the data.</p>
 
-  <p>The terms <i>fire</i> and <i>dispatch</i> are used
+  <p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used
   interchangeably in the context of events, as in the DOM Events
   specifications. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a></p>
 
@@ -1650,7 +1650,7 @@
 
   <h4 id=resources><span class=secno>2.1.6 </span>Resources</h4>
 
-  <p>The specification uses the term <i>supported</i> when referring
+  <p>The specification uses the term <dfn title="">supported</dfn> when referring
   to whether a user agent has an implementation capable of decoding
   the semantics of an external resource. A format or type is said to
   be <i>supported</i> if the implementation can process an external
@@ -56605,12 +56605,12 @@
   history</a> consists of batches of one or more of the
   following:</p>
 
-  <ul><li>Changes to the <a href=#content-attributes>content attributes</a> of an
-   <code>Element</code> node.</li>
+  <ul><li>Changes to the content attributes of an <code>Element</code>
+   node.</li>
 
-   <li>Changes to the <a href=#dom-attributes>DOM attributes</a> of a
-   <code>Node</code>.</li> <!-- XXX uh, these change on their own, so
-   clearly this isn't going to fly. Which DOM attributes, exactly? -->
+   <li>Changes to the DOM attributes of a <code>Node</code>.</li> <!--
+   XXX uh, these change on their own, so clearly this isn't going to
+   fly. Which DOM attributes, exactly? -->
 
    <li>Changes to the DOM hierarchy of nodes that are descendants of
    the <code><a href=#htmldocument>HTMLDocument</a></code> object (<code>parentNode</code>,
@@ -70910,6 +70910,7 @@
   Martin Kutschker,
   Masataka Yakura,
   Mathieu Henri,
+  Matt Schmidt,
   Matt Wright,
   Matthew Gregan,
   Matthew Mastracci,

Modified: source
===================================================================
--- source	2009-06-01 19:49:10 UTC (rev 3160)
+++ source	2009-06-01 20:09:35 UTC (rev 3161)
@@ -429,12 +429,13 @@
 
   <p>This specification refers to both HTML and XML attributes and DOM
   attributes, often in the same context. When it is not clear which is
-  being referred to, they are referred to as <dfn>content
-  attributes</dfn> for HTML and XML attributes, and <dfn>DOM
+  being referred to, they are referred to as <dfn title="">content
+  attributes</dfn> for HTML and XML attributes, and <dfn title="">DOM
   attributes</dfn> for those from the DOM. Similarly, the term
   "properties" is used for both JavaScript object properties and CSS
-  properties. When these are ambiguous they are qualified as object
-  properties and CSS properties respectively.</p>
+  properties. When these are ambiguous they are qualified as <dfn
+  title="">object properties</dfn> and <dfn title="">CSS properties
+  respectively</dfn>.</p>
 
   <p>The term <span>HTML documents</span> is sometimes used in
   contrast with <span>XML documents</span> to specifically mean
@@ -448,16 +449,17 @@
   out by explicitly stating that it does not apply to the other
   format, as in "for HTML, ... (this does not apply to XHTML)".</p>
 
-  <p>This specification uses the term <i>document</i> to
+  <p>This specification uses the term <dfn title="">document</dfn> to
   refer to any use of HTML, ranging from short static documents to
   long essays or reports with rich multimedia, as well as to
   fully-fledged interactive applications.</p>
 
-  <p>For simplicity, terms such as <i>shown</i>, <i>displayed</i>,
-  and <i>visible</i> might sometimes be used when referring to the
-  way a document is rendered to the user. These terms are not meant to
-  imply a visual medium; they must be considered to apply to other
-  media in equivalent ways.</p>
+  <p>For simplicity, terms such as <dfn title="">shown</dfn>, <dfn
+  title="">displayed</dfn>, and <dfn title="">visible</dfn> might
+  sometimes be used when referring to the way a document is rendered
+  to the user. These terms are not meant to imply a visual medium;
+  they must be considered to apply to other media in equivalent
+  ways.</p>
 
   <p>When an algorithm B says to return to another algorithm A, it
   implies that A called B. Upon returning to A, the implementation
@@ -555,9 +557,9 @@
   of the more accurate "an object implementing the interface
   <code>Foo</code>".</p>
 
-  <p>A DOM attribute is said to be <i>getting</i> when its value is
+  <p>A DOM attribute is said to be <dfn title="">getting</dfn> when its value is
   being retrieved (e.g. by author script), and is said to be
-  <i>setting</i> when a new value is assigned to it.</p>
+  <dfn title="">setting</dfn> when a new value is assigned to it.</p>
 
   <p>If a DOM object is said to be <dfn>live</dfn>, then that means
   that any attributes returning that object <span
@@ -566,7 +568,7 @@
   <span class="impl">must</span> operate on the actual underlying
   data, not a snapshot of the data.</p>
 
-  <p>The terms <i>fire</i> and <i>dispatch</i> are used
+  <p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used
   interchangeably in the context of events, as in the DOM Events
   specifications. <a href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>
 
@@ -615,7 +617,7 @@
 
   <h4>Resources</h4>
 
-  <p>The specification uses the term <i>supported</i> when referring
+  <p>The specification uses the term <dfn title="">supported</dfn> when referring
   to whether a user agent has an implementation capable of decoding
   the semantics of an external resource. A format or type is said to
   be <i>supported</i> if the implementation can process an external
@@ -66379,12 +66381,12 @@
 
   <ul>
 
-   <li>Changes to the <span>content attributes</span> of an
-   <code>Element</code> node.</li>
+   <li>Changes to the content attributes of an <code>Element</code>
+   node.</li>
 
-   <li>Changes to the <span>DOM attributes</span> of a
-   <code>Node</code>.</li> <!-- XXX uh, these change on their own, so
-   clearly this isn't going to fly. Which DOM attributes, exactly? -->
+   <li>Changes to the DOM attributes of a <code>Node</code>.</li> <!--
+   XXX uh, these change on their own, so clearly this isn't going to
+   fly. Which DOM attributes, exactly? -->
 
    <li>Changes to the DOM hierarchy of nodes that are descendants of
    the <code>HTMLDocument</code> object (<code>parentNode</code>,
@@ -83570,6 +83572,7 @@
   Martin Kutschker,
   Masataka Yakura,
   Mathieu Henri,
+  Matt Schmidt,
   Matt Wright,
   Matthew Gregan,
   Matthew Mastracci,




More information about the Commit-Watchers mailing list