On Sat, Aug 20, 2022 at 10:51:07AM +0300, Eli Zaretskii wrote: > > Date: Sat, 20 Aug 2022 09:39:26 +0200 > > From: Patrice Dumas <[email protected]> > > Cc: [email protected] > > > > 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. > > Ideally, ??? should only appear if the character cannot be encoded in > the locale's codeset. Otherwise, the reader should encode in the > locale's codeset before writing. So, for example, Latin-1 characters > in a UTF-8 encoded document should appear as themselves if the > locale's encoding is Latin-1.
It is the case, the ??? appear for characters that are not in latin1, characters in the UTF-8 encoded Info file that are in latin1 are encoded as themselves in latin1. > > There is a specific issue with --apropos, I guess. > > Why is it special? I don't know. I tried to read the code a bit to see if I could understand where it was different from regular Info reading but I abandonned rapidly. Hence the report here, as a bug. -- Pat
