- From: Daniel Veillard <daniel@veillard.com>
- Date: Fri, 22 Sep 2006 14:17:16 +0200
- To: "Henry S. Thompson" <ht@inf.ed.ac.uk>
- Cc: daniel@veillard.com, "Grosso, Paul" <pgrosso@ptc.com>, public-xml-core-wg@w3.org
On Fri, Sep 22, 2006 at 11:14:19AM +0100, Henry S. Thompson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Daniel Veillard writes: > > > It would be cool if W3C web server could avoid sending > > Content-Type: text/html; charset=iso-8859-1 > > when it has no idea of what it is doing and the document is > > stating > > <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> > > Fixed, I think. Heh, cool :-) That works now ! ...... Accept-Ranges: bytes Content-Length: 91624 Connection: close Content-Type: text/html; charset=utf-8 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html lang="EN"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"> ...... I remember hitting this last year, and didn't expect it to be fixed that fast. Kudos to the systeam :-) I still think having HTTP header overriding the charset indicated in the document (XML or HTML) to be a profundly absurd technical decision, but heh at least it can be made to work sometimes ... Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/
Received on Friday, 22 September 2006 12:17:32 UTC