W3C home > Mailing lists > Public > public-html-diffs@w3.org > April 2010

hixie: americanization (whatwg r4918)

From: poot <cvsmail@w3.org>
Date: Thu, 1 Apr 2010 14:46:01 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100401054601.9FA102BBF1@toro.w3.mag.keio.ac.jp>
hixie: americanization (whatwg r4918)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3938&r2=1.3939&f=h
http://html5.org/tools/web-apps-tracker?from=4917&to=4918

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3938
retrieving revision 1.3939
diff -u -d -r1.3938 -r1.3939
--- Overview.html	31 Mar 2010 08:37:28 -0000	1.3938
+++ Overview.html	31 Mar 2010 08:46:02 -0000	1.3939
@@ -1605,10 +1605,10 @@
 
     <p>It is significantly easier to maintain a site written in such a
     way that the markup is style-independent. For example, changing
-    the colour of a site that uses
-    <code>&lt;font&nbsp;color=""&gt;</code> throughout requires changes
-    across the entire site, whereas a similar change to a site based
-    on CSS can be done by changing a single file.</p>
+    the color of a site that uses <code>&lt;font&nbsp;color=""&gt;</code>
+    throughout requires changes across the entire site, whereas a
+    similar change to a site based on CSS can be done by changing a
+    single file.</p>
 
    </dd>
 
@@ -2731,7 +2731,7 @@
   either this specification can be updated accordingly, or an
   extension specification can be written that overrides the
   requirements in this specification. When someone applying this
-  specification to their activities decides that they will recognise
+  specification to their activities decides that they will recognize
   the requirements of such an extension specification, it becomes an
   <dfn id="other-applicable-specifications" title="other applicable specifications">applicable
   specification</dfn> for the purposes of conformance requirements in
@@ -8542,7 +8542,7 @@
   <p>User agents are required to implement ARIA semantics on all
   <a href="#html-elements">HTML elements</a>, as defined in the ARIA
   specifications. The <span>implicit ARIA semantics</span> defined
-  below must be recognised by implementations. <a href="#refsARIAIMPL">[ARIAIMPL]</a></p>
+  below must be recognized by implementations. <a href="#refsARIAIMPL">[ARIAIMPL]</a></p>
 
   </div><p>The following table defines the <span>strong native
   semantics</span> <span class="impl">and corresponding <span>implicit
@@ -16657,7 +16657,7 @@
 
   <p class="warning">While user agents are encouraged to repair cases
   of missing <code title="attr-img-alt"><a href="#attr-img-alt">alt</a></code> attributes, authors
-  must not rely on such behaviour. <a href="#alt">Requirements for
+  must not rely on such behavior. <a href="#alt">Requirements for
   providing text to act as an alternative for images</a> are described
   in detail below.</p>
 
@@ -19700,7 +19700,7 @@
    <p>If the author isn't sure if the user agents will all be able to
    render the media resources provided, the author can listen to the
    <code title="event-error">error</code> event on the last
