Re: Non-ASCII characters in @include search path

[Patrice Dumas]

On Sun, Feb 20, 2022 at 02:48:39PM +0000, Gavin Smith wrote:
> On Sun, Feb 20, 2022 at 03:35:57PM +0200, Eli Zaretskii wrote:
> > 
> > If you want the Texinfo sources to be in UTF-8 internally, it might be
> > impossible not to decode the command-line arguments into UTF-8.  Only
> > if the command-line argument is used to access file names, and doesn't
> > seep into the rest of the output, you can use the original byte
> > sequence.  And even then it might be problematic: e.g., what if the
> > argument of -I is in some non-UTF-8 encoding, and the source uses
> > @include with a non-ASCII file name encoded according top
> > @documentencoding, which is UTF-8?  You need to construct a complete
> > file name from 2 parts that are encoded differently.
> 
> The byte sequences are just concatenated and used as the path to the file,
> even if it's not validly encoded.  This shouldn't cause a problem.

It will cause a problem if the include file name itself is not ASCII.
To avoid any problem and mismatch, decoding at input, doing everything
in the code with internal perl unicode and encoding on output seems to
me the best.

> The arguments to -I shouldn't get into the output file.

-- 
Pat