Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6389
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
In-Reply-To: <200312121956.43562.ilia@prohost.org>
References: <25BBBBC2-2CD2-11D8-8FCC-000A95CE0C62@at.wakwak.com> <200312121509.19291.ilia@prohost.org> <F3C2C394-2CDF-11D8-9A2A-000A95CE0C62@at.wakwak.com> <200312121956.43562.ilia@prohost.org>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <E7F4A8CB-2D07-11D8-9A2A-000A95CE0C62@at.wakwak.com>
Content-Transfer-Encoding: 7bit
Cc: PHP Internals <internals@lists.php.net>
Date: Sat, 13 Dec 2003 10:01:38 +0900
To: ilia@prohost.org
Subject: Re: [PHP-DEV] Re: Regarding the latest patch on fgetcsv() (stable branch)
From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi)

On 2003/12/13, at 9:56, Ilia Alshanetsky wrote:

> On December 12, 2003 03:15 pm, Moriyoshi Koizumi wrote:
>> If we limited the support to UTF-8 or EUC encoding only, we'd be
>> able to drastically gain much better performance. But it won't
>> actually solve practical problems where it is in action.
>
> Could iconv stream filters be used to convert various encoding (if 
> needed) to
> UTF-8 thus addressing the problem?

Actually it might do, but doing so leads to great overheads, because
you have to reconvert the strings to restore the initial form.
Besides the conversion is sometimes irreversible. And even it wouldn't
make sense unless iconv extension becomes built-in.

Moriyoshi