[] (0) Recommend against support for EBCDIC-based encodings. (credit:…

… hs) git-svn-id: http://svn.whatwg.org/webapps@2125 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 29, 2008 · e57fbd8 · e57fbd8
1 parent 46d2f3f
commit e57fbd8
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 5 deletions.
diff --git a/index b/index
@@ -46737,12 +46737,16 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
    encodings. <a href="#refsCESU8">[CESU8]</a> <a href="#refsUTF7">[UTF7]</a>
    <a href="#refsBOCU1">[BOCU1]</a> <a href="#refsSCSU">[SCSU]</a>
 
+  <p>Support for encodings based on EBCDIC is not recommended. This encoding
+   is rarely used for publicly-facing Web content.
+
   <p>Support for UTF-32 is not recommended. This encoding is rarely used, and
    frequently misimplemented.
 
   <p class=note>This specification does not make any attempt to support
-   UTF-32 in its algorithms; support and use of UTF-32 can thus lead to
-   unexpected behavior in implementations of this specification.
+   EBCDIC-based encodings and UTF-32 in its algorithms; support and use of
+   these encodings can thus lead to unexpected behavior in implementations of
+   this specification.
 
   <h5 id=preprocessing><span class=secno>8.2.2.3. </span>Preprocessing the
    input stream</h5>

diff --git a/source b/source
@@ -44138,13 +44138,16 @@ interface <dfn>MessageChannel</dfn> {
   href="#refsUTF7">[UTF7]</a> <a href="#refsBOCU1">[BOCU1]</a> <a
   href="#refsSCSU">[SCSU]</a></p>
 
+  <p>Support for encodings based on EBCDIC is not recommended. This
+  encoding is rarely used for publicly-facing Web content.</p>
+
   <p>Support for UTF-32 is not recommended. This encoding is rarely
   used, and frequently misimplemented.</p>
 
   <p class="note">This specification does not make any attempt to
-  support UTF-32 in its algorithms; support and use of UTF-32 can thus
-  lead to unexpected behavior in implementations of this
-  specification.</p>
+  support EBCDIC-based encodings and UTF-32 in its algorithms; support
+  and use of these encodings can thus lead to unexpected behavior in
+  implementations of this specification.</p>