On Sat, Aug 20, 2022 at 09:06:39AM +0300, Eli Zaretskii wrote: > > The command line should be decoded using the locale's codeset, not > UTF-8. Because that's how the shell works: it uses the current > locale's codeset.
Indeed, you are right, here UTF-8 was the encoding of my locale. > As for decoding the document, given that we have the @documentencoding > directive, which could specify any encoding whatsoever, the Info > reader should use the encoding specified for the document. This is > already fixed for the Emacs reader, which uses the 'coding:' cookie at > the end of the Info file, so the simplest thing for the stand-alone > reader is to use the same. The stand-alone reader already does that for regular Info browsing. I tested both in a 8bit encoded locale and in an UTF-8 locale, reading Info files in iso-8859-1 and utf-8 encodings, and it works well, including searching. In the 8bit locale, the UTF-8 characters appear as ??? but that's the best possible output. There is a specific issue with --apropos, I guess. > When outputting to the terminal, the reader should indeed use the > locale's encoding. The standalone Info reader always output to the terminal... -- Pat
