LaTeX output can be very verbose. Just for your reference, here is a (rather long) example of output (taken from the .log file that is created each time anew from every program involved in the process that uses TeX in the background)[1]:
This is TeX, Version 3.14159 (Web2C 7.3.1) (format=jadetex 2001.10.25) 7 JAN 2004 07:26 **EN-Book.tex (EN-Book.tex JadeTeX 2001/07/19: 3.11 LaTeX Font Info: Try loading font information for T1+ptm on input line 1. (/usr/share/texmf/tex/latex/psnfss/t1ptm.fd File: t1ptm.fd 2000/01/12 PSNFSS-v8.1 font definitions for T1/ptm. ) (jadetex.cfg (/usr/share/texmf/tex/generic/babel/babel.sty Package: babel 2001/03/01 v3.7h The Babel package (/usr/share/texmf/tex/generic/babel/english.ldf Language: english 2001/02/07 v3.3k English support from the babel system (/usr/share/texmf/tex/generic/babel/babel.def File: babel.def 2001/03/01 v3.7h Babel common definitions \babel@savecnt=\count114 \U@D=\dimen131 ) \l@canadian = a dialect from \language\l@english )) (/usr/share/texmf/tex/generic/thumbpdf/thumbpdf.sty Package: thumbpdf 2001/04/02 v2.10 Inclusion of thumbnails (HO) Package thumbpdf Warning: You need pdfTeX in PDF mode for driver `pdftex'. ) (/usr/share/texmf/tex/latex/ae/ae.sty Package: ae 1998/11/17 1.0 Almost European Computer Modern (/usr/share/texmf/tex/latex/base/fontenc.sty Package: fontenc 2000/08/30 v1.91 Standard <application>LaTeX</application> package (/usr/share/texmf/tex/latex/base/t1enc.def File: t1enc.def 2000/08/30 v1.91 Standard <application>LaTeX</application> file LaTeX Font Info: Redeclaring font encoding T1 on input line 38. ) LaTeX Font Info: Try loading font information for T1+aer on input line 96. (/usr/share/texmf/tex/latex/ae/t1aer.fd File: t1aer.fd 1997/11/16 Font definitions for T1/aer. ))) (/usr/share/texmf/tex/latex/ae/aecompl.sty Package: aecompl 1998/07/23 0.9 T1 Complements for AE fonts (D. Roegel) ) Package hyperref Info: Option `plainpages' set `false' on input line 128. Package hyperref Info: Option `colorlinks' set `true' on input line 128. Package hyperref Info: Option `bookmarksopen' set `true' on input line 128. Package hyperref Info: Option `colorlinks' set `true' on input line 128. Package hyperref Info: Option `breaklinks' set `true' on input line 128. Package hyperref Warning: Option `pagebackref' has already been used, (hyperref) setting the option has no effect on input line 128. ) Elements will be labelled Jade begin document sequence at 19 |
As you can see from the last line, Jade just started its work. ![]()
It goes on with font checking as follows:
(EN-Book.aux) \openout1 = `EN-Book.aux'. LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for T2A/cmr/m/n on input line 19. LaTeX Font Info: Try loading font information for T2A+cmr on input line 19. (/usr/share/texmf/tex/latex/cyrillic/t2acmr.fd File: t2acmr.fd 1999/01/07 v1.0 Computer Modern Cyrillic font definitions ) LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for TS1/cmr/m/n on input line 19. LaTeX Font Info: Try loading font information for TS1+cmr on input line 19. (/usr/share/texmf/tex/latex/base/ts1cmr.fd File: ts1cmr.fd 1999/05/25 v2.5h Standard <application>LaTeX</application> font definitions ) LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LECO/omseco/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LECX/omsecx/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LECY/omsecy/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LEGR/omsegr/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LEHA/omseha/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LEIP/omseip/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LELA/omsela/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. LaTeX Font Info: Checking defaults for LETI/omseti/m/n on input line 19. LaTeX Font Info: ... okay on input line 19. Package hyperref Info: Link coloring ON on input line 19. (/usr/share/texmf/tex/latex/hyperref/nameref.sty Package: nameref 2000/05/08 v2.18 Cross-referencing by name of section \c@section@level=\count115 ) LaTeX Info: Redefining \ref on input line 19. LaTeX Info: Redefining \pageref on input line 19. LaTeX Font Info: Try loading font information for T1+aess on input line 99. (/usr/share/texmf/tex/latex/ae/t1aess.fd File: t1aess.fd 1997/11/16 Font definitions for T1/aess. ) [1.0.37] File: logo1.eps Graphic file (type eps) <logo1.eps> File: logo2.eps Graphic file (type eps) <logo2.eps> Overfull \hbox (2655.0092pt too wide) in alignment at lines 610--899 |
Somewhere from this point on, you will start seeing LaTeX processing the pages of your document one after the other - and outputting errors and warnings like the “ Overfull \hbox” above.
There are some fairly common error messages and warnings. I'll cover those here using material from the chapter on “ LyX and LaTeX errors” of the Extended Features manual for LyX, available from LyX' Help menu. You should look at a good LaTeX book for a complete listing.
“ LaTeX Warning:“
Anything beginning with these word is a warning message for the purpose of “debugging” the LaTeX code itself. You'll get messages like this if you added or changed cross-references or bibliography entries, in which case, LaTeX is trying to tell you that you need to make another run.
You can by-and-large ignore these.
“ LaTeX Font Warning:”
Another warning message, this time about fonts which LaTeX couldn't find. The rest of the message will often say something about a replacement font that LaTeX used.
You can safely ignore these.
“ Overfull \hbox”
LaTeX absolutely loves to spew these out. They are warning you about lines that were too long and run past the right margin. Almost always, this is unnoticeable in the final output. Or, only one or two characters extend past the margin. LaTeX seems to generate at least one of these messages for just about any document you write.
You can ignore these stupid messages. Your eyes will tell you if there's a problem with something that's too wide; just look at the output.
“ Underfull \hbox”
Not quite as common as its cousin. LaTeX seems to like to print lines that are a bit too wide as opposed to ones that are a bit too narrow. We have no idea why.
You can ignore these, too.
“ Overfull \vbox” and “ Underfull \vbox”
Warnings about troubles breaking the page. Once again, just look at the output. Your eyes will tell you where something has gone wrong.
“ LaTeX Error: File ‘Xxxx’ not found”
The file “Xxxx” isn't installed on this system. This usually appears because some package your document needs isn't installed. If you didn't touch the preamble or didn't use the \usepackage{} command, then one of the packages LyX tried to load is missing. Use Help->La TeX Configuration, to get a list of packages that LyX knows about. This file is updated whenever you reconfigure LyX (using Edit->Reconfigure) and tells you which packages have been detected and what they do.
If you did use the \usepackage{} command, and the package in question isn't installed, you'll need to install it yourself.
“ LaTeX Error: Unknown option”
Error messages beginning with this are trying to tell you that you specified a bad or undefined option to a package. Check the package's documentation.
“Undefined control sequence”
If you've inserted LaTeX code into your document, but made a typo, you'll get one of these. You may have forgotten to load a package. In any case, this error message usually means that you used an undefined command.
LaTeX Error: Undefined color `rtlred'
Theoretically, you can define your own colours in jadetex.cfg. For example, the following block of code defines three new colours, rtlred, rtlblue and rtlgreen (the green being a bit darker than usual):
\usepackage{color}
\definecolor{rltred}{rgb}{0.75,0,0}
\definecolor{rltgreen}{rgb}{0,0.5,0}
\definecolor{rltblue}{rgb}{0,0,0.75}
|
However, no matter where I position this code in jadetex.cfg (i.e. either before or after the call to hypersetup), I get the above error. For the time being, my remedy is to stick to the standard colours. Please inform me if you find a better solution.
Andreas Ekenbäck (private communication) has found that by having double declarations of a colour:
\newcmykcolor{abstractYellow}{0.02 0.02 0.35 0.0}
\definecolor{abstractYellow}{cmyk}{0.02,0.02,0.35,0.0}
|
in jadetex.cfg, it works. On his Fedora Core 4 workstation, he says, it is even enough to have the first declaration.
Further reading: see the chapter on “ LyX and LaTeX errors” of the Extended Features manual for LyX for tips on how to handle LaTeX errors and warnings.
| [1] |
The example is from the processing of the LyX file for the PHP-Nuke HOWTO. Visit the
Homepage of the PHP-Nuke HOWTO to see the result. |
| Last updated Mon Sep 24 01:19:25 CEST 2007 | Permalink: http://www.karakas-online.de/mySGML/latex-errors.html | All contents © 2002-2007 Chris Karakas |