On Thu, Feb 06, 2025 at 08:06:19AM +0000, Werner LEMBERG wrote:
> Processing with `texi2pdf` gives a warning:
>
> ```
> pdfTeX warning (ext4): destination with the same identifier (name{Bogen}) has
> b
> een already used, duplicate ignored
> <to be read again>
> @penalty
> @safewhatsit ...um @whatsitpenalty >9999 @penalty
> @whatsitpenalty @fi @else
> ...
>
> @setref #1#2->@pdfmkdest {#1}
> @iflinks {@requireauxfile @atdummies @def
> @valu...
>
> @@anchor:impl #1->@savesf @setref {#1}{Yanchor}
> @restoresf @ignorespaces
> l.17 @anchor{Bögen}
> ```
>
> In the PDF, the reference to 'Bögen' is the same as with 'Bogen'.
>
Initial testing with the following patch appears to fix the problem:
diff --git a/doc/texinfo.tex b/doc/texinfo.tex
index 23c00827a0..a0830cf5dd 100644
--- a/doc/texinfo.tex
+++ b/doc/texinfo.tex
@@ -985,12 +985,16 @@ where each line of input produces a line of output.}
\luatextrue
\fi
+% Whether to use Unicode in internal link targets. Presently this
+% is always on.
+\newif\iftxiuseunicodedestname
+\txiuseunicodedestnametrue
+
%
% For LuaTeX
%
\newif\iftxiuseunicodedestname
-\txiuseunicodedestnamefalse % For pdfTeX etc.
\ifluatex
% Use Unicode destination names
However, more testing is needed. Presumably there was some reason
we didn't use this setting for pdftex at the time it was introduced.
Link to initial discussion:
https://lists.gnu.org/archive/html/bug-texinfo/2016-08/msg00002.html
There was also discussion about PDF files being potentially broken about
the same time:
https://lists.gnu.org/archive/html/help-texinfo/2016-06/msg00014.html
