Re: Unicode strings?
Pierre Joye wrote:
ICU Text Access allows other formats, such as UTF-8 or non-contiguous
UTF-16 strings, to be placed in a UText wrapper and then passed to ICU
services.
This is running in circle and does not really help to move forwards...
Lester has a point with the UTF-8 testing. I am almost done with the
tests code and will publish it soonish.
Also I do not get your argument earlier in this discussion saying that
we should not implement objects or pseudo-objects for unicode support.
where is the problem? It can work with existing functions as well,
does not break BC, does not introduce weird syntax that prevents code
from running in 5.x and 6.x (u"foo" will f.e.). The more I look at it,
the more I think it is the way.
I think we are both heading to the same point from different ends Pierre? That is as far as handling unicode data is concerned. It's not so much running in a circle as the chicken and egg. Select any 3 out of four options to get to the final answer?
I'm back on windows platform looking at problems there and I had forgotten just how badly Borland C++ handles widestring, but running ICU there and stripping that code will work for me! I'm not sure that a library in the middle is needed, JUST some pseudo-objects to smooth the transition? ICU running in UTF-8 mode does seem to be the answer, but while I can test C++ builds I'm just not into the PHP codebase enough to do the sort of testing that is needed :( Conversion to C++ is something I could deal with ...
Unicode variable names ARE secondary, but if the handling of unicode works as well as it seems to be for me then it may be an option that can be considered.
--
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
Thread (28 messages)