<h1>Why doesn't my processed TeX submission look the way I expected it?</h1> <p>There are a number of common reasons why the processed version of TeX submissions to arXiv may not appear the same as it does when processed locally. In most cases there are fixes that can be applied and the submission replaced to correct the problems.</p> <ul> <li><a href="#toc_links">Lines in the table of contents don&apos;t wrap</a></li> <li><a href="#fuzzy_pdf">Fuzzy fonts in PDF</a></li> <li><a href="#distiller_params">PostScript figures lose quality in the arXiv-generated PDF</a></li> <li><a href="#powerpoint">Extra white space around figures covers up some of the text</a></li> <li><a href="feynmf#nolabel">Why don't the labels for my figures appear when I use Feynmf?</a></li> <li><a href="dvips">Why are the margins different? Why is my text truncated?</a></li> <li><a href="today">Why does my paper give the wrong date?</a></li> <li><a href="citelinks">Why do my citations appear in long form [1,2,3,4] instead of short form [1-4]?</a></li> <li><a href="pd1enc">Why do my user defined symbols (e.g., <tt>\i, \l, \L, \o, \ae,</tt> etc.) display incorrectly in the processed document?</a></li> <li><a href="/help/faq/psbad">Why are there problems with my postscript file?</a></li> <li><a href="/help/faq/pdfrotate">Why are some pages in the generated PDF file rotated and how do I avoid this?</a></li> </ul> <hr noshade /> <br /> <dl> <dt><a name="toc_links"></a><b>Lines in the table of contents don&apos;t wrap</b></dt> <dd> <p>By default, papers are processed with the automatic addition of hyperlinks using the <a href="http://arxiv.org/hypertex">HyperTeX</a> package. Hyperlinks in the table of contents can create a problem with latex's ability to break lines. This problem can be solved by passing the option <code>linktocpage</code> to hyperref. Include the line</p> <pre> \PassOptionsToPackage{linktocpage}{hyperref} </pre> <p>in the preamble. This will create a hyperlink for the the page numbers instead of the whole table of contents line, and thus avoid the line break problem.</p> <p>An alternative solution is to allow hyperref to break links and thus wrap lines. To enable this, add the following to the preamble:</p> <pre> \usepackage[hyperindex,breaklinks]{hyperref} </pre> <br /> </dd> <dt><a name="fuzzy_pdf"></a><b>Fuzzy fonts in PDF</b></dt> <dd> <p>If you use the <code>fontenc</code> package and <code>T1</code> fonts you may find that the fonts appear fuzzy in PDF output from arXiv. Our suggested solution in most cases is to include packages <code>ae</code> and <code>aecompl</code> in the latex source. To do this add 2 additional lines after the <code>fontenc</code> inclusion:</p> <pre> \usepackage[T1]{fontenc} \usepackage{ae} \usepackage{aecompl} </pre> <p>CAREFULLY INSPECT the generated PDF for proper display of accented characters, character omissions, or other peculiarities. These problems can only be spotted by careful visual inspection, something which cannot be expected from arXiv admins and instead has to be performed by the author(s).</p> <p>Here are some pointers to entries in the TeX FAQ that address this issue:</p> <ul> <li><a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf">Quality of PDF from PostScript</a></li> <li><a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1">Fonts go fuzzy when you switch to T1</a></li> <li><a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice">Choice of scalable outline fonts</a></li> <li><a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1">Finding '8-bit' Type 1 fonts</a></li> <li><a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift">Weird characters in dvips output</a></li> </ul> <br /> </dd> <dt><a name="distiller_params"></a><b>PostScript figures lose quality in the arXiv-generated PDF</b></dt> <dd> <p>arXiv uses Ghostscripts's PDF Writer device to generate the PDF versions of TeX submissions. A variety of parameters affects the conversion of PostScript to PDF. In particular bitmap figures are frequently downsampled to the target device resolution, and color spaces are converted as necessary. While arXiv's default settings, the defaults of Ghostscript's PDF Writer device, usually give reasonable quality, some figures may require individual parameter fine tuning for optimal quality of display and/or printout.</p> <p>Clearly arXiv's automated service cannot provide that level of individual tuning for authors. However it is possible to augment PostScript figures with hints (distiller parameters) to be used by the PDF converter. So authors can directly control the resulting image quality themselves via the following modification to their PostScript figure file(s).</p> <p>In the Prolog section of the affected figure(s) insert a text block like:</p> <pre> /setdistillerparams where {pop}{userdict /setdistillerparams {pop} put}ifelse << /AutoFilterColorImages false /AutoFilterGrayImages false /ColorImageFilter /FlateEncode /GrayImageFilter /FlateEncode /UseCIEColor true /ColorACSImageDict .printerACSImageDict >> setdistillerparams </pre> <p>These parameter settings often improve the appearance of (high resolution bitmap) figures in PDFs generated by arXiv. Other parameters are available, however. For a list, see the table available near the end of the Options section of the help page for the Ghostscript PDF Writer device:</p> <p><a href="http://pages.cs.wisc.edu/~ghost/doc/cvs/Ps2pdf.htm#Options">http://pages.cs.wisc.edu/~ghost/doc/cvs/Ps2pdf.htm#Options</a></p> <p>All <tt>ps2pdf</tt> parameters can be set in PostScript prologs via definition of a dictionary (key-value lookup table) as a list of key-value pairs:</p> <pre> /setdistillerparams where {pop}{userdict /setdistillerparams {pop}put}ifelse << /key1 /value1 /key2 /value2 .... >> setdistillerparams </pre> <p>either in a particular PostScript figure or via a literal PostScript <tt>\special</tt> in the TeX source.</p> </dd> <dt><a name="powerpoint"></a><b>Extra white space around figures covers up some of the text</b></dt> <dd> <p> These problems are characteristic of PostScript figures that have been created from PowerPoint. Microsoft PowerPoint does not generate appropriate PostScript code. If you must use PowerPoint to generate figures, you should export the figure to another format such as JPEG. JPEG figures can be included directly using <a href="http://arxiv.org/help/submit_tex#pdflatex">PDFLaTeX</a>, or they can be converted back to PostScript using a program such as '<code><a href="http://arxiv.org/help/bitmap/software#jpeg2ps">jpeg2ps</a></code>'. The '<code>jpeg2ps</code>' program is freely available for all platforms. </dd> </dl>