Edit report at https://bugs.php.net/bug.php?id=61484&edit=1
ID: 61484
Comment by: alec at alec dot pl
Reported by: juzna dot cz at gmail dot com
Summary: iconv //IGNORE option doesn't work anymore in PHP5.4
Status: Open
Type: Bug
Package: ICONV related
Operating System: Ubuntu
PHP Version: 5.4.0
Block user comment: N
Private report: N
New Comment:
The bug exists in PHP 5.3.10 and Ubuntu EGLIBC 2.15-0ubuntu10
Previous Comments:
------------------------------------------------------------------------
[2012-08-28 16:55:32] hrach dot cz at gmail dot com
PHP 5.4.6
iconv implementation libiconv
iconv library version 1.11
works!
------------------------------------------------------------------------
[2012-05-14 06:56:22] juzna dot cz at gmail dot com
The //ignore option is still broken as of the latest stable release (5.4.3).
From reading some of the other bug reports on this, apparently new versions of iconv no longer
support the //ignore option, and instead -c must be passed. So PHP needs to detect the //ignore
option and in that case pass the "-c" option to iconv.
------------------------------------------------------------------------
[2012-03-25 08:15:33] laruence@php.net
@rasmus yes, 5.3 and 5.4 behavior inconsistently, that is because icovn doesn't
accept //IGNORE anymore, and now return -1, then comes a bug(see #52211), felipe
fixed this in 5.4, but didn't fix 5.3. so now, 5.3 and 5.4 behave differently,
but the fundamental reason seems still is the glibc change their iconv behavior.
thanks, :)
------------------------------------------------------------------------
[2012-03-23 07:14:31] rasmus@php.net
Not sure this is a libc thing. 5.3 and 5.4 on the same libc behave differently.
They both report:
iconv implementation => glibc
iconv library version => 2.13
------------------------------------------------------------------------
[2012-03-23 07:11:09] laruence@php.net
see http://sources.redhat.com/bugzilla/show_bug.cgi?id=13518
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=61484--
Edit this bug report at https://bugs.php.net/bug.php?id=61484&edit=1