[e] (0) Clarify text that some people thought implied you had to impl…

…ement aliases for encodings you didn't support (whatever that would mean). git-svn-id: http://svn.whatwg.org/webapps@3682 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 26, 2009 · 4da1e2e · 4da1e2e
1 parent 40c1c42
commit 4da1e2e
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 8 deletions.
diff --git a/index b/index
@@ -5072,7 +5072,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <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 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 <!-- 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

diff --git a/source b/source
@@ -4771,7 +4771,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <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 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 <!-- 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>