Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108866
To: internals@lists.php.net
References: <09dd1b84-ed33-a059-82f9-5efd179e69d6@gmx.de>
Message-ID: <0233ec6d-267f-a5e4-b114-17b4c9bbff60@alec.pl>
Date: Thu, 5 Mar 2020 12:59:45 +0100
MIME-Version: 1.0
In-Reply-To: <09dd1b84-ed33-a059-82f9-5efd179e69d6@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] iconv vs. mbstring
From: alec@alec.pl (Aleksander Machniak)

On 03.03.2020 23:16, Christoph M. Becker wrote:
> For users learning PHP, and also for new code, it would be beneficial to
> not have to decide which of these extensions to use; if they need
> character encoding conversion, iconv() would be preferable; for more
> general string functionality, it would be ext/mbstring.

From my experience iconv does not support all charsets e.g. UTF7-IMAP or
ISO-2022-JP-MS, that mbstring does.

Also, I have a case in which iconv_* functions were much much slower
than mbstring. See wordwrap implementation in
https://github.com/roundcube/roundcubemail/blob/master/program/lib/Roundcube/rcube_mime.php#L589

I did not do any performance comparison for iconv() function itself and
I'm not sure it should be considered preferable. I saw a lot of
performance improvements in mbstring in the last year or so. Do anyone
have some perf. comparison for charset conversion cases?

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com