[fpc-devel] Unicode and UTF8String

Michael Schnell mschnell at lumino.de
Tue Dec 2 10:25:45 CET 2008

> Don't forget that the ansistring type is actually multiple encodings and
> even multi byte (even not considering UTF-8). The point is: nobody took
> care of it.
IMHO a major confusion is generated by calling a string that is supposed 
to hold UTF8 data "ANSIString". This never should have happened ! If the 
Unicode support requires that there are strings that hold ANSI code and 
those that hold UTF8 code they should be denoted correctly as ANSIString 
and UTF8String. Storing ÚTF8 in an ANSIString is a sin :). IMHO, not 
providing automatic conversion between these type is a major shortcoming 
of the compiler/RTL and if it not does so, it should not provide the 
types. (Which does not mean that providing the (best possible) automatic 
conversion between these type solves all problems !)


More information about the fpc-devel mailing list