Re: Skip filename recoding tests on MS-Windows

[Eli Zaretskii]

> Date: Tue, 25 Oct 2022 21:49:04 +0200
> From: pertusus@free.fr
> Cc: GavinSmith0123@gmail.com, bug-texinfo@gnu.org
> 
> > The only part that is I think different on Windows is the encoding of
> > file names, because Windows doesn't treat file names as opaque
> > bytestreams.  But anything that comes from a Texinfo source, even the
> > name of an included file, should be interpreted according to
> > @documentencoding.  When accessing included files on Windows, we
> > should re-encode the file names to the locale's encoding, because
> > nothing else will work reliably.  Is that what we do?
> 
> Yes, but it does not work reliably either, as shown by the tests
> results.  The test which uses the locale's encoding fails (formatting
> manual_include_accented_file_name_latin1), while the test in which the
> document encoding is used, (formatting
> manual_include_accented_file_name_latin1_explicit_encoding) does not
> fail.  As analysed just before, it works because both Windows and Perl
> are consistently wrong, but still it seems to work better.

Perhaps the logic of these tests fails on Windows?  Can you perhaps
describe the logic of each of these tests?  In general, I see no
reason why encoding file names using the locale's encoding should fail
on Windows if done correctly.  The idea of maintaining file names in
UTF-8 internally and encoding them to the locale's encoding before
using in file I/O calls is correct, and should work on Windows.