Ulrich Telle

> Sorry, I replied earlier, but maybe because of network problems, I didn't update the content of the reply to github. Well, as you could check for yourself, your reply...

> At present, I have also encountered a problem. When calling the sqlite_key function during system startup, this log display occasionally appears. Setting key failed,Encryption is not supported by the...

> > The kernel version is 4.19. > [...] > > As said above, I suspect that the problem may be related to the dated kernel version of your system....

> I think this is is what [@utelle](https://github.com/utelle)'s intention was. Correct. In prior wx versions the Windows date and time picker control **always** used the system locale, independent of the...

> Just to make clear: I was not arguing for reverting the change, I just wanted to list it among those changing the behaviour compared to 3.2. As @vadz already...

> I'm still not sure about the consistency argument. It's good in theory, of course, but in practice the difference is that many locales use the same numbers representation as...

> > AFAICT [StrCmpLogical()](https://learn.microsoft.com/en-us/windows/win32/api/shlwapi/nf-shlwapi-strcmplogicalw) does not involve any locale. > > While it is not documented, I think it does use the "Windows" locale. Yes, you are right - never...

> As long as an application is not explicitly told to use a specific locale setting, it should always use the system settings. Unfortunately, this is wishful thinking. C/C++ applications...

> > I have an application that worked fine in that area until I started using 3.3.0. I then had the effect, that my (German) system was showing American date...

> I understand your arguments, Ulrich, and this is why I had originally agreed (although not without a lot of hesitation) to make these changes. I know. And I hope...