[fpc-devel] Unicode support (again)

[Michael Schnell]

> Your example shows just how accurate Widestring should be interpreted: 
> It just only shows it is a two ore more byte  sequence to represend a 
> single character. It doesn't say anything about the content or the use 
> of a specific (meta) encoding like UCS2 or Unicode16.
Of course I did mean that in the each string type (UTF8String, 
ANSIString, (UTF16)Widestring and (UCS2)WideString, the content is 
encoded as the native string name requests (of course there right now is 
no type UTF16String and UCS2String, but with all the current examples 
(not using surrogate pairs) the bits in same (and in WideString) are the 
same.)


-Michael