On Wed, Nov 13, 2024 at 10:37:37PM +0200, Eli Zaretskii wrote:
> Can they be included as some kind or archive? Like shar file, for
> example? Then users on Posix systems could unpack that before running
> the test suite, and users of Windows won't.
>
> Or some other similar solution; removing the tests sounds too harsh to
> me.
I feel like this should be quite easy to achieve for the input
files, at least, as we already do something similar for an input
file with a Latin-1 name, which we place in a directory in the
build directory ("built_input"). This is the rule to build
"input_file_names_recoded_stamp.txt" in tp/tests/Makefile.am.
I've started work for something similar for files such as
tp/tests/encoded/osé_utf8.texi - this will take me some time to finish
properly.
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).
> If worse comes to worst, i.e. no reasonable solution presents itself,
> you can always leave things as they are: I eventually found the way to
> delete these files, so will know how to solve this next time it comes
> up.
