On Sat, Feb 15, 2025 at 09:51:41PM +0000, Werner LEMBERG wrote:
> >> Yes, exactly – in HTML split mode, `@anchorlabel` (or `@label`,
> >> which I won't stop advertising :-) plus `@XXXheading` should be on
> >> the same page as the last `@node` command.
> >
> > @label could be ok for the command, but it could be confusing as
> > there is a \label command in LaTeX [...]
>
> Ah, ok. Then `@label` should be indeed avoided. I would still like
> to have a snappy command name, maybe `@mark` or `@tag`?
Well, in some of the earlier proposals we were using the word "label" to
refer to what would be printed for a cross-reference, rather than the
node name, anchor name or equivalent. However in other proposals it
was used for the anchor name.
Here's a comparison of possible usages:
1. "Label" as the printed reference name:
@heading Bögen
@anchorlabel{Bögen}
@anchor{Bows}
The thinking here is that the anchor name is "Bows", and when you
write "@xref{Bows}", you get "See Bögen", pursuant to the @anchorlabel
argument.
2. "Label" as the anchor name:
@label Bows
@heading Bögen
Here there would be an anchor created called "Bows". @xref{Bows}
would produce "See Bögen", pursuant to the @heading.
It's case 1 that clashes with the LaTeX use.
