On Wed, Feb 12, 2025 at 10:12:15PM +0100, [email protected] wrote:
> I do not like the automatic association of an inline command like
> @anchor, that may happen anywhere, to another command. I think that it
> would be cleaner to have an @-command with two arguments, instead, like
>
> @anchorlabel Bows, Bögen
Could also be inline, like @namedanchor{Bows @comma{} and something else,
Bögen, und etwas anderes}.
> Note that having separate anchor and label most likely requires changing
> diverse things, because the anchor part always need to be 'hidden'. For
> instance cross references should be like @ref{Bows, Bögen, Bögen,
> manual}, which complexifies somewhat cross-references writing.
In Info, for instance, the anchor part would always be visible. This is
probably not an issue for a manual such as the Lilypond manual, that
is probably not often read in Info. Maybe documenting that it is better
to avoid if Info format is used is enough, though.
--
Pat
