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