On Sat, Jun 28, 2025 at 08:53:21PM +0100, Gavin Smith wrote: > On Sat, Jun 28, 2025 at 10:23:59PM +0300, Eli Zaretskii wrote: > > > From: Gavin Smith <gavinsmith0...@gmail.com> > > > Date: Sat, 28 Jun 2025 19:54:36 +0100 > > > > > > I also don't think it is a huge restriction to have "Index" in the > > > node name. Non-English Info manuals could have English node names, or > > > they could have the word "Index" in addition to the translation. > > > > Info files that don't support the index markers have no other way of > > signaling that a node is an index node. > > Yes, I believe I said this in another message. I'll try again to explain > how I think Info should find Info nodes: > > 1. Go through all the nodes with "Index" in the name. > 2. For each of them, check if it contains the index marker. > 3. If any contain an index marker, the index nodes are those with "Index" > in the name and with an index marker. > 4. If none contain an index marker, the index nodes are all those with > "Index" in the name.
I will implement that. A variant could be, instead of only going through the nodes with "Index" in the name, to go through all the nodes after the first node with "Index" in the name. > Optionally, we could check all the nodes, like this: > > 1. Go through all the nodes. > 2. For each of them, check if it contains the index marker. > 3. If any contain an index marker, the index nodes are those with > an index marker. > 4. If none contain an index marker, the index nodes are all those with > "Index" in the name. > > However, this second method is potentially more time consuming. What about adding a 'Local Variables' with the name of the first node with indices with makeinfo and using that instead of "Index" in nodes names to determine the first node with indices as I proposed? -- Pat
