• From: MURATA Makoto <EB2M-MRT@a...>
• To: Bjoern Hoehrmann <derhoermi@g...>
• Date: Sun, 28 Oct 2001 22:17:54 +0900

Bjoern Hoehrmann wrote:

>   * HTML requires user agents to assume no default encoding
>   * HTTP requires user agents to assume iso-8859-1
>   * MIME requires user agents to assume us-ascii
>   * XML requires user agents to assume us-ascii
> 
> Obviously, this is a very strict community...

Yes.

> XML does not need to change MIME, XML can just go and mandate UTF-8
> defaulting from XML processors. Mandating UTF-8 is as inconsistent with
> HTTP as is mandating us-ascii. And who cares about consistency? Look at
> HTML, it forbids any defaulting behaivour, but allows user agents to use
> heuristics to determine the encoding. Welcome to the wonderful world
> of nonsense.

Which UTF-8?  UTF-8 with the Unicode signature or UTF-8 without the 
Unicode signature?

As far as IETF is concerned, the default for HTML is ISO-8859-1.  W3C 
specifications and IETF RFCs are inconsistent here.  More about this, 
see RFC 2854.

Cheers,

Makoto

• Follow-Ups:
  • Re: Text/xml with omitted charset parameter
    • From: Bjoern Hoehrmann <derhoermi@g...>
  • Re: Text/xml with omitted charset parameter
    • From: Elliotte Rusty Harold <elharo@m...>

• References:
  • Re: Text/xml with omitted charset parameter
    • From: Bjoern Hoehrmann <derhoermi@g...>

• Prev by Date: Re: Text/xml with omitted charset parameter
• Next by Date: Re: Text/xml with omitted charset parameter
• Previous by thread: Re: Text/xml with omitted charset parameter
• Next by thread: Re: Text/xml with omitted charset parameter
• Index(es):
  • Date
  • Thread