On Sat, Oct 24, 2026 at 07:21:58PM +0100, Gavin Smith wrote: > Date: Sat, 24 Oct 2026 19:13:42 +0100 > From: Gavin Smith <[email protected]> > To: [email protected] > Cc: Eli Zaretskii <[email protected]>, [email protected] > Subject: Re: bug#57277: 29.0.50; Support quoted node names in Info > > On Sat, Oct 24, 2026 at 06:36:22PM +0200, [email protected] wrote: > > Also, a dot after @ref is ignored with a node argument only, with or > > without space after: > > > > CC @ref{aa}.b > > > > DD @ref{aa}. f > > > > leads to > > > > CC *note aa::.b > > > > DD *note aa::. f > > That looks correct. Is there a problem with this?
No, no problem. It shows that :: is added even if there is a . > So it appears that . not followed by a space does need to be quoted in > a *note cross-reference. Indeed, and it is what is already done. What Eli would like is to have a . not followed by a space be also quoted in a menu entry name even if it is not required there. > I tested that with Info, an index entry like the following goes to the > correct node: > > * CONFIG_COMMANDS: Obsolete config.status Use. > (line 10) > > (From "(autoconf)Concept Index".) > > If "." ended the node name, it would try to go to a node "Obsolete config" > rather than "Obsolete config.status Use". In practice, in the output of > @printindex the terminating "." is always followed by space or newline, so > there was no reason not to make index entries such as these work as intended. > > So the inconsistency between menu entries and *note references as to whether > "." terminates a cross-reference without following whitespace appears to me > to be justified in terms of supporting Info files. (I cannot remember any > details of previous discussions on this, although there probably have been > some.) In fact, I now understand that what Eli would like to change is not this difference between menu and cross-reference, it is the difference regarding quoting (which is a consequence of the aforementioned difference). -- Pat
