Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62396
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5034931A.8050309@lsces.co.uk>
References: <503388D3.6060403@hoa-project.net>
	<CAEZPtU4EdwP7fTMGdQYDConGk=xHZxJ45eOo0xnGceo+DuNTvQ@mail.gmail.com>
	<50348488.4000701@hoa-project.net>
	<5034931A.8050309@lsces.co.uk>
Date: Wed, 22 Aug 2012 10:18:51 +0200
Message-ID: <CAEZPtU7WbG7eEYTUzpPZctNg9Omq-xWvA8iaxY-bX2E34D8rqA@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] UTF-8 files and include
From: pierre.php@gmail.com (Pierre Joye)

hi Lester,

On Wed, Aug 22, 2012 at 10:06 AM, Lester Caine <lester@lsces.co.uk> wrote:
> Ivan Enderlin @ Hoa wrote:
>>>
>>> As it may (very often) works smoothly on most unices, it won't work
>>> ever using current releases or master on Windows. One has to set the
>>> correct codepage and do the conversion from/to UTF-8.
>>
>> Exactly. I can detect if PHP is running on Windows and making the
>> conversion
>> on-the-fly but what kind of conversion? I have tried with utf8_decode()
>> but it
>> seems to also fail. Any other idea?
>
>
> Oh that it was so simple ;)
>
> This is perhaps one of the reasons development of PHP6 ground to a halt?

No, it was not.

Also unicode support on windows for IO operations (on the paths, not
the contents) is planed for php-next+1 (aka not the 5.5 but the one
after).

I'd also to ask to do not hijack this thread with a php6/whatever else
rant and keep focusing on answering Ivan's questions instead.

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org