Re: Non-ASCII characters in @include search path

[Gavin Smith]

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.