From: Frank Yung-Fong Tang (email@example.com)
Date: Thu May 06 2004 - 10:34:47 CDT
3.1 Text/xml Registration
Conformant with [RFC2046], if a text/xml entity is received with
the charset parameter omitted, MIME processors and XML processors
MUST use the default charset value of "us-ascii"[ASCII]. In cases
where the XML MIME entity is transmitted via HTTP, the default
charset value is still "us-ascii".
Notice if the type is application/xml, the rule changed!!!
3.2 Application/xml Registration
If an application/xml entity is received where the charset
parameter is omitted, no information is being provided about the
charset by the MIME Content-Type header. Conforming XML
processors MUST follow the requirements in section 4.3.3 of [XML]
that directly address this contingency. However, MIME processors
that are not XML processors SHOULD NOT assume a default charset if
the charset parameter is omitted from an application/xml entity.
:( :( :(
This archive was generated by hypermail 2.1.5 : Fri May 07 2004 - 18:45:26 CDT