That is because FPC has no unicode string type yet (as must have been repeated about 20 times by now).
We are not discussing what it has, but what it should have and how this can be done in a way that provides decent performance on all platforms, is easy to use, compatible to D2009 and optimally versatile (see the first message in this thread). This of course only can be provided with user-settable options, that can be set according to the needs of the specific project.

Nobody is complaining that the currant state is like it is but that does not mean that it should stay this way.

-Michael
_______________________________________________
fpc-devel maillist  -  [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply via email to