[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Text/xml with omitted charset parameter

• From: Bjoern Hoehrmann <derhoermi@g...>
• To: ietf-xml-mime@i...
• Date: Fri, 26 Oct 2001 03:07:04 +0200

Hi,

Quoting RFC 3023, section 8.5:

| 8.5 Text/xml with Omitted Charset
| 
|    Content-type: text/xml
| 
|    {BOM}<?xml version="1.0" encoding="utf-16"?>
| 
|    or
| 
|    {BOM}<?xml version="1.0"?>
| 
|    This example shows text/xml with the charset parameter omitted.  In
|    this case, MIME and XML processors MUST assume the charset is "us-
|    ascii",

... and issue a fatal error, no BOM in US-ASCII. Mentioning UTF-16 in
this example is absurd, XML documents labeled as text/xml without
charset parameter can never ever be UTF-16 encoded. So, who tells me I
am wrong and text/xml documents without charset parameter may still be
UTF-8 encoded (and use non-ASCII characters)? Apache uses text/xml as
default type for .xml documents, are they asking for interoperability
problems or what?
-- 
Björn Höhrmann { mailto:bjoern@h... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

• Follow-Ups:
  • Re: Text/xml with omitted charset parameter
    • From: Rick Jelliffe <ricko@a...>
  • Re: Text/xml with omitted charset parameter
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: Schema training recommendation
• Next by Date: RE: Text/xml with omitted charset parameter
• Previous by thread: expectations (was Re: Microsoft's deeply cynical appealto"standards comp liance")
• Next by thread: Re: Text/xml with omitted charset parameter
• Index(es):
  • Date
  • Thread