[html5] r3682 - [e] (0) Clarify text that some people thought implied you had to implement alias [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Aug 26 15:33:18 PDT 2009
Author: ianh
Date: 2009-08-26 15:33:17 -0700 (Wed, 26 Aug 2009)
New Revision: 3682
Modified:
index
source
Log:
[e] (0) Clarify text that some people thought implied you had to implement aliases for encodings you didn't support (whatever that would mean).
Modified: index
===================================================================
--- index 2009-08-26 22:29:48 UTC (rev 3681)
+++ index 2009-08-26 22:33:17 UTC (rev 3682)
@@ -5072,7 +5072,8 @@
<p>User agents must support the preferred MIME name of every
character encoding they support that has a preferred MIME name, and
- should support all the IANA-registered aliases. <a href=#refsIANACHARSET>[IANACHARSET]</a></p>
+ should support all the IANA-registered aliases of every character
+ encoding they support. <a href=#refsIANACHARSET>[IANACHARSET]</a></p>
<p>When comparing a string specifying a character encoding with the
name or alias of a character encoding to determine if they are
@@ -5083,9 +5084,10 @@
<!-- this bit will be replaced by actual alias registrations in due course -->
<p>In addition, user agents must support the aliases given in the
- following table, so that labels from the first column are treated as
- equivalent to the labels given in the corresponding cell from the
- second column on the same row.</p>
+ following table for every character encoding they support, so that
+ labels from the first column are treated as equivalent to the labels
+ given in the corresponding cell from the second column on the same
+ row.</p>
<table><caption>Additional character encoding aliases</caption>
<thead><tr><th> Alias <th> Corresponding encoding <th> References
Modified: source
===================================================================
--- source 2009-08-26 22:29:48 UTC (rev 3681)
+++ source 2009-08-26 22:33:17 UTC (rev 3682)
@@ -4771,7 +4771,8 @@
<p>User agents must support the preferred MIME name of every
character encoding they support that has a preferred MIME name, and
- should support all the IANA-registered aliases. <a
+ should support all the IANA-registered aliases of every character
+ encoding they support. <a
href="#refsIANACHARSET">[IANACHARSET]</a></p>
<p>When comparing a string specifying a character encoding with the
@@ -4784,9 +4785,10 @@
<!-- this bit will be replaced by actual alias registrations in due course -->
<p>In addition, user agents must support the aliases given in the
- following table, so that labels from the first column are treated as
- equivalent to the labels given in the corresponding cell from the
- second column on the same row.</p>
+ following table for every character encoding they support, so that
+ labels from the first column are treated as equivalent to the labels
+ given in the corresponding cell from the second column on the same
+ row.</p>
<table>
<caption>Additional character encoding aliases</caption>
More information about the Commit-Watchers
mailing list