Re: Non-ASCII characters in @include search path

[Patrice Dumas]

On Sat, Feb 26, 2022 at 10:23:04PM +0000, Gavin Smith wrote:
> 
> Just as you recommended.  In texi2any.pl, decode all customization
> variables as you suggested before.  I guess the locale encoding would
> be used for this.
> 
> When encoding file names, use the @documentencoding if they came
> from the document.  I'm not sure about encoding strings from the
> command-line but the @documentencoding is probably okay for this too
> (I'm not sure if it would always be possible to tell where the strings
> came from.)

Currently the locale is used.  I think it is ok, because it is a good
guess, and also because we know the @documentencoding only much later.
If the user is not happy with the locale encoding he can also set the
customization variable directly.

> Don't use the locale encoding by default for encoding filenames.

Ok.

> I'm happy to work on this.  I won't have time until tomorrow afternoon
> (GMT) at the earliest, but it may be several days later.  I'm happy if
> you want to try implementing this before I do.

Ok, I'll probably have time tomorrow to do part of it.

-- 
Pat