Re: charset parameter

From: Bjoern Hoehrmann (derhoermi@gmx.net)
Date: Sat, Jul 28 2001

  • Next message: Terje Bless: "Re: Error Index / Summary"

    From: Bjoern Hoehrmann <derhoermi@gmx.net>
    To: Nick Kew <nick@webthing.com>
    Cc: Martin Duerst <duerst@w3.org>, W3C Validator <www-validator@w3.org>
    Date: Sat, 28 Jul 2001 22:35:35 +0200
    Message-ID: <o886mt09l9f63c6ki0ic5idtrojn3hp4vi@4ax.com>
    Subject: Re: charset parameter
    
    * Nick Kew wrote:
    >OK, smart****, what's this with charset="ISO-2022-JP" for posting to
    >this list?  Or are you really in Japan?
    
    His Received:-history implies this, yes :-)
    
    >> >3) Check for a CGI "charset" parameter.
    >> >   a) If found, use unconditionally, overriding META, but mark doc invalid.
    >> 
    >> This overrides both META and HTTP, so it should come first.
    >> The 'charset' parameter corresponds to an explicit (per page) user setting
    >> in a browser.
    >
    >er??? WTF is a CGI "charset" parameter?
    
    What he means is a user selectable charset
    that is passed via CGI to the script.
    
    >Is there some other HTTP charset header set by browsers?
    
    If they POST some form they may send a charset parameter for some types,
    as you certainly know :)
    -- 
    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/