Re: Non-ASCII characters in @include search path

[Eli Zaretskii]

> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Mon, 21 Feb 2022 21:42:14 +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:
> > > Do you know if TeX distributions for Windows do any handling of filename
> > > encodings?
> > 
> > I never used non-ASCII variant of TeX (XeTeX, I guess?) on Windows, so
> > I don't know, sorry.
> 
> It's standard TeX that processes bytes with values from 0 up to 255.  Bytes
> 128 to 255 are non-ASCII.  So this issue could arise even with the regular,
> 8-bit TeX.

If so, I think the Windows port of TeX/Web2c does nothing special for
non-ASCII characters, it just uses them as-is.  Which means the
non-ASCII characters of the current system locale are seamlessly
supported by using them in their encoded form (per the current system
codepage), but characters outside of that cannot be used.