On Thu, 10 Dec 2015 12:02:31 +0000 Graeme Geldenhuys <mailingli...@geldenhuys.co.uk> wrote:
> On 2015-12-10 11:16, Jonas Maebe wrote: > > There is no such thing as "official FPC Unicode". We added support for > > codepage-aware ansistrings. We added unicodestring overloads for a > > Does the type UnicodeString always mean UTF-16 encoded text (like it's > Delphi counterpart)? If so, that unfortunate. Yes. > Can the encoding of UnicodeString be changed to say UTF-8? No. > And yes, I > know there is a UTF8String type too, but I'm specifically referring to > UnicodeString (as in the Unicode standard supporting multiple > encodings), as many RTL functions seem to use that specific type. Many RTL functions support UTF8String, AnsiString too, as Jonas already pointed out. > > The test program you posted later does not work completely because it > > uses routines that have not yet been adapted (UpCase and ToUpper are > > OK, so FPC unicode is still far from usable, as some RTL function will > work, and others won't. :-/ With that conclusion, I'll then keep > fpGUI's Unicode support exactly as it currently is. If you have a working Unicode solution there is no reason to abandon it. The FPC team did a great job keeping compatibility (contrary to Delphi). Mattias _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
