Windows test package: print the shortcut target in UTF-8 (false error and unmasked user name in wintest-4) #39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "windows-wintest-utf8"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A fix to the Windows test package, found in the real-PC run wintest-4 (ogc-messungen issue #7).
packaging/windows/test/lnk-aumid.cprinted the shortcut's target withwprintf, so the target came out in the console's code page.run-tests.ps1reads programs' output as UTF-8, so a profile folder with an accented user name came out garbled ("C:\Users\Ren� …"). Two things followed:%USERPROFILE%did not match, so the tester's user name stood in the report.The helper now converts its two lines with
WideCharToMultiByte(CP_UTF8)and writes them withWriteFile.notification-state.calready writes UTF-8.Tests: in the container,
packaging/windows/test/wine-test.sh(which reads shortcuts with the helper) anddist.shwith the app bundle pass. Wine's own profile has no accented name, so the accented case itself is checked only by the next real-PC run.Everything else in wintest-4 worked on the real Windows 11 PC; see the issue.