On Thu, 04 Dec 2014 08:10:00 +0100
Hans-Peter Diettrich <drdiettri...@aol.com> wrote:
>[...]
> >> Using UTF-8 sources *and* {$codepage UTF8} cures the unusable CP_ACP
> >> encoding of string literals, they are converted as expected in immediate
> >> output or when assigned to any AnsiString. Other settings cannot work
> >> with the current handling of AnsiString :-(
> >
> > CP_ACP is usable with the DefaultSystemCodepage.
>
> Currently AnsiUpperCase etc. will work on Windows *only* if
> DefaultSystemCodePage matches the WinAPI CP_ACP.
Probably some other widestringmanager function have the same problem.
And some other functions have some unneeded overhead for
DefaultSystemCodePage CP_UTF8.
Maybe the paswstring can be adapted.
Mattias
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
