Re: Non-ASCII characters in @include search path

[pertusus]

On Sun, Feb 20, 2022 at 03:06:57PM +0200, Eli Zaretskii wrote:
> 
> The only thorough solution, IMO, is to assume the file names are
> encoded in the filesystem as specified by the locale's codeset.  That,
> too, can be false, but at least in the absolute majority of use cases
> it will be true.  The only better solution is to let the user specify
> the file-name encoding.

I do not think that it is a good solution either.  On Linux, unless I
missed something, the file name encoding should be utf-8 irrespective of
the locale, or the Texinfo document encoding.  Maybe on Windows the
locale and the file-name encoding match, then we should use that.

In any case, I do not think that letting the user specify the file-name
encoding would be any good, we should manage to get it right.

-- 
Pat