On Sun, Oct 23, 2022 at 05:38:37PM +0100, Gavin Smith wrote: > On Sun, Oct 23, 2022 at 05:25:26PM +0200, [email protected] wrote: > > Which is right. > > > > > and the first two fail if it says "OK". > > > > Which is problematic, it means that with a correctly setup input file > > with latin1 encoded character in the name, something wrong is going on. > > I do not think that these tests are going to work correctly on Eli's > system or on MS-Windows in general. Can we add a check for MS-Windows to > maintain/copy_change_file_name_encoding.pl and report a failure so that > these tests are skipped?
I do not think that copy_change_file_name_encoding.pl is the right place for that. This script just allows to setup a latin1 encoded file name, it should only fail and communicate so if it is not possible to setup a latin1 encoded file name. If the corresponding tests fail, it is for another reason, we can skip them on Windows, but I think that copy_change_file_name_encoding.pl should be left out of it. -- Pat
