Consider the following MWE (thanks to this nice article from Maïeul Rouquette (in French)) that makes possible to have both:

  • indices built with (tex)xindy,
  • hyperlinked page numbers and "see",

(named, say, test.tex):

(markup-keyword-list :open "\targetindexentry{" :close "}" )
(markup-crossref-list :class "see" :open "\seelink{" :sep "; " :close "}{}")

(define-crossref-class "hyperindexformat")
(markup-crossref-list :class "hyperindexformat" :open
      "\hyperindexformat{" :sep "; " :close "}{}")

(markup-locref :open "\hyperpage{" :close "}")
(markup-locref :open "\hyperpage{" :close "}" :attr "hyperpage")

\makeindex[options=-M \jobname.xdy]

If it is compiled with:

  1. pdflatex test (or lualatex test or xelatex test),
  2. texindy -M test.xdy test.idx
  3. pdflatex test (or lualatex test or xelatex test),

we notice 3 different behaviors:

  • with pdflatex, there is a warning (which is not really informative but seems to be serious):

    pdfTeX warning (ext4): destination with the same identifier (name{index:bar}) has been already used, duplicate ignored \AtBegShi@Output ...ipout \box \AtBeginShipoutBox \fi \fi l.39 \end{document}

  • with lualatex, there is a warning:

    warning (pdf backend): ignoring duplicate destination with the name 'index:bar '

  • with xelatex, everything's okay.

I guess the warning with pdflatex comes from the LICR in the .ind file:


  \item \targetindexentry{bar}, \hyperpage{1}


  \item \targetindexentry{caf\IeC {\'e}}
    \subitem \targetindexentry{bar}, \hyperpage{1}


Here is my question(s):

How to get rid of the warning in pdflatex (and also in lualatex) case? (And how do you explain the differences between xelatex and lualatex while the .ind file is the same in both cases?)

  • 1
    The warning is correct: There are two link targets with the same name index:bar under letter B and C. Therefore, the item for the subitems should be included in the target name, because the subitem name is not unique. – Heiko Oberdiek Oct 8 '16 at 19:01
  • @HeikoOberdiek Okay, I'll try to figure out how to include the item as well. Can we consider as a bug the fact xelatex doesn't tell anything about this? – Denis Bitouzé Oct 8 '16 at 21:36
  • Call it bug, missing feature or whatever. As long as nobody invests time to implement the warning in XeTeX, nothing will change. – Heiko Oberdiek Oct 8 '16 at 22:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.