Re: Non-ASCII characters in @include search path

[Eli Zaretskii]

> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Sun, 20 Feb 2022 14:53:46 +0000
> 
> On Sun, Feb 20, 2022 at 02:42:04PM +0100, Patrice Dumas wrote:
> > On Sun, Feb 20, 2022 at 12:45:59PM +0000, Gavin Smith wrote:
> > > 
> > > I made a similar change in commit e11835b62d.
> > 
> > I propose another plan:
> > * decode arguments on the command line arguments based on the
> >   locale
> > * if on windows use the locale to determine the encoding
> >   for the file names, otherwise use utf-8.  Encode file names
> >   as late as possible, just before calling -e, stat, open...
> > 
> > The first point is important in general, I think, not only for
> > file names, but also for customization variables strings in case
> > one use accented characters in those.
> 
> Decoding command-line arguments might be a good idea for everything
> EXCEPT file names.  Why go to the bother of decoding file names when
> they have to be encoded again to use them?

Because you may need to encode them into a different encoding than it
was before you decoded them.