5 ms·

Make UTF-8 default on Windows

by Affric 2y ago

johannes1234321 2y ago
Since Windows Version 1903 (May 2019 Update) they push for Utf-8. But Windows is a big pile of compatible legacy.
tedivm 2y ago
That's exactly what this proposal (which has been accepted) is going to do.
- lolinder 2y ago
  I think they mean that the Windows operating system should default to UTF-8.
pjc50 2y ago
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 ?
- cryptonector 2y ago
  ApiFunctionA is UTF-8 capable. Needs a run-time switch too, not just compile-time.
  - garaetjjte 2y ago
    It's now possible, but for years the excuse was that MBCS encodings only supported characters up to 2 bytes.
  - ComputerGuru 2y ago
    Only under windows 11, I believe. And that switch is off by default.
    - int_19h 2y ago
      You'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 2y ago
    Yes: 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.
layer8 2y ago
That would break so many applications and workflows that it will never happen.
deleted 2y ago
[deleted]
numpad0 2y ago
lots of apps can't even handle non-ASCII username on Windows
- Affric 2y ago
  I have seen the worst of it. Too many companies running franken-software from decades ago.

Make UTF-8 default on Windows

by Affric 2y ago

Make UTF-8 default on Windows

johannes1234321 2y ago

Since Windows Version 1903 (May 2019 Update) they push for Utf-8. But Windows is a big pile of compatible legacy.

tedivm 2y ago

That's exactly what this proposal (which has been accepted) is going to do.

lolinder 2y ago
I think they mean that the Windows operating system should default to UTF-8.

pjc50 2y ago

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 ?

cryptonector 2y ago
ApiFunctionA is UTF-8 capable. Needs a run-time switch too, not just compile-time.
- garaetjjte 2y ago
  It's now possible, but for years the excuse was that MBCS encodings only supported characters up to 2 bytes.
- ComputerGuru 2y ago
  Only under windows 11, I believe. And that switch is off by default.
  - int_19h 2y ago
    You'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 2y ago
  Yes: 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.

layer8 2y ago

That would break so many applications and workflows that it will never happen.

deleted 2y ago

[deleted]

numpad0 2y ago

lots of apps can't even handle non-ASCII username on Windows

Affric 2y ago
I have seen the worst of it. Too many companies running franken-software from decades ago.