Re: iconv's input_encoding useless?
| From: | Moriyoshi Koizumi | Date: | Wed, 06 Oct 2004 01:50:46 +0000 |
| Subject: | Re: iconv's input_encoding useless? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-13189@lists.php.net to get a copy of this message | ||
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 file it in bugs.php.net?
Thanks
Moriyoshi
On 2004/10/06, at 1:23, 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? Here's a small script to reproduce: ====================================================== <?php iconv_set_encoding('internal_encoding', 'iso-8859-1'); iconv_set_encoding('input_encoding', 'utf-8'); iconv_set_encoding('output_encoding', 'utf-8'); ob_start('ob_iconv_handler'); ?> <form method="post" action="?"> <input name="data" type="text"> <input type="submit"> </form> <hr> <pre> <?php print_r($_POST); foreach ($_POST as $k => $v) $_POST[$k] = iconv('utf-8', 'iso-8859-1', $v); print_r($_POST); ?> </pre> ====================================================== Many thanks, -- Michael - < mike(@)php.net >