On Thu, Nov 14, 2024 at 08:47:25AM +0200, Eli Zaretskii wrote: > > For the reference test results, this does not work, as these results > > are checked in a fixed location in srcdir. > > > > The easiest solution that comes to mind is to post-process the test > > results to escape file names. So instead of > > > > encoded/res_parser/non_ascii_command_line/intérnal.txt > > > > you would have something like > > > > encoded/res_parser/non_ascii_command_line/int\xc3\xa9rnal.txt > > > > All the distributed reference test results would have ASCII file names > > and the non-ASCII file names would only be used if the tests were actually > > run, which would be disabled on MS-Windows (again, as already happens > > for some tests, I believe). > > I'm not sure I follow: do you intend to use "int\xc3\xa9rnal.txt" as > an actual file name on disk? In that case, please note that a > backslash cannot be part of a file name on Windows: it's a directory > separator. If you want an escape character, it should be something > else, like # for example.
I had meant that - but I had forgotten that a backslash shouldn't be used in a file name on Windows.
