> -Original Message-
> From: Andrei Zmievski [mailto:[EMAIL PROTECTED]
> Sent: 10 July 2006 23:50
> To: [EMAIL PROTECTED]
> Cc: 'Sara Golemon'; internals@lists.php.net
> Subject: Re: [PHP-DEV] Re: [PHP-I18N] RFC: Error handling in
> HTTP input decodin
e: [PHP-DEV] Re: [PHP-I18N] RFC: Error handling in
HTTP input decoding
W3 standard is to have the charset parameter on the Content-Type
header.
Unfortunately this breaks too much server side software, so no
UserAgents do
it.
Hence the _charset_ kludge Microsoft introduced awhile back, and
Firefox a
>
>
> > P.S. - Has anyone considered offering up an RFC to IETF or
> > W3C about adding
> > a header to the spec? Or just asking the nice Firefox folks
> > to blaze the
> > trail with an X-header? PHP can't be the only web-language
> > dealing with
> > this issue.
>
> W3 standard is to ha
W3 standard is to have the charset parameter on the Content-Type
header.
Unfortunately this breaks too much server side software, so no
UserAgents do
it.
Hence the _charset_ kludge Microsoft introduced awhile back, and
Firefox and
Opera (afaik) have now adopted.
As far as I know, the form a
> P.S. - Has anyone considered offering up an RFC to IETF or
> W3C about adding
> a header to the spec? Or just asking the nice Firefox folks
> to blaze the
> trail with an X-header? PHP can't be the only web-language
> dealing with
> this issue.
W3 standard is to have the charset paramete
