Re: Non-ASCII characters in @include search path

[Patrice Dumas]

On Sun, Feb 20, 2022 at 06:39:47PM +0000, Gavin Smith wrote:
> On Sun, Feb 20, 2022 at 07:00:23PM +0100, Patrice Dumas wrote:
> > I don't get it.  If everything is decoded to internal perl encoding and
> > then the file name is encoded to the local, here Latin-1, everything
> > will be ok, as long as the characters in manuals can be output in
> > Latin-1.
> 
> The point is that the file name won't be recoded unless the user goes
> to the extra effort of recoding it.  Suppose you are extracting a .tar.gz
> file; tar doesn't look at the current locale settings and convert the
> filenames so that they are valid in the current locale.

Ok, but the user would have to recode the file name to do anything with
it anyway.  Seems like convmv is the command that allows to do that,
even if tar, understandably, does not.  Otherwise the user cannot even
call makeinfo on the file.  It seems to me that considering that the
user converts filenames to the locale he uses seems to me to be the more
reasonable guess.

-- 
Pat