Microsoft Windows Beta UTF-8 support for Ansi API could break things

[Tommi Prami 157]

Wiki Article of the Change

https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows#cite_note-10

 

One of out customer had selected that and we started to experience very weird problems and took some time to find out why it misbehaves.

None of the application could connect to Firebird SQL server (Ours or third party) successfully.

So would be smart to go through all tooling and code with that setting, we never know what M$oft will do with that, will it ever be released or will it soon be default for all.

 

One coder switched this on and started to get weird results, he could not specify what all symptoms, but said that lot of work to be done before that setting can be enabled.

Could be smart to Check how your environment, tools and code will behave.

[Kryvich 178]

Is it affect programs, written in Unicode enabled Delphi versions (Delphi 2009 and above)?

[Der schöne Günther 336]

Interesting option, I never knew. Anyways, I suppose this should only affect applications from Delphi environments that are over a decade old?

[pyscripter 793]

This is a very promising change in Windows.  However right now it breaks many things including Excel addins.

[Tommi Prami 157]

19 hours ago, pyscripter said:

This is a very promising change in Windows.  However right now it breaks many things including Excel addins.

Sure is, but in other hand, why not use "Unicode API" at first place.

 

I would guess  they use Ansi API just as proxy to and from Unicode UTF16 API.  

SomeWindowsApiA -> String Conversion to UTF16 -> SomeWindowsApiAW 

Have not checked, just my hunch...

In other hand If they have UTF-8 enabled API that is not just proxy to Wide API, then it could provide speed improvement if App uses UTF-8 strings.