- From: Vojtech Rynda <voitech@seznam.cz>
- Date: Wed, 4 Sep 2002 16:06:12 -0400 (EDT)
- To: Thanasis Kinias <tkinias@optimalco.com>
- Cc: Lloyd Wood <l.wood@eim.surrey.ac.uk>, Olivier Thereaux <ot@w3.org>, Liam Quinn <liam@htmlhelp.com>, <www-validator@w3.org>
Wednesday, September 4, 2002, 5:27:31 PM: TK> scripsit Lloyd Wood: >> >> On Wed, 4 Sep 2002, Olivier Thereaux wrote: >> >> > On Wed, Sep 04, 2002, Lloyd Wood wrote: >> > > > Your server is sending the header >> > > > Content-Type: text/html; charset=us-ascii >> > > > which overrides the charset specified within the HTML document. >> > > >> > > Surely the charset in the document should take precedence? >> > >> > No, see http://www.w3.org/TR/REC-html40/charset.html#h-5.2.2 >> >> Thanks. >> >> I can't decide if that's a very subtle way to get Content-Type used >> properly, or just very very broken. TK> IMHO it's broken simply because a huge amount of Web content is deployed TK> by developers/designers who have no control over their servers. I may TK> develop a Japanese-language Web site hosted in the U.S., where the Web TK> server wants to call everything Latin-1 -- so I would use a <meta> to TK> tell clients I'm using UTF-8. Unless I have the financial resources to TK> set up a colo which is mine to play with, I have to live with imperfect TK> server configuration. It's a fact of life for most private-citizen TK> sites. So if I get it well, there's nothing I can do about it, because the charset specification is altered by the server anyway? XOXOXOX Vojtech Rynda
Received on Wednesday, 4 September 2002 20:20:48 UTC