When you add LazUtils, it replaces the AnsiUpperCase call with UTF8UpperCase, which understands UTF8.
I did not use LazUtils anywhere in bithelpers demo, but maybe some of the used units uses it. Thanks for the info!
Note in the icon/manifest project section there is a tick to use the newer Windows 10 utf8 default option
I was not aware of that. Thanks! That can not be applied to console applications, right?
@Kays: I must admit that I didn't expect to see that FPC does not have any Upper derivate that goes beyond ASCII. Maybe there is a way to let OS handle it?
OS? No, that ain’t no task of an OS.
So what are functions like CharUpperBuffW() or LCMapStringA() doing in Windows API?
behavior of ANSIUpperCase depends on the utilized wide string manager. The following works on a Linux system
Thanks! It's more clear now.
So, it's not a bug after all...