HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2125Recommend against support for EBCDIC-based encodings. (credit: hs)2008-08-29 09:35
@@ -44131,27 +44131,30 @@ interface <dfn>MessageChannel</dfn> {
   <p class="note">The requirement to treat certain encodings as other
   encodings according to the table above is a willful violation of the
   W3C Character Model specification. <a
   href="#refsCHARMOD">[CHARMOD]</a></p>
 
   <p>User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU
   encodings. <a href="#refsCESU8">[CESU8]</a> <a
   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>
 
 
 
   <h5>Preprocessing the input stream</h5>
 
   <p>Given an encoding, the bytes in the input stream must be
   converted to Unicode characters for the tokeniser, as described by
   the rules for that encoding, except that the leading U+FEFF BYTE
   ORDER MARK character, if any, must not be stripped by the encoding
   layer (it is stripped by the rule below).</p> <!-- this is to

|