Seems like a documentation problem. Since its introduction
the iconv extension has never had such a function that converts the
HTTP queries into those of another encoding, so that setting
is useless at all. But there is the opposite function that
converts the output into another encoding.
Could you
Hi Derick Rethans, you wrote:
> This can never reproduce it, as the request variables are parsed
> before the script starts. Besides that, I don't think that this
> setting is indeed used at all.
Well ok, but setting this up in php.ini doesn't change anything...
Regards,
--
Michael - < mike(@)
On Tue, 5 Oct 2004, Michael Wallner wrote:
> Hi,
>
> perhaps I'm just missing something, the docs don't
> really mention anything about that issue...
>
> Shouldn't iconv decode HTTP input from "input_encoding"
> to "internal_encoding", and if not, then what is the
> input_encoding setting for?
>
>
Hi,
perhaps I'm just missing something, the docs don't
really mention anything about that issue...
Shouldn't iconv decode HTTP input from "input_encoding"
to "internal_encoding", and if not, then what is the
input_encoding setting for?
Here's a small script to reproduce:
===
