> From: Gavin Smith <[email protected]> > Date: Sat, 24 Oct 2026 19:13:40 +0100 > Cc: Eli Zaretskii <[email protected]>, [email protected] > > So it appears that . not followed by a space does need to be quoted in > a *note cross-reference.
A cross-reference at the end of a sentence will not necessarily have a space after it, it could have a newline. And in any case, "does not need" just means that a sufficiently sophisticated algorithm could discern between them. It doesn't mean it's easy, let alone simple. > 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".) An Index is not a "normal" menu, as you explained previously. Menus in index nodes have their own special formatting rules. > Note that such menu entries are most likely to occur in indices, as it is > fairly rare for entries elswhere in menus to have a separate label and node. Exactly my point: we seem to support this for cases that seldom if ever happen. > For example, here is the entry for this node in its parent node's menu: > > * Obsolete config.status Use:: Obsolete convention for ‘config.status’ > > The . in "config.status" occurs before a colon on the line so there is no > question of it terminating anything. The problem I raised was with a menu entry that does have a label, like this: * Foo bar: node.with.periods. Your example is different.
