3 ms·

Cries in WinAPI

• jsheard 2y ago
  They're getting there, starting from later builds of Windows 10 there's a manifest flag you can set on your executables which makes all of the legacy ASCII interfaces accept and return UTF-8 instead. Windows is probably just converting to and from UTF-16 internally but that's not your problem anymore.
  • im3w1l 2y ago
    Will it refuse to run on older versions of windows or silently do the wrong thing?
    • jsheard 2y ago
      I believe it silently does the wrong thing so you should probably enforce a minimum Windows version by some other means. The last version to not support that UTF-8 flag has been officially EOL for years so cutting it off completely is on the table, depending on your audience.
      • andreyv 2y ago
        Even the original version 1507 is still supported on the LTSC channel. Support for UTF-8 manifest was added only in version 1903.
  • Tempest1981 2y ago
    Maybe this? https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page https://learn.microsoft.com/en-us/windows/apps/design/global...
• pjmlp 2y ago
  Isn't that bad actually, (licks WinRT scars).