On Tue, December 2, 2008 13:59, Graeme Geldenhuys wrote: > On Tue, Dec 2, 2008 at 2:47 PM, Sergei Gorelkin <[EMAIL PROTECTED]> > wrote: >> >> Unfortunately what those frameworks did isn't directly applicable to >> FPC. >> First, as I understand, they have only one (UTF-16) string type. This is >> good because it avoids whatever mess related to conversions, but not an >> option for FPC (because FPC requires compatibility with existing code). > > Then for backward compatibility use UTF-8 as the only string type. > That's what UTF-8 was designed for - backward compatibility. That's > also the reason LCL uses UTF-8. . .
As already stated several times, UTF-8 is not backwards compatible to the various character set encodings in active use (even with FPC), UTF-8 is only backwards compatible to plain 7-bit ASCII. Tomas _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
