LaTeX package conflicts

From Exterior Memory
Revision as of 01:08, 10 January 2009 by MacFreek (Talk | contribs)

Jump to: navigation, search

LaTeX package conflicts

Package conflicts in LaTeX are a hell. Perhaps I should have used ConTeX after all (ConTeX does not have package conflicts; I guess mostly because there are no packages...)


Hyperref is by far the package causing most conflicts. Do yourself a favour and do read the hyperref README file (Section 6 on Package Compatibility). It contains an extensive, albeit not complete list of conflicts and solutions.

Hyperref and preamble pages


pdfTeX warning (ext4): destination with the same identifier (name{page.2}) has been already used, duplicate ignored

If you have a preamble, e.g. you make a thesis and use \frontmatter, \mainmatter and \backmatter, then the page numbers in front matter are roman (i, ii, iii, iv, v, vi, etc.) The page numbers in main matter are arabic (1, 2, 3, 4, etc.). However, the page labels are the same in both cases (page.1, page.2, page.3, etc.). This leads to the error. To circumvent, tell the hyperref package to use page labels with roman symbols (page.i, page.ii, page.iii, etc.)

See also the LaTeX FAQ entry on Hyperref and repeated page numbers.



Hyperref and Fancy headers


pdfTeX warning (ext4): destination with the same identifier (name{figure.1.1}) has been already used, duplicate ignored

If you get errors like the above, even though you really have only one figure 1.1, perhaps you experience a conflict between hyperref and fancy headers.

Solution: Hyperref must be loaded after fancy headers.


Hyperref and Algorithm

LaTeX gives an error in lines with a \ref{} command that points to an algorithm:

undefined control sequence

If the above error occurs the second time you run latex, but not the first time, you may experience a conflict between the hyperref and algorithm package.

If algorithm is loaded after hyperref, any \label{alg:myalgorithm} statements ends up faulty in the .aux file (it contains a spurious \theAlgorithm statement). This causes the above error if latex is run the second time (when it includes the faulty aux file).

See also hyperref README file (Section 6 on Package Compatibility).

Solution: hyperref must be loaded before algorithm, but after float.


Hyperref and Algorithmic


pdfTeX warning (ext4): destination with the same identifier (name{ALC@rem.1}) has been already used, duplicate ignored

If you include multiple algorithms in your document, the labels for the line numbers are the same for each algorithm, and the hyperref package complains about that.

See also fix hyperref warnings with line numbers

Solution: this is a bug in the algorithmic package. The above website contains a page against algorithmic version of 2006/06/02. Below is the diff. Copy this to a file, save as algorithmic.diff and apply using diff < algorithmic.diff (of course after you made a backup of the original algorithmic.sty):

