[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: different encodings for input and output file names and command line
From: |
Patrice Dumas |
Subject: |
Re: different encodings for input and output file names and command line |
Date: |
Sun, 6 Mar 2022 15:44:53 +0100 |
On Fri, Mar 04, 2022 at 06:36:09PM +0000, Gavin Smith wrote:
> End:
> $ # so far so good
> $ ../texi2any.pl é.texi -c DOC_ENCODING_FOR_INPUT_FILE_NAME=0 -c
> LOCALE_INPUT_FILE_NAME_ENCODING=ISO-8859-1
> é.texi:7: @include: could not find aß.texi
> $ ../texi2any.pl é.texi -c DOC_ENCODING_FOR_INPUT_FILE_NAME=0
>
> é.texi:7: @include: could not find aß.texi
> $ TEXINFO_XS=omit ../texi2any.pl é.texi -c DOC_ENCODING_FOR_INPUT_FILE_NAME=0
> é.texi:7: @include: could not find aß.texi
> $ TEXINFO_XS=omit ../texi2any.pl é.texi -c DOC_ENCODING_FOR_INPUT_FILE_NAME=0
> -c LOCALE_INPUT_FILE_NAME_ENCODING=ISO-8859-1
> é.texi:7: @include: could not find aß.texi
>
>
> --------------
>
> On making the following change, it appears that
> LOCALE_INPUT_FILE_NAME_ENCODING
> is undefined:
This was the issue, it was not set in texi2any.pl because it was not
registered as Parser configuration. It should be solved by commit
5fca718c9fe71d15e9287df5dec9c05a9b8b6d0b for both parsers.
I will add a test.
--
Pat
- Re: different encodings for input and output file names and command line, (continued)