Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62394
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.128 cause and error)
Message-ID: <5034931A.8050309@lsces.co.uk>
Date: Wed, 22 Aug 2012 09:06:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <503388D3.6060403@hoa-project.net> <CAEZPtU4EdwP7fTMGdQYDConGk=xHZxJ45eOo0xnGceo+DuNTvQ@mail.gmail.com> <50348488.4000701@hoa-project.net>
In-Reply-To: <50348488.4000701@hoa-project.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] UTF-8 files and include
From: lester@lsces.co.uk (Lester Caine)

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? 
'detecting and fixing' something which seems to change at random is somewhat 
difficult. For a long time I only used only lowercase file names when I was 
heavily into cross OS working. Fortunately most of the customer sites who would 
not allow Linux servers back then are now installing them themselves :)

This makes life a little easy now ... but add more than European character sets 
into the equation, and windows is still the sticking point simply because of 
'code page conversion'. When PHP6 was being roadmapped, personally I was looking 
to it as the solution to these problem, but without the OS getting it right in 
the first place there is not a lot we can do except just take a lot of care with 
how we use unicode characters :(

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk