Re: Non-ASCII characters in @include search path

[Eli Zaretskii]

> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Sun, 20 Feb 2022 15:38:17 +0000
> Cc: pertusus@free.fr, trash.paradise@protonmail.com, bug-texinfo@gnu.org
> 
> On Sun, Feb 20, 2022 at 05:07:32PM +0200, Eli Zaretskii wrote:
> > > The locale codeset could very easily be incorrect.  Suppose somebody sets
> > > a Latin-1 locale, should they then be unable to build Texinfo manuals
> > > with non-ASCII UTF-8 filenames?
> > 
> > They will see garbled file names.
> > 
> > You can try this yourself.  E.g., Emacs lets you control the file-name
> > encoding, so you could create a file with Latin-1 encoded name on a
> > system whose locale's codeset is UTF-8.  Then ask 'ls' or some GUI
> > file manager to display the file's name.
> 
> The file names will be garbled but they should still be able to process
> the files with texi2any.

If they indeed have such files whose names are in UTF-8.

And the downside of what you propose is that the frequent and "usual"
setup, whereby file names are encoded according to the locale, will be
punished because we want to support the infrequent and "unusual" ones.