-   <code><a href="#the-source-element">source</a></code> element and trigger fallback behaviour:</p>
+   <code><a href="#the-source-element">source</a></code> element and trigger fallback behavior:</p>
 
    <pre>&lt;script&gt;
  function fallback(video) {
@@ -29067,9 +29067,9 @@
 
    <p>...might render as:</p>
 
-   <p><img alt="A vertical slider control whose primary colour is black and whose background colour is beige, with the slider having five tick marks, one long one at each extremity, and three short ones clustered around the midpoint." src="http://dev.w3.org/html5/spec/images/sample-range.png"><p>Note how the UA determined the orientation of the control from
+   <p><img alt="A vertical slider control whose primary color is black and whose background color is beige, with the slider having five tick marks, one long one at each extremity, and three short ones clustered around the midpoint." src="http://dev.w3.org/html5/spec/images/sample-range.png"><p>Note how the UA determined the orientation of the control from
    the ratio of the style-sheet-specified height and width properties.
-   The colours were similiarly derived from the style sheet. The tick
+   The colors were similiarly derived from the style sheet. The tick
    marks, however, were derived from the markup. In particular, the
    <code title="attr-input-step"><a href="#attr-input-step">step</a></code> attribute has not
    affected the placement of tick marks, the UA deciding to only use
@@ -31968,7 +31968,7 @@
   table lists the keywords and states for the attribute &mdash; the
   keywords in the left column map to the states listed in the cell in
   the second column on the same row as the keyword. User agents are
-  not required to support these values, and must only recognise values
+  not required to support these values, and must only recognize values
   whose corresponding algorithms they support.<table><thead><tr><th> Keyword <th> State
    <tbody><tr><td> <code title="">rsa</code>
      <td> <i title="">RSA</i>
@@ -37247,7 +37247,7 @@
   &lt;/menu&gt;
  &lt;/menu&gt;
 &lt;/form&gt;</pre><p>The behavior in supporting user agents is similar to the example
-  above, but here the legacy behaviour consists of a single
+  above, but here the legacy behavior consists of a single
   <code><a href="#the-select-element">select</a></code> element with a submit button. The submit button
   doesn't appear in the toolbar, because it is not a direct child of
   the <code><a href="#menus">menu</a></code> element or of its <code><a href="#the-li-element">li</a></code>
@@ -49184,7 +49184,7 @@
   the <code title="event-drop"><a href="#event-drop">drop</a></code> event, which allows the
   actual drop to be performed. This event also needs to be canceled,
   so that the <code title="dom-DataTransfer-DropEffect"><a href="#dom-datatransfer-dropeffect">dropEffect</a></code> attribute's
-  value can be used by the source (otherwise it's reset).<p>For example:<pre>&lt;p&gt;Drop your favourite fruits below:&lt;/p&gt;
+  value can be used by the source (otherwise it's reset).<p>For example:<pre>&lt;p&gt;Drop your favorite fruits below:&lt;/p&gt;
 &lt;ol class="dropzone"
     ondragenter="dragEnterHandler(event)"
     ondragover="dragOverHandler(event)"
@@ -59790,7 +59790,7 @@
     <p class="note">If there is a <var title="">context</var> element,
     no <code title="">DOCTYPE</code> is passed to the parser, and
     therefore no external subset is referenced, and therefore no
-    entities will be recognised.</p>
+    entities will be recognized.</p>
 
    </li>
 
@@ -62271,7 +62271,7 @@
    <dd><p>Repeat the <code><a href="#the-object-element">object</a></code> element completely each time the resource is to be reused.</dd>
 
    <dt><dfn id="attr-object-standby" title="attr-object-standby"><code>standby</code></dfn> on <code><a href="#the-object-element">object</a></code> elements</dt>
-   <dd><p>Optimise the linked resource so that it loads quickly or, at least, incrementally.</dd>
+   <dd><p>Optimize the linked resource so that it loads quickly or, at least, incrementally.</dd>
 
    <dt><dfn id="attr-param-type" title="attr-param-type"><code>type</code></dfn> on <code><a href="#the-param-element">param</a></code> elements</dt>
    <dt><dfn id="attr-param-valuetype" title="attr-param-valuetype"><code>valuetype</code></dfn> on <code><a href="#the-param-element">param</a></code> elements</dt>
@@ -63178,7 +63178,7 @@
   <p>User agents may treat the <code title="attr-meta-scheme"><a href="#attr-meta-scheme">scheme</a></code> content attribute on the
   <code><a href="#meta">meta</a></code> element as an extension of the element's <code title="attr-meta-name"><a href="#attr-meta-name">name</a></code> content attribute when processing
   a <code><a href="#meta">meta</a></code> element with a <code title="attr-meta-name"><a href="#attr-meta-name">name</a></code> attribute whose value is one that
-  the user agent recognises as supporting the <code title="attr-meta-scheme"><a href="#attr-meta-scheme">scheme</a></code> attribute.</p>
+  the user agent recognizes as supporting the <code title="attr-meta-scheme"><a href="#attr-meta-scheme">scheme</a></code> attribute.</p>
 
   <p>User agents are encouraged to ignore the <code title="attr-meta-scheme"><a href="#attr-meta-scheme">scheme</a></code> attribute and instead process
   the value given to the metadata name as if it had been specified for
@@ -67102,7 +67102,7 @@
    for information interchange</cite>. Japanese Standards Association.</dd>
 
    <dt id="refsSRGB">[SRGB]</dt>
-   <dd><cite><a href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&amp;Click=">IEC
+   <dd><cite lang="en-GB"><a href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&amp;Click=">IEC
    61966-2-1: Multimedia systems and equipment &mdash; Colour measurement
    and management &mdash; Part 2-1: Colour management &mdash; Default RGB colour
    space &mdash; sRGB</a></cite>. IEC.</dd>
Received on Thursday, 1 April 2010 05:46:30 GMT

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