> Date: Sun, 23 Oct 2022 17:21:18 +0200 > From: [email protected] > Cc: [email protected], [email protected] > > > FAIL: test_scripts/formatting_non_ascii_command_line.sh > > FAIL: test_scripts/formatting_non_ascii_test_epub.sh > > FAIL: test_scripts/formatting_non_ascii_test_rawtext.sh > > FAIL: test_scripts/formatting_non_ascii_no_setfilename_test_rawtext.sh > > FAIL: test_scripts/formatting_non_ascii_test_latex.sh > > FAIL: input_dir_non_ascii.sh > > FAIL: output_dir_non_ascii.sh > > FAIL: output_dir_file_non_ascii.sh > > > > Sounds like all of these should be disabled if there's FAILED in that > > file? > > No, these do not need the latin1 encoded file. All those cases are > failed because there are encoded arguments on the command line, and it > is probably the sshell that mangles the names.
Not just the shell mangles them, but the invoked commands cannot cope with such encoded arguments, unless they are encoded in the system locale's codeset, i.e. the system codepage. So if they don't depend on that input file, and if the encoded arguments must be in UTF-8 or somesuch, those tests should be disabled on Windows.
