Re: Skip filename recoding tests on MS-Windows

[pertusus]

On Mon, Oct 24, 2022 at 10:35:04PM +0300, Eli Zaretskii wrote:
> > Date: Mon, 24 Oct 2022 21:27:03 +0200
> > From: pertusus@free.fr
> > Cc: GavinSmith0123@gmail.com, bug-texinfo@gnu.org
> > 
> > > > input_file_name_encoding should be the string "ISO-8859-1", I checked
> > > > that it is the case for me.
> > > 
> > > Where is it set?  I mean, where is the original setting from which it
> > > is taken the first time?  Is it some file?
> > 
> > It is on the command line, see  -c INPUT_FILE_NAME_ENCODING=ISO-8859-1:
> > perl -w ./..//texi2any.pl -c TEXI2HTML --force --conf-dir ./../t/init/ 
> > --conf-dir ./../init --conf-dir ./../ext -I ./formatting/ -I formatting// 
> > -I ./ -I .  --error-limit=1000 -c TEST=1  --output 
> > formatting//out_parser/manual_include_accented_file_name_latin1_explicit_encoding/
> >  --info -c INPUT_FILE_NAME_ENCODING=ISO-8859-1 -D 'needrecodedfilenames 
> > Need recoded file names' 
> > ./formatting//manual_include_accented_file_name_latin1.texi
> 
> Ouch!  Sorry, it looks like I was somehow running the wrong command
> line all the time.  When I run the above, the encoding does work, and
> the included file is found and read.  The output of the command is:
> 
>   included_latεn1.texi:4: unknown command `unknowncmd'
> 
> where the ε part is the 0xEE byte interpreted by the Windows console.
> 
> Where does this leave us?

The test should pass then.  Can you check
diff -u 
formatting//out_parser/manual_include_accented_file_name_latin1_explicit_encoding/
 
formatting/res_parser/manual_include_accented_file_name_latin1_explicit_encoding/

-- 
Pat