* Ian Hickson wrote: >Accept-Charset was the one that has been mentioned several times -- >certainly unrestricting it (making it accept things that the UA won't know >how to handle) doesn't seem very useful, since the UA will be unable to >provide either a responseXML or responseText in that case.
Unless it is somehow guranteed that the response is in UTF-8 or UTF-16 scripts would have to deal with this in any case since the response may use an unsupported encoding no matter what the Accept-Charset header is set to, especially if implementations don't use *;q=0 or equivalent. -- Björn Höhrmann · mailto:[EMAIL PROTECTED] · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
