Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72841 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72066 invoked from network); 27 Feb 2014 11:28:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2014 11:28:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:55630] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/64-41714-0512F035 for ; Thu, 27 Feb 2014 06:28:16 -0500 Received: (qmail 5452 invoked by uid 89); 27 Feb 2014 11:28:13 -0000 Received: by simscan 1.3.1 ppid: 5446, pid: 5449, t: 0.1021s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 27 Feb 2014 11:28:13 -0000 Message-ID: <530F2264.10200@lsces.co.uk> Date: Thu, 27 Feb 2014 11:32:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24 MIME-Version: 1.0 To: PHP internals References: <530F0BF8.4040307@lsces.co.uk> <530F18C6.1000301@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: [php6] Unicode support, options? From: lester@lsces.co.uk (Lester Caine) Pierre Joye wrote: >> It may well be that windows is a special case that needs it's own conversion >> >layer, but that should not form part of any core upgrade. It is not needed >> >for many installations? > Sorry if I was not clear earlier. No matter what we do, we will have > to convert to or from UTF-8 for all file related APIs on Windows > anyway. But that will happen before 6, so not really a unicode problem > in this case, more a bug fix to bring windows in line with linux, > about UTF-8 paths support (and longer paths), but that's a different > topic. > I do not understand what you mean by "not form part of any core upgrade". Actually you have already provided a better answer to that than I could have :) Handling the remaining windows related problems only really relate to windows builds? I was naively thinking that the windows conversions were part of this as the easl library seemed to be more involved with that than simple UTF-8 handling? I'll put my hand up that I've not worried about windows for some time now, but I do have a number of PHP5.2 sites that will need to be upgraded soon and the discussion on Firebird is also about ICU and Windows ... but none of those sites will ever need anything more than simple ASCII anyway. -- 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