Re: info --apropos should decode/encode nodes/index entries

[Patrice Dumas]

On Sat, Aug 20, 2022 at 12:16:49PM +0100, Gavin Smith wrote:
> On Sat, Aug 20, 2022 at 09:39:26AM +0200, Patrice Dumas wrote:
> 
> I don't want to go to the same efforts that we went through for
> texi2any to get character encoding done right in info, as this could
> be too complicated and take too long to do.

We do not need to handle non ascii filenames in info (and we could
document it in the manual, by the way), but getting the right output
for encoded content seems important to me.

> It's probably not a perfect fix as now we are running iconv twice over
> each label, once for internal storage, once for display.  I'm going to check
> that in the common case, when everything is in UTF-8, iconv isn't called
> at all.

As long as iconv isn't called at all with UTF-8, it seems rather fine to
me for iconv to be called twice in other cases, to me it is rather sane.
I think that it is what happens in texi2any too.

I think that we should support non UTF-8 locales such that things work
for those, but I do not think that we should optimize for those cases,
in the long term all the locales and Texinfo manuals should be UTF-8.

-- 
Pat