Next message: K.C. Jones: "Error Index / Summary"
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Martin Duerst <duerst@w3.org>
Cc: Terje Bless <link@pobox.com>, W3C Validator <www-validator@w3.org>
Date: Sat, 28 Jul 2001 05:07:01 +0200
Message-ID: <9qa4mtgooea2bsqer444273lqgc8pjhp4n@4ax.com>
Subject: Re: charset parameter
* Martin Duerst wrote:
>>No, the intent was, that _servers_ parse the HTML document and send the
>>correct Content-Type: header, HTML 4 even says so.
>
>Where?
E.g. http://www.w3.org/TR/html4/struct/global.html#adef-http-equiv
obviously.
>Is that a must?
For whom? An HTTP server implementing HTML?
>>[1] I think the http-equiv attribute is the worst thing ever
>> incorporated into HTML. It hasn't been implemented, it beeing
>> abused, semantics aren't clearly defined, the definition is
>> ambigious, only a small number of people put syntactically valid
>> information in the content attribute for some HTTP headers, etc.pp.
>> I'll find some evil hellcat to put even more evil spells on the HTML
>> WG members if this attribute won't be kicked out of XHTML 2.0 (or
>> replaced by something with value) };-)
>
>This is easy to guess. XHTML 2.0 will use the XML 'encoding' pseudo-attribute.
The http-equiv attribute is used for far more things than just the
Content-Type: header, unfortunaly.
--
Björn Höhrmann { mailto:bjoern@hoehrmann.de } 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/