--- algorithmic.sty     2006-06-02 00:00:00.000000000 +0000
+++ algorithmic.sty     2006-12-15 00:00:00.000000000 +0000
@@ -16,7 +16,7 @@
 % Boston, MA  02111-1307, USA.
 \typeout{Document Style `algorithmic' - environment}
@@ -26,6 +26,7 @@
@@ -128,7 +129,19 @@
-  \newcommand{\ALC@it}{\refstepcounter{ALC@rem}\refstepcounter{ALC@line}\ifthenelse{\equal{\arabic{ALC@rem}}{#1}}{\setcounter{ALC@rem}{0}}{}\item\ALC@setref}
+  \newcommand{\ALC@it}{\@ifundefined{href}{% if not hyperref then do a simple refstepcounter
+    \refstepcounter{ALC@rem}%
+}{% else if hyperref, do the anchor so 2 lines in two differents algorithms cannot have the same href
+\@ifundefined{href}{% if not hyperref then do a simple refstepcounter
+    \refstepcounter{ALC@line}%
+}{% else if hyperref, do the anchor so 2 lines in two differents algorithms cannot have the same href
 {}{\ \algorithmiccomment{##1}}}

PGF and double subscripts


Latex Error: ./mydocument.tex:8 Double subscript.

Strangely enough, this may be caused by an older version of the pgf package. (Strange because PGF is a draw package, and I did not expect it to interfere with mathematical equations).

The following code is a minimal example that throws the error just after the second \sum_ statement.



The grand total is:
s = \sum_{y} \: \sum_{x} x*y


Solution: PGF version 1.10 exhibits this behaviour. Upgrade to a newer version (PGF 2.00 works fine for me), or simply slightly change the formula. Simply changing the spacing from \: to \; solves the problem as well.

XeLaTeX with pdftex driver


hpdftex.def:442 Undefined control sequence.

with line causing the error:


If you use xelatex instead of pdflatex as the typesetting program, and you specify pdftex as the driver for some packages:

%!TEX TS-program = xelatex


This is in conflict. XeTeX does not work properly with the pdftex driver. Instead, specify xetex as the driver:

%!TEX TS-program = xelatex


Note: this works fine for XeTeX 0.996-patch1. Up till XeTeX 0.996, the default graphics driver for Mac OS X was xdv2pdf. However, since XeTeX 0.997 this has changed to xdvipdfmx for all platforms. For what I understand, the option [xetex] selects the xdv2pdf driver, while the option [dvipdfmx] selects the xdvipdfmx driver. If you use a newer version of XeTeX, let me know what works for you!

XltXtra and Graphicx


LaTeX Error: Option clash for package graphicx.

The xltxtra (which loads fontspec, xunicode and defines the \xetex shortcut) does also load the graphicx pacakage. However, it does not specify any options, so if you later load the graphicx package with options, this does conflict each other.


There are two solutions. The first is to simply not load the graphicx package anymore, or don't specify any options either:


The second, and better, solution is to load the graphicx package before loading the xltxtra package.


Amssymb with Xunicode


Latex Error: /opt/local/share/texmf-dist/tex/latex/amsfonts/amssymb.sty:252 Command `\Finv' already defined.

Solution: include amssymb before xunicode:


Note that if you include xltxtra, that automatically includes xunicode, so amssymb should also go before xltxtra:

\usepackage{xltxtra}    % xltxtra includes xunicode

Fontspec and Inputenc

The following is completely redundant:


The fontspec package requires XeTeX or xelatex to run. XeTeX always expects UTF-8 input, so it is completely redundant to specify that using the inputenc package. While I have not seen any error, I'm told that this may cause unexpected behaviour. If you use fontspec, you should not use inputenc. Also, I'm told that fontspec and babel packages don't mix well. If you still want more explicit unicode support, have a look at the xunicode package instead (though I found that even without, you can simply type any UTF-8 character which are all understood by XeTex).


or nearly equivalent:

\usepackage{xltxtra}   % loads graphicx, fontspec, xunicode and others

XeTeX 0.996, fontspec and Latin Modern


Random characters (garbled text) when using the fontspec pacakge.

Latin Modern is an extension to the older Computer Modern font set. It is loaded by default by the fontspec package. However, the naming convention of Latin Modern (lm) changed around the time TexLive 2007 came out. This causes the random characters in the output file. In order to fix this, either use another font, such as Computer Modern Unicode (CMU) or upgrade to a newer version of XeTeX and the fontspec package.

Disclaimer: I haven't tried the last solution yet.

\usepackage{fontspec}   % OpenType/TrueType font support. Requires XeTeX.
% CMU = Computer Modern Unicode, see
\setmainfont{CMU Serif}
\setsansfont{CMU Sans Serif}
\setmonofont{CMU Typewriter Text}

Bold Typewriter is Not Bold

Error: \texttt{Typewriter \textbf{Bold}} gives normal (not bold) text.

The standard LaTeX typewriter (Computer Modern) font does not have a distinguishable bold variant. Neither does the replacement font Latin Modern.

See LaTeX Bold Typewriter Font how to solve this.

Output File Removed

If you run XeTeX, and no PDF file is created and the output gives the notice:

Output file removed.

If you see this, you can get more details by splitting the run process in two:

xelatex --no-pdf test
xdvipdfmx test.xdv

or (depending on your default driver):

xelatex --no-pdf test
xdv2pdf test.xdv

The xdvipdfmx or xdv2pdf driver typically gives a more detailed error message.

Type1 Font Error


xdv2pdf <Error>: can't find font object for font id 2949602.
xdv2pdf <Error>: WARNING: Type1 font data returned by OFAStreamPSDownload isn't in the correct format required by the Adobe Type 1Font Format specification.
xdv2pdf <Error>: ATSFontGetPostScriptName failed: error -984.
ttf_create_with_id: failed to find font object for id 2949602.
xdv2pdf <Error>: WARNING: --font-2949602-6--: missing or invalid font descriptor.

All these errors are caused by xdv2pdf, which is a relative old driver for XeTeX. You are recommended to use the xdvipdfmx driver, which is the default since XeTeX 0.999.7 (present in TexLive 2008 or later). Alternatively, specify the driver explicitly (though you may need to install it first):

xelatex -output-driver=xdvipdfmx test


xelatex --no-pdf test
xdvipdfmx test.xdv

Note: if you only the the warning

WARNING: Type1 font data returned by OFAStreamPSDownload isn't in the correct format required by the Adobe Type 1Font Format specification.

Then the output will typically look good. [TODO: write that the output has missing text in formulas and picutre, when the above errors occur]

[TODO: write about these errors:

 -   ** WARNING ** Found file "/Library/Fonts/Optima.dfont" for PFB font but it doesn't look like a PFB...
     *** ERROR ** Invalid font: -1 (0)
 -   ** ERROR ** Cannot proceed without the "native" font: CMUSerif-Roman (CMU Serif Roman)...

solution: upgrade to xelatex 0.999.7 or higher]

This article is unfinished.

This is a XeLaTeX related error. The cause of this error is yet unknown.

The solution according to the XeTeX site is to use a different Font. However, I found that even then, I still got problems, presumably because of the fonts in PDF images. So it may also help to change or set to driver for the graphicx package.

Here is how to specify the Computer Modern Unicode (CMU) font (Install using the regular installation method for your operating system, not in the textmf folder. XeLaTeX is able to find system installed fonts!):

\usepackage{fontspec}   % OpenType/TrueType font support. Requires XeTeX; incompatible with inputenc package
% Set default fonts for each series. Computer Modern Unicode, since I have trouble with Latin Modern.
\setmainfont{CMU Serif}
\setsansfont{CMU Sans Serif}
\setmonofont{CMU Typewriter Text}

This is how to specify the xdvipdfmx driver for the graphicx package: