Re: different encodings for input and output file names and command line

[Gavin Smith]

On Tue, Mar 01, 2022 at 01:42:50AM +0100, Patrice Dumas wrote:
> On Mon, Feb 28, 2022 at 10:29:02AM +0100, Patrice Dumas wrote:
> > Hello,
> > 
> > * input file name encoding:
> >    My preference would be the locale, but Gavin proposal to use
> >    @documentencoding also has merit, so let stick to @documentencoding
> >    except on Windows where the locale is used.
> > * output file encoding:
> >    Use the locale in the default case.
> > * command lines called from texi2any
> >    Always use the encoding already used for messages defaulting to the
> >    locale encoding
> 
> I commited an implementation.  The XS parser part is incomplete, I coded
> passing the informations, but not using the information, for instance in
> encode_file_name().  Also encode_file_name() should be used for CPP file
> directive, as I reported in another mail.

I've tried to do the line directive in the XS code in commit 03dc9e8efd.
It fixes the error message in the attached test file under a Latin-1
locale.

test3.texi
Description: TeXInfo document