[html5] r4918 - [e] (0) americanization Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=6763
whatwg at whatwg.org
whatwg at whatwg.org
Wed Mar 31 01:45:53 PDT 2010
Author: ianh
Date: 2010-03-31 01:45:52 -0700 (Wed, 31 Mar 2010)
New Revision: 4918
Modified:
complete.html
index
source
Log:
[e] (0) americanization
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=6763
Modified: complete.html
===================================================================
--- complete.html 2010-03-31 08:37:24 UTC (rev 4917)
+++ complete.html 2010-03-31 08:45:52 UTC (rev 4918)
@@ -1946,10 +1946,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><font color=""></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><font color=""></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>
@@ -3233,7 +3233,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
@@ -10013,7 +10013,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>
@@ -19455,7 +19455,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>
@@ -22887,7 +22887,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><script>
function fallback(video) {
@@ -36124,9 +36124,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=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=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
@@ -39486,7 +39486,7 @@
table lists the keywords and states for the attribute — 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.</p>
<table><thead><tr><th> Keyword <th> State
@@ -45155,7 +45155,7 @@
</form></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>
@@ -49060,7 +49060,7 @@
<p class=note>The algorithms in this section are especially
inefficient, in the interests of keeping them easy to
understand. Implementors are strongly encouraged to refactor and
- optimise them in their user agents.</p>
+ optimize them in their user agents.</p>
<div class=example>
@@ -63005,7 +63005,7 @@
<p>For example:</p>
- <pre><p>Drop your favourite fruits below:</p>
+ <pre><p>Drop your favorite fruits below:</p>
<ol class="dropzone"
ondragenter="dragEnterHandler(event)"
ondragover="dragOverHandler(event)"
@@ -69013,7 +69013,7 @@
established">established</a> or for that connection to have
<a href=#fail-the-websocket-connection title="fail the WebSocket connection">failed</a>. If
multiple connections to the same IP address are attempted
- simultaneously, the user agent must serialise them so that there
+ simultaneously, the user agent must serialize them so that there
is no more than one connection at a time running through the
following steps.</p>
@@ -70200,7 +70200,7 @@
</dd>
- </dl><p>Unrecognised fields can be safely ignored, and are probably
+ </dl><p>Unrecognized fields can be safely ignored, and are probably
either the result of intermediaries injecting fields unrelated to
the operation of the WebSocket protocol, or clients that support
future versions of the protocol offering options that the server
@@ -70603,7 +70603,7 @@
<h6 id=handling-errors-in-utf-8-from-the-client><span class=secno>10.3.4.4.4 </span>Handling errors in UTF-8 from the client</h6>
<p>When a server is to interpret a byte stream as UTF-8 but finds
- that the byte stream is not in fact a valid UTF-8 stream, behaviour
+ that the byte stream is not in fact a valid UTF-8 stream, behavior
is undefined. A server could close the connection, convert invalid
byte sequences to U+FFFD REPLACEMENT CHARACTERs, store the data
verbatim, or perform application-specific processing. Subprotocols
@@ -81551,7 +81551,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>
@@ -84174,7 +84174,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>
@@ -85081,7 +85081,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
@@ -89237,7 +89237,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&Click=">IEC
+ <dd><cite lang=en-GB><a href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&Click=">IEC
61966-2-1: Multimedia systems and equipment — Colour measurement
and management — Part 2-1: Colour management — Default RGB colour
space — sRGB</a></cite>. IEC.</dd>
Modified: index
===================================================================
--- index 2010-03-31 08:37:24 UTC (rev 4917)
+++ index 2010-03-31 08:45:52 UTC (rev 4918)
@@ -1844,10 +1844,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><font color=""></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><font color=""></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>
@@ -3131,7 +3131,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
@@ -9911,7 +9911,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>
@@ -19353,7 +19353,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>
@@ -22788,7 +22788,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><script>
function fallback(video) {
@@ -36025,9 +36025,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=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=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
@@ -39387,7 +39387,7 @@
table lists the keywords and states for the attribute — 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.</p>
<table><thead><tr><th> Keyword <th> State
@@ -45056,7 +45056,7 @@
</form></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>
@@ -48961,7 +48961,7 @@
<p class=note>The algorithms in this section are especially
inefficient, in the interests of keeping them easy to
understand. Implementors are strongly encouraged to refactor and
- optimise them in their user agents.</p>
+ optimize them in their user agents.</p>
<div class=example>
@@ -62932,7 +62932,7 @@
<p>For example:</p>
- <pre><p>Drop your favourite fruits below:</p>
+ <pre><p>Drop your favorite fruits below:</p>
<ol class="dropzone"
ondragenter="dragEnterHandler(event)"
ondragover="dragOverHandler(event)"
@@ -74823,7 +74823,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>
@@ -77446,7 +77446,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>
@@ -78353,7 +78353,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
@@ -82641,7 +82641,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&Click=">IEC
+ <dd><cite lang=en-GB><a href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&Click=">IEC
61966-2-1: Multimedia systems and equipment — Colour measurement
and management — Part 2-1: Colour management — Default RGB colour
space — sRGB</a></cite>. IEC.</dd>
Modified: source
===================================================================
--- source 2010-03-31 08:37:24 UTC (rev 4917)
+++ source 2010-03-31 08:45:52 UTC (rev 4918)
@@ -770,10 +770,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><font color=""></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><font color=""></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>
@@ -2152,7 +2152,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 title="other applicable specifications">applicable
specification</dfn> for the purposes of conformance requirements in
@@ -10116,7 +10116,7 @@
<p>User agents are required to implement ARIA semantics on all
<span>HTML elements</span>, as defined in the ARIA
specifications. The <span>implicit ARIA semantics</span> defined
- below must be recognised by implementations. <a
+ below must be recognized by implementations. <a
href="#refsARIAIMPL">[ARIAIMPL]</a></p>
</div>
@@ -20640,7 +20640,7 @@
<p class="warning">While user agents are encouraged to repair cases
of missing <code title="attr-img-alt">alt</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>
@@ -24438,7 +24438,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>source</code> element and trigger fallback behaviour:</p>
+ <code>source</code> element and trigger fallback behavior:</p>
<pre><script>
function fallback(video) {
@@ -39936,11 +39936,11 @@
<p>...might render as:</p>
- <p><img src="images/sample-range.png" 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.">
+ <p><img src="images/sample-range.png" 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.">
<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">step</code> attribute has not
affected the placement of tick marks, the UA deciding to only use
@@ -43910,7 +43910,7 @@
table lists the keywords and states for the attribute — 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.</p>
<table>
@@ -50135,7 +50135,7 @@
</form></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>select</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>menu</code> element or of its <code>li</code>
@@ -54647,7 +54647,7 @@
<p class="note">The algorithms in this section are especially
inefficient, in the interests of keeping them easy to
understand. Implementors are strongly encouraged to refactor and
- optimise them in their user agents.</p>
+ optimize them in their user agents.</p>
<div class="example">
@@ -71187,7 +71187,7 @@
<p>For example:</p>
- <pre><p>Drop your favourite fruits below:</p>
+ <pre><p>Drop your favorite fruits below:</p>
<ol class="dropzone"
ondragenter="dragEnterHandler(event)"
ondragover="dragOverHandler(event)"
@@ -77452,7 +77452,7 @@
established">established</span> or for that connection to have
<span title="fail the WebSocket connection">failed</span>. If
multiple connections to the same IP address are attempted
- simultaneously, the user agent must serialise them so that there
+ simultaneously, the user agent must serialize them so that there
is no more than one connection at a time running through the
following steps.</p>
@@ -78790,7 +78790,7 @@
</dl>
- <p>Unrecognised fields can be safely ignored, and are probably
+ <p>Unrecognized fields can be safely ignored, and are probably
either the result of intermediaries injecting fields unrelated to
the operation of the WebSocket protocol, or clients that support
future versions of the protocol offering options that the server
@@ -79261,7 +79261,7 @@
<h6>Handling errors in UTF-8 from the client</h6>
<p>When a server is to interpret a byte stream as UTF-8 but finds
- that the byte stream is not in fact a valid UTF-8 stream, behaviour
+ that the byte stream is not in fact a valid UTF-8 stream, behavior
is undefined. A server could close the connection, convert invalid
byte sequences to U+FFFD REPLACEMENT CHARACTERs, store the data
verbatim, or perform application-specific processing. Subprotocols
@@ -92863,7 +92863,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>
@@ -95854,7 +95854,7 @@
<dd><p>Repeat the <code>object</code> element completely each time the resource is to be reused.</p></dd>
<dt><dfn title="attr-object-standby"><code>standby</code></dfn> on <code>object</code> elements</dt>
- <dd><p>Optimise the linked resource so that it loads quickly or, at least, incrementally.</p></dd>
+ <dd><p>Optimize the linked resource so that it loads quickly or, at least, incrementally.</p></dd>
<dt><dfn title="attr-param-type"><code>type</code></dfn> on <code>param</code> elements</dt>
<dt><dfn title="attr-param-valuetype"><code>valuetype</code></dfn> on <code>param</code> elements</dt>
@@ -96982,7 +96982,7 @@
title="attr-meta-name">name</code> content attribute when processing
a <code>meta</code> element with a <code
title="attr-meta-name">name</code> attribute whose value is one that
- the user agent recognises as supporting the <code
+ the user agent recognizes as supporting the <code
title="attr-meta-scheme">scheme</code> attribute.</p>
<p>User agents are encouraged to ignore the <code
@@ -102192,7 +102192,7 @@
<dd>The precise dialect has not yet been specified.</dd>
<dt id="refsSRGB">[SRGB]</dt>
- <dd><cite><a
+ <dd><cite lang="en-GB"><a
href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&Click=">IEC
61966-2-1: Multimedia systems and equipment — Colour measurement
and management — Part 2-1: Colour management — Default RGB colour
More information about the Commit-Watchers
mailing list