3 ms·
ApiFunctionA is UTF-8 capable. Needs a run-time switch too, not just compile-time.
by cryptonector 3y ago
ApiFunctionA is UTF-8 capable. Needs a run-time switch too, not just compile-time.
- garaetjjte 3y agoIt's now possible, but for years the excuse was that MBCS encodings only supported characters up to 2 bytes.
- ComputerGuru 3y agoOnly under windows 11, I believe. And that switch is off by default.
- int_19h 3y agoYou're thinking of the global setting that is enabled by the user and applies to all apps that operate in terms of "current code page" - if enabled, that codepage becomes 65001 (UTF-8). However, on Win10+, apps themselves can explicitly opt into UTF-8 for all non-widechar Win32 APIs regardless of the current locale/codepage.
- sebazzz 3y agoYes: https://learn.microsoft.com/en-us/windows/win32/sbscs/application-manifests#activecodepage https://learn.microsoft.com/en-us/windows/win32/sbscs/applic... > On Windows 10, this element forces a process to use UTF-8 as the process code page. For more information, see Use the UTF-8 code page. On Windows 10, the only valid value for activeCodePage is UTF-8. > This element was first added in Windows 10 version 1903 (May 2019 Update). You can declare this property and target/run on earlier Windows builds, but you must handle legacy code page detection and conversion as usual. This element has no attributes.