[texinfo.tex 2025-02-06.22]
> Yes, it was a bug. I've committed a fix in version 2025-02-06.22,
> and rethought how the space trimming works for macro arguments and
> hopefully made the implementation in texinfo.tex a bit simpler.
> Thanks for the report.
Thanks for the quick fix!
> > > 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.
>
> Well, at present the HTML and PDF output does different things with
> this option, for no good reason. The default is "on" for HTML and
> "off" for PDF, but that isn't even enough to explain it, as they do
> different things with xrefs to anchors.
>
> I've made the changes already for texinfo.tex (in version
> 2025-02-03.17).
Thanks again. Alas, this fails with `@xrefautomaticsectiontitle on`
and non-ASCII characters. Attached is an example that worked with
`texinfo.tex` version 2025-01-31.21, and which now yields
```
./ref.texinfo:19: Missing @endcsname inserted.
<to be read again>
@relax
@ensuredmath #1->$@relax
#1$
@u8:· ...lbyte @string �}@else @ensuremath @cdot
@fi
<argument> Col·
lisions of objects-snt
@getrefx ...after @let @expandafter #2@csname XR#1
@endcsname
@getprintedrefname ...@else @getrefx {#1-snt}@tmp
@ifx @tmp @Yanchor @def @p...
...
l.19 Foo @ref{Col·lisions of objects}.
```
Werner
\input texinfo
@documentlanguage ca
@xrefautomaticsectiontitle on
@node Top
@top Top
Top
@node Col·lisions of objects
@chapter Col·lisions of objects
Col·lisions of objects
@page
@node Foo
@chapter Foo
Foo @ref{Col·lisions of objects}.
@bye
