Is there a way to ignore all these and make everything to work with UTF-8? Like setting some global variable that makes all strings (ansistrings) "UTF-8 codepage" or something that also causes any system-specific calls (Assign, Writeln, etc) to do automatic conversion from/to whatever the underlying OS uses?
On Fri, Jan 3, 2014 at 11:42 PM, Graeme Geldenhuys <mailingli...@geldenhuys.co.uk> wrote: > On 2014-01-03 21:37, Sven Barth wrote: >> >> This might bite you with 2.7.1 as ShortString is considered as being >> encoded in CP_ACP. Thus on systems were the system code page is not > > Thanks for pointing that out, and I've made a note to test this when the > time comes. As previously mentioned, fpGUI only uses UTF-8 internally, > and has fpg* specific functions for working with RTL and custom string > functions. So when there is a String[4] or AnsiString type used > somewhere, it is what some here consider a "AnsiString hack".. ie: an > array of bytes representing a UTF-8 string, but stored in an AnsiString > container. When TfpgChar or TfpgString is used, the framework knows it > contains UTF-8 encoded text. > > All this will be revisited and tested once the FPC 2.8.0 (or 3.0) > release gets closer to realisation. > > > Regards, > - Graeme - > > -- > fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal > http://fpgui.sourceforge.net/ > > -- > _______________________________________________ > Lazarus mailing list > Lazarus@lists.lazarus.freepascal.org > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus