latex3 / hyperref

Hypertext support for LaTeX

The expl3 (LaTeX3) Development Repository

Overview

The repository contains development material for expl3. This includes not only code to be developed into the expl3 kernel, but also a variety of test, documentation and more experimental material. All of this code works on top of LaTeX2e.

The following directories are present in the repository:

• l3kernel: code forms the expl3 kernel and all stable code. With a modern LaTeX2e kernel, this code is loaded during format creation; when using an older LaTeX2e kernel, this material is accessible using the expl3 package.
• l3backend: code for backend (driver) level interfaces across the expl3 codebase; none of this code has public interfaces, and so no distinction is made between stable and experimental code.
• l3packages: code which is written to be used on top of LaTeX2e to explore interfaces; this bundle is now made up of historical material, and the concepts have been migrated to the LaTeX2e kernel
• l3experimental: code which is written to be used on top of LaTeX2e to experiment with code and interface concepts. The interfaces for these packages are still under active discussion. Parts of this code may eventually be migrated to l3kernel.
• l3trial: material which is under very active development, for potential addition to l3kernel or l3experimental. Material in this directory may include potential replacements for existing modules, where large-scale changes are under-way. This code is not released to CTAN.
• l3leftovers: code which has been developed in the past by The LaTeX Project but is not suitable for use in its current form. Parts of this code may be used as the basis for new developments in l3kernel or l3experimental over time.

Support material for development is found in:

• support, which contains files for the automated test suite which are 'local' to the repository.

Documentation is found in:

• articles: discussion of concepts by team members for publication in TUGBoat or elsewhere.

The repository also contains the directory xpackages. This contain code which is being moved (broadly) l3experimental. Over time, xpackages is expected to be removed from the repository.

Issues

The issue tracker for expl3 is currently located on GitHub.

Build status

We use GitHub Actions as a hosted continuous integration service. For each commit, the build status is tested using the current release of TeX Live.

Current build status:

Development team

This code is developed by The LaTeX Project.

Copyright

This README file is copyright 2021-2024 The LaTeX Project.

hyperref's Issues

Checkboxes do not appear in some PDF viewers

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?153, author Mike )

Checkboxes in the PDF form that I'm creating do not show up in Preview.app or Adobe Reader on OS X 10.7. My cursor changes if I mouse over where the box should be, and if I click on it I can even see the briefest flicker of the box and checkmark. Both promptly disappear.

In Adobe Reader on Windows, the checkboxes are initially invisible, but show up the first time I click on them. In FoxIt Reader they work exactly as expected.

I have attached examples of my TeX source, the PDF output, and a screenshot of what the PDF looks like when I open it.

There is a discussion of this issue on StackExchange: http://tex.stackexchange.com/questions/32810/checkboxes-in-pdf-forms-dont-show-up-in-os-x

-- comment 1:

I confirm this problem in evince 3.4.0 for linux (ubuntu 12.04). \CheckBox creates working checkboxes in acroread (print only, no save), PDF-XChange Viewer, and okular but NOT in evince. (The mouse changes on hover but no check appears on click. The document registers an edit because evince displays the save options on closing.)

I also filed this as an evince bug, but evince does handle PDF checkboxes created with other form editors (such as OpenOffice).

Best,
Michael

test.pdf
test.tex.txt

\href in \contentsline

Dear all,

down here at Debian we got complains that doxygen generated documents cannot be compiled with hyperref (anymore? - I don't know whether it worked before), see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835162

I have reduced this to the following MWE:

\documentclass{article}
\usepackage{hyperref}
\begin{document}

\contentsline{section}{note: \href{http://a.b.c/d#EEE}{link} }{}{}

\end{document}

which gives an error when compiled with pdflatex, coming from nameref.sty is my guess.

I am not even sure whether it makes sense to have links in TOC entries, because the TOC entries by themselves are links within the document, but who knows ...

If you have any comments, please let me know.

Thanks

Norbert

include source for paper.pdf and slides.pdf

the hyperref distribution includes two (old) files paper.pdf and slides.pdf. For no good reason, the sources for those PDFs are in the hyperref-docsrc package in TL (and, afaik, nowhere else public):
texmf-dist/doc/latex/hyperref-docsrc/paperslides99.zip

It is just that single zip file (and a README). Could you import it into the main hyperref distribution here, please, and eliminate this special case? Thanks ...

tex capacity exceeded ... input levels for 1000+ citations

I am working on a book which currently contains 1000+ citations.

When backref=page is enabled I get the dreaded "tex capacity exceeded" error (increasing the file limit has no effect). Everything works fine if this option is commented out.

Everything works ok for a subset of thebook that only contains 600 citations:
http://shape-of-code.coding-guidelines.com/2017/01/29/empirical-software-engineering-using-r-first-draft-available-for-download/

Does hyperref has an internal limit (perhaps an implicit assumption) on the number of citations? Any suggestions for increasing the number of supported citations?

unicode option produces irregular output

I came across a situation using the unicode package option that I believe is a bug.

When loading either unicode or unicode=true as a package option via \usepackage, many of the Doc Info fields are output as strings of hex. The string of hex is surrounded by < and > (not parentheses, as expected). For example:

<</Creator<feff006d0069006b007400650078002c002000780065006c0061007400650078002c0020006d0061006b00650069006e006400650078002c0020006d0061006b00650067006c006f0073007300610072006900650073002c0020006200690062006c006100740065007800200028006200690062006500720029>/Producer(XeTeX 0.99996)/CreationDate(D:20170405214902+10'00')>>

This seems to apply to most text fields, such as pdftitle, pdfsubject,pdfkeywords, and pdfcreator. It applies whether these fields are loaded as package options also, or via \hypersetup.

If unicode is set also in \hypersetup, this behavior still occurs.

However, if you remove unicode from the package options and only use it in \hypersetup, then the text appears normally. For example:

<</Creator(unicode bug test)/Producer(XeTeX 0.99996)/CreationDate(D:20170405215804+10'00')>>

MWE:

\documentclass{article}

\usepackage[xetex]{hyperref}%works as expected
\usepackage[xetex,unicode]{hyperref}%causes issue described above

\hypersetup{%
    unicode,%works alone, but with unicode loaded above, it is ignored
    pdfcreator={unicode bug test},%
}%

\begin{document}
Test
\end{document}

No support for \and in \author (pdfusetitle)

What I attempted

\documentclass{article}

\usepackage[pdfusetitle]{hyperref}

\author{John Doe\and Jane Doe}
\title{A Paper}

\begin{document}
  \maketitle
\end{document}

What I expected to happen

As \and is the standard way to separate multiple authors, I expected to see PDF metadata which separates the authors in a format commonly assigned the semantics of a list by software. (There seems to be no standard about this, AFAIK, exiftool only parses /Author(John Doe, Jane Doe) while Adobe produces /Author(John Doe; Jane Doe) but will recognize the former)

What happened

The metadata produced was an unseparated string:

/Author(John DoeJaneDoe)

Problem with labels when hyperref is turn on

I have not investigated much, but just try the following example :

• First compile without \usepackage {hyperref}
• Then compile with \usepackage {hyperref}

An error occurs in the second compilation: "Paragraph ended before \Hy@setref@link was complete"

\documentclass [a4paper]{article}
\usepackage [T1]{fontenc}
\usepackage [utf8]{inputenc}
%\usepackage [verbose]{hyperref}

% --------------------------------------------
\begin{document}

\section {One\label {One}}
\vskip5cm

Reference to \ref{One}.

\end{document}
% ---------------------------------------------

hyperref causes a vertical shift of print space after dvips

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?166, author Ulf Rehmann )

Hi,

The attached (essentially minimal) tex file can demonstrate a bug in hyperref or in the driver dvips.

While the dvi file produced by latex looks correct, the ps file derived from that dvi file by 'dvips -t a4 ...' (or similar) shows a vertical downshift of the print space (Satzspiegel). The same holds for the pdf file, derived from the latter by ps2pdf, say.

This vertical shift does not appear when the line '\usepackage{hyperref}' is commented out.

File list produced by \listfiles see below.

Thanks for any help.

Best regards,
Ulf Rehmann

File List
article.cls 2007/10/19 v1.4h Standard LaTeX document class
size10.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
hyperref.sty 2009/10/09 v6.79a Hypertext links for LaTeX
keyval.sty 1999/03/16 v1.13 key=value parser (DPC)
ifpdf.sty 2009/04/10 v2.0 Provides the ifpdf switch (HO)
ifvtex.sty 2008/11/04 v1.4 Switches for detecting VTeX and its modes (HO)
ifxetex.sty 2009/01/23 v0.5 Provides ifxetex conditional
hycolor.sty 2009/10/02 v1.5 Code for color options of hyperref/bookmark (HO
)
xcolor-patch.sty 2009/10/02 xcolor patch
pd1enc.def 2009/10/09 v6.79a Hyperref: PDFDocEncoding definition (HO)
etexcmds.sty 2007/12/12 v1.2 Prefix for e-TeX command names (HO)
infwarerr.sty 2007/09/09 v1.2 Providing info/warning/message (HO)
hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive
kvoptions.sty 2009/08/13 v3.4 Keyval support for LaTeX options (HO)
kvsetkeys.sty 2009/07/30 v1.5 Key value parser with default handler support
(HO)
url.sty 2006/04/12 ver 3.3 Verb mode for urls, etc.
bitset.sty 2007/09/28 v1.0 Data type bit set (HO)
intcalc.sty 2007/09/27 v1.1 Expandable integer calculations (HO)
bigintcalc.sty 2007/11/11 v1.1 Expandable big integer calculations (HO)
pdftexcmds.sty 2009/09/23 v0.6 LuaTeX support for pdfTeX utility functions (
HO)
ifluatex.sty 2009/04/17 v1.2 Provides the ifluatex switch (HO)
ltxcmds.sty 2009/08/05 v1.0 Some LaTeX kernel commands for general use (HO)

atbegshi.sty 2008/07/31 v1.9 At begin shipout hook (HO)
hdvips.def 2009/10/09 v6.79a Hyperref driver for dvips
pdfmark.def 2009/10/09 v6.79a Hyperref definitions for pdfmark specials
nameref.sty 2007/05/29 v2.31 Cross-referencing by name of section
refcount.sty 2008/08/11 v3.1 Data extraction from references (HO)
test.out
test.out

---

(no files were attached; i'm following up with the author --karl)

UTF8 in TextField's value

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?204, author Thorsten )

Hi. I have the following packages:

\usepackage[ngerman]{babel}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}

When I create a textfield with

\TextField[name=test, value=Groß]{test}

the value shows as "GroT1ss"

How can I fix this?

error when combining hyperref, amsart and itemize within theorem

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?193, author Kristian Debrabant )

I recently discovered the following strange behaviour when hyperref is combined with an ams class:

The following code:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\documentclass{amsart}
\usepackage{hyperref}
\newtheorem{example}{Example}
\begin{document}
\ \newpage
\begin{example}\label{ex}
\begin{itemize}
\item
\end{itemize}
\end{example}
\ref{ex}
\end{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

(all packages in the last version of CTAN) results in a pdfTeX warning “(dest): name{example.1} has been referenced but does not exist, replaced by a fixed one”. And indeed, the hyperlink created by \cref{ex} does not point to the actual example, but to the first (empty) page.

The strange thing is that one can cure this by inserting a “\noindent” before the itemize, so

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\documentclass{amsart}
\usepackage{hyperref}
\newtheorem{example}{Example}
\begin{document}
\ \newpage
\begin{example}\label{ex}
\begin{itemize}
\item
\end{itemize}
\end{example}
\ref{ex}
\end{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

works as it should.

-- comment 1:
Sorry, the second code example in the error description is the same as the first one, instead it should have been the first one with a "noindent" added, i.e.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\documentclass{amsart}
\usepackage{hyperref}
\newtheorem{example}{Example}
\begin{document}
\ \newpage
\begin{example}\label{ex}\noindent
\begin{itemize}
\item
\end{itemize}
\end{example}
\ref{ex}
\end{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Catalan translation

(import from https://puszcza.gnu.org.ua/bugs/index.php?265, author Xavier )

The catalan translation is not provided. I send you the translation

\def\HyLang@catalan{%
\def\equationautorefname{Equaci'o}%
\def\footnoteautorefname{Nota al peu de p{a}gina}% \def\itemautorefname{Element}% \def\figureautorefname{Figura}% \def\tableautorefname{Taula}% \def\partautorefname{Part}% \def\appendixautorefname{Ap{e}ndix}%
\def\chapterautorefname{Cap'itol}%
\def\sectionautorefname{Secci'o}%
\def\subsectionautorefname{Subsecci'o}%
\def\subsubsectionautorefname{Subsubsecci'o}%
\def\paragraphautorefname{Par{a}graf}% \def\subparagraphautorefname{Subpar{a}graf}%
\def\FancyVerbLineautorefname{L'inia}%
\def\theoremautorefname{Teorema}%
\def\pageautorefname{P`{a}gina}%

I hope see it in next release.

Reference: https://tex.stackexchange.com/questions/94509/make-hyperrefs-autoref-output-in-bulgarian

pdfa option incorrectly forces pdfminorversion to be 1.4

Hi Heiko,

This coding from hyperref.sty makes it hard to declare valid PDF/A-2 and PDF/A-3 documents to have \pdfminorversion greater than 4; yet these formats are based on PDF 1.7.

\Hy@DisableOption{pdfa}
\ifHy@pdfa
\kvsetkeys{Hyp}{pdfversion=1.4}%
\Hy@DisableOption{pdfversion}%

Surely the version requirement for PDF/A should be "at least 1.4" rather than exactly 1.4.
It would be nice to be able to do this using hyperref options only.

In fact pdftex is currently defaulting to a \pdfminorversion of 5, yet after coding such as below we are down to 4.

\showthe\pdfminorversion
\PassOptionsToPackage{pdfversion=1.6,pdfa}{hyperref}
\documentclass[manuscript]{aomart}
\showthe\pdfminorversion

Setting \pdfminorversion directly, after hyperref has loaded, is possible provided it is done before anything is written into the PDF file; e.g. bookmarks, link annotations, Color Profile, Metadata packet, etc.

Can hyperref please be updated to allow this?

Ross

UTF8 in TextField's 'default'

Like #5, LuaLaTeX produces an incorrect result if you use non-ASCII characters for 'default' in TextField.
It seems pdfLaTeX produces the correct result if you use only LATIN1-characters, but this problem occurs on pdfLaTeX too, if you use Japanese characters for 'default'.
The following hack fixes this problem.
(dank des Kommentars von Frau Fischer in #5)

\documentclass{article}

\usepackage{fontspec}		% ---- for LuaLaTeX
% \usepackage[utf8]{inputenc}	% ---- for pdfLaTeX

\usepackage[unicode=true]{hyperref}
\usepackage[T1]{fontenc}

% FIX for 'default'
% See also the fix for 'value' by Frau Fischer
% ( https://github.com/ho-tex/hyperref/issues/5 ).
% I just replaced 'value' with 'default'.
\makeatletter
\define@key{Field}{default}{%
  \Hy@pdfstringdef\Fld@default{#1}}
\makeatother

% NOTE:
%   This fix IS needed for pdfLaTeX too, when you use Japanese
%   characters.
%
% \documentclass{article}
% \usepackage[whole]{bxcjkjatype}
% \usepackage[utf8]{inputenc}
% \begin{document}
% \begin{Form}
%   % without fix, fails to compile
%   \TextField[name=addr,default=東京]{Address} %Tokyo
% \end{Form}
% \end{document}

\begin{document}
\begin{Form}
  % OK, of course
  \TextField[name=textfield1]{Address} \\

  % OK
  \TextField[name=textfield2,value=Köln]{Address} \\

  % correct on pdfLaTeX (but incorrect if you use Japanese characters)
  % incorrect without FIX on LuaLaTeX
  \TextField[name=textfield3,default=München]{Address} \\

  % (though this is probably meaningless)
  % incorrect (internally) on LuaLaTeX
  % 
  % $ pdftk pr-textfield-default-encoding.pdf dump_data_fields
  % ...
  % FieldValue: Köln			% This is OK, but
  % FieldValueDefault: München	% Quatsch!
  % ...
  \TextField[name=textfield4,value=Köln,default=München]{Address}
\end{Form}
\end{document}

No way to specify capitalization

The english strings contain e.g. Figure and section. http://tex.stackexchange.com/questions/36575/autorefs-inserted-text-has-not-the-correct-case are people that want to write Figure with a small letter, and here are other people who want to capitalize section.

Since there are obviously different styles in use, it struck me as odd that hyperref has opinionated defaults and no way to override it. Or am I missing something?

pdfstringdef bug

Hi, I found a bug \pdfstringdef crash (I head some commands in \section).
Message:

! Missing \endcsname inserted.
<to be read again>
\aaa
l.14 \pdfstringdef\foo{\mydef abc}

MWE:

\documentclass{article}
\usepackage{hyperref}

\makeatletter
\DeclareRobustCommand\mydef[1]{
  \def\aaa {ab}
  \@ifundefined{qq\aaa}{}{}
  }
\makeatother

\begin{document}
\pdfstringdef\foo{\mydef abc}
\end{document}

No hyperlink created when using \hyperlink and \phantom with xelatex

I noticed this issue when trying to use the acro package. Creating links to the acronyms list works with pdflatex, but not with xelatex.

Clemens Niederberger posted a MWE, which shows that the issue is in the hyperref package.

% arara: xelatex
% arara: xelatex
\documentclass{article}
\usepackage{hyperref}

\begin{document}

\hypertarget{name}{text}
\clearpage
\hyperlink{name}{\phantom{text}}text

\end{document}

hyperref's patch to equation is only partial when amsmath is loaded

This issue was raised at http://tex.stackexchange.com/questions/235665/incorrect-spacing-after-minus-sign-with-combination-of-amsmath-and-hyperref. I commented upon it in my answer at http://tex.stackexchange.com/a/235715. Following code gives wrong spacing around first unary minus.

\documentclass{article}
\usepackage{amsmath}
\usepackage{hyperref}
\begin{document}
\begin{equation}
  -1 = -1 % output: - 1 = -1
\end{equation}
\end{document}

For some reason the patch to equation done by hyperref is seemingly partial, when amsmath is loaded.

In my answer http://tex.stackexchange.com/a/235715 I mention a similar but non-related to hyperref problem, involving amsmath and it is now bug report https://www.latex-project.org/cgi-bin/ltxbugs2html?pr=amslatex/4461&category=AMS+LaTeX&responsible=anyone&state=open&keyword=&search=

Modify backref to add a list of where the ref­er­ence was cited, to each bib­li­og­ra­phy en­try similar to hypdvips.sty implementation.

When compiling via latex->dvi->ps->pdf using hyperref, backref and hypdvips, the bibliographic entries are formatted as such:

D. Knuth, The TEXbook. Addison-Wesley Professional, 1984.
(Referenced on pages 16 and 19.)

When using pdflatex it is just:

D. Knuth, The TEXbook. Addison-Wesley Professional, 1984. 16, 19

The relevant code in hypdvips.sty is this:

\ifHy@backref
    \ifx\backrefxxx\hyper@section@backref
      \@ifpackageloaded{cleveref}
        {
        \renewcommand*{\backrefalt}[4]{%
          \setlength{\pp@offset}{\baselineskip}%
          \\\scriptsize(Referenced in
          \setlength{\baselineskip}{\pp@offset}%
          ##2.)
          }
        }
        {
        \renewcommand*{\backrefalt}[4]{\\\scriptsize(Referenced\ in: ##2.)}
        }
    \fi
    \ifx\backrefxxx\hyper@page@backref
      \renewcommand*{\backrefalt}[4]{%
        \ifcase##1%
        \or%
          \\\scriptsize(Referenced\ on\ page ##2.)
        \else%
          \\\scriptsize(Referenced\ on\ pages ##2.)
        \fi%
      }
    \fi
  \fi

There is a related patch here https://www.ctan.org/pkg/ut-backref

Can we have the same format output no matter what the compiler used?

Fillable forms with default/preselected buttons

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?202, author Thorsten )

Hi. I am trying to generate forms with preselected buttons using the "default" parameter. This works for the first example/button but not for the second example/button.

\documentclass{article}
\usepackage{hyperref}

\begin{document}
\begin{Form}
\ChoiceMenu[default=y,radio,name=atesta]{Question:}{yes=y,no=n}
\end{Form}

\begin{Form}
\ChoiceMenu[default=n,radio,name=btestb]{Question:}{yes=y,no=n}
\end{Form}
\end{document}

How can I fix this?

Thx, Thorsten

Program versions are:

Hyperref 2012/11/06 v6.83m

$ pdflatex -v
pdfTeX 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
kpathsea version 6.1.1
Copyright 2013 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.2.49; using libpng 1.2.49
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with poppler version 0.24.3

-- (comment #1)

I played around with pdftk and the uncompressed pdf. It seems that for every radio button both "/V" entries must have the default value.

The following "dirty" patch works for me.

--- hpdftex.def.bak 2014-01-14 10:31:34.050531142 +0100
+++ hpdftex.def 2014-01-14 11:03:08.438525051 +0100
@@ -1607,8 +1607,8 @@
/V/\Fld@default
/DV/\Fld@default
\else

• /V/Off%
• /DV/Off%
• /V/\Fld@default
• /DV/\Fld@default
  \fi
  \Fld@additionalactions
  }

improve documentation of PDF form parameters

While creating a PDF form I found out that the parameter borderstyle can have the values
U (underlined), S (solid), D (dashed), B (bevel) or I (inverted bevel)

But borderstyle is not even mentioned in the hyperref manual.

I also found out that the settings
color
borderstyle=B
borderstyle=I
have no effect for popdown choice menus.

I assume that this is not a bug in hyperref but just not described, right? If so, could this information please be added to the manual that others don't have the same problems.

PDF form parameter 'menulength' does not work

I use hyperref v6.85a and pdfTeX 1.40.17.

In the hyperref manual it is stated that menulength will determine the number of displayed entries in a list. But

\renewcommand*{\DefaultOptionsofPopdownBox}{print, menulength=2}
\ChoiceMenu[popdown, name=country2, default=Ar]{Country:}{Albania=Al, Armenia=Ar, Azerbaidschan=Az}

shows me all 3 entries instead of the desired 2. I am quite sure that menulength worked in previous versions of hyperref.

hyperref: possible bug when using \@addtoreset {<counter>}{@ckpt}

Hello,

The LaTeX macro \cl@@ckpt maintains a list of counter.
The simplest way to append a counter in the list is to use :
@addtoreset {counter}{@ckpt}

But hyperref redefines @addtoreset in order for it to define
\theH
without the longer test made when the command \theH
does not exist: if \theH does not exist, hyperref
executes \HyCnt@ProvideTheHCounter which looks into \cl@@ckpt
to find a possibly parent counter.

But @ckpt is NOT a counter, and \cl@@ckpt is NOT comparable
to \cl@section for example.

So:
@addtoreset {counter}{@ckpt}

has not the same meaning as :
@addtoreset {counter}{parent-counter}

But hyperref does not make the check, so that:
@addtoreset {counter}{@ckpt}

finally defines: \theHcounter -> \the@clckpt .\the\value {counter}

And \the@ckpt is a undefined control sequence, since @ckpt is not a counter.

I think hyperref should check that special use of @addtoreset with @ckpt, when redefining @addtoreset.

Minimal example that shows the problem :
%------------------------------------------------------------
\documentclass [a4paper]{article}
\usepackage [T1]{fontenc}
\usepackage [utf8]{inputenc}
\usepackage {hyperref}

\makeatletter
\newcount \c@mycount
@addtoreset {mycount}{@ckpt}

\begin{document}

meaning of theHmycount = \meaning\theHmycount

\end{document}
% ----------------------------------------------------------

Hook for aditional \hyper@normalise defs

Hi, would be good to have a hook in \hyper@normalise where one could overwrite his own.
For example now \texttildelow does not work in \href (re-typesetting is not an option) .

\documentclass{article}
\usepackage{textcomp}
\usepackage{hyperref}

\begin{document}
\href{http://www.tilde.com/\protect\texttildelow}{www.tilde.com/\protect\texttildelow}
\end{document}

Hook could be somewhere:

\gdef\hyper@normalise{^^A
   \begingroup
   \catcode`\^^M\active
   \def^^M{ }^^A
   \catcode`\%\active
   \let%\@percentchar
   \let\%\@percentchar
   \catcode`\#\active
   \def#{\hyper@hash}^^A
   \def\#{\hyper@hash}^^A
   \@makeother\&^^A
   \edef&{\string&}^^A
   \edef\&{\string&}^^A
   \edef\textunderscore{\string_}^^A
   \let\_\textunderscore
   \catcode`\_\active
   \let_\textunderscore
   \let~\hyper@tilde
   \let\~\hyper@tilde
   \let\textasciitilde\hyper@tilde
   \let\\\@backslashchar
   \edef${\string$}^^A
   \Hy@safe@activestrue
   \csname hyper@normalise@hook\endcsname % <--HERE
   \hyper@n@rmalise
   }

pdfauthor and pdftitle 'eat away' last char

Mn-WE included: lipsum.zip

Buggy Code In Question:
\newcommand{\AuthorName}{Ntentos Stavros}
... pdftitle={Thesis of \AuthorName}, pdfauthor={\AuthorName} ...

produces

If we include in the \newcommand{\AuthorName}{Ntentos Stavros} anything (a letter, an unbreakable space "\ ", even a "breakable space", ie " "), the output is:

Hyperref + makeindex + entails problem

I am not certain that this is a hyperref bug. If you can determine that it is not, please let me know and I will file this bug elsewhere.

I maintain the PVS package (http://pvs.csl.sri.com/) for the Fedora Linux distribution. A few years ago, after a TeXLive update, the build started failing while trying to make the user manual. Details are available here: https://bugzilla.redhat.com/show_bug.cgi?id=886158. The issue arises with this paragraph in the manual:

The \cmd{x-show-current-proof} command creates a window showing the
cur-rent proof tree. Every sequent in the tree is represented by a
$\vdash$ symbol\index{"|-@$\vdash$}. The proof commands used to create
the tree will also be shown between the $\vdash$ symbols. This tree will
be automatically updated after every proof command.

Prior to TeXLive 2012, that index command resulted in the following entry in user-guide.ind (the last entry in the section for symbols):

\item $\vdash$, \hyperpage{52}

With TeXLive 2012 and later, this is generated instead:

\item $\vdash$}, 52

The missing \hyperpage is annoying, but the extraneous right curly brace is fatal. The problem seems to be caused by hyperref deciding that the - in "|- might represent a page range and wrapping the whole thing in hyperindexformat, thereby hiding the escaping " from makeindex. If I have misdiagnosed the problem, pointers in the right direction would be appreciated. Thank you.

Using \noboundary as a Text-Command, and similar issues

Hi Heiko.

This cannot be correct, as it redefines a TeX primitive:
.../hyperref/puarenc.def:88:\DeclareTextCommand{\noboundary}{PU}{\9040\015}% U+200D

\documentclass[11pt, oneside]{article}
\usepackage[unicode,arabic,psdextra]{hyperref}
\begin{document}
\noboundary
\end{document}

gives an error:

LaTeX Error: Command \textlozenge unavailable in encoding OT1.

The right way (as I'm sure you know) is something like:
\DeclareTextCommand{\textPUnoboundary}{PU}{\9040\015}% U+200D
with
\let\noboundary\textPUnoboundary
included in \pdfstringdefDisableCommands (or elsewhere) when needed.

Another command showing a similar kind of error is: \textlozenge
when used with packages like: gfsdidot, gfsbodoni, gfsartemisia etc. or drm.sty

\textbullet is another that gets (re)defined in various packages.

Here's another that works smoothly, but results in different output, dependent upon the order in which the packages are loaded.

\documentclass[11pt, oneside]{article}
\usepackage{baskervillef}
\usepackage[unicode]{hyperref}
%\usepackage{baskervillef}
\begin{document}
\textcircled{A}
\end{document}

Then there is the package: ptmxcomp that redefines quite a few \text... macros.

I was hit with similar issues for L8U (pseudo-)encoding, with pdfx.sty.
I've been talking about such issues with Chris, David and Frank. They now realise the importance of pseudo-encodings (as we now call them) such as PU, PD1 and L8U, which are not associated with fonts, but still want to use some of the methods developed for font-encodings.

Cheers,

Ross

the patch of longtable for footnotes does not work if ``\footnote[N]`` form

Example:

\documentclass{article}
\usepackage{longtable}
\usepackage{hyperref}
\begin{document}
\begin{longtable}[c]{lp{3cm}p{3cm}}
  Hello&Hello&Hello\\
\endfirsthead
\endhead
\endfoot
\endlastfoot
 X
  \footnote[3]{%
    with optional argument in l column
  }
&X
  \footnote[5]{%
    with optional argument in p column
  }
&X
  \footnote{%
    without optional argument in p column
  }
\end{longtable}
\clearpage
Next page
\end{document}

The second footnote has wrong number at bottom of page (but the hyperlink does find its right target).

hyperlink to theorem begin with enumerate wrong

I use amsthm for theorems and hyperref for hyperlink. I have some theorem begin with enumerates. In this case, the hyperlink associated to the theorem is wrong.

\documentclass{article}
\usepackage{amsthm, hyperref}
\newtheorem{theorem}{Theorem}
\begin{document}
\autoref{thm:1}.
\autoref{thm:2},
\autoref{item:1}.
\clearpage
\begin{theorem}\label{thm:1}
  This is a test for theorem.
\end{theorem}
\clearpage
\begin{theorem}\label{thm:2}
  \begin{enumerate}
    \item\label{item:1} Item 1
    \item\label{item:2} Item 2
  \end{enumerate}
\end{theorem}
\end{document}

I found that the hyperlink Theorem 1 and item 1 work well, but Theorem 2 seems have no target.

And, I get some warning name{theorem 2} has been referenced but does not exist, replaced by a fixed one.

So, is there something wrong, here?

markup for dead links

Please consider the following "patch" by Ulrike Fischer ( [email protected] ) for markup of dead links.
Maybe \color{red} #3 is just fine for some color provided by the user.

https://de.comp.text.tex.narkive.com/r7OOusMU/hyperef-farbe-fur-tote-links

\documentclass{article}
\usepackage{xcolor}
\usepackage{hyperref}

\makeatletter
\def\label@@hyperref#1#2#3{%
  \ifx#1\relax
    \protect\G@refundefinedtrue
    \@latex@warning{%
      Hyper reference `#2' on page \thepage \space undefined%
    }%
    \begingroup
      \colorbox{yellow}{\color{red}\bfseries #3}%was auch immer
    \endgroup
  \else
    \hyper@@link{\expandafter\@fifthoffive#1}%
      {\expandafter\@fourthoffive#1\@empty\@empty}{#3}%
  \fi
}
\makeatother
\begin{document}

\hyperref[target]{text}

% \label{target}

\end{document}

Link across two pages is visually broken (includes header/footer)

See https://tex.stackexchange.com/q/330669 for a MWE, a result (picture) and a workaround.

When a link spans across pages, page header and footer also become part of this link, which looks broken.

XeTeX fails with % and non-ASCII characters in headings

When combining '%' with a non-ASCII character in a heading, hyperref's output does not work with XeTeX. The following example fails on the second pass when using xelatex:

\documentclass{article}
\usepackage{hyperref}
\begin{document}
\section{\%á}
\end{document}

It gives the following error:

Runaway argument?
{
! File ended while scanning use of \@@BOOKMARK.
<inserted text> 
                \par 
l.3     \begin{document}

To fix this, one can either use \usepackage[unicode]{hyperref} or add \usepackage{bookmark}. Adding \hypersetup{unicode=true} results in the same error.

This problem and the solution was discussed on StackExchange last year, but it doesn't seem to have been reported here yet.

Error: pdfendlink ended up in different nesting level than \pdfstartlink

\hyperref works without issues for me in a (bibtex) bibliography set in normal one-column mode.

In two-column mode, it often crashes with the above error. This has been previously reported, e.g.
http://tex.stackexchange.com/questions/265881/pdftex-error-ext4-pdfendlink-ended-up-in-different-nesting-level-than-pd

and is understood to be a problem when a link is broken across a page or column. My bibliography is about 5000 entries covering 100 pages, so any sort of manual fix is out of the question.

Assistance in getting a fix would be greatly appreciated

checked checkboxes and default radiobuttons

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?203, author A. van der Lee )

Hi all,

I have two similar problems, one with checkboxes and the other with radiobuttons:

Checkbuttons:

\documentclass{minimal}
\usepackage{hyperref}
\begin{document}
\begin{Form}
\CheckBox[checked,name=ch1]{Yes}
\end{Form}
\end{document}

This does not give a checked checkbox with a number of versions of Acrobat Reader. Reader 9 works, but not 10 and 11, nor Adobe Professional 10. It appears that such a problem was reported in 2005, but with Reader 5,6.

The other example, with radiobuttons tries to define a checked radiobutton for the second button.

\documentclass{article}
\listfiles
\usepackage[pdftex]{hyperref}
\begin{document}
\begin{Form}
\ChoiceMenu[radio,default=no,name=yesno]{Yes or no:}{Yes=yes,No=no}
\end{Form}
\end{document}

Setting default=yes works. I have not seen differences for different versions of Adobe Reader.
The problem is similar as for the one reported yesterday by Thorsten for choicemenus.

pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9)
Package: hyperref 2012/11/06 v6.83m Hypertext links for LaTeX

best wishes, Arie

pdfhighlight doesn't work with XeTeX

MWE:

\documentclass{scrartcl}
\usepackage[pdfhighlight=/N]{hyperref}
\begin{document}
\tableofcontents
\section{test}
\end{document}

A fix for this was already posted over at tex.se:

\makeatletter
\usepackage{ifxetex}
\ifxetex
  \let\Hy@setpdfborderOrig\Hy@setpdfborder
  \def\Hy@setpdfborder{
    \ifx\@pdfhightlight\@empty
    \else
      /H\@pdfhighlight
    \fi
    \Hy@setpdfborderOrig
  }
\fi
\makeatother

Please include it if possible.

fitH value not recognized by pdfremotestartview

Roughly translated from

http://www.guitex.org/home/en/forum/5-tex-e-latex/109472-hyperref-valore-non-riconosciuto-da-pdfremotestartview#109497

\documentclass{article}
\usepackage[pdfremotestartview=FitH]{hyperref}
\begin{document}
Prova
\end{document}

appears to be valid according to the list on page 11 of the manual, but produces

Package hyperref Warning: Invalid value `FitH'
(hyperref)                of `pdfremotestartview'
(hyperref)                is replaced by `Fit' on input line 4362.

hyperref pdfcreator

Could you please consider changing line 7021 in the file hyperref.dtx from

\def\@pdfcreator{LaTeX with hyperref package}

to

\let\@pdfcreator\relax

Like what you said yourself in tex-xet/bidi#60 the pdfinfo metadata should not be forced by a package.

Include information about NoHyper in the documentation

There are quite some questions concerning the temporary disabling of hyperlinks using the hyperref package (e.g. https://tex.stackexchange.com/q/116338/134144, https://tex.stackexchange.com/q/118182/134144, https://tex.stackexchange.com/q/6093/134144, https://tex.stackexchange.com/q/415625/134144) where using the NoHyper environment comes in handy.

Looking throught the documentation I could unfortunately not find any information on this useful environment, so it might be worth adding some explanation to help users find out about it.

Way too normal size of references in stackrel when running `latex`

Consider the code

\documentclass{article}
\usepackage{algorithm2e}
\usepackage[hidelinks]{hyperref}
\begin{document}
\newtheorem{thm}{Theorem}
\begin{thm}\label{BC}B=C.\end{thm}
\LinesNumbered
\begin{algorithm}
  A:=B\nllabel{lineFoo}\;
\end{algorithm}
$A\stackrel{\mathrm{line}\ \ref{lineFoo}}{=}B\stackrel{\mathrm{Thm.}\ \ref{BC}}{=}C$.
\end{document}

When running latex on it, the resulting dvi file has normal-sized labels 1, while the labels should be, in fact, small-sized.

Later, when dvi is translated to postscript or to pdf, the normal size of 1 is maintained, resulting in an unpleasant output. (Remark: when running pdflatex, the size is small as expected.)

Thanks for repairing in advance!

\url|....| support in hyperref

Wishlist: no idea if it's feasible, but it would be nice if hyperref supported \url|...|, since the original url.sty does. Right now it takes the first | as the argument, as in \url{|}.

links not coloured when main font has non-default colour

When using a main font with any other than the default colour, links are not rendered in colour (if any colour has been set for them).

Here is an MWE:

\documentclass{report}

\usepackage[table,hyperref]{xcolor}
\definecolorset{RGB}{}{}{dark-grey,50,48,46;link-blue,0,0,153}
\globalcolorstrue

\usepackage{fontspec}
% \defaultfontfeatures{Color=dark-grey} %%% uncomment this line and the links will no longer be blue
\setmainfont{Helvetica Neue Light}[BoldFont={Helvetica Neue Bold},ItalicFont={* Italic}]

\usepackage{hyperref}
\hypersetup{%
  linktoc=all,%
  linkcolor=link-blue,%
  urlcolor=link-blue,%
  colorlinks=true,%
}

\begin{document}
\section{The First section}
\label{sec:first-section}
This is some text that we will refer to using the \href{https://github.com/ho-tex/hyperref}{hyperref package}.

\section{The Second Section}
\label{sec:second-section}
This is more text in the second section. The important stuff has been said in \autoref{sec:first-section} already.

\end{document}

If you uncomment the line just below \usepackage{fontspec} to change the main font colour to a non-default one, the links lose their blue colouring.

As discussed in latex3/fontspec#247, a workaround is to add

\makeatletter
\def\HyColor@@@@UseColor#1\@nil{\addfontfeatures{Color=#1}}
\makeatother

immediately after \hypersetup{} in the MWE, or in the same location sans \makeatletter and \makeatother when using a custom document class. It seems that this allows hyperref to override the font colour override by fontspec.

To me it wouldn't seem a too uncommon wish to set a non-default the main font colour and still be able to have hyperref links be coloured? The Stack Exchange discussion cited in latex3/fontspec#247 dates back to 2011, so I'd be surprised to be the first person to ask for this...

What would speak against including the \def\HyColor@@@@UseColor... line in hyperrefitself?

Bad interaction with portuges babel in captions

Dear all,
down at Debian we got a bug report that using hyperref and portuges babel breaks captions. A MNWE is:

\documentclass{article}
\usepackage[portuges]{babel}
\usepackage[pdftex,plainpages=false]{hyperref}
\begin{document}
\begin{table}
\caption{Table "title" }
% this works: \caption{Table title }
\end{table}
\end{document}

The problem is in the handling of ", the error message is:

! Extra \endcsname.
\language@active@arg" ...@"@\string #1@\endcsname 
                                                  \fi 
l.6 \caption{Table "title" }

I'm not sure if that can be fixed in hyperref or in portuges, but I thought I ask.

Thanks

Norbert

Too much vspace before theorem if previous line full

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?165, author Hilmar Preusse )

Down here in the DBTS we got a bug report telling that the vspace visible in the document is sometimes too large. The problem disappears as soon as one stops using hyperref.

http://bugs.debian.org/673991

The minimal example is attached, the log file for the LaTeX run too.
Hilmar Preusse

(no files were attached, but i presume they are in the debian bug, so doing nothing further right now. --karl)

link rectangle too small with (x)dvipdfmx

with the document below and everything from the TL16 pretest (or earlier versions, this is not new), process with xelatex (hence xdvipdfmx), the "link rectangle" as displayed by xpdf around the text "J.exam.or" is too tight -- right up against the black pixels in every dimension. same results with latex|dvipdfmx.

process with pdflatex, there is a small but better-than-nothing margin.

\documentclass{article}
\usepackage{hyperref}
\begin{document}
\href{foo}{J.exam.or}
\end{document}

i know it could be, maybe even probably is, something in (x)dvipdfmx. i know its algorithm for computing that link rectangle is necessarily completely different from pdftex's.

however, i see various kludge factors in hyperref specifically relating to the link rectangles for the (x)dvipdfm(x) backend, although i admit i could not easily discern what they all were and what they were supposed to do. therefore i wondered if it is something at the hyperref level.

would you mind taking a look? thanks.

Breaking links with `ocgcolorlinks` enabled.

As one of the maintainers stated, breaking links across lines is not possible with ocgcolorlinks enabled (hence being marked as experimental).
In this tex.sx thread Ben Berner posted a workaround and mentioned that he tried to contact the maintainers, but never heard back.
Since it seems to work fine with pdfLaTeX (but I also don't know where it could lead to problems, no knowledge of TeX/PDF internals), I thought I'd post it here, in case you missed it. Feel free to close the issue, if this was settled long ago.
Note: it does not work with luaLaTeX (\pdfpagewidth not found)

Using dvips will lead to PDFs having XMP with broken character encoding

When compiling a file into DVI and then further via dvips, the resulting file will have XMP metadata. In the metadata, non-ASCII Latin1 characters are broken into some three-byte sequences, while non-Latin1 characters (like Š in the example below) produce the correct UTF-8 byte sequence.

For the document

\documentclass{article}
\usepackage[utf8]{inputenc}
\title{Non-AŠCIÍ} \newcommand{\keywords}{ümlauts, accénts}
\usepackage[unicode,pdfusetitle]{hyperref}\hypersetup{pdfkeywords=\keywords}
\begin{document}
Hello world
\end{document}

compiled with etex -fmt=latex main.tex && dvips main.dvi && ps2pdf main.ps, exiftool will report

Producer                        : dvips + GPL Ghostscript 9.20
Keywords                        : mlauts, acc￩nts
Creator Tool                    : LaTeX with hyperref package
Format                          : application/pdf
Title                           : Non-AŠCIￍ

I’m not really sure whether this is a hyperref bug or if the fault lies somewhere else... The documentation does not mention XMP being produced, so if this is a “feature” of some other tool in the chain, a warning or some pointers might be in order.

Greek language for \autoref

I would like to contribute the Greek translations for \autoref, since Greek is not supported currently, but I can't find the way. Could you point me to the place where the changes should be made, or the person I should contact?

Hyperref in amsmath's \text doesn't get hyperlinked

This is a follow-up to https://tex.stackexchange.com/questions/310877/why-does-usepackageamsmath-break-hyperref-in-textnormal :) In the following example, when using xelatex, the first hyperlink is properly activated, but not the second one:

\documentclass{article}

\usepackage{amsmath} % Removing this makes the second link work
\usepackage{hyperref}

\begin{document}
  \hyperref[abc-def]{link} % This link works
  \(\textnormal{\hyperref[abc-def]{link}}\) % But not this one
  \label{abc-def} Target
\end{document}

Removing amsmath activates both links.

Thanks!

Less verbosity

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?190, author Cristian Klein )

TL;DR

Provide an option "trustdriverautodetect" to disable the autodetected driver message and have a cleaner console output.
Long version

Some users prefer having the LaTeX console as clean as possible, to allow them to focus only on important messages, such as warnings and errors. Hyperref currently displays a message of the form "Package hyperref Message: Driver (autodetected): hpdftex". For some users, this message is important only once, when setting up a new LaTeX project, therefore, they may consider it unimportant and would prefer disabling it.

To reconcile the two categories of users, those who want to see this output and those who do not, I propose adding a new option to hyperref, called "trustdriverautodetect". If the users does not pass this option, hyperref defaults to showing the driver autodetect message. Then, when users are confident that this is no longer needed, they can pass "trustdriverautodetect=true", to instruct hyperref not to show the autodetect message any more.

The attached patch implements this proposition.

hyperref.diff.txt

Href doesn't work with abolute local path in linux

Suppose I have a tex file in a directory called /mytexfiles/texfile.tex which contains a line like

\href{/path/to/my/pdf/file.pdf}{pdf-file}

If I open the compiled document in evince and click on the link, it displays an error message which indicates that evince tries to look at the combined path for the file, i.e. /mytexfiles/path/to/my/pdf/file.pdf so it couldn't open the file.

hyperref generated PDF forms can not be imported correctly using poppler

(import from https://puszcza.gnu.org.ua/bugs/?272)
or Mupdf, so there are to my knowledge no PDF viewers left in Linux, which could work on them.
Fortunately, the word processor of Libreoffice 5.1.0 seems to spit out ODFs in a format, which is exported by poppler in a way, that it will later understand.

I have attached the uncompressed pdf output for comparison (LOFormWin-uncomp.pdf), so adapting hyperref output to poppler’s suggestions would most likely fix the issue. Could not see any differences in acroread or Windows readers.

Reproducible: Always

Steps to reproduce:

1. pdflatex .tex
2. Open the resulting pdf in either qpdfview, okular, evince, mupdf, pdf-tools (emacs), doc-view (emacs) or inkscape (poppler-import)

Expected results:
Radio Buttons deselect, when clicking another. Checkbox may be (de-)activated. Rendering should be correct for the last three ones (no form support).

Actual results:
Second Radio Button is rendered as \ding{123} (all in docView). Nothing is rendered in mupdf. Clicking another Radio Button will not deselect the others. \ding{123} will show up when clicking the invisible Radio Buttons in mupdf.
The checkbox can not be activated.

I used the following minimal example to investigate the issue:

\pdfminorversion=7
\documentclass[a4paper]{article}
\usepackage[english]{babel}
\usepackage[utf8]{inputenc}
\usepackage[pdftex]{hyperref}

\begin{document}
\begin{Form}
\ChoiceMenu[radio,radiosymbol=\ding{108},name={myGroupOfRadiobuttons}]{Multi}{A, B}
\ChoiceMenu[radio,radiosymbol=\ding{108},name={myGroupOfRadiobuttons}]{Single}{C}
\medskip

\CheckBox[name=checkbox, checkboxsymbol=\ding{110}]{Checkbox}
\bigskip

\TextField[name=textfield,altname=textfield, width=0.6\textwidth]{TextField}
\end{Form}
\end{document}

Additional Information:

Resetting the form data in “Master PDF Editor” will get the checkbox to work everywhere and the radio buttons in mupdf. Attached the diff between those two as ‘bugexMPEres.diff’
Simply saving it in “Win Acrobat Reader” has the same effect. Saving it in “Foxit Reader” will replace the \ding{123} signs, but has otherwise no effect. The identical effect is achieved by not resetting the form in MPE.

Inkscape has a nice checkbox to toggle poppler import. Enabling it, leads to exactly the same appearance. Otherwise, just the text is shown, which excludes the viewers from influencing the issue. (shown in lininkevi.png; left inkscape, right evince).

The last one shows pdf-tools left, which has no form support, but at least recognizes the mid radio button as annotation, and mupdf right, which selects the buttons as \ding{123}.

Other bugs involved:

Of course poppler’s pdf import could be improved, but since its count of PDF form bugs is already quite high, filing another one would be to no avail.

Linux Libreoffice 5.0.4 could not create an odt, which could export to working PDF forms. I created that example one with LO 5.1.0 in a Windows VM. Once it is packaged on Gentoo, I’ll retest that to see if I get different results.

Mupdf might freeze, when entering the text field.

pdflatex version:
pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015)
kpathsea version 6.2.1
Copyright 2015 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.6.19+apng; using libpng 1.6.19+apng
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with poppler version 0.32.0

texlive-2015 (meta) with texlive-latex-2015 (containing hyperref).

Best regards,
Manuel Ullmann
Manuel Ullmann
LOFormWin-uncomp.pdf


bugexMPEres.diff.txt