On Mon, Oct 12, 2026 at 06:40:58PM +0300, Eli Zaretskii wrote: > > Date: Mon, 12 Oct 2026 17:22:34 +0200 > > From: Patrice Dumas <[email protected]> > > Cc: [email protected] > > > > On Mon, Oct 12, 2026 at 06:02:20PM +0300, Eli Zaretskii wrote: > > > Something like having the node written as (assuming French > > > translation): > > > > > > Node: L'indice^?[Index]^? > > > > > > where ^? are the DEL characters (or some other special sequence). > > > > The issue with such possibilities is that they are not backward > > compatible, past Info reader cannot render correctly the node name. > > I don't understand: aren't we discussing this because we want to > support translated manuals? Such manuals currently are not supported > at all. > > Also, whoever generates the manual should make sure they use the > version of texi2any that is compatible with the Info readers expected > to be used by the users.
I do not necessarily disagree with you, your idea has merit, but we need to weight the pros and cons. An advantage of your idea is that it use about the same method for accelerating the search as it already used, and therefore is already mostly backward compatible. > > It could still be a better idea, especially for the middle term than a > > new tag in the tag table, as what you propose would not lead any Info > > reader to malfunction, there would only be a weird node name. A new tag > > could still be the best long-term solution, but it could only be used > > years away from 2025. > > > > Scanning the whole file, however, does not have any visible effect, save > > time passed and electricity consumption. > > Scanning a 5MB file each time the user types "i <something> RET" is > not fun. I'd prefer having "Index" untranslated any day. In the standalone Info reader, it is not each time, concatenated indices are cached until the file for which the index is searched changes. But I get your point. Notice that having Index untrlanslated will always be possible in my proposal anyway and be tried first, such that the search can be accelerated by putting untranslated "Index" in the node name. -- Pat
