> The problem with changing the output for a cross-reference to
> anchors is that some manuals may be depending on the existing
> output, with the anchor names used in HTML output. So I think we
> should change the output in DVI/PDF instead to match the current
> HTML output, and use the anchor names in the output text.
Yes, exactly.
> This would mean that the xrefautomaticsectiontitle setting would not
> have an effect on cross-references to anchors.
This would be fine with me. However, it would be
backward-incompatible, thus my suggestion of a new option.
>> I suggest to add an option that controls whether `@anchor` honors
>> `@xrefautomaticsectiontitle on`.
>
> Actually, it already honoured it for PDF output, but in the opposite way
> to which you wanted: if xrefautomaticsectiontitle was off, then the
> anchor name would be used in the output cross-reference.
Yes, I know that, and I like a lot that `@xrefautomaticsectiontitle`
exists, since many such references in Lilypond's documentation need a
typewriter font.
> If this causes a problem, we could consider introducing another
> setting like @xrefautomaticsectiontitle that affects
> cross-references to anchors only. For such an setting, it might be
> ok to use the contents of @*heading commands for the reference text
> as you suggest, although there isn't an immediate need for this if
> we make the change above.
Yep.
>> In the PDF, if I hover with the mouse above an `@xref` to that
>> anchor, I see 'Articulations and ornamentations', but I want to see
>> 'Controlling the vertical ordering of scripts', because this is the
>> heading next to the `@anchor`.
>
> That depends on the PDF viewing program being used. [...]
It is a minor point, yes.
>> [BTW, we would really, really benefit if Texinfo introduced
>> equivalents to LaTeX's `\part`! Right now, we define
>> `@subsubsubheading` by simply calling `@subsubheading`.]
>
> Can you explain how this differs from @part?
Ooh, I completely missed that Texinfo 5.0 introduced `@part`! I've
just noticed an old remark in the LilyPond documentation, complaining
that such a command is missing... Sorry for the noise.
Werner
