fopen() fails with paths that have non-ASCII characters #29

Closed
opened 2022-11-09 22:00:15 +01:00 by williamjcm · 1 comment
Owner

Windows being Windows.

Easiest fix is to switch from MSVCRT to UCRT and force the codepage for the app to be UTF-8.

According to the MS docs, just linking to a recent enough UCRT (Win SDK 1803 and up) and using setlocale(LC_ALL, ".UTF-8") is enough to get UTF-8 support, and that shipping the DLLs with the app would make it work on Win7/8/8.1.

But at the same time, Windows 7 and 8 are out of support, with 8.1 following on 2023-01-10, so I may as well just drop support for those at the same time.

Windows being Windows. Easiest fix is to switch from MSVCRT to UCRT and force the codepage for the app to be UTF-8. According to the MS docs, just linking to a recent enough UCRT (Win SDK 1803 and up) and using `setlocale(LC_ALL, ".UTF-8")` is enough to get UTF-8 support, and that shipping the DLLs with the app would make it work on Win7/8/8.1. But at the same time, Windows 7 and 8 are out of support, with 8.1 following on 2023-01-10, so I may as well just drop support for those at the same time.
williamjcm added this to the v1.4.0 milestone 2022-11-09 22:00:15 +01:00
williamjcm added the
bug
label 2022-11-09 22:00:15 +01:00
williamjcm self-assigned this 2022-11-09 22:00:15 +01:00
williamjcm removed reference the-road-to-1point4 2022-11-21 08:36:32 +01:00
Author
Owner

Should be closable now that I switched to UCRT.

***Should*** be closable now that I switched to UCRT.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: williamjcm/MassBuilderSaveTool#29
No description provided.