←back to thread

238 points GalaxySnail | 1 comments | | HN request time: 0s | source
Show context
Affric ◴[] No.40169026[source]
Make UTF-8 default on Windows
replies(6): >>40169144 #>>40169474 #>>40170343 #>>40171178 #>>40173598 #>>40175253 #
pjc50 ◴[] No.40170343[source]
In addition to ApiFunctionA and ApiFunctionW, introduce ApiFunction8? (times whole API surface)

Introduce a #define UNICODE_NO_REALLY_ALL_UNICODE_WE_MEAN_IT_THIS_TIME ?

replies(1): >>40170814 #
cryptonector ◴[] No.40170814[source]
ApiFunctionA is UTF-8 capable. Needs a run-time switch too, not just compile-time.
replies(3): >>40170987 #>>40173012 #>>40174417 #
1. sebazzz ◴[] No.40174417[source]
Yes: 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.