References for TeX and Friends

<a name=“idp2784336” id=“idp2784336” title=“idp2784336”></a>

Table of Contents $ [[#tex|1 TeX]]: $ 1 PlainTeX: $ [[#plaintex-ovw|1.1 Overview]]: $ 2 LaTeX: $ [[#parameters|2.4 Parameters]]: $ 3 LaTeX Packages: $ [[#small-packages|3.12 Several Small Packages]]: $ 4 Generic Packages: $ [[#pstricks|4.2 PSTricks]]: $ 6 ConTeXt (tbd.): $ [[#context-ovw|6.1 Overview]]: $ 7 Texinfo (tbd.): $ [[#pdftex|2 pdfTeX]]: $ 1 Options: $ [[#pdftex-option-version|1.18 --version]]: $ 2 Environment: $ [[#metapost|4 MetaPost]]: $ 1 Options: $ [[#metapost-option-version|1.14 --version]]: $ 2 Environment: $ [[#bibtex|5 BibTeX]]: $ 3 bib files: $ [[#bibtex-field-types|3.5 Field Types]]: $ 4 bst files: $ 4.5 UNSRT.BST:

$ [[#makeindex|6 Make-Index]]: $ 1 Options: $ [[#makeindex-option-T|1.12 -T]]: $ 2 Style File: $ [[#makeindex-output-style-specs|2.2 Output Style Specifiers]]: $ 5 Special Effects: $ [[#xindy|7 xindy]]: $ 1 Command List: $ [[#xindy-command-list-raw-index|1.3 Raw Index Interface]]: $ 2 Invoking xindy: $ 2.2 Search Path:

• A Appendices $ Index:

List of Tables $ 1.12 Special coordinates and angles:

LaTeX2e is a document preparation system implemented as a macro package for Donald E. Knuth's TeX typesetting program.

LaTeX was originally conceived by Leslie Lamport.

This updated LaTeX reference is by no means complete, but it's a first step towards a more complete LaTeX reference! We welcome if we'll get pointed to missing commands or even better when you make additions and further improvements and send them to the authors.

<a target=“_top” href=“http://www.tug.org”>TUG (TeX User Group)</a> and <a target=“_top” href=“http://www.dante.de”>DANTE (German TeX User Group)</a> both have excellent FAQ's which answer many questions or give great pointers to additional resources both on the internet or in books. Most if not all missing packages can also be found on the CTAN servers.

This reference is not meant to replace the package documentation or the standard literature like the LaTeX handbook and the LaTeX companion. Look there for detailed descriptions of the commands and even mostly more options and examples.

The authors intend to extend this documentation to other TeX related packages (e.g. ConTeXt, MetaPost, Metafont, etc.). Contributions are very welcome!

<a name=“idp6288864” id=“idp6288864” title=“idp6288864”></a>

Table of Contents $ [[#plaintex|1 PlainTeX]]: $ 1.1 Overview: $ [[#latex|2 LaTeX]]: $ 2.4 Parameters: $ [[#latex-packages|3 LaTeX Packages]]: $ 3.12 Several Small Packages: $ [[#generic-packages|4 Generic Packages]]: $ 4.2 PSTricks: $ [[#context|6 ConTeXt (tbd.)]]: $ 6.1 Overview: $ 7 Texinfo (tbd.):

<a name=“idp6293888” id=“idp6293888” title=“idp6293888”></a>

For a really excellent reference of all TeX primitive control sequences see David Bausum's<a name=“idp6297408” id=“idp6297408” title=“idp6297408”></a> <a target=“_top” href=“http://www.tug.org/utilities/plain/cseq.html”> TeX Primitive Control Sequences </a>.

The original file latex2e.texi contains the following copyright and permission notice:

“Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies.”

“Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.”

<a name=“idp6306048” id=“idp6306048” title=“idp6306048”></a>

LaTeX understands the following command line options.

<a name=“idp6309744” id=“idp6309744” title=“idp6309744”></a>

Print error messages in the form file:line:error.

<a name=“idp6314144” id=“idp6314144” title=“idp6314144”></a>

Use FMTMAME instead of program name or a %& line.

<a name=“idp6318544” id=“idp6318544” title=“idp6318544”></a>

Be initex, for dumping formats; this is implicitly true if the program is called as initex.

<a name=“idp6323568” id=“idp6323568” title=“idp6323568”></a>

Set interaction mode (STRING=batchmode/nonstopmode/scrollmode/errorstopmode).

<a name=“idp6327968” id=“idp6327968” title=“idp6327968”></a>

Send DVI output to a socket as well as the usual output file.

Note: not available on all systems.

<a name=“idp6332128” id=“idp6332128” title=“idp6332128”></a>

As -ipc, and also start the server at the other end.

Note: not available on all systems.

<a name=“idp6336912” id=“idp6336912” title=“idp6336912”></a>

Set the job name to STRING.

<a name=“idp6341312” id=“idp6341312” title=“idp6341312”></a>

Sets path searching debugging flags according to the bits of NUMBER.

<a name=“idp6345712” id=“idp6345712” title=“idp6345712”></a>

Disable/enable mktexFMT generation (FMT=tex/tfm).

<a name=“idp6350112” id=“idp6350112” title=“idp6350112”></a>

Enable MLTeX extensions such as \charsubdef.

<a name=“idp6354512” id=“idp6354512” title=“idp6354512”></a>

use STRING for DVI file comment instead of date.

<a name=“idp6358912” id=“idp6358912” title=“idp6358912”></a>

Parse of the first line of the input file.

<a name=“idp6362688” id=“idp6362688” title=“idp6362688”></a>

Set program (and fmt) name to STRING.

<a name=“idp6367088” id=“idp6367088” title=“idp6367088”></a>

Enable filename recorder.

<a name=“idp6370864” id=“idp6370864” title=“idp6370864”></a>

Enable \write18{SHELL COMMAND}.

<a name=“idp6375264” id=“idp6375264” title=“idp6375264”></a>

Insert source specials into the DVI file.

<a name=“idp6379040” id=“idp6379040” title=“idp6379040”></a>

Insert source specials in certain places of the DVI file. WHERE is a comma-separated value list: cr display hbox math par parend vbox.

<a name=“idp6384064” id=“idp6384064” title=“idp6384064”></a>

Use the TCX file TCXNAME.

<a name=“idp6389088” id=“idp6389088” title=“idp6389088”></a>

Display this help and exit.

<a name=“idp6392864” id=“idp6392864” title=“idp6392864”></a>

Output version information and exit.

<a name=“idp6396784” id=“idp6396784” title=“idp6396784”></a><a name=“idp6397536” id=“idp6397536” title=“idp6397536”></a>

The LaTeX command typesets a file of text using the TeX program and the LaTeX Macro package for TeX. To be more specific, it processes an input file containing the text of a document with interspersed commands that describe how the text should be formatted. It produces at least three files as output:

1 <p>A Device Independent, or .dvi file. This contains commands that can be translated into commands for a variety of output devices. You can view the output of LaTeX by using a program such as xdvi, which actually uses the .dvi file.</p> 1 <p>A transcript or .log file that contains summary information and diagnostic messages for any errors discovered in the input file.</p> 1 <p>An auxiliary or .aux file. This is used by LaTeX itself, for things such as sectioning.</p>

For a description of what goes on inside TeX, you should consult The TeXbook by Donald E. Knuth, ISBN 0-201-13448-9, published jointly by the American Mathematical Society and Addison-Wesley Publishing Company.

For a description of LaTeX, you should consult:

LaTeX: A Document Preparation System, by Leslie Lamport,<a name=“idp6411792” id=“idp6411792” title=“idp6411792”></a> Addison-Wesley Publishing Company, 2nd edition, 1994.

The LaTeX Companion, by Michel Goossens,<a name=“idp6413824” id=“idp6413824” title=“idp6413824”></a> Frank Mittelbach, <a name=“idp6414832” id=“idp6414832” title=“idp6414832”></a> and Alexander Samarin,<a name=“idp6415840” id=“idp6415840” title=“idp6415840”></a> Addison-Wesley, 1994.

A LaTeX command begins with the command name, which consists of a \ followed by either (a) a string of letters or (b) a single non-letter. Arguments contained in square brackets, [], are optional while arguments contained in braces, {}, are required.

NOTE: LaTeX is case sensitive. Enter all commands in lower case unless explicitly directed to do otherwise.

<a name=“idp6423008” id=“idp6423008” title=“idp6423008”></a><a name=“idp6423760” id=“idp6423760” title=“idp6423760”></a>

Everything LaTeX numbers for you has a counter associated with it. The name of the counter is the same as the name of the environment or command that produces the number, except with no \ (enumi - enumiv are used for the nested enumerate environment). Below is a list of the counters used in LaTeX's standard document classes to control numbering.

part            paragraph       figure          enumi chapter         subparagraph    table           enumii section         page            footnote        enumiii subsection      equation        mpfootnote      enumiv subsubsection 

<a name=“idp6429968” id=“idp6429968” title=“idp6429968”></a>

The \addtocounter command increments the counter by the amount specified by the value argument. The value argument can be negative.

<a name=“idp6434832” id=“idp6434832” title=“idp6434832”></a><a name=“idp6435584” id=“idp6435584” title=“idp6435584”></a>

This command causes the value of the counter to be printed in alphabetic characters. The \alph command uses lower case alphabetic alphabetic characters, i.e., a, b, c… while the \Alph command uses upper case alphabetic characters, i.e., A, B, C….

<a name=“idp6441072” id=“idp6441072” title=“idp6441072”></a>

The \arabic command causes the value of the counter to be printed in Arabic numbers, i.e., 3.

<a name=“idp6445312” id=“idp6445312” title=“idp6445312”></a>

The \fnsymbol command causes the value of the counter to be printed in a specific sequence of nine symbols that can be used for numbering footnotes.

NB. counter must have a value between 1 and 9 inclusive.

<a name=“idp6450064” id=“idp6450064” title=“idp6450064”></a><a name=“idp6450816” id=“idp6450816” title=“idp6450816”></a>

The \newcounter command defines a new counter named foo. The counter is initialized to zero.

The optional argument [counter] causes the counter foo to be reset whenever the counter named in the optional argument is incremented.

<a name=“idp6456176” id=“idp6456176” title=“idp6456176”></a>

The \refstepcounter command works like \stepcounter. See <a href=“#cmd-stepcounter-title” title=“2.3.1. \stepcounter{counter}”>\stepcounter</a>, except it also defines the current \ref value to be the result of \thecounter.

<a name=“idp6473968” id=“idp6473968” title=“idp6473968”></a><a name=“idp6474720” id=“idp6474720” title=“idp6474720”></a>

This command causes the value of the counter to be printed in Roman numerals. The \roman command uses lower case Roman numerals, i.e., i, ii, iii…, while the \Roman command uses upper case Roman numerals, i.e., I, II, III….

<a name=“idp6480368” id=“idp6480368” title=“idp6480368”></a>

The \stepcounter command adds one to the counter and resets all subsidiary counters.

<a name=“idp6483984” id=“idp6483984” title=“idp6483984”></a><a name=“idp6484736” id=“idp6484736” title=“idp6484736”></a>

The \setcounter command sets the value of the counter to that specified by the value argument.

<a name=“idp6488976” id=“idp6488976” title=“idp6488976”></a>

The \usecounter command is used in the second argument of the list environment to allow the counter specified to be used to number the list items.

<a name=“idp6492784” id=“idp6492784” title=“idp6492784”></a><a name=“idp6493536” id=“idp6493536” title=“idp6493536”></a>

The \value command produces the value of the counter named in the mandatory argument. It can be used where LaTeX expects an integer or number, such as the second argument of a \setcounter or \addtocounter command, or in:

\hspace{\value{foo}\parindent} 

It is useful for doing arithmetic with counters.

<a name=“idp6499984” id=“idp6499984” title=“idp6499984”></a>

One reason for numbering things like figures and equations is to refer the reader to them, as in See Figure 3 for more details. A smarter version of the cross reference commands is available in the package <a href=“#varioref” title=“3.11 varioref”>varioref</a>.

<a name=“idp6503968” id=“idp6503968” title=“idp6503968”></a>

A \label command appearing in ordinary text assigns to the key the number of the current sectional unit; one appearing inside a numbered environment assigns that number to the key.

A key can consist of any sequence of letters, digits, or punctuation characters. Upper and lowercase letters are different.

To avoid accidentally creating two labels with the same name, it is common to use labels consisting of a prefix and a suffix separated by a colon. The prefixes conventionally used are

• cha for chapters
• sec for lower-level sectioning commands
• fig for figures
• tab for tables
• eq for equations

Thus, a label for a figure would look like fig:bandersnatch.

<a name=“idp6518144” id=“idp6518144” title=“idp6518144”></a><a name=“idp6518896” id=“idp6518896” title=“idp6518896”></a>

The \pageref command produces the page number of the place in the text where the corresponding \label command appears. ie. where \label{key} appears. For a smart version see \vpageref.

<a name=“idp6524240” id=“idp6524240” title=“idp6524240”></a><a name=“idp6524992” id=“idp6524992” title=“idp6524992”></a>

The \ref command produces the number of the sectional unit, equation number, … of the corresponding \label command. For a smart version see \vref.

<a name=“idp6530864” id=“idp6530864” title=“idp6530864”></a><a name=“idp6531616” id=“idp6531616” title=“idp6531616”></a><a name=“idp6532368” id=“idp6532368” title=“idp6532368”></a> <pre>\newcommand{cmd}[args]{definition} \newcommand{cmd}[args][default]{definition} \renewcommand{cmd}[args]{definition} \renewcommand{cmd}[args][default]{definition} </pre>

These commands define (or redefine) a command.

<a name=“table-newcommand” id=“table-newcommand” title=“table-newcommand”></a>

Table 1.1. Options for \newcommand

<table summary=“Options for \newcommand” border=“0”> <tbody> <tr> <td align=“left”>cmd</td> <td align=“justify”>A command name beginning with a \. For \newcommand it must not be already defined and must not begin with \end; for \renewcommand it must already be defined.</td> </tr> <tr> <td align=“left”>args</td> <td align=“justify”>An integer from 1 to 9 denoting the number of arguments of the command being defined. The default is for the command to have no arguments.</td> </tr> <tr> <td align=“left”>def</td> <td align=“justify”>If this optional parameter is present, it means that the command's first argument is optional. The default value of the optional argument is def.</td> </tr> <tr> <td align=“left”>definition</td> <td align=“justify”>The text to be substituted for every occurrence of cmd; a parameter of the form #n in cmd is replaced by the text of the nth argument when this substitution takes place.</td> </tr> </tbody> </table>

<br />

<a name=“idp6551168” id=“idp6551168” title=“idp6551168”></a><a name=“idp6551920” id=“idp6551920” title=“idp6551920”></a><a name=“idp6552672” id=“idp6552672” title=“idp6552672”></a> <pre>\newenvironment{nam}[args]{begdef}{enddef} \newenvironment{nam}[args][default]{begdef}{enddef} \renewenvironment{nam}[args]{begdef}{enddef} </pre>

These commands define or redefine an environment.

<a name=“table-newenvironment” id=“table-newenvironment” title=“table-newenvironment”></a>

Table 1.2. Options for \newenvironment

<table summary=“Options for \newenvironment” border=“0”> <tbody> <tr> <td align=“left”>nam</td> <td align=“justify”>The name of the environment. For \newenvironment there must be no currently defined environment by that name, and the command \nam must be undefined. For \renewenvironment the environment must already be defined.</td> </tr> <tr> <td align=“left”>args</td> <td align=“justify”>An integer from 1 to 9 denoting the number of arguments of the newly-defined environment. The default is no arguments. Arguments can only be used in te {begdef} part.</td> </tr> <tr> <td align=“left”>default</td> <td align=“justify”>If this is specified, the first argument is optional, and default gives the default value for that argument.</td> </tr> <tr> <td align=“left”>begdef</td> <td align=“justify”>The text substituted for every occurrence of \begin{nam}; a parameter of the form #n in cmd is replaced by the text of the nth argument when this substitution takes place.</td> </tr> <tr> <td align=“left”>enddef</td> <td align=“justify”>The text substituted for every occurrence of \end{nam}. It may not contain any argument parameters.</td> </tr> </tbody> </table>

<br />

<a name=“idp6573200” id=“idp6573200” title=“idp6573200”></a><a name=“idp6573952” id=“idp6573952” title=“idp6573952”></a><a name=“idp6574704” id=“idp6574704” title=“idp6574704”></a> <pre>\newtheorem{env_name}{caption}[within] \newtheorem{env_name}[numbered_like]{caption} </pre>

This command defines a theorem-like environment.

<a name=“table-newtheorem” id=“table-newtheorem” title=“table-newtheorem”></a>

Table 1.3. Options for \newtheorem

<table summary=“Options for \newtheorem” border=“0”> <tbody> <tr> <td align=“left”>env_name</td> <td align=“justify”>The name of the environment to be defined. A string of letters. It must not be the name of an existing environment or counter.</td> </tr> <tr> <td align=“left”>caption</td> <td align=“justify”>The text printed at the beginning of the environment, right before the number. This may simply say Theorem, for example.</td> </tr> <tr> <td align=“left”>within</td> <td align=“justify”>The name of an already defined counter, usually of a sectional unit. Provides a means of resetting the new theorem counter within the sectional unit.</td> </tr> <tr> <td align=“left”>numbered_like</td> <td align=“justify”>The name of an already defined theorem-like environment.</td> </tr> </tbody> </table>

The \newtheorem command may have at most one optional argument.

<a name=“idp6590208” id=“idp6590208” title=“idp6590208”></a><a name=“idp6590960” id=“idp6590960” title=“idp6590960”></a><a name=“idp6591712” id=“idp6591712” title=“idp6591712”></a>

\newfont{cmd}{font_name}

Defines the command name cmd, which must not be currently defined, to be a declaration that selects the font named font_name to be the current font.

<a name=“idp6596336” id=“idp6596336” title=“idp6596336”></a><a name=“idp6597088” id=“idp6597088” title=“idp6597088”></a><a name=“idp6597840” id=“idp6597840” title=“idp6597840”></a><a name=“idp6598592” id=“idp6598592” title=“idp6598592”></a><a name=“idp6599344” id=“idp6599344” title=“idp6599344”></a><a name=“idp6600096” id=“idp6600096” title=“idp6600096”></a><a name=“idp6600848” id=“idp6600848” title=“idp6600848”></a>

Valid LaTeX document classes include:

• article
• report
• letter
• book
• slides

Other document classes are often available. See <a href=“#overview” title=“2.2 Overview of LaTeX and Local Guide”>Overview</a>, for details. They are selected with the following command:

\documentclass [options] {class}

All the standard classes (except slides) accept the following options for selecting the typeface size (10pt is default):

10pt, 11pt, 12pt

All classes accept these options for selecting the paper size (default is letter):

a4paper, a5paper, b5paper, letterpaper, legalpaper, executivepaper

Miscellaneous options:

• landscape — selects landscape format. Default is portrait.
• titlepage, notitlepage — selects if there should be a separate title page.
• leqno — equation number on left side of equations. Default is right side.
• fleqn — displayed formulas flush left. Default is centered.
• openbib — use open bibliography format.
• draft, final — mark/do not mark overfull boxes with a rule. Default is final.

These options are not available with the slides class:

• oneside, twoside — selects one- or twosided layout. Default is oneside, except for the book class.
• openright, openany — determines if a chapter should start on a right-hand page. Default is openright for book.
• onecolumn, twocolumn — one or two columns. Defaults to one column.

The slides class offers the option clock for printing the time at the bottom of each note.

If you specify more than one option, they must be separated by a comma.

Additional packages are loaded by a

<a name=“usepackage-linkend” id=“usepackage-linkend” title=“usepackage-linkend”></a> \usepackage[options]{pkg} <a name=“idp6624320” id=“idp6624320” title=“idp6624320”></a>

command. If you specify more than one package, they must be separated by a comma. <a name=“idp6625568” id=“idp6625568” title=“idp6625568”></a> <a name=“idp6626320” id=“idp6626320” title=“idp6626320”></a>

Any options given in the \documentclass command that are unknown by the selected document class are passed on to the packages loaded with \usepackage. <a name=“idp6628832” id=“idp6628832” title=“idp6628832”></a> <a name=“idp6629584” id=“idp6629584” title=“idp6629584”></a> <a name=“idp6630464” id=“idp6630464” title=“idp6630464”></a>

Miscellaneous commands for controlling the general layout of the page.

<a name=“idp6634176” id=“idp6634176” title=“idp6634176”></a>

The \flushbottom declaration makes all text pages the same height, adding extra vertical space when necessary to fill out the page.

This is the standard if twocolumn mode is selected.

<a name=“idp6637696” id=“idp6637696” title=“idp6637696”></a>

The \onecolumn declaration starts a new page and produces single-column output.

<a name=“idp6640784” id=“idp6640784” title=“idp6640784”></a>

The \raggedbottom declaration makes all pages the height of the text on that page. No extra vertical space is added.

<a name=“idp6643904” id=“idp6643904” title=“idp6643904”></a><a name=“idp6644656” id=“idp6644656” title=“idp6644656”></a>

\twocolumn[text]

The \twocolumn declaration starts a new page and produces two-column output. If the optional text argument is present, it is typeset in one-column mode.

<a name=“idp6649616” id=“idp6649616” title=“idp6649616”></a><a name=“idp6650368” id=“idp6650368” title=“idp6650368”></a><a name=“idp6651120” id=“idp6651120” title=“idp6651120”></a>

LaTeX provides a number of different paragraph-making environments. Each environment begins and ends in the same manner.

\begin{environment-name}  .  .  . \end{environment-name} 

<a name=“idp6654224” id=“idp6654224” title=“idp6654224”></a><a name=“idp6654976” id=“idp6654976” title=“idp6654976”></a> <pre>\begin{array}{col1col2…coln} column 1 entry & column 2 entry … & column n entry
. . . \end{array} </pre>

Math arrays are produced with the array environment. It has a single mandatory argument describing the number of columns and the alignment within them. Each column, coln, is specified by a single letter that tells how items in that row should be formatted.

• c — for centered
• l — for flush left
• r — for flush right

Column entries must be separated by an &. Column entries may include other LaTeX commands. Each row of the array must be terminated with the string \\.

Note that the array environment can only be used in math mode, so normally it is used inside an equation environment.

<a name=“idp6667472” id=“idp6667472” title=“idp6667472”></a><a name=“idp6668224” id=“idp6668224” title=“idp6668224”></a> <pre>\begin{center} Text on line 1
Text on line 2
. . . \end{center} </pre>

The center environment allows you to create a paragraph consisting of lines that are centered within the left and right margins on the current page. Each line must be terminated with the string \\.

<a name=“idp6672784” id=“idp6672784” title=“idp6672784”></a><a name=“idp6673536” id=“idp6673536” title=“idp6673536”></a><a name=“idp6674288” id=“idp6674288” title=“idp6674288”></a>

This declaration corresponds to the center environment. This declaration can be used inside an environment such as quote or in a parbox. The text of a figure or table can be centered on the page by putting a \centering command at the beginning of the figure or table environment.

Unlike the center environment, the \centering command does not start a new paragraph; it simply changes how LaTeX formats paragraph units. To affect a paragraph unit's format, the scope of the declaration must contain the blank line or \end command (of an environment like quote) that ends the paragraph unit.

<a name=“idp6682416” id=“idp6682416” title=“idp6682416”></a><a name=“idp6683168” id=“idp6683168” title=“idp6683168”></a> <pre>\begin{description} \item [label] First item \item [label] Second item . . . \end{description} </pre>

The description environment is used to make labelled lists. The label is bold face and flushed right.

<a name=“idp6687600” id=“idp6687600” title=“idp6687600”></a><a name=“idp6688352” id=“idp6688352” title=“idp6688352”></a> <pre>\begin{enumerate} \item First item \item Second item . . . \end{enumerate} </pre>

The enumerate environment produces a numbered list. Enumerations can be nested within one another, up to four levels deep. They can also be nested within other paragraph-making environments.

Each item of an enumerated list begins with an \item command. There must be at least one \item command within the environment.

The enumerate environment uses the enumi through enumiv counters (see <a href=“#counters” title=“2.3.1 Counters”>Counters</a>). The type of numbering can be changed by redefining \theenumi etc.

<a name=“idp6697488” id=“idp6697488” title=“idp6697488”></a><a name=“idp6698240” id=“idp6698240” title=“idp6698240”></a><a name=“idp6698992” id=“idp6698992” title=“idp6698992”></a> <pre>\begin{eqnarray} math formula 1 \\ math formula 2 \\ . . . \end{eqnarray} </pre>

The eqnarray environment is used to display a sequence of equations or inequalities. It is very much like a three-column array environment, with consecutive rows separated by
and consecutive items within a row separated by an &.

An equation number is placed on every line unless that line has a \nonumber command. <a name=“idp6704656” id=“idp6704656” title=“idp6704656”></a>

The command \lefteqn is used for splitting long formulas across lines. It typesets its argument in display style flush left in a box of zero width.

<a name=“idp6707808” id=“idp6707808” title=“idp6707808”></a><a name=“idp6708560” id=“idp6708560” title=“idp6708560”></a><a name=“idp6709312” id=“idp6709312” title=“idp6709312”></a> <pre>\begin{equation} math formula \end{equation} </pre>

The equation environment centers your equation on the page and places the equation number in the right margin.

<a name=“idp6713056” id=“idp6713056” title=“idp6713056”></a><a name=“idp6713808” id=“idp6713808” title=“idp6713808”></a> <pre>\begin{figure}[placement] body of the figure \caption{figure title} \end{figure} </pre> <a name=“idp6715280” id=“idp6715280” title=“idp6715280”></a>

Figures are objects that are not part of the normal text, and are usually floated to a convenient place, like the top of a page. Figures will not be split between two pages.

The optional argument [placement] determines where LaTeX will try to place your figure. There are four places where LaTeX can possibly put a float:

1 <p>h (Here) - at the position in the text where the figure environment appears.</p> 1 <p>t (Top) - at the top of a text page.</p> 1 <p>b (Bottom) - at the bottom of a text page.</p> 1 <p>p (Page of floats) - on a separate float page, which is a page containing no text, only floats.</p>

The standard report and article classes use the default placement tbp.

The body of the figure is made up of whatever text, LaTeX commands, etc. you wish. The \caption command allows you to title your figure.

<a name=“idp6728816” id=“idp6728816” title=“idp6728816”></a><a name=“idp6729568” id=“idp6729568” title=“idp6729568”></a><a name=“idp6730320” id=“idp6730320” title=“idp6730320”></a> <pre>\begin{flushleft} Text on line 1
Text on line 2
. . . \end{flushleft} </pre>

The flushleft environment allows you to create a paragraph consisting of lines that are flushed left, to the left-hand margin. Each line must be terminated with the string \\.

<a name=“idp6734864” id=“idp6734864” title=“idp6734864”></a><a name=“idp6735616” id=“idp6735616” title=“idp6735616”></a><a name=“idp6736368” id=“idp6736368” title=“idp6736368”></a><a name=“idp6737120” id=“idp6737120” title=“idp6737120”></a>

This declaration corresponds to the flushleft environment. This declaration can be used inside an environment such as quote or in a parbox.

Unlike the flushleft environment, the \raggedright command does not start a new paragraph; it simply changes how LaTeX formats paragraph units. To affect a paragraph unit's format, the scope of the declaration must contain the blank line or \end command (of an environment like quote) that ends the paragraph unit.

<a name=“idp6744448” id=“idp6744448” title=“idp6744448”></a><a name=“idp6745200” id=“idp6745200” title=“idp6745200”></a><a name=“idp6745952” id=“idp6745952” title=“idp6745952”></a> <pre>\begin{flushright} Text on line 1
Text on line 2
. . . \end{flushright} </pre>

The flushright environment allows you to create a paragraph consisting of lines that are flushed right, to the right-hand margin. Each line must be terminated with the string \\.

<a name=“idp6750480” id=“idp6750480” title=“idp6750480”></a><a name=“idp6751232” id=“idp6751232” title=“idp6751232”></a><a name=“idp6751984” id=“idp6751984” title=“idp6751984”></a><a name=“idp6752736” id=“idp6752736” title=“idp6752736”></a>

This declaration corresponds to the flushright environment. This declaration can be used inside an environment such as quote or in a parbox.

Unlike the flushright environment, the \raggedleft command does not start a new paragraph; it simply changes how LaTeX formats paragraph units. To affect a paragraph unit's format, the scope of the declaration must contain the blank line or \end command (of an environment like quote) that ends the paragraph unit.

<a name=“idp6760064” id=“idp6760064” title=“idp6760064”></a><a name=“idp6760816” id=“idp6760816” title=“idp6760816”></a><a name=“idp6761568” id=“idp6761568” title=“idp6761568”></a> <pre>\begin{itemize} \item First item \item Second item . . . \end{itemize} </pre>

The itemize environment produces a bulleted list. Itemizations can be nested within one another, up to four levels deep. They can also be nested within other paragraph-making environments.

Each item of an itemized list begins with an \item command. There must be at least one \item command within the environment.

The itemize environment uses the itemi through itemiv counters (see <a href=“#counters” title=“2.3.1 Counters”>Counters</a>). The type of numbering can be changed by redefining \theitemi etc.

<a name=“idp6771680” id=“idp6771680” title=“idp6771680”></a>

This environment is used for creating letters. See <a href=“#letters” title=“2.3.9 Letters”>Letters</a>.

<a name=“idp6774752” id=“idp6774752” title=“idp6774752”></a><a name=“idp6775504” id=“idp6775504” title=“idp6775504”></a>

The list environment is a generic environment which is used for defining many of the more specific environments. It is seldom used in documents, but often in macros.

\begin{list}{label}{spacing} \item First item \item Second item  .  .  . \end{list} 

The {label} argument specifies how items should be labelled. This argument is a piece of text that is inserted in a box to form the label. This argument can and usually does contain other LaTeX commands.

The {spacing} argument contains commands to change the spacing parameters for the list. This argument will most often be null, i.e., {}. This will select all default spacing which should suffice for most cases.

<a name=“idp6782912” id=“idp6782912” title=“idp6782912”></a><a name=“idp6783664” id=“idp6783664” title=“idp6783664”></a><a name=“idp6784416” id=“idp6784416” title=“idp6784416”></a><a name=“idp6785168” id=“idp6785168” title=“idp6785168”></a> <pre>\begin{minipage}[position][height][inner-pos]{width} text \end{minipage} </pre>

The minipage environment is similar to a \parbox command. It takes the same optional position argument and mandatory width argument. You may use other paragraph-making environments inside a minipage.

Footnotes in a minipage environment are handled in a way that is particularly useful for putting footnotes in figures or tables. A \footnote or \footnotetext command puts the footnote at the bottom of the minipage instead of at the bottom of the page, and it uses the mpfootnote counter instead of the ordinary footnote counter See <a href=“#counters” title=“2.3.1 Counters”>Counters</a>.

NOTE: Don't put one minipage inside another if you are using footnotes; they may wind up at the bottom of the wrong minipage.

<a name=“idp6795824” id=“idp6795824” title=“idp6795824”></a><a name=“idp6796576” id=“idp6796576” title=“idp6796576”></a><a name=“idp6797328” id=“idp6797328” title=“idp6797328”></a> <pre>\begin{picture}(width,height)(x offset,y offset) . . picture commands . . \end{picture} </pre>

The picture environment allows you to create just about any kind of picture you want containing text, lines, arrows and circles. You tell LaTeX where to put things in the picture by specifying their coordinates. A coordinate is a number that may have a decimal point and a minus sign — a number like 5, 2.3 or -3.1416. A coordinate specifies a length in multiples of the unit length \unitlength, so if \unitlength has been set to 1cm, then the coordinate 2.54 specifies a length of 2.54 centimetres. You can change the value of \unitlength anywhere you want, using the \setlength command, but strange things will happen if you try changing it inside the picture environment.

A position is a pair of coordinates, such as (2.4,-5), specifying the point with x-coordinate 2.4 and y-coordinate -5. Coordinates are specified in the usual way with respect to an origin, which is normally at the lower-left corner of the picture. Note that when a position appears as an argument, it is not enclosed in braces; the parentheses serve to delimit the argument.

The picture environment has one mandatory argument, which is a position. It specifies the size of the picture. The environment produces a rectangular box with width and height determined by this argument's x- and y-coordinates.

The picture environment also has an optional position argument, following the size argument, that can change the origin. (Unlike ordinary optional arguments, this argument is not contained in square brackets.) The optional argument gives the coordinates of the point at the lower-left corner of the picture (thereby determining the origin). For example, if \unitlength has been set to 1mm, the command

\begin{picture}(100,200)(10,20) 

produces a picture of width 100 millimetres and height 200 millimetres, whose lower-left corner is the point (10,20) and whose upper-right corner is therefore the point (110,220). When you first draw a picture, you will omit the optional argument, leaving the origin at the lower-left corner. If you then want to modify your picture by shifting everything, you just add the appropriate optional argument.

The environment's mandatory argument determines the nominal size of the picture. This need bear no relation to how large the picture really is; LaTeX will happily allow you to put things outside the picture, or even off the page. The picture's nominal size is used by LaTeX in determining how much room to leave for it.

Everything that appears in a picture is drawn by the \put command. The command

\put (11.3,-.3){...} 

puts the object specified by … in the picture, with its reference point at coordinates (11.3,-.3). The reference points for various objects will be described below.

The \put command creates an LR box. You can put anything in the text argument of the \put command that you'd put into the argument of an \mbox and related commands. When you do this, the reference point will be the lower left corner of the box.

Picture commands:

<a name=“idp6824048” id=“idp6824048” title=“idp6824048”></a>

The \circle command produces a circle with a diameter as close to the specified one as possible. If the *-form of the command is used, LaTeX draws a solid circle.

Note that only circles up to 40 pt can be drawn.

<a name=“idp6828560” id=“idp6828560” title=“idp6828560”></a>

Draws a box with a dashed line.

\dashbox{dash_length}(width,height){…}

The \dashbox has an extra argument which specifies the width of each dash. A dashed box looks best when the width and height are multiples of the dash_length.

<a name=“idp6834816” id=“idp6834816” title=“idp6834816”></a>

The \frame command puts a rectangular frame around the object specified in the argument. The reference point is the bottom left corner of the frame. No extra space is put between the frame and the object.

<a name=“idp6838048” id=“idp6838048” title=“idp6838048”></a>

The \framebox command is exactly the same as the \makebox command, except that it puts a frame around the outside of the box that it creates.

The framebox command produces a rule of thickness \fboxrule, and leaves a space \fboxsep between the rule and the contents of the box.

<a name=“idp6844032” id=“idp6844032” title=“idp6844032”></a>

The \line command draws a line of the specified length and slope.

Note that LaTeX can only draw lines with slope = x/y, where x and y have integer values from -6 through 6.

<a name=“idp6849168” id=“idp6849168” title=“idp6849168”></a>

Declares the thickness of horizontal and vertical lines in a picture environment to be dimension, which must be a positive length. It does not affect the thickness of slanted lines and circles, or the quarter circles drawn by \oval to form the corners of an oval.

<a name=“idp6853072” id=“idp6853072” title=“idp6853072”></a>

The \makebox command for the picture environment is similar to the normal \makebox command except that you must specify a width and height in multiples of \unitlength.

The optional argument, [position], specifies the quadrant that your text appears in. You may select up to two of the following:

• t - Moves the item to the top of the rectangle
• b - Moves the item to the bottom
• l - Moves the item to the left
• r - Moves the item to the right

See <a href=“#cmd-makebox” title=“2.3.17. \makebox”>\makebox</a>.

<a name=“idp6866560” id=“idp6866560” title=“idp6866560”></a>

The \multiput command can be used when you are putting the same object in a regular pattern across a picture.

<a name=“idp6869680” id=“idp6869680” title=“idp6869680”></a>

The \oval command produces a rectangle with rounded corners. The optional argument, [portion], allows you to select part of the oval.

• t - Selects the top portion
• b - Selects the bottom portion
• r - Selects the right portion
• l - Selects the left portion

Note that the corners of the oval are made with quarter circles with a maximum radius of 20 pt, so large ovals will look more like boxes with rounded corners.

<a name=“idp6880432” id=“idp6880432” title=“idp6880432”></a>

The \put command places the item specified by the mandatory argument at the given coordinates.

<a name=“idp6883536” id=“idp6883536” title=“idp6883536”></a>

The \shortstack command produces a stack of objects. The valid positions are:

• r - Moves the objects to the right of the stack
• l - Moves the objects to the left of the stack
• c - Moves the objects to the centre of the stack (default)

<a name=“idp6891200” id=“idp6891200” title=“idp6891200”></a>

The \vector command draws a line with an arrow of the specified length and slope. The x and y values must lie between -4 and +4, inclusive.

<a name=“idp6895536” id=“idp6895536” title=“idp6895536”></a><a name=“idp6896288” id=“idp6896288” title=“idp6896288”></a><a name=“idp6897040” id=“idp6897040” title=“idp6897040”></a> <pre>\begin{quotation} text \end{quotation} </pre>

The margins of the quotation environment are indented on the left and the right. The text is justified at both margins and there is paragraph indentation. Leaving a blank line between text produces a new paragraph.

<a name=“idp6900880” id=“idp6900880” title=“idp6900880”></a><a name=“idp6901632” id=“idp6901632” title=“idp6901632”></a><a name=“idp6902384” id=“idp6902384” title=“idp6902384”></a> <pre>\begin{quote} text \end{quote} </pre>

The margins of the quote environment are indented on the left and the right. The text is justified at both margins. Leaving a blank line between text produces a new paragraph.

<a name"idp6906192" id="idp6906192" title="idp6906192"></a><a name="idp6906944" id="idp6906944" title="idp6906944"></a><a name="idp6907696" id="idp6907696" title="idp6907696"></a> <pre>\begin{tabbing} text \ more text \= still more text \= last text
second row \> \> more
. . . \end{tabbing} </pre>

The tabbing environment provides a way to align text in columns. It works by setting tab stops and tabbing to them much the way you do with an ordinary typewriter.

It is best suited for cases where the width of each column is constant and known in advance.

This environment can be broken across pages, unlike the tabular environment.

The following commands can be used inside a tabbing environment:

<a name=“table-tabbing” id=“table-tabbing” title=“table-tabbing”></a>

Table 1.4. Commands in a tabbing environment

<table summary"Commands in a tabbing environment" border="0"> <tbody> <tr> <td align="left">\ <a name"idp6917632" id="idp6917632" title="idp6917632"></a></td> <td align="justify">Sets a tab stop at the current position.</td> </tr> <tr> <td align="left">\> <a name="idp6919648" id="idp6919648" title="idp6919648"></a></td> <td align="justify">Advances to the next tab stop.</td> </tr> <tr> <td align="left">\< <a name="idp6921664" id="idp6921664" title="idp6921664"></a></td> <td align="justify">This command allows you to put something to the left of the local margin without changing the margin. Can only be used at the start of the line.</td> </tr> <tr> <td align="left">\+ <a name="idp6923872" id="idp6923872" title="idp6923872"></a></td> <td align="justify">Moves the left margin of the next and all the following commands one tab stop to the right.</td> </tr> <tr> <td align="left">\- <a name="idp6926016" id="idp6926016" title="idp6926016"></a></td> <td align="justify">Moves the left margin of the next and all the following commands one tab stop to the left.</td> </tr> <tr> <td align="left">\' <a name="idp6928160" id="idp6928160" title="idp6928160"></a></td> <td align="justify">Moves everything that you have typed so far in the current column, i.e. everything from the most recent \>, \<, \', \\, or \kill command, to the right of the previous column, flush against the current column's tab stop.</td> </tr> <tr> <td align="left">\` <a name="idp6933568" id="idp6933568" title="idp6933568"></a></td> <td align="justify">Allows you to put text flush right against any tab stop, including tab stop 0. However, it can't move text to the right of the last column because there's no tab stop there. The \` command moves all the text that follows it, up to the \\ or \end{tabbing} command that ends the line, to the right margin of the tabbing environment. There must be no \> or \' command between the \` and the command that ends the line.</td> </tr> <tr> <td align="left">\kill <a name="idp6939776" id="idp6939776" title="idp6939776"></a></td> <td align="justify">Sets tab stops without producing text. Works just like \\ except that it throws away the current line instead of producing output for it. The effect of any \, \+ or \- commands in that line remain in effect.</td> </tr> <tr> <td align"left">\pushtabs <a name="idp6944512" id="idp6944512" title="idp6944512"></a></td> <td align="justify">Saves all current tab stop positions. Useful for temporarily changing tab stop positions in the middle of a tabbing environment.</td> </tr> <tr> <td align="left">\poptabs <a name="idp6947296" id="idp6947296" title="idp6947296"></a></td> <td align="justify">Restores the tab stop positions saved by the last \pushtabs.</td> </tr> <tr> <td align="left">\a <a name="idp6950016" id="idp6950016" title="idp6950016"></a></td> <td align="justify">In a tabbing environment, the commands \, \' and \` do not produce accents as normal. Instead, the commands \a=, \a' and \a` are used.</td> </tr> </tbody> </table>

This example typesets a Pascal function in a traditional format:

\begin{tabbing} function \= fact(n : integer) : integer;\\     \> begin \= \+ \\         \> if \= n $>$ 1 then \+ \\                   fact := n * fact(n-1) \- \\               else \+ \\                   fact := 1; \-\- \\               end;\\ \end{tabbing} 

<a name=“idp6959168” id=“idp6959168” title=“idp6959168”></a><a name=“idp6959920” id=“idp6959920” title=“idp6959920”></a><a name=“idp6960672” id=“idp6960672” title=“idp6960672”></a> <pre>\begin{table}[placement] body of the table \caption{table title} \end{table} </pre>

Tables are objects that are not part of the normal text, and are usually floated to a convenient place, like the top of a page. Tables will not be split between two pages.

The optional argument [placement] determines where LaTeX will try to place your table. There are four places where LaTeX can possibly put a float:

• h : Here - at the position in the text where the table environment appears.
• t : Top - at the top of a text page.
• b : Bottom - at the bottom of a text page.
• p : Page of floats - on a separate float page, which is a page containing no text, only floats.

The standard report and article classes use the default placement [tbp].

The body of the table is made up of whatever text, LaTeX commands, etc., you wish. The \caption command allows you to title your table.

<a name=“idp6975872” id=“idp6975872” title=“idp6975872”></a><a name=“idp6976624” id=“idp6976624” title=“idp6976624”></a><a name=“idp6977376” id=“idp6977376” title=“idp6977376”></a> <pre>\begin{tabular}[pos]{cols} column 1 entry & column 2 entry … & column n entry
. . . \end{tabular} </pre>

or

\begin{tabular*}{width}[pos]{cols} column 1 entry & column 2 entry ... & column n entry \\  .  .  . \end{tabular*} 

These environments produce a box consisting of a sequence of rows of items, aligned vertically in columns. The mandatory and optional arguments consist of:

<a name=“table-tabular” id=“table-tabular” title=“table-tabular”></a>

Table 1.5. Commands used inside a tabular environment

<table summary=“Commands used inside a tabular environment” border=“0”> <tbody> <tr> <td align=“left”>width</td> <td align=“justify”>Specifies the width of the tabular* environment. There must be rubber space between columns that can stretch to fill out the specified width.</td> </tr> <tr> <td align=“left”>pos</td> <td align=“justify”>Specifies the vertical position; default is alignment on the centre of the environment.

• t - align on top row
• b - align on bottom row

</td> </tr> <tr> <td align=“left”>cols</td> <td align=“justify”>Specifies the column formatting. It consists of a sequence of the following specifiers, corresponding to the sequence of columns and intercolumn material.

• l - A column of left-aligned items.
• r - A column of right-aligned items.
• c - A column of centred items.
• | - A vertical line the full height and depth of the environment.
• @{text} - This inserts text in every row. An @-expression suppresses the intercolumn space normally inserted between columns; any desired space between the inserted text and the adjacent items must be included in text. An \extracolsep{wd} command in an @-expression causes an extra space of width wd to appear to the left of all subsequent columns, until countermanded by another \extracolsep command. Unlike ordinary intercolumn space, this extra space is not suppressed by an @-expression. An \extracolsep command can be used only in an @-expression in the cols argument.
• <p>p{wd} - Produces a column with each item typeset in a parbox of width wd, as if it were the argument of a \parbox[t]{wd} command. However, a
  may not appear in the item, except in the following situations:</p> <p> <ol class=“orderedlist”> <li class=“listitem”>inside an environment like minipage, array, or tabular.</li> <li class=“listitem”>inside an explicit \parbox.</li> <li class=“listitem”>in the scope of a \centering, \raggedright, or \raggedleft declaration. The latter declarations must appear inside braces or an environment when used in a p-column element.</li> </ol> </p>
• *{num}{cols} - Equivalent to num copies of cols, where num is any positive integer and cols is any list of column-specifiers, which may contain another *-expression.

</td> </tr> </tbody> </table>

These commands can be used inside a tabular environment:

<a name=“idp7023088” id=“idp7023088” title=“idp7023088”></a>

The \cline command draws horizontal lines across the columns specified, beginning in column i and ending in column j, which are identified in the mandatory argument.

<a name=“idp7027520” id=“idp7027520” title=“idp7027520”></a>

The \hline command will draw a horizontal line the width of the table. It's most commonly used to draw a line at the top, bottom, and between the rows of the table.

<a name=“idp7030704” id=“idp7030704” title=“idp7030704”></a>

\multicolumn{cols}{pos}{text}

The \multicolumn is used to make an entry that spans several columns. The first mandatory argument, cols, specifies the number of columns to span. The second mandatory argument, pos, specifies the formatting of the entry; c for centred, l for flushleft, r for flushright. The third mandatory argument, text, specifies what text is to make up the entry.

<a name=“idp7038608” id=“idp7038608” title=“idp7038608”></a>

The \vline command will draw a vertical line extending the full height and depth of its row. An \hfill command can be used to move the line to the edge of the column. It can also be used in an @-expression.

<a name=“idp7042480” id=“idp7042480” title=“idp7042480”></a><a name=“idp7043232” id=“idp7043232” title=“idp7043232”></a> <pre>\begin{thebibliography}{widest-label} \bibitem[label]{cite_key} . . . \end{thebibliography} </pre>

The thebibliography environment produces a bibliography or reference list. In the article class, this reference list is labelled _References_; in the report class, it is labelled Bibliography.

• widest-label: Text that, when printed, is approximately as wide as the widest item label produces by the \bibitem commands.

<a name=“idp7051696” id=“idp7051696” title=“idp7051696”></a>

The \bibitem command generates an entry labelled by label. If the label argument is missing, a number is generated as the label, using the enumi counter. The cite_key is any sequence of letters, numbers, and punctuation symbols not containing a comma. This command writes an entry on the .aux file containing cite_key and the item's label. When this .aux file is read by the \begin{document} command, the item's label is associated with cite_key, causing the reference to cite_key by a \cite command to produce the associated label.

<a name=“idp7064288” id=“idp7064288” title=“idp7064288”></a>

The key_list argument is a list of citation keys. This command generates an in-text citation to the references associated with the keys in key_list by entries on the .aux file read by the \begin{document} command.

The optional text argument will appear after the citation, i.e. \cite[p.~2f.]{knuth} might produce `[Knuth, p. 2]'.

<a name=“idp7070048” id=“idp7070048” title=“idp7070048”></a> The package cite.sty allows a line break in the \cite reference and can sort numerical entries.

<a name=“idp7072688” id=“idp7072688” title=“idp7072688”></a> overcite.sty makes citations like footnotes.

<a name=“idp7075680” id=“idp7075680” title=“idp7075680”></a>

The \nocite command produces no text, but writes key_list, which is a list of one or more citation keys, on the .aux file. \nocite{*} uses all entries from the BibTeX database.

<a name=“idp7080656” id=“idp7080656” title=“idp7080656”></a><a name=“idp7081440” id=“idp7081440” title=“idp7081440”></a><a name=“idp7082928” id=“idp7082928” title=“idp7082928”></a><a name=“idp7083760” id=“idp7083760” title=“idp7083760”></a><a name=“idp7084960” id=“idp7084960” title=“idp7084960”></a>

If you use the BibTeX program by Oren Patashnik (highly recommended if you need a bibliography of more than a couple of titles) to maintain your bibliography, you don't use the thebibliography environment. Instead, you include the lines

\bibliographystyle{style} \bibliography{bibfile} 

where style refers to a file style.bst, which defines how your citations will look.

<a name=“table-standard-styles” id=“table-standard-styles” title=“table-standard-styles”></a>

Table 1.6. Standard styles distributed with BibTeX

<table summary=“Standard styles distributed with BibTeX” border=“0”> <tbody> <tr> <td align=“left”>alpha</td> <td align=“justify”>Sorted alphabetically. Labels are formed from name of author and year of publication.</td> </tr> <tr> <td align=“left”>plain</td> <td align=“justify”>Sorted alphabetically. Labels are numeric.</td> </tr> <tr> <td align=“left”>unsrt</td> <td align=“justify”>Like plain, but entries are in order of citation.</td> </tr> <tr> <td align=“left”>abbrv</td> <td align=“justify”>Like plain, but more compact labels.</td> </tr> </tbody> </table>

In addition, numerous other BibTeX style files exist tailored to the demands of various publications.

The argument to \bibliography refers to the file bibfile.bib, which should contain your database in BibTeX format. Only the entries referred to via \cite and \nocite will be listed in the bibliography.

<a name=“idp7104656” id=“idp7104656” title=“idp7104656”></a><a name=“idp7105408” id=“idp7105408” title=“idp7105408”></a> <pre>\begin{theorem} theorem text \end{theorem} </pre>

The theorem environment produces Theorem x in boldface followed by your theorem text.

<a name=“idp7109408” id=“idp7109408” title=“idp7109408”></a><a name=“idp7110160” id=“idp7110160” title=“idp7110160”></a><a name=“idp7110912” id=“idp7110912” title=“idp7110912”></a> <pre>\begin{titlepage} text \end{titlepage} </pre>

The titlepage environment creates a title page, i.e. a page with no printed page number or heading. It also causes the following page to be numbered page one. Formatting the title page is left to you. The \today command comes in handy for title pages. <a name=“idp7114032” id=“idp7114032” title=“idp7114032”></a>

Note that you can use the \maketitle (see <a href=“#cmd-maketitle” title=“2.3.15. \maketitle”>\maketitle</a>) command to produce a standard title page.

<a name=“idp7117776” id=“idp7117776” title=“idp7117776”></a><a name=“idp7118528” id=“idp7118528” title=“idp7118528”></a><a name=“idp7119280” id=“idp7119280” title=“idp7119280”></a><a name=“idp7120032” id=“idp7120032” title=“idp7120032”></a><a name=“idp7120784” id=“idp7120784” title=“idp7120784”></a> <pre>\begin{verbatim} text \end{verbatim} </pre>

The verbatim environment is a paragraph-making environment that gets LaTeX to print exactly what you type in. It turns LaTeX into a typewriter with carriage returns and blanks having the same effect that they would on a typewriter.

<a name=“idp7125936” id=“idp7125936” title=“idp7125936”></a><a name=“idp7126688” id=“idp7126688” title=“idp7126688”></a>

Typesets literal_text exactly as typed, including special characters and spaces, using a typewriter (\tt) type style. There may be no space between \verb or \verb* and char (space is shown here only for clarity). The *-form differs only in that spaces are printed

<a name=“idp7132912” id=“idp7132912” title=“idp7132912”></a><a name=“idp7133664” id=“idp7133664” title=“idp7133664”></a> <pre>\begin{verse} text \end{verse} </pre>

The verse environment is designed for poetry, though you may find other uses for it.

The margins are indented on the left and the right. Separate the lines of each stanza with \\, and use one or more blank lines to separate the stanzas.

<a name=“idp7138784” id=“idp7138784” title=“idp7138784”></a>

Footnotes can be produced in one of two ways. They can be produced with one command, the \footnote command. They can also be produced with two commands, the \footnotemark and the \footnotetext commands. See the specific command for information on why you would use one over the other.

<a name=“idp7143264” id=“idp7143264” title=“idp7143264”></a>

The \footnote command places the numbered footnote text at the bottom of the current page. The optional argument, number, is used to change the default footnote number. This command can only be used in outer paragraph mode; i.e., you cannot use it in sectioning commands like \chapter, in figures, tables or in a tabular environment.

<a name=“idp7149024” id=“idp7149024” title=“idp7149024”></a>

The \footnotemark command puts the footnote number in the text. This command can be used in inner paragraph mode. The text of the footnote is supplied by the \footnotetext command.

This command can be used to produce several consecutive footnote markers referring to the same footnote by using

\footnotemark[\value{footnote}]

after the first \footnote command.

<a name=“idp7155824” id=“idp7155824” title=“idp7155824”></a>

The \footnotetext command produces the text to be placed at the bottom of the page. This command can come anywhere after the \footnotemark command. The \footnotetext command must appear in outer paragraph mode.

The optional argument, number, is used to change the default footnote number.

<a name=“idp7161904” id=“idp7161904” title=“idp7161904”></a>

A length is a measure of distance. Many LaTeX commands take a length as an argument.

<a name=“idp7165280” id=“idp7165280” title=“idp7165280”></a><a name=“idp7166032” id=“idp7166032” title=“idp7166032”></a>

\newlength{\gnat}

The \newlength command defines the mandatory argument, \gnat, as a length command with a value of 0in. An error occurs if a \gnat command already exists.

<a name=“idp7172400” id=“idp7172400” title=“idp7172400”></a><a name=“idp7173152” id=“idp7173152” title=“idp7173152”></a>

\setlength{\gnat}{length}

The \setlength command is used to set the value of a length command. The length argument can be expressed in any terms of length LaTeX understands, i.e., inches (in), millimetres (mm), points (pt), etc.

<a name=“idp7180400” id=“idp7180400” title=“idp7180400”></a><a name=“idp7181152” id=“idp7181152” title=“idp7181152”></a>

\addtolength{\gnat}{length}

The \addtolength command increments length command by the amount specified in the length argument. It can be a negative amount.

<a name=“idp7185904” id=“idp7185904” title=“idp7185904”></a>

\settodepth{\gnat}{text}

The \settodepth command sets the value of a length command equal to the depth of the text argument.

<a name=“idp7190896” id=“idp7190896” title=“idp7190896”></a>

\settoheight{\gnat}{text}

The \settoheight command sets the value of a length command equal to the height of the text argument.

<a name=“idp7195888” id=“idp7195888” title=“idp7195888”></a>

\settowidth{\gnat}{text}

The \settowidth command sets the value of a length command equal to the width of the text argument.

<a name=“idp7200880” id=“idp7200880” title=“idp7200880”></a><a name=“idp7201632” id=“idp7201632” title=“idp7201632”></a>

<a name=“cmd-length-pre-width” id=“cmd-length-pre-width” title=“cmd-length-pre-width”></a>\width <a name=“idp7203376” id=“idp7203376” title=“idp7203376”></a>

<a name=“cmd-length-pre-height” id=“cmd-length-pre-height” title=“cmd-length-pre-height”></a>\height <a name=“idp7205248” id=“idp7205248” title=“idp7205248”></a>

<a name=“cmd-length-pre-depth” id=“cmd-length-pre-depth” title=“cmd-length-pre-depth”></a>\depth <a name=“idp7207120” id=“idp7207120” title=“idp7207120”></a>

<a name=“cmd-length-pre-totalheight” id=“cmd-length-pre-totalheight” title=“cmd-length-pre-totalheight”></a>\totalheight <a name=“idp7208992” id=“idp7208992” title=“idp7208992”></a>

These length parameters can be used in the arguments of the box-making commands See <a href=“#spaces-and-boxes” title=“2.3.17 Spaces & Boxes”>Spaces & Boxes</a>. They specify the natural width etc. of the text in the box. \totalheight equals \height + \depth. To make a box with the text stretched to double the natural size, e.g., say

\makebox[2\width]{Get a stretcher}

<a name=“idp7215280” id=“idp7215280” title=“idp7215280”></a><a name=“idp7216032” id=“idp7216032” title=“idp7216032”></a>

You can use LaTeX to typeset letters, both personal and business. The letter document class is designed to make a number of letters at once, although you can make just one if you so desire.

Your .tex source file has the same minimum commands as the other document classes, i.e., you must have the following commands as a minimum:

\documentclass{letter} \begin{document}  ... letters ... \end{document} 

Each letter is a letter environment, whose argument is the name and address of the recipient. For example, you might have:

\begin{letter}{Mr. Joe Smith\\ 2345 Princess St.\\ Edinburgh, EH1 1AA}   ... \end{letter} 

The letter itself begins with the \opening command. The text of the letter follows. It is typed as ordinary LaTeX input. Commands that make no sense in a letter, like \chapter, do not work. The letter closes with a \closing command.

After the closing, you can have additional material. The \cc command produces the usual cc: …. There's also a similar \encl command for a list of enclosures. With both these commands, use
to separate the items.

These commands are used with the letter class:

<a name=“idp7230320” id=“idp7230320” title=“idp7230320”></a>

\address{Return address}

The return address, as it should appear on the letter and the envelope. Separate lines of the address should be separated by
commands. If you do not make an \address declaration, then the letter will be formatted for copying onto your organisation's standard letterhead. (See <a href=“#overview” title=“2.2 Overview of LaTeX and Local Guide”>Overview</a>, for details on your local implementation). If you give an \address declaration, then the letter will be formatted as a personal letter.

<a name=“idp7236064” id=“idp7236064” title=“idp7236064”></a><a name=“idp7236816” id=“idp7236816” title=“idp7236816”></a>

\cc{Kate Schechter\\Rob McKenna}

Generate a list of other persons the letter was sent to. Each name is printed on a separate line.

<a name=“idp7239824” id=“idp7239824” title=“idp7239824”></a><a name=“idp7240576” id=“idp7240576” title=“idp7240576”></a>

\closing{text}

The letter closes with a \closing command, i.e.,

\closing{Best Regards,} 

<a name=“idp7244704” id=“idp7244704” title=“idp7244704”></a><a name=“idp7245456” id=“idp7245456” title=“idp7245456”></a>

\encl{CV\\Certificates}

Generate a list of enclosed material.

<a name=“idp7248336” id=“idp7248336” title=“idp7248336”></a>

\location{address}

This modifies your organisation's standard address. This only appears if the firstpage pagestyle is selected.

<a name=“idp7251936” id=“idp7251936” title=“idp7251936”></a>

\makelabels{number}

If you issue this command in the preamble, LaTeX will create a sheet of address labels. This sheet will be output before the letters.

<a name=“idp7255312” id=“idp7255312” title=“idp7255312”></a>

\name{June Davenport}

Your name, used for printing on the envelope together with the return address.

<a name=“idp7258288” id=“idp7258288” title=“idp7258288”></a><a name=“idp7259040” id=“idp7259040” title=“idp7259040”></a>

\opening{text}

The letter begins with the \opening command. The mandatory argument, text, is whatever text you wish to start your letter, i.e.,

\opening{Dear Joe,}  

<a name=“idp7263872” id=“idp7263872” title=“idp7263872”></a>

\ps

Use this command before a postscript.

<a name=“idp7266752” id=“idp7266752” title=“idp7266752”></a>

\signature{Harvey Swick}

Your name, as it should appear at the end of the letter underneath the space for your signature. Items that should go on separate lines should be separated by
commands.

<a name=“idp7270448” id=“idp7270448” title=“idp7270448”></a>

\startbreaks

Used after a \stopbreaks command to allow page breaks again.

<a name=“idp7273952” id=“idp7273952” title=“idp7273952”></a>

\stopbreaks

Inhibit page breaks until a \startbreaks command occurs.

<a name=“idp7277456” id=“idp7277456” title=“idp7277456”></a>

\telephone{number}

This is your telephone number. This only appears if the firstpage pagestyle is selected.

<a name=“idp7281424” id=“idp7281424” title=“idp7281424”></a><a name=“idp7282176” id=“idp7282176” title=“idp7282176”></a><a name=“idp7282928” id=“idp7282928” title=“idp7282928”></a>

The first thing LaTeX does when processing ordinary text is to translate your input file into a string of glyphs and spaces. To produce a printed document, this string must be broken into lines, and these lines must be broken into pages. In some environments, you do the line breaking yourself with the
command, but LaTeX usually does it for you.

<a name=“idp7286640” id=“idp7286640” title=“idp7286640”></a><a name=“idp7287392” id=“idp7287392” title=“idp7287392”></a>

\\[extra-space], \\*[extra-space] The \\ command tells LaTeX to start a new line. It has an optional argument, extra-space, that specifies how much extra vertical space is to be inserted before the next line. This can be a negative amount. The \\* command is the same as the ordinary \\ command except that it tells LaTeX not to start a new page after the line. == <a name="cmd-dash-op-hyphenation-cp" id="cmd-dash-op-hyphenation-cp" title="cmd-dash-op-hyphenation-cp"></a>\- == <a name="idp7294144" id="idp7294144" title="idp7294144"></a><a name="idp7294896" id="idp7294896" title="idp7294896"></a> The \- command tells LaTeX that it may hyphenate the word at that point. LaTeX is very good at hyphenating, and it will usually find all correct hyphenation points. The \- command is used for the exceptional cases. Note that when you insert \- commands in a word, the word will only be hyphenated at those points and not at any of the hyphenation points that LaTeX might otherwise have chosen. == <a name="cmd-cleardoublepage" id="cmd-cleardoublepage" title="cmd-cleardoublepage"></a>\cleardoublepage == <a name="idp7300560" id="idp7300560" title="idp7300560"></a><a name="idp7301312" id="idp7301312" title="idp7301312"></a> The \cleardoublepage command ends the current page and causes all figures and tables that have so far appeared in the input to be printed. In a two-sided printing style, it also makes the next page a right-hand (odd-numbered) page, producing a blank page if necessary. == <a name="cmd-clearpage" id="cmd-clearpage" title="cmd-clearpage"></a>\clearpage == <a name="idp7304224" id="idp7304224" title="idp7304224"></a><a name="idp7304976" id="idp7304976" title="idp7304976"></a> The \clearpage command ends the current page and causes all figures and tables that have so far appeared in the input to be printed. == <a name="cmd-enlargethispage" id="cmd-enlargethispage" title="cmd-enlargethispage"></a>\enlargethispage == <a name="idp7307744" id="idp7307744" title="idp7307744"></a><a name="idp7308496" id="idp7308496" title="idp7308496"></a> \enlargethispage{size} \enlargethispage*{size} Enlarge the \textheight for the current page by the specified amount; e.g. \enlargethispage{\baselineskip} will allow one additional line. The starred form tries to squeeze the material together on the page as much as possible. This is normally used together with an explicit \pagebreak. == <a name="cmd-samepage" id="cmd-samepage" title="cmd-samepage"></a>\samepage == <a name="idp7314752" id="idp7314752" title="idp7314752"></a> \samepage The object in the argument {} should be on the current page. == <a name="cmd-fussy" id="cmd-fussy" title="cmd-fussy"></a>\fussy == <a name="idp7318256" id="idp7318256" title="idp7318256"></a> \fussy This declaration (which is the default) makes TeX more fussy about line breaking. This can avoids too much space between words, but may produce overfull boxes. This command cancels the effect of a previous \sloppy command. <a href="#cmd-sloppy" title="2.3.10. \sloppy">\sloppy</a> == <a name="cmd-hyphenation" id="cmd-hyphenation" title="cmd-hyphenation"></a>\hyphenation == <a name="idp7323296" id="idp7323296" title="idp7323296"></a><a name="idp7324048" id="idp7324048" title="idp7324048"></a> \hyphenation{words} The \hyphenation command declares allowed hyphenation points, where words is a list of words, separated by spaces, in which each hyphenation point is indicated by a - character. == <a name="cmd-linebreak" id="cmd-linebreak" title="cmd-linebreak"></a>\linebreak == <a name="idp7328992" id="idp7328992" title="idp7328992"></a><a name="idp7329744" id="idp7329744" title="idp7329744"></a> \linebreak[number] The \linebreak command tells LaTeX to break the current line at the point of the command. With the optional argument, number, you can convert the \linebreak command from a demand to a request. The number must be a number from 0 to 4. The higher the number, the more insistent the request is. The \linebreak command causes LaTeX to stretch the line so it extends to the right margin. == <a name="cmd-newline" id="cmd-newline" title="cmd-newline"></a>\newline == <a name="idp7336624" id="idp7336624" title="idp7336624"></a><a name="idp7337376" id="idp7337376" title="idp7337376"></a> The \newline command breaks the line right where it is. It can only be used in paragraph mode. == <a name="cmd-newpage" id="cmd-newpage" title="cmd-newpage"></a>\newpage == <a name="idp7340112" id="idp7340112" title="idp7340112"></a><a name="idp7340864" id="idp7340864" title="idp7340864"></a> The \newpage command ends the current page. In contrast to <a href="#cmd-pagebreak" title="2.3.10. \pagebreak">\pagebreak</a> it can produce a partly empty page, even when <a href="#cmd-flushbottom-title" title="2.3.5. \flushbottom">\flushbottom</a> is active. == <a name="cmd-nolinebreak" id="cmd-nolinebreak" title="cmd-nolinebreak"></a>\nolinebreak == <a name="idp7344896" id="idp7344896" title="idp7344896"></a> \nolinebreak[number] The \nolinebreak command prevents LaTeX from breaking the current line at the point of the command. With the optional argument, number, you can convert the \nolinebreak command from a demand to a request. The number must be a number from 0 to 4. The higher the number, the more insistent the request is. == <a name="cmd-nopagebreak" id="cmd-nopagebreak" title="cmd-nopagebreak"></a>\nopagebreak == <a name="idp7350304" id="idp7350304" title="idp7350304"></a> \nopagebreak[number] The \nopagebreak command prevents LaTeX from breaking the current page at the point of the command. With the optional argument, number, you can convert the \nopagebreak command from a demand to a request. The number must be a number from 0 to 4. The higher the number, the more insistent the request is. == <a name="cmd-pagebreak" id="cmd-pagebreak" title="cmd-pagebreak"></a>\pagebreak == <a name="idp7355712" id="idp7355712" title="idp7355712"></a><a name="idp7356464" id="idp7356464" title="idp7356464"></a> \pagebreak[number] The \pagebreak command tells LaTeX to break the current page at the point of the command. With the optional argument, number, you can convert the \pagebreak command from a demand to a request. The number must be a number from 0 to 4. The higher the number, the more insistent the request is. == <a name="cmd-sloppy" id="cmd-sloppy" title="cmd-sloppy"></a>\sloppy == <a name="idp7361888" id="idp7361888" title="idp7361888"></a> \sloppy This declaration makes TeX less fussy about line breaking. This can prevent overfull boxes, but may leave too much space between words. Lasts until a \fussy command is issued. <a href="#cmd-fussy" title="2.3.10. \fussy">\fussy</a>. === <a name="making-paragraphs" id="making-paragraphs" title="making-paragraphs"></a>2.3.11 Making Paragraphs === <a name="idp7367312" id="idp7367312" title="idp7367312"></a><a name="idp7368064" id="idp7368064" title="idp7368064"></a> A paragraph is ended by one or more completely blank lines --- lines not containing even a %. A blank line should not appear where a new paragraph cannot be started, such as in math mode or in the argument of a sectioning command. == <a name="cmd-indent" id="cmd-indent" title="cmd-indent"></a>\indent == <a name="idp7370976" id="idp7370976" title="idp7370976"></a><a name="idp7371728" id="idp7371728" title="idp7371728"></a> \indent This produces a horizontal space whose width equals the width of the paragraph indentation. It is used to add paragraph indentation where it would otherwise be suppressed. == <a name="cmd-noindent" id="cmd-noindent" title="cmd-noindent"></a>\noindent == <a name="idp7374816" id="idp7374816" title="idp7374816"></a><a name="idp7375568" id="idp7375568" title="idp7375568"></a> \noindent When used at the beginning of the paragraph, it suppresses the paragraph indentation. It has no effect when used in the middle of a paragraph. == <a name="cmd-par" id="cmd-par" title="cmd-par"></a>\par == <a name="idp7378624" id="idp7378624" title="idp7378624"></a><a name="idp7379376" id="idp7379376" title="idp7379376"></a> Equivalent to a blank line; often used to make command or environment definitions easier to read. === <a name="margin-notes" id="margin-notes" title="margin-notes"></a>2.3.12 Margin Notes === <a name="idp7381888" id="idp7381888" title="idp7381888"></a><a name="idp7382640" id="idp7382640" title="idp7382640"></a><a name="idp7383392" id="idp7383392" title="idp7383392"></a> The command \marginpar[left]{right} creates a note in the margin. The first line will be at the same height as the line in the text where the \marginpar occurs. When you only specify the mandatory argument right, the text will be placed * in the right margin for one-sided layout * in the outside margin for two-sided layout * in the nearest margin for two-column layout. By issuing the command \reversemarginpar, you can force the marginal notes to go into the opposite (inside) margin. When you specify both arguments, left is used for the left margin, and right is used for the right margin. The first word will normally not be hyphenated; you can enable hyphenation by prefixing the first word with a \hspace{0pt} command. === <a name="math-formulae" id="math-formulae" title="math-formulae"></a>2.3.13 Math Formulae === <a name="idp7394608" id="idp7394608" title="idp7394608"></a><a name="idp7395360" id="idp7395360" title="idp7395360"></a><a name="idp7396112" id="idp7396112" title="idp7396112"></a><a name="idp7396864" id="idp7396864" title="idp7396864"></a><a name="idp7397616" id="idp7397616" title="idp7397616"></a><a name="idp7398368" id="idp7398368" title="idp7398368"></a><a name="idp7399120" id="idp7399120" title="idp7399120"></a><a name="idp7399872" id="idp7399872" title="idp7399872"></a> <a name="table-math-mode" id="table-math-mode" title="table-math-mode"></a> **Table 1.7. Three environments that put LaTeX in math mode** <table summary="Three environments that put LaTeX in math mode" border="0"> <tbody> <tr> <td align="left">math</td> <td align="justify">For Formulae that appear right in the text.</td> </tr> <tr> <td align="left">displaymath</td> <td align="justify">For Formulae that appear on their own line.</td> </tr> <tr> <td align="left">equation</td> <td align="justify">The same as the displaymath environment except that it adds an equation number in the right margin.</td> </tr> </tbody> </table> The math environment can be used in both paragraph and LR mode, but the displaymath and equation environments can be used only in paragraph mode. The math and displaymath environments are used so often that they have the following short forms: <code> \(...\) instead of \begin{math}...\end{math} \[...\] instead of \begin{displaymath}...\end{displaymath} </code> In fact, the math environment is so common that it has an even shorter form:

$ ... $     instead of     \(...\) 

<a name=“idp7414912” id=“idp7414912” title=“idp7414912”></a>

<a name=“idp7416528” id=“idp7416528” title=“idp7416528”></a><a name=“idp7417280” id=“idp7417280” title=“idp7417280”></a><a name=“idp7418032” id=“idp7418032” title=“idp7418032”></a><a name=“idp7418784” id=“idp7418784” title=“idp7418784”></a>

To get an expression exp to appear as a subscript, you just type _{ exp } . To get exp to appear as a superscript, you type ^{ exp }. LaTeX handles superscripted superscripts and all of that stuff in the natural way. It even does the right thing when something has both a subscript and a superscript.

<a name=“idp7425008” id=“idp7425008” title=“idp7425008”></a><a name=“idp7425760” id=“idp7425760” title=“idp7425760”></a><a name=“idp7426512” id=“idp7426512” title=“idp7426512”></a>

<a name=“idp7428128” id=“idp7428128” title=“idp7428128”></a><a name=“idp7428880” id=“idp7428880” title=“idp7428880”></a>

In a math environment, LaTeX ignores the spaces you type and puts in the spacing that it thinks is best. LaTeX formats mathematics the way it's done in mathematics texts. If you want different spacing, LaTeX provides the following four commands for use in math mode: <a name=“idp7432096” id=“idp7432096” title=“idp7432096”></a><a name=“idp7432848” id=“idp7432848” title=“idp7432848”></a><a name=“idp7433600” id=“idp7433600” title=“idp7433600”></a><a name=“idp7434352” id=“idp7434352” title=“idp7434352”></a>

1 <p>\; - a thick space</p> 1 <p>\: - a medium space</p> 1 <p>\, - a thin space</p> 1 <p>\! - a negative thin space</p>

<a name=“idp7441248” id=“idp7441248” title=“idp7441248”></a>

<a name=“table-math-miscellany” id=“table-math-miscellany” title=“table-math-miscellany”></a>

Table 1.8. Math Miscellany

<table summary=“Math Miscellany” border=“0”> <tbody> <tr> <td align=“left”><a name=“cmd-math-misc-cdots” id=“cmd-math-misc-cdots” title=“cmd-math-misc-cdots”></a>\cdots<a name=“idp7446336” id=“idp7446336” title=“idp7446336”></a></td> <td align=“justify”>Produces a horizontal ellipsis where the dots are raised to the centre of the line.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-ddots” id=“cmd-math-misc-ddots” title=“cmd-math-misc-ddots”></a>\ddots <a name=“idp7448960” id=“idp7448960” title=“idp7448960”></a></td> <td align=“justify”>Produces a diagonal ellipsis.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-frac” id=“cmd-math-misc-frac” title=“cmd-math-misc-frac”></a>\frac{num}{den} <a name=“idp7451216” id=“idp7451216” title=“idp7451216”></a></td> <td align=“justify”>Produces the fraction num divided by den.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-ldots” id=“cmd-math-misc-ldots” title=“cmd-math-misc-ldots”></a>\ldots <a name=“idp7454720” id=“idp7454720” title=“idp7454720”></a></td> <td align=“justify”>Produces an ellipsis. This command works in any mode, not just math mode.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-overbrace” id=“cmd-math-misc-overbrace” title=“cmd-math-misc-overbrace”></a>\overbrace{text} <a name=“idp7457072” id=“idp7457072” title=“idp7457072”></a></td> <td align=“justify”>Generates a brace over text.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-overline” id=“cmd-math-misc-overline” title=“cmd-math-misc-overline”></a>\overline{text} <a name=“idp7459328” id=“idp7459328” title=“idp7459328”></a></td> <td align=“justify”>Causes the argument text to be overlined.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-sqrt” id=“cmd-math-misc-sqrt” title=“cmd-math-misc-sqrt”></a>\sqrt[root]{arg} <a name=“idp7461584” id=“idp7461584” title=“idp7461584”></a></td> <td align=“justify”>Produces the square root of its argument. The optional argument, root, determines what root to produce, i.e., the cube root of x+y would be typed as $\sqrt[3]{x+y}$.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-underbrace” id=“cmd-math-misc-underbrace” title=“cmd-math-misc-underbrace”></a>\underbrace{text} <a name=“idp7465888” id=“idp7465888” title=“idp7465888”></a></td> <td align=“justify”>Generates text with a brace underneath.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-underline” id=“cmd-math-misc-underline” title=“cmd-math-misc-underline”></a>\underline{text} <a name=“idp7468144” id=“idp7468144” title=“idp7468144”></a></td> <td align=“justify”>Causes the argument text to be underlined. This command can also be used in paragraph and LR modes.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-vdots” id=“cmd-math-misc-vdots” title=“cmd-math-misc-vdots”></a>\vdots <a name=“idp7470656” id=“idp7470656” title=“idp7470656”></a></td> <td align=“justify”>Produces a vertical ellipsis.</td> </tr> <tr> <td align=“left”><a name=“cmd-math-misc-ensuremath” id=“cmd-math-misc-ensuremath” title=“cmd-math-misc-ensuremath”></a>\ensuremath{} <a name=“idp7473040” id=“idp7473040” title=“idp7473040”></a></td> <td align=“justify”>It's argument is set in math mode. This is needed for own definitions.</td> </tr> </tbody> </table>

<a name=“idp7476160” id=“idp7476160” title=“idp7476160”></a><a name=“idp7476912” id=“idp7476912” title=“idp7476912”></a><a name=“idp7477664” id=“idp7477664” title=“idp7477664”></a><a name=“idp7478416” id=“idp7478416” title=“idp7478416”></a><a name=“idp7479168” id=“idp7479168” title=“idp7479168”></a>

When LaTeX is processing your input text, it is always in one of three modes:

• paragraph mode
• Math mode
• Left-to-right mode, called LR mode for short

LaTeX changes mode only when it goes up or down a staircase to a different level, though not all level changes produce mode changes. Mode changes occur only when entering or leaving an environment, or when LaTeX is processing the argument of certain text-producing commands.

Paragraph mode is the most common; it's the one LaTeX is in when processing ordinary text. In that mode, LaTeX breaks your text into lines and breaks the lines into pages. LaTeX is in math mode when it's generating a mathematical formula. In LR mode, as in paragraph mode, LaTeX considers the output that it produces to be a string of words with spaces between them. However, unlike paragraph mode, LaTeX keeps going from left to right; it never starts a new line in LR mode. Even if you put a hundred words into an \mbox, LaTeX would keep typesetting them from left to right inside a single box, and then complain because the resulting box was too wide to fit on the line.

LaTeX is in LR mode when it starts making a box with an \mbox command. You can get it to enter a different mode inside the box - for example, you can make it enter math mode to put a formula in the box. There are also several text-producing commands and environments for making a box that put LaTeX in paragraph mode. The box make by one of these commands or environments will be called a parbox. When LaTeX is in paragraph mode while making a box, it is said to be in inner paragraph mode. Its normal paragraph mode, which it starts out in, is called outer paragraph mode.

<a name=“idp7495072” id=“idp7495072” title=“idp7495072”></a><a name=“idp7495824” id=“idp7495824” title=“idp7495824”></a>

The \documentclass command determines the size and position of the page's head and foot. The page style determines what goes in them.

<a name=“idp7498592” id=“idp7498592” title=“idp7498592”></a><a name=“idp7499344” id=“idp7499344” title=“idp7499344”></a>

\maketitle

The \maketitle command generates a title on a separate title page. In the article class, \maketitle will also switch to pagestyle plain. See <a href=“#page-styles” title=“2.3.15 Page Styles”>Page Styles</a> for commands to change page numbering.

Information used to produce the title is obtained from the following declarations:

See <a href=“#page-styles” title=“2.3.15 Page Styles”>Page Styles</a> for the commands to give the information.

<a name=“idp7507120” id=“idp7507120” title=“idp7507120”></a><a name=“idp7507872” id=“idp7507872” title=“idp7507872”></a>

\author{names}

The \author command declares the author(s), where names is a list of authors separated by \and commands. Use
to separate lines within a single author's entry – for example, to give the author's institution or address.

<a name=“idp7513392” id=“idp7513392” title=“idp7513392”></a><a name=“idp7514144” id=“idp7514144” title=“idp7514144”></a>

\date{text}

The \date command declares text to be the document's date. With no \date command, the current date is used.

<a name=“idp7518656” id=“idp7518656” title=“idp7518656”></a><a name=“idp7519408” id=“idp7519408” title=“idp7519408”></a>

\thanks{text}

The \thanks command produces a \footnote to the title.

<a name=“idp7523536” id=“idp7523536” title=“idp7523536”></a><a name=“idp7524288” id=“idp7524288” title=“idp7524288”></a>

\title{text}

The \title command declares text to be the title. Use
to tell LaTeX where to start a new line in a long title.

<a name=“idp7529424” id=“idp7529424” title=“idp7529424”></a><a name=“idp7530176” id=“idp7530176” title=“idp7530176”></a>

\pagenumbering{num_style}

Specifies the style of page numbers. Possible values of num_style are:

• arabic - Arabic numerals
• roman - Lowercase Roman numerals
• Roman - Uppercase Roman numerals
• alph - Lowercase letters
• Alph - Uppercase letters

<a name=“idp7540064” id=“idp7540064” title=“idp7540064”></a>

\pagestyle{option}

The \pagestyle command changes the style from the current page on throughout the remainder of your document.

The valid options are:

• plain - Just a plain page number.
• empty - Produces empty heads and feet - no page numbers.
• headings - Puts running headings on each page. The document style specifies what goes in the headings.
• myheadings - You specify what is to go in the heading with the \markboth or the \markright commands.

<a name=“idp7550784” id=“idp7550784” title=“idp7550784”></a> <pre>\markboth{left head}{right head} </pre>

The \markboth command is used in conjunction with the page style myheadings for setting both the left and the right heading. You should note that a left-hand heading is generated by the last \markboth command before the end of the page, while a right-hand heading is generated by the first \markboth or \markright that comes on the page if there is one, otherwise by the last one before the page.

<a name=“idp7557584” id=“idp7557584” title=“idp7557584”></a> <pre>\markright{right head} </pre>

The \markright command is used in conjunction with the page style myheadings for setting the right heading, leaving the left heading unchanged. You should note that a left-hand heading is generated by the last \markboth command before the end of the page, while a right-hand heading is generated by the first \markboth or \markright that comes on the page if there is one, otherwise by the last one before the page.

<a name=“idp7564400” id=“idp7564400” title=“idp7564400”></a>

\thispagestyle{option}

The \thispagestyle command works in the same manner as the \pagestyle command except that it changes the style for the current page only.

<a name=“idp7569008” id=“idp7569008” title=“idp7569008”></a><a name=“idp7569760” id=“idp7569760” title=“idp7569760”></a><a name=“idp7570512” id=“idp7570512” title=“idp7570512”></a><a name=“idp7571264” id=“idp7571264” title=“idp7571264”></a><a name=“idp7572016” id=“idp7572016” title=“idp7572016”></a><a name=“idp7572768” id=“idp7572768” title=“idp7572768”></a>

Sectioning commands provide the means to structure your text into units.

• <a name=“cmd-sectioning-part” id=“cmd-sectioning-part” title=“cmd-sectioning-part”></a>\part
• <a name=“cmd-sectioning-chapter” id=“cmd-sectioning-chapter” title=“cmd-sectioning-chapter”></a>\chapter (report and book class only)
• <a name=“cmd-sectioning-section” id=“cmd-sectioning-section” title=“cmd-sectioning-section”></a>\section
• <a name=“cmd-sectioning-subsection” id=“cmd-sectioning-subsection” title=“cmd-sectioning-subsection”></a>\subsection
• <a name=“cmd-sectioning-subsubsection” id=“cmd-sectioning-subsubsection” title=“cmd-sectioning-subsubsection”></a>\subsubsection
• <a name=“cmd-sectioning-paragraph” id=“cmd-sectioning-paragraph” title=“cmd-sectioning-paragraph”></a>\paragraph
• <a name=“cmd-sectioning-subparagraph” id=“cmd-sectioning-subparagraph” title=“cmd-sectioning-subparagraph”></a>\subparagraph

All sectioning commands take the same general form, i.e.,

\chapter[optional]{title}

In addition to providing the heading in the text, the mandatory argument of the sectioning command can appear in two other places:

1 <p>The table of contents</p> 1 <p>The running head at the top of the page</p>

You may not want the same thing to appear in these other two places as appears in the text heading. To handle this situation, the sectioning commands have an optional argument that provides the text for these other two purposes.

All sectioning commands have *-forms that print a title, but do not include a number and do not make an entry in the table of contents. <a name=“idp7590944” id=“idp7590944” title=“idp7590944”></a><a name=“idp7591696” id=“idp7591696” title=“idp7591696”></a>

<a name=“cmd-sectioning-appendix” id=“cmd-sectioning-appendix” title=“cmd-sectioning-appendix”></a>\appendix

The \appendix command changes the way sectional units are numbered. The \appendix command generates no text and does not affect the numbering of parts. The normal use of this command is something like

\chapter{The First Chapter}  ... \appendix \chapter{The First Appendix} 

<a name=“idp7597392” id=“idp7597392” title=“idp7597392”></a><a name=“idp7598144” id=“idp7598144” title=“idp7598144”></a>

All the predefined length parameters See <a href=“#predefined-lengths-title” title=“2.3.8. Predefined lengths”>Predefined lengths</a> can be used in the arguments of the box-making commands.

<a name=“idp7600848” id=“idp7600848” title=“idp7600848”></a>

The \dotfill command produces a rubber length that produces dots instead of just spaces.

<a name=“idp7603856” id=“idp7603856” title=“idp7603856”></a>

The \hfill fill command produces a rubber length which can stretch or shrink horizontally. It will be filled with spaces.

<a name=“idp7606960” id=“idp7606960” title=“idp7606960”></a>

The \hrulefill fill command produces a rubber length which can stretch or shrink horizontally. It will be filled with a horizontal rule.

<a name=“idp7610080” id=“idp7610080” title=“idp7610080”></a>

\hspace{length}, \hspace*{length}

The \hspace command adds horizontal space. The length of the space can be expressed in any terms that LaTeX understands, i.e., points, inches, etc. You can add negative as well as positive space with an \hspace command. Adding negative space is like backspacing.

LaTeX removes horizontal space that comes at the end of a line. If you don't want LaTeX to remove this space, include the optional * argument. Then the space is never removed.

<a name=“idp7616656” id=“idp7616656” title=“idp7616656”></a><a name=“idp7617408” id=“idp7617408” title=“idp7617408”></a><a name=“idp7618160” id=“idp7618160” title=“idp7618160”></a>

\addvspace{length}

The \addvspace command normally adds a vertical space of height length. However, if vertical space has already been added to the same point in the output by a previous \addvspace command, then this command will not add more space than needed to make the natural length of the total vertical space equal to length.

<a name=“idp7623264” id=“idp7623264” title=“idp7623264”></a>

The \bigskip command is equivalent to \vspace{bigskipamount} where bigskipamount is determined by the document class.

<a name=“idp7627136” id=“idp7627136” title=“idp7627136”></a>

The \medskip command is equivalent to \vspace{medskipamount} where medskipamount is determined by the document class.

<a name=“idp7631008” id=“idp7631008” title=“idp7631008”></a>

\smallskip

The \smallskip command is equivalent to \vspace{smallskipamount} where smallskipamount is determined by the document class.

<a name=“idp7635760” id=“idp7635760” title=“idp7635760”></a>

The \vfill fill command produces a rubber length which can stretch or shrink vertically.

<a name=“idp7638480” id=“idp7638480” title=“idp7638480”></a>

\vspace{length}, \vspace*{length}

The \vspace command adds vertical space. The length of the space can be expressed in any terms that LaTeX understands, i.e., points, inches, etc. You can add negative as well as positive space with an \vspace command.

LaTeX removes vertical space that comes at the end of a page. If you don't want LaTeX to remove this space, include the optional * argument. Then the space is never removed.

<a name=“idp7644976” id=“idp7644976” title=“idp7644976”></a>

\fbox{text}

The \fbox command is exactly the same as the \mbox command, except that it puts a frame around the outside of the box that it creates.

<a name=“idp7648976” id=“idp7648976” title=“idp7648976”></a>

\framebox[width][position]{text}

The \framebox command is exactly the same as the \makebox command, except that it puts a frame around the outside of the box that it creates.

The framebox command produces a rule of thickness \fboxrule, and leaves a space \fboxsep between the rule and the contents of the box.

<a name=“idp7654848” id=“idp7654848” title=“idp7654848”></a>

\begin{lrbox}{cmd} text \end{lrbox}

This is the environment form of \sbox.

The text inside the environment is saved in the box cmd, which must have been declared with \newsavebox.

<a name=“idp7660064” id=“idp7660064” title=“idp7660064”></a>

\makebox[width][position]{text}

The \makebox command creates a box just wide enough to contain the text specified. The width of the box is specified by the optional width argument. The position of the text within the box is determined by the optional position argument.

• c — centred (default)
• l — flushleft
• r — flushright
• s — stretch from left to right margin. The text must contain stretchable space for this to work.

See <a href=“#cmd-makebox-op-picture-cp” title=“2.3.6. \makebox(width,height)[position]{…}”>\makebox (picture)</a>.

<a name=“idp7672016” id=“idp7672016” title=“idp7672016”></a>

\mbox{text}

The \mbox command creates a box just wide enough to hold the text created by its argument.

Use this command to prevent text from being split across lines.

<a name=“idp7676112” id=“idp7676112” title=“idp7676112”></a>

\newsavebox{cmd}

Declares cmd, which must be a command name that is not already defined, to be a bin for saving boxes.

<a name=“idp7679728” id=“idp7679728” title=“idp7679728”></a>

\parbox[position][height][inner-pos]{width}{text}

A parbox is a box whose contents are created in paragraph mode. The \parbox has two mandatory arguments:

• width - specifies the width of the parbox, and
• text - the text that goes inside the parbox.

LaTeX will position a parbox so its centre lines up with the centre of the text line. The optional position argument allows you to line up either the top or bottom line in the parbox (default is top).

If the height argument is not given, the box will have the natural height of the text.

The inner-pos argument controls the placement of the text inside the box. If it is not specified, position is used.

• t — text is placed at the top of the box.
• c — text is centred in the box.
• b — text is placed at the bottom of the box.
• s — stretch vertically. The text must contain vertically stretchable space for this to work.

A \parbox command is used for a parbox containing a small piece of text, with nothing fancy inside. In particular, you shouldn't use any of the paragraph-making environments inside a \parbox argument. For larger pieces of text, including ones containing a paragraph-making environment, you should use a minipage environment See <a href=“#env-minipage” title=“2.3.6. minipage”>minipage</a>.

<a name=“idp7699776” id=“idp7699776” title=“idp7699776”></a>

\raisebox{distance}[extend-above][extend-below]{text}

The \raisebox command is used to raise or lower text. The first mandatory argument specifies how high the text is to be raised (or lowered if it is a negative amount). The text itself is processed in LR mode.

Sometimes it's useful to make LaTeX think something has a different size than it really does - or a different size than LaTeX would normally think it has. The \raisebox command lets you tell LaTeX how tall it is.

The first optional argument, extend-above, makes LaTeX think that the text extends above the line by the amount specified. The second optional argument, extend-below, makes LaTeX think that the text extends below the line by the amount specified.

<a name=“idp7709024” id=“idp7709024” title=“idp7709024”></a>

\rule[raise-height]{width}{thickness}

The \rule command is used to produce horizontal lines. The arguments are defined as follows:

• raise-height - specifies how high to raise the rule (optional)
• width - specifies the length of the rule (mandatory)
• thickness - specifies the thickness of the rule (mandatory)

<a name=“idp7716832” id=“idp7716832” title=“idp7716832”></a>

\savebox{cmd}[width][pos]{text}

This command typeset text in a box just as for \makebox. However, instead of printing the resulting box, it saves it in bin cmd, which must have been declared with \newsavebox.

<a name=“idp7722176” id=“idp7722176” title=“idp7722176”></a>

\sbox{cmd}\{text}

This commands typesets text in a box just as for \mbox. However, instead of printing the resulting box, it saves it in cmd, which must have been declared with \newsavebox.

<a name=“idp7727744” id=“idp7727744” title=“idp7727744”></a>

\usebox{cmd}

Prints the box most recently saved in bin cmd by a \savebox command.

<a name=“idp7733136” id=“idp7733136” title=“idp7733136”></a><a name=“idp7733952” id=“idp7733952” title=“idp7733952”></a><a name=“idp7734768” id=“idp7734768” title=“idp7734768”></a><a name=“idp7735584” id=“idp7735584” title=“idp7735584”></a>

The following characters play a special role in LaTeX and are called special printing characters, or simply special characters.

# $ % & ~ _ ^ \ { } 

Whenever you put one of these special characters into your file, you are doing something special. If you simply want the character to be printed just as any other letter, include a \ in front of the character. For example, \$ will produce $ in your output.

One exception to this rule is the \ itself because
has its own special meaning. A \ is produced by typing $\backslash$ in your file.

Also, \~ means `place a tilde accent over the following letter', so you will probably want to use \verb instead. <a name=“idp7746800” id=“idp7746800” title=“idp7746800”></a><a name=“idp7747616” id=“idp7747616” title=“idp7747616”></a><a name=“idp7748432” id=“idp7748432” title=“idp7748432”></a>

In addition, you can access any character of a font once you know its number by using the \symbol command. For example, the character used for displaying spaces in the \verb* command has the code decimal 32, so it can be typed as \symbol{32}.

You can also specify octal numbers with ' or hexadecimal numbers with “, so the previous example could also be written as \symbol{'40} or \symbol{“20}.

<a name=“idp7756944” id=“idp7756944” title=“idp7756944”></a>

<a name=“idp7759808” id=“idp7759808” title=“idp7759808”></a>

The rules differ somewhat depending whether you are in <a href=”#modes” title=“2.3.14 Modes”>text mode</a>, <a href=“#modes” title=“2.3.14 Modes”>math modes</a>, or the <a href=“#env-tabbing” title=“2.3.6. tabbing”>tabbing environment</a>.

The following accents may be placed on letters. Although o is used in most of the example, the accents may be placed on any letter. Accents may even be placed above a missing letter; for example, \~{} produces a tilde over a blank space.

The following commands may be used only in paragraph or LR mode:

• \`{o} produces a grave accent, ò
• \'{o} produces an acute accent, ó
• \^{o} produces a circumflex, ô
• \“{o} produces an umlaut or dieresis, ö
• \H{o} produces a long Hungarian umlaut
• \~{o} produces a tilde, õ
• \c{c} produces a cedilla, ç
• \={o} produces a macron accent (a bar over the letter)
• \b{o} produces a bar under the letter
• \.{o} produces a dot over the letter
• \d{o} produces a dot under the letter
• \u{o} produces a breve over the letter
• \v{o} produces a v over the letter
• \t{oo} produces a tie (inverted u) over the two letters

Note that the letters i and j require special treatment when they are given accents because it is often desirable to replace the dot with the accent. For this purpose, the commands \i and \j can be used to produce dotless letters.

For example,

• \^{\i} should be used for i, circumflex, î
• \”{\i} should be used for i, umlaut, ï

Several of the above and some similar accents can also be produced in math mode. The following commands may be used only in math mode:

• \hat{o} is similar to the circumflex (cf. \^)
• \widehat{oo} is a wide version of \hat over several letters
• \check{o} is a vee or check (cf. \v)
• \tilde{o} is a tilde (cf. \~)
• \widetilde{oo} is a wide version of \tilde over several letters
• \acute{o} is an acute accent (cf. \`)
• \grave{o} is a grave accent (cf. >\')
• \dot{o} is a dot over the letter (cf. \.)
• \ddot{o} is a double dot over the letter
• \breve{o} is a breve (cf. \u)
• \bar{o} is a macron (cf. \
• \vec{o} is a vector (arrow) over the letter

Some of the accent marks used in running text have other uses in the <a href=“#env-tabbing” title=“2.3.6. tabbing”>Tabbing Environment</a>. In that case they can be created with the following command:

• >\a' for an acute accent
• \a` for a grave accent
• \a= for a macron accent

<a name=“idp7832544” id=“idp7832544” title=“idp7832544”></a>

LaTeX provides commands for all sorts of arrows. The following commands are used only in math mode.

In general the command names are created from left, right, up, or down. leftright gives a double headed arrow. Prefacing with long gives a longer arrow. Capitalizing the first letter gives a double-shanked arrow.

Examples are:

• \leftarrow
• \Leftarrow
• \longleftarrow
• \Longleftarrow
• \rightarrow
• \Rightarrow
• \longrightarrow
• \Longrightarrow
• \leftrightarrow
• \Leftrightarrow
• \longleftrightarrow
• \uparrow
• \downarrow
• \Uparrow
• >\nearrow points from southwest to northeast
• \searrow points from northwest to southeast
• \swarrow points from northeast to southwest
• \nwarrow points from southeast to northwest

The \stackrel command is useful for putting things over or under your arrow.

See also:

• <a href=“#math-symbols-title” title=“2.3.13. Math Symbols” class=“link”>Math Symbols</a>
• <a href=“#binary-and-relational-ops-title” title=“2.3.19. Binary and Relational Operators” class=“link”>Binary and Relational Operators</a>
• <a href=“#greek-letters-title” title=“2.3.19. Greek Letters” class=“link”>Greek Letters</a>
• <a href=“#misc-symbols-title” title=“2.3.19. Miscellaneous Symbols” class=“link”>Miscellaneous Symbols</a>
• <a href=“#variable-math-size-symbols-title” title=“2.3.19. Variable Size Math Symbols” class=“link”>Variable Size Math Symbols</a>

<a name=“idp7874080” id=“idp7874080” title=“idp7874080”></a><a name=“idp7875152” id=“idp7875152” title=“idp7875152”></a><a name=“idp7876224” id=“idp7876224” title=“idp7876224”></a><a name=“idp7877712” id=“idp7877712” title=“idp7877712”></a>

Some math symbols are obtained by typing the corresponding keyboard character. Examples include

+ - = < >  

plus, minus, and equal sign may be used in either text or math mode, but < and > are math mode only (they produce inverted exclamation and question marks, respectively, in text mode).

The following commands may be used only in math mode:

• \pm plus or minus sign
• \mp minus or plus sign
• \times times (an “x”)
• \div divided by sign
• \ast an asterisk (centered)
• \star a five-point star (centered)
• \bullet a bullet
• \circ an open bullet
• \cdot a centered dot
• \leq less than or equal to
• \ll much less than
• \subset is a subset of
• \geq greater than or equal to
• \gg much greater than
• \equiv equivalence symbol
• \sim similar to
• \simeq similar or equal to
• \approx approximately equal to
• \neq not equal to
• \per “perpendicular to” symbols
• \propto proportional to

Note that greater than and less than are obtained simply by entering > and <.

A slash, indicating not can be placed through a symbol (or a letter) with the \not command. For example, not less than is \not< and not less than or equal to is \not\leq. If the slash isn't properly positioned it can be moved by putting a math mode spacing command between the \notand the symbol.

<a name=“idp7919776” id=“idp7919776” title=“idp7919776”></a>

Delimiters are objects which act logically like parentheses. These can be used only in math mode.

The delimiters recognized by LaTeX include:

• ( (left parenthesis)
• ) (right parenthesis)
• [ (left bracket)
• ] (right bracket)
• \{ (left brace)
• \} (right brace)
• | (vertical line)
• \vert (vertical line)
• \| (double vertical lines)
• \Vert (double vertical lines)
• / (slash)
• \backslash (backslash)
• \langle (left angle bracket)
• \rangle (right angle bracket)
• \uparrow (uparrow)
• \downarrow (down arrow)
• \updownarrow (up/down arrow)

Delimiters in formulas should be big enough to fit around the formulas they delimit (for example arround arrays). To obtain stretchable delimiters (LaTeX makes them the appropriate size) type a \left or \right command before the delimiter. \left and \right commands must come in matching pairs, although the delimiters themselves need not be the same. Thus, \left \{ … \right \[ produces a legal pair. In cases where only one delimiter is desired, it is possible to make the matching delimiter //invisible// by typing a period (.) after the command, i.e., \left. or \right. In an <a href="#env-eqnarray" title="2.3.6. eqnarray">eqnarray</a> environment the matching \left and \right cannot be split between lines and it may be necessary to use an //invisible// \right. and \left. to terminate and begin parts on different lines. In this case a second problem may arise, since the size of the delimiters will be chosen only for the //local part//, so that the size of the //visible// //left// and //right// delimiters might not match. The solution is to trick LaTeX into thinking that both parts have the same vertical height. This can be done by placing a strut, that is a zero-width \rule. It can also be accomplished with the \vphantom command, which I have not found documented, but which appears to work. \vphantom{construct} creates a zero-width object with the height of construct. The argument can contain things such as \frac or the //variable size math symbols// and should be chosen according to what is in the section with the delimiter you want to match. == <a name="idp7966848" id="idp7966848" title="idp7966848"></a>Some Examples == == <a name="idp7967536" id="idp7967536" title="idp7967536"></a>A six-j symbol == <pre>\[ \left\{ \begin{array}{ccc} a & b & c \\ d & e & f \end{array} \right>\} \] </pre>

This should be displayed something like (insofar as it can be rendered in “ascii art”):

( a b c ) -       - ( d e f ) 

Note that the \[ ... \] set this off as Display Math, and that the Array Environment is used to generate the three centered columns inside the braces.

<pre>\[ f(x) = \left\{ \begin{array}{l} 0, x < 0 \\ 1, x = 0 \\ 2, x > 0 \end{array} \right. \] </pre>

will be displayed as

        ( 0, x < 0 f(x) =  - 1, x = 0         ( 2, x > 0 

Note that the invisible \right delimiter is specified using a period.

<a name=“idp7977696” id=“idp7977696” title=“idp7977696”></a>

Ellipses (three dots) can be produced by the following commands

• \ldots horizontally at bottom of line
• \cdots horizontally center of line (math mode only)
• \ddots diagonal (math mode only)
• \vdots vertical (math mode only)

<a name=“idp7986560” id=“idp7986560” title=“idp7986560”></a>

These commands may be used only in math mode:

• \alpha
• \beta
• \gamma
• \delta
• \epsilon
• \varepsilon (variation, script-like)
• \zeta
• \eta
• \theta
• \vartheta (variation, script-like)
• \iota
• \kappa
• \lambda
• \mu
• \nu
• \xi
• \pi
• \varpi (variation)
• \rho
• \varrho (variation, with the tail)
• \sigma
• \varsigma (variation, script-like)
• \tau
• \upsilon
• \phi
• \varphi (variation, script-like)
• \chi
• \psi
• \omega

Capital letters:

• \Gamma
• \Delta
• \Theta
• \Lambda
• \Xi
• \Pi
• \Sigma
• \Upsilon
• \Phi
• \Psi
• \Omega

See also:

• <a href=“#math-symbols-title” title=“2.3.13. Math Symbols” class=“link”>Math Symbols</a>
• <a href=“#accents-on-chars-title” title=“2.3.19. Accents on Characters” class=“link”>Accents</a>
• <a href=“#misc-symbols-title” title=“2.3.19. Miscellaneous Symbols” class=“link”>Miscellaneous Symbols</a>

<a name=“idp8045424” id=“idp8045424” title=“idp8045424”></a>

The following symbols are also used only in math mode

• <a name=“cmd-misc-symbol-aleph” id=“cmd-misc-symbol-aleph” title=“cmd-misc-symbol-aleph”></a>\aleph Hebrew aleph
• <a name=“cmd-misc-symbol-hbar” id=“cmd-misc-symbol-hbar” title=“cmd-misc-symbol-hbar”></a>\hbar h-bar, Planck's constant
• <a name=“cmd-misc-symbol-imath” id=“cmd-misc-symbol-imath” title=“cmd-misc-symbol-imath”></a>\imath variation on _i_; no dot
• <a name=“cmd-misc-symbol-jmath” id=“cmd-misc-symbol-jmath” title=“cmd-misc-symbol-jmath”></a>\jmath variation on _j_; no dot
• <a name=“cmd-misc-symbol-ell” id=“cmd-misc-symbol-ell” title=“cmd-misc-symbol-ell”></a>\ell script (loop) l
• <a name=“cmd-misc-symbol-wp” id=“cmd-misc-symbol-wp” title=“cmd-misc-symbol-wp”></a>\wp fancy script lowercase P
• <a name=“cmd-misc-symbol-re” id=“cmd-misc-symbol-re” title=“cmd-misc-symbol-re”></a>\Re script capital R ( Real)
• <a name=“cmd-misc-symbol-im” id=“cmd-misc-symbol-im” title=“cmd-misc-symbol-im”></a>\Im script capital I ( Imaginary)
• <a name=“cmd-misc-symbol-prime” id=“cmd-misc-symbol-prime” title=“cmd-misc-symbol-prime”></a>\prime prime (also obtained by typing ')
• <a name=“cmd-misc-symbol-nabla” id=“cmd-misc-symbol-nabla” title=“cmd-misc-symbol-nabla”></a>\nabla inverted capital Delta
• <a name=“cmd-misc-symbol-surd” id=“cmd-misc-symbol-surd” title=“cmd-misc-symbol-surd”></a>\surd radical (square root) symbol
• <a name=“cmd-misc-symbol-angle” id=“cmd-misc-symbol-angle” title=“cmd-misc-symbol-angle”></a>\angle angle symbol
• <a name=“cmd-misc-symbol-forall” id=“cmd-misc-symbol-forall” title=“cmd-misc-symbol-forall”></a>\forall for all (inverted A)
• <a name=“cmd-misc-symbol-exists” id=“cmd-misc-symbol-exists” title=“cmd-misc-symbol-exists”></a>\exists exists (left-facing E)
• <a name=“cmd-misc-symbol-partial” id=“cmd-misc-symbol-partial” title=“cmd-misc-symbol-partial”></a>\partial partial derivative symbol
• <a name=“cmd-misc-symbol-infty” id=“cmd-misc-symbol-infty” title=“cmd-misc-symbol-infty”></a>\infty infinity symbol
• <a name=“cmd-misc-symbol-triangle” id=“cmd-misc-symbol-triangle” title=“cmd-misc-symbol-triangle”></a>\triangle open triangle symbol
• <a name=“cmd-misc-symbol-box” id=“cmd-misc-symbol-box” title=“cmd-misc-symbol-box”></a>\Box open square
• <a name=“cmd-misc-symbol-diamond” id=“cmd-misc-symbol-diamond” title=“cmd-misc-symbol-diamond”></a>\Diamond open diamond
• <a name=“cmd-misc-symbol-flat” id=“cmd-misc-symbol-flat” title=“cmd-misc-symbol-flat”></a>\flat music: flat symbol
• <a name=“cmd-misc-symbol-natural” id=“cmd-misc-symbol-natural” title=“cmd-misc-symbol-natural”></a>\natural music: natural symbol
• <a name=“cmd-misc-symbol-clubsuit” id=“cmd-misc-symbol-clubsuit” title=“cmd-misc-symbol-clubsuit”></a>\clubsuit playing cards: club suit symbol
• <a name=“cmd-misc-symbol-diamondsuit” id=“cmd-misc-symbol-diamondsuit” title=“cmd-misc-symbol-diamondsuit”></a>\diamondsuit playing cards: diamond suit symbol
• <a name=“cmd-misc-symbol-heartsuit” id=“cmd-misc-symbol-heartsuit” title=“cmd-misc-symbol-heartsuit”></a>\heartsuit playing cards: heart suit symbol
• <a name=“cmd-misc-symbol-spadsuit” id=“cmd-misc-symbol-spadsuit” title=“cmd-misc-symbol-spadsuit”></a>\spadesuit playing cards: space suit symbol

The following symbols can be used in any mode:

• <a name=“cmd-other-symbol-dag” id=“cmd-other-symbol-dag” title=“cmd-other-symbol-dag”></a>\dag dagger
• <a name=“cmd-other-symbol-ddag” id=“cmd-other-symbol-ddag” title=“cmd-other-symbol-ddag”></a»\ddag double dagger
• <a name=“cmd-other-symbol-s” id=“cmd-other-symbol-s” title=“cmd-other-symbol-s”></a»\S section symbol
• <a name=“cmd-other-symbol-p” id=“cmd-other-symbol-p” title=“cmd-other-symbol-p”></a»\P paragraph symbol
• <a name=“cmd-other-symbol-copyright” id=“cmd-other-symbol-copyright” title=“cmd-other-symbol-copyright”></a»\copyright copyright symbol
• <a name=“cmd-other-symbol-pounds” id=“cmd-other-symbol-pounds” title=“cmd-other-symbol-pounds”></a»\pounds British pound sterling symbol

Twenty-six calligraphic letters are provided (the upper case alphabet). These can only be used in math mode.

In LaTeX 2.09 they are produced with the \cal declaration:

${\cal A}$ 

In LaTeX2e they are obtained with the \mathcal command:

$\mathcal{CAL}$ 

<a name=“idp8119200” id=“idp8119200” title=“idp8119200”></a>

Functions like log or cos are normally used in math mode. However, inmath mode strings of letters are treated as a product of variables, which would normally be displayed in math italics rather than a text font which would be appropriate for these functions. To get proper display of such functions they are generated with LaTeX commands.

Some of these commands are:

• <a name=“cmd-math-func-arccos” id=“cmd-math-func-arccos” title=“cmd-math-func-arccos”></a>\arccos
• <a name=“cmd-math-func-arcsin” id=“cmd-math-func-arcsin” title=“cmd-math-func-arcsin”></a>\arcsin
• <a name=“cmd-math-func-arctan” id=“cmd-math-func-arctan” title=“cmd-math-func-arctan”></a>\arctan
• <a name=“cmd-math-func-cos” id=“cmd-math-func-cos” title=“cmd-math-func-cos”></a>\cos
• <a name=“cmd-math-func-cosh” id=“cmd-math-func-cosh” title=“cmd-math-func-cosh”></a>\cosh
• <a name=“cmd-math-func-cot” id=“cmd-math-func-cot” title=“cmd-math-func-cot”></a>\cot
• <a name=“cmd-math-func-coth” id=“cmd-math-func-coth” title=“cmd-math-func-coth”></a>\coth
• <a name=“cmd-math-func-csc” id=“cmd-math-func-csc” title=“cmd-math-func-csc”></a>\csc
• <a name=“cmd-math-func-deg” id=“cmd-math-func-deg” title=“cmd-math-func-deg”></a>\deg
• <a name=“cmd-math-func-det” id=“cmd-math-func-det” title=“cmd-math-func-det”></a>\det
• <a name=“cmd-math-func-dim” id=“cmd-math-func-dim” title=“cmd-math-func-dim”></a>\dim
• <a name=“cmd-math-func-exp” id=“cmd-math-func-exp” title=“cmd-math-func-exp”></a>\exp
• <a name=“cmd-math-func-gcd” id=“cmd-math-func-gcd” title=“cmd-math-func-gcd”></a>\gcd
• <a name=“cmd-math-func-hom” id=“cmd-math-func-hom” title=“cmd-math-func-hom”></a>\hom
• <a name=“cmd-math-func-inf” id=“cmd-math-func-inf” title=“cmd-math-func-inf”></a>\inf
• <a name=“cmd-math-func-ker” id=“cmd-math-func-ker” title=“cmd-math-func-ker”></a>\ker
• <a name=“cmd-math-func-lg” id=“cmd-math-func-lg” title=“cmd-math-func-lg”></a>\lg
• <a name=“cmd-math-func-lim” id=“cmd-math-func-lim” title=“cmd-math-func-lim”></a>\lim
• <a name=“cmd-math-func-liminf” id=“cmd-math-func-liminf” title=“cmd-math-func-liminf”></a>\liminf
• <a name=“cmd-math-func-limsup” id=“cmd-math-func-limsup” title=“cmd-math-func-limsup”></a>\limsup
• <a name=“cmd-math-func-ln” id=“cmd-math-func-ln” title=“cmd-math-func-ln”></a>\ln
• <a name=“cmd-math-func-log” id=“cmd-math-func-log” title=“cmd-math-func-log”></a>\log
• <a name=“cmd-math-func-max” id=“cmd-math-func-max” title=“cmd-math-func-max”></a>\max
• <a name=“cmd-math-func-min” id=“cmd-math-func-min” title=“cmd-math-func-min”></a>\min
• <a name=“cmd-math-func-sec” id=“cmd-math-func-sec” title=“cmd-math-func-sec”></a>\sec
• <a name=“cmd-math-func-sin” id=“cmd-math-func-sin” title=“cmd-math-func-sin”></a>\sin
• <a name=“cmd-math-func-sinh” id=“cmd-math-func-sinh” title=“cmd-math-func-sinh”></a>\sinh
• <a name=“cmd-math-func-sup” id=“cmd-math-func-sup” title=“cmd-math-func-sup”></a>\sup
• <a name=“cmd-math-func-tan” id=“cmd-math-func-tan” title=“cmd-math-func-tan”></a>\tan
• <a name=“cmd-math-func-tanh” id=“cmd-math-func-tanh” title=“cmd-math-func-tanh”></a>\tanh

Two commands are provided for the “modulus” function

• <a name=“cmd-math-func-bmod” id=“cmd-math-func-bmod” title=“cmd-math-func-bmod”></a>\bmod
• <a name=“cmd-math-func-pmod” id=“cmd-math-func-pmod” title=“cmd-math-func-pmod”></a>\pmod{}

The former would be used to write “a mod b” as a \bmod b and the latter, which requires an argument that is displayed in parentheses, would be used to write “n = i (mod j)” as n = i \pmod{j}

<a name=“idp8179888” id=“idp8179888” title=“idp8179888”></a>

The size of some mathematical symbols, notably summation signs, product signs, and integral signs, depends on the environment in which they appear (i.e., displaymath as opposed to math environments.

These include:

• <a name=“cmd-math-symbol-sum” id=“cmd-math-symbol-sum” title=“cmd-math-symbol-sum”></a>\sum a summation sign (capital sigma)
• <a name=“cmd-math-symbol-prod” id=“cmd-math-symbol-prod” title=“cmd-math-symbol-prod”></a>\prod a product (capital pi)
• <a name=“cmd-math-symbol-coprod” id=“cmd-math-symbol-coprod” title=“cmd-math-symbol-coprod”></a>\coprod a coproduct (inverted capital pi)
• <a name=“cmd-math-symbol-int” id=“cmd-math-symbol-int” title=“cmd-math-symbol-int”></a>\int an integral sign
• <a name=“cmd-math-symbol-oint” id=“cmd-math-symbol-oint” title=“cmd-math-symbol-oint”></a>\oint a surface (circular) integral sign
• <a name=“cmd-math-symbol-bigcup” id=“cmd-math-symbol-bigcup” title=“cmd-math-symbol-bigcup”></a>\bigcup big “U”
• <a name=“cmd-math-symbol-bigcap” id=“cmd-math-symbol-bigcap” title=“cmd-math-symbol-bigcap”></a>\bigcap big inverted “U”
• <a name=“cmd-math-symbol-bigvee” id=“cmd-math-symbol-bigvee” title=“cmd-math-symbol-bigvee”></a>\bigvee big “V”
• <a name=“cmd-math-symbol-bigwedge” id=“cmd-math-symbol-bigwedge” title=“cmd-math-symbol-bigwedge”></a>\bigwedge big inverted “V”
• <a name=“cmd-math-symbol-bigodot” id=“cmd-math-symbol-bigodot” title=“cmd-math-symbol-bigodot”></a>\bigodot big “O” with dot at center
• <a name=“cmd-math-symbol-bigotimes” id=“cmd-math-symbol-bigotimes” title=“cmd-math-symbol-bigotimes”></a>\bigotimes big “O” with cross inside
• <a name=“cmd-math-symbol-bigoplus” id=“cmd-math-symbol-bigoplus” title=“cmd-math-symbol-bigoplus”></a>\bigoplus big “O” with a + inside
• <a name=“cmd-math-symbol-biguplus” id=“cmd-math-symbol-biguplus” title=“cmd-math-symbol-biguplus”></a>\biguplus big “U” with a + inside

The \sqrt command also produces a variable size symbol appropriate for the size of hte radicand argument.

The “limits” associated with these symbols are entered as subscripts for entries appearing below the symbol and as superscripts for entries appearing above the symbol. For example the sum from n=0 to infinity of xⁿ would be entered as

\sum_{n=0}^{\infty} x_{n} 

The actual placement of the limits depends on whether this is in displaymath mode in which case they are placed below/above or in math mode in running text in which case they are placed as regular subscripts and superscripts.

Note that it is possible to treat several of these symbols (a common example would be a double sum) as a single symbol for placing limits above and/or below by using the \mathop command.

Hats and tildes over symbols which stretch (as best they can) to the correct size for their arguments are produced by \widehat and \widetilde

<a name=“idp8218784” id=“idp8218784” title=“idp8218784”></a><a name=“idp8219568” id=“idp8219568” title=“idp8219568”></a>

A large document requires a lot of input. Rather than putting the whole input in a single large file, it's more efficient to split it into several smaller ones. Regardless of how many separate files you use, there is one that is the root file; it is the one whose name you type when you run LaTeX.

<a name=“idp8222720” id=“idp8222720” title=“idp8222720”></a>

\include{file}

The \include command is used in conjunction with the \includeonly command for selective inclusion of files. The file argument is the first name of a file, denoting file.tex. If file is one the file names in the file list of the \includeonly command or if there is no \includeonly command, the \include command is equivalent to

\clearpage \input{file} \clearpage 

except that if the file file.tex does not exist, then a warning message rather than an error is produced. If the file is not in the file list, the \include command is equivalent to \clearpage.

The \include command may not appear in the preamble or in a file read by another \include command.

<a name=“idp8237344” id=“idp8237344” title=“idp8237344”></a>

\includeonly{ _filelist }

The \includeonly command controls which files will be read in by an \include command. _filelist should be a comma-separated list of filenames. Each filename must match exactly a filename specified in a \include command. This command can only appear in the preamble.

<a name=“idp8244320” id=“idp8244320” title=“idp8244320”></a>

\input{file}

The \input command causes the indicated file to be read and processed, exactly as if its contents had been inserted in the current file at that point. The file name may be a complete file name with extension or just a first name, in which case the file file.tex is used.

<a name=“idp8250608” id=“idp8250608” title=“idp8250608”></a><a name=“idp8251424” id=“idp8251424” title=“idp8251424”></a>

Your input file must contain the following commands as a minimum:

\documentclass{class} \begin{document}   ... your text goes here ... \end{document} 

where the class selected is one of the valid classes for LaTeX. See <a href=“#document-classes” title=“2.3.4 Document Classes”>Document Classes</a> (and see <a href=“#overview” title=“2.2 Overview of LaTeX and Local Guide”>Overview</a>), for details of the various document classes available locally.

You may include other LaTeX commands between the \documentclass and the \begin{document} commands (i.e., in the `preamble').

<a name=“idp8260752” id=“idp8260752” title=“idp8260752”></a>

A table of contents is produced with the \tableofcontents <a name=“idp8262592” id=“idp8262592” title=“idp8262592”></a> command. You put the command right where you want the table of contents to go; LaTeX does the rest for you. It produces a heading, but it does not automatically start a new page. If you want a new page after the table of contents, include a \newpage command after the \tableofcontents command.

There are similar commands \listoffigures <a name=“idp8266752” id=“idp8266752” title=“idp8266752”></a> and \listoftables <a name=“idp8268288” id=“idp8268288” title=“idp8268288”></a> for producing a list of figures and a list of tables, respectively. Everything works exactly the same as for the table of contents.

NOTE: If you want any of these items to be generated, you cannot have the \nofiles <a name=“idp8270432” id=“idp8270432” title=“idp8270432”></a> command in your document.

<a name=“idp8272608” id=“idp8272608” title=“idp8272608”></a>

\addcontentsline{file}{sec_unit}{entry}

The \addcontentsline command adds an entry to the specified list or table where:

• file is the extension of the file on which information is to be written: toc (table of contents), lof (list of figures), or lot (list of tables).
• <p>sec_unit controls the formatting of the entry. It should be one of the following, depending upon the value of the file argument:</p> <p> <ol class=“orderedlist”> <li class=“listitem”>toc — the name of the sectional unit, such as part or subsection.</li> <li class=“listitem”>lof — figure</li> <li class=“listitem”>lot — table</li> </ol> </p>
• entry is the text of the entry.

<a name=“idp8287920” id=“idp8287920” title=“idp8287920”></a>

\addtocontents{file}{text}

The \addtocontents command adds text (or formatting commands) directly to the file that generates the table of contents or list of figures or tables.

• file is the extension of the file on which information is to be written: toc (table of contents), lof (list of figures), or lot (list of tables).
• text is the information to be written.

<a name=“idp8298048” id=“idp8298048” title=“idp8298048”></a><a name=“idp8298864” id=“idp8298864” title=“idp8298864”></a>

<a name=“idp8300800” id=“idp8300800” title=“idp8300800”></a>

\typein[cmd]{msg}

Prints msg on the terminal and causes LaTeX to stop and wait for you to type a line of input, ending with return. If the cmd argument is missing, the typed input is processed as if it had been included in the input file in place of the \typein command. If the cmd argument is present, it must be a command name. This command name is then defined or redefined to be the typed input.

<a name=“idp8307536” id=“idp8307536” title=“idp8307536”></a>

\typeout{msg}

Prints msg on the terminal and in the log file. Commands in msg that are defined with \newcommand or \renewcommand are replaced by their definitions before being printed.

LaTeX's usual rules for treating multiple spaces as a single space and ignoring spaces after a command name apply to msg. A \space command in msg causes a single space to be printed. A ^^J in msg prints a newline.

<a name=“idp8319248” id=“idp8319248” title=“idp8319248”></a><a name=“idp8320064” id=“idp8320064” title=“idp8320064”></a>

The typeface is specified by giving the size and style. A typeface is also called a font.

<a name=“idp8324560” id=“idp8324560” title=“idp8324560”></a><a name=“idp8325376” id=“idp8325376” title=“idp8325376”></a><a name=“idp8326192” id=“idp8326192” title=“idp8326192”></a>

The following type style commands are supported by LaTeX.

These commands are used like \textit{italics text}. The corresponding command in parenthesis is the declaration form, which takes no arguments. The scope of the declaration form lasts until the next type style command or the end of the current group.

The declaration forms are cumulative; i.e., you can say \sffamily\bfseries to get sans serif boldface.

You can also use the environment form of the declaration forms; e.g. \begin{ttfamily}…\end{ttfamily}.

<a name=“table-typefaces” id=“table-typefaces” title=“table-typefaces”></a>

Table 1.9. Typefaces

<table summary=“Typefaces” border=“0”> <tbody> <tr> <td align=“left”>\textrm (\rmfamily) <a name=“idp8336464” id=“idp8336464” title=“idp8336464”></a> <a name=“idp8337280” id=“idp8337280” title=“idp8337280”></a></td> <td align=“justify”>Roman.</td> </tr> <tr> <td align=“left”>\textit (\itshape) <a name=“idp8339440” id=“idp8339440” title=“idp8339440”></a> <a name=“idp8340256” id=“idp8340256” title=“idp8340256”></a>, \emph <a name=“idp8341104” id=“idp8341104” title=“idp8341104”></a></td> <td align=“justify”>Emphasis (toggles between \textit and \textrm).</td> </tr> <tr> <td align=“left”>\textmd (\mdseries) <a name=“idp8343296” id=“idp8343296” title=“idp8343296”></a> <a name=“idp8344112” id=“idp8344112” title=“idp8344112”></a></td> <td align=“justify”>Medium weight (default). The opposite of boldface.</td> </tr> <tr> <td align=“left”>\textbf (\bfseries) <a name=“idp8346320” id=“idp8346320” title=“idp8346320”></a> <a name=“idp8347136” id=“idp8347136” title=“idp8347136”></a></td> <td align=“justify”>Boldface.</td> </tr> <tr> <td align=“left”>\textup (\upshape) <a name=“idp8349296” id=“idp8349296” title=“idp8349296”></a> <a name=“idp8350112” id=“idp8350112” title=“idp8350112”></a></td> <td align=“justify”>Upright (default). The opposite of slanted.</td> </tr> <tr> <td align=“left”>\textsl (\slshape) <a name=“idp8352304” id=“idp8352304” title=“idp8352304”></a> <a name=“idp8353120” id=“idp8353120” title=“idp8353120”></a></td> <td align=“justify”>Slanted.</td> </tr> <tr> <td align=“left”>\textsf (\sffamily) <a name=“idp8355280” id=“idp8355280” title=“idp8355280”></a> <a name=“idp8356096” id=“idp8356096” title=“idp8356096”></a></td> <td align=“justify”>Sans serif.</td> </tr> <tr> <td align=“left”>\textsc (\scshape) <a name=“idp8358256” id=“idp8358256” title=“idp8358256”></a> <a name=“idp8359072” id=“idp8359072” title=“idp8359072”></a></td> <td align=“justify”>Small caps.</td> </tr> <tr> <td align=“left”>\texttt (\ttfamily) <a name=“idp8361232” id=“idp8361232” title=“idp8361232”></a> <a name=“idp8362048” id=“idp8362048” title=“idp8362048”></a></td> <td align=“justify”>Typewriter.</td> </tr> <tr> <td align=“left”>\textnormal (\normalfont) <a name=“idp8364208” id=“idp8364208” title=“idp8364208”></a> <a name=“idp8365024” id=“idp8365024” title=“idp8365024”></a></td> <td align=“justify”>Main document font.</td> </tr> <tr> <td align=“left”>\mathrm <a name=“idp8367184” id=“idp8367184” title=“idp8367184”></a></td> <td align=“justify”>Roman, for use in math mode.</td> </tr> <tr> <td align=“left”>\mathbf <a name=“idp8369344” id=“idp8369344” title=“idp8369344”></a></td> <td align=“justify”>Boldface, for use in math mode. For bold symbols or complete equations take a look at \boldsymbol and \bm.</td> </tr> <tr> <td align=“left”>\mathsf <a name=“idp8374272” id=“idp8374272” title=“idp8374272”></a></td> <td align=“justify”>Sans serif, for use in math mode.</td> </tr> <tr> <td align=“left”>\mathtt <a name=“idp8376432” id=“idp8376432” title=“idp8376432”></a></td> <td align=“justify”>Typewriter, for use in math mode.</td> </tr> <tr> <td align=“left”>\mathit <a name=“idp8378592” id=“idp8378592” title=“idp8378592”></a></td> <td align=“justify”>Italics, for use in math mode, e.g. variable names with several letters.</td> </tr> <tr> <td align=“left”>\mathnormal <a name=“idp8380800” id=“idp8380800” title=“idp8380800”></a></td> <td align=“justify”>For use in math mode, e.g. inside another type style declaration.</td> </tr> <tr> <td align=“left”>\mathcal <a name=“idp8383008” id=“idp8383008” title=“idp8383008”></a></td> <td align=“justify”>`Calligraphic' letters, for use in math mode.</td> </tr> </tbody> </table>

In addition, the command \mathversion{bold} <a name=“idp8385904” id=“idp8385904” title=“idp8385904”></a> can be used for switching to bold letters and symbols in formulas. \mathversion{normal} restores the default.

<a name=“idp8388848” id=“idp8388848” title=“idp8388848”></a><a name=“idp8389664” id=“idp8389664” title=“idp8389664”></a><a name=“idp8390480” id=“idp8390480” title=“idp8390480”></a>

The following standard type size commands are supported by LaTeX.

The commands as listed here are “declaration forms”. The scope of the declaration form lasts until the next type style command or the end of the current group.

You can also use the environment form of these commands; e.g. \begin{tiny}…\end{tiny}.

<a name=“table-standard-type-size-commands” id=“table-standard-type-size-commands” title=“table-standard-type-size-commands”></a>

Table 1.10. Standard type size commands

<table summary=“Standard type size commands” border=“0”> <tbody> <tr> <td align=“left”>\tiny<a name=“idp8398464” id=“idp8398464” title=“idp8398464”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\scriptsize <a name=“idp8400960” id=“idp8400960” title=“idp8400960”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\footnotesize <a name=“idp8403200” id=“idp8403200” title=“idp8403200”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\small <a name=“idp8405440” id=“idp8405440” title=“idp8405440”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\normalsize <a name=“idp8407680” id=“idp8407680” title=“idp8407680”></a></td> <td align=“justify”>(default)</td> </tr> <tr> <td align=“left”>\large <a name=“idp8409952” id=“idp8409952” title=“idp8409952”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\Large <a name=“idp8412192” id=“idp8412192” title=“idp8412192”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\LARGE <a name=“idp8414432” id=“idp8414432” title=“idp8414432”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\huge <a name=“idp8416672” id=“idp8416672” title=“idp8416672”></a></td> <td align=“justify”> </td> </tr> <tr> <td align=“left”>\Huge <a name=“idp8418912” id=“idp8418912” title=“idp8418912”></a></td> <td align=“justify”> </td> </tr> </tbody> </table>

<br />

<a name=“idp8421824” id=“idp8421824” title=“idp8421824”></a><a name=“idp8422640” id=“idp8422640” title=“idp8422640”></a>

These commands are primarily intended for writers of macros and packages. The commands listed here are only a subset of the available ones. For full details, you should consult Chapter 7 of The LaTeX Companion.

<a name=“table-low-level-font-commands” id=“table-low-level-font-commands” title=“table-low-level-font-commands”></a>

Table 1.11. Low-level font commands

<table summary=“Low-level font commands” border=“0”> <tbody> <tr> <td align=“left”>\fontencoding{enc} <a name=“idp8429296” id=“idp8429296” title=“idp8429296”></a></td> <td align=“justify”>Select font encoding. Valid encodings include OT1 and T1.</td> </tr> <tr> <td align=“left”>\fontfamily{family} <a name=“idp8432864” id=“idp8432864” title=“idp8432864”></a></td> <td align=“justify”>Select font family. Valid families include:

• cmr for Computer Modern Roman
• cmss for Computer Modern Sans Serif
• cmtt for Computer Modern Typewriter

and numerous others.</td> </tr> <tr> <td align=“left”>\fontseries{series} <a name=“idp8439552” id=“idp8439552” title=“idp8439552”></a></td> <td align=“justify”>Select font series. Valid series include:

• m Medium (normal)
• b Bold
• c Condensed
• bc Bold condensed
• bx Bold extended

and various other combinations.</td> </tr> <tr> <td align=“left”>\fontshape{shape} <a name=“idp8448576” id=“idp8448576” title=“idp8448576”></a></td> <td align=“justify”>Select font shape. Valid shapes are:

• n Upright (normal)
• it Italic
• sl Slanted (oblique)
• sc Small caps
• ui Upright italics
• ol Outline

The two last shapes are not available for most font families.</td> </tr> <tr> <td align=“left”>\fontsize{size}{skip} <a name=“idp8458864” id=“idp8458864” title=“idp8458864”></a></td> <td align=“justify”>Set font size. The first parameter is the font size to switch to; the second is the \baselineskip to use. The unit of both parameters defaults to pt. A rule of thumb is that the baselineskip should be 1.2 times the font size.</td> </tr> <tr> <td align=“left”>\selectfont <a name=“idp8461936” id=“idp8461936” title=“idp8461936”></a></td> <td align=“justify”>The changes made by calling the four font commands described above do not come into effect until \selectfont is called.</td> </tr> <tr> <td align=“left”>\usefont{enc}{family}{series}{shape} <a name=“idp8464928” id=“idp8464928” title=“idp8464928”></a></td> <td align=“justify”>Equivalent to calling \fontencoding, \fontfamily, \fontseries and \fontshape with the given parameters, followed by \selectfont.</td> </tr> </tbody> </table>

<a name=“idp8472336” id=“idp8472336” title=“idp8472336”></a>

The input file specification indicates the file to be formatted; TeX uses .tex as a default file extension. If you omit the input file entirely, TeX accepts input from the terminal. You specify command options by supplying a string as a parameter to the command; e.g.

latex \scrollmode\input foo.tex

will process foo.tex without pausing after every error.

Output files are always created in the current directory. When you fail to specify an input file name, TeX bases the output names on the file specification associated with the logical name TEX_OUTPUT, typically texput.log.

<a name=“idp8481440” id=“idp8481440” title=“idp8481440”></a>

<a name=“idp8484512” id=“idp8484512” title=“idp8484512”></a><a name=“idp8485328” id=“idp8485328” title=“idp8485328”></a>

amsmath consists of several packages to aid in typesetting math.

<a name=“boldsymbol-linkend” id=“boldsymbol-linkend” title=“boldsymbol-linkend”></a>

• \boldsymbol <a name=“idp8490112” id=“idp8490112” title=“idp8490112” class=“indexterm”></a> <p>Produces a bold math symbol. When not only a single symbol, but a complete equation has to be bold you might consider using the superior \bm command which takes better care of spacing.</p>
• <a name=“pmb-linkend” id=“pmb-linkend” title=“pmb-linkend”></a>\pmb <a name=“idp8495024” id=“idp8495024” title=“idp8495024” class=“indexterm”></a> <p>Can be used for mathematic symbols, when no bold version is available. It prints the standard symbol several times slightly shifted and is inferior to a real bold font</p>

<a name=“idp8499568” id=“idp8499568” title=“idp8499568”></a><a name=“idp8500384” id=“idp8500384” title=“idp8500384”></a>

\usepackage{dcolumn}

Defines a system for defining columns of entries in an array or tabular which are to be aligned on a decimal point.

This package defines D to be a column specifier with three arguments:

D{sep.tex}{sep.dvi}{decimal places} 

sep.tex should be a single character, this is used as the separator in the .tex file. It will usually be '.' or ','.

sep.dvi is used as the separator in the output.

decimal places should be the maximum number of decimal places in the column.

\newcolumntype can be used to define own column types.

<a name=“idp8515552” id=“idp8515552” title=“idp8515552”></a>

The contents of this section was taken from the documentation of float v1.3d of 2001/11/08.

“This style option improves the interface for defining objects such as figures and tabels in LaTeX. It adds the notion of a float style that governs the appearance of floats.”

• \newfloat{<placement>}{<ext>}[<within>] <a name=“idp8521344” id=“idp8521344” title=“idp8521344” class=“indexterm”></a><a name=“idp8522160” id=“idp8522160” title=“idp8522160” class=“indexterm”></a> <p>Add a new class of floats.</p>
• \floatstyle{<style>} <a name=“idp8525728” id=“idp8525728” title=“idp8525728” class=“indexterm”></a><a name=“idp8526544” id=“idp8526544” title=“idp8526544” class=“indexterm”></a> <p>Sets a default float style.</p>
• \floatname{<style>}{<name>} <a name=“idp8530080” id=“idp8530080” title=“idp8530080” class=“indexterm”></a><a name=“idp8530896” id=“idp8530896” title=“idp8530896” class=“indexterm”></a> <p>Define the float name used in the caption of a float.</p>
• \floatplacement{<>}{<placement>} <a name=“idp8534880” id=“idp8534880” title=“idp8534880” class=“indexterm”></a><a name=“idp8535696” id=“idp8535696” title=“idp8535696” class=“indexterm”></a> <p>Resets the default placement specifier of a class of floats.</p>
• \restylefloat<style> <a name=“idp8539248” id=“idp8539248” title=“idp8539248” class=“indexterm”></a><a name=“idp8540064” id=“idp8540064” title=“idp8540064” class=“indexterm”></a> <p>Change styles for the standard float types figure and table.</p>
• \listof{<type>}{<title>} <a name=“idp8545040” id=“idp8545040” title=“idp8545040” class=“indexterm”></a><a name=“idp8545856” id=“idp8545856” title=“idp8545856” class=“indexterm”></a> <p>Produces a list of all floats of a given class.</p>

<a name=“idp8550560” id=“idp8550560” title=“idp8550560”></a>

\usepackage[T1]{fontenc}

chooses T1-fonts and allows correct automatic hyphenation.

<a name=“idp8555184” id=“idp8555184” title=“idp8555184”></a><a name=“idp8556000” id=“idp8556000” title=“idp8556000”></a>

Das german Paket muß geladen sein:

• “a <a name=“idp8560464” id=“idp8560464” title=“idp8560464” class=“indexterm”></a> <p>erzeugt ein ä </p> <p>entsprechend “o, “u, “A, “O, “U, “s (ß)</p>
• “ck <a name=“idp8568768” id=“idp8568768” title=“idp8568768” class=“indexterm”></a> <p>wird bei Trennung zu k-k</p>
• “ff <a name=“idp8572720” id=“idp8572720” title=“idp8572720” class=“indexterm”></a> <p>wird bei Trennung zu ff-f</p> <p>entsprechend “ll, “mm, “pp, “rr, “tt</p>
• \glqq <a name=“idp8580720” id=“idp8580720” title=“idp8580720” class=“indexterm”></a> <p>oder “` erzeugt untere doppelte Anführungszeichen</p>
• <a name=“cmd-grqq” id=“cmd-grqq” title=“cmd-grqq”></a>\grqq <a name=“idp8585504” id=“idp8585504” title=“idp8585504” class=“indexterm”></a> <p>oder ”' erzeugt obere doppelte Anführungszeichen</p>
• \glq <a name=“idp8589808” id=“idp8589808” title=“idp8589808” class=“indexterm”></a> <p>erzeugt untere einfache Anführungszeichen</p>
• \flqq <a name=“idp8593376” id=“idp8593376” title=“idp8593376” class=“indexterm”></a> <p>oder ”< doppelte linke französische Anführungszeichen</p>
• \frqq <a name=“idp8597680” id=“idp8597680” title=“idp8597680” class=“indexterm”></a> <p>oder ”> doppelte rechte französische Anführungszeichen</p>
• \flq <a name=“idp8601984” id=“idp8601984” title=“idp8601984” class=“indexterm”></a> <p>einfache linke französische Anführungszeichen</p>
• \frq <a name=“idp8605552” id=“idp8605552” title=“idp8605552” class=“indexterm”></a> <p>einfache rechte französische Anführungszeichen</p>
• “| <a name=“idp8609088” id=“idp8609088” title=“idp8609088” class=“indexterm”></a> <p>verhindert eine Ligatur an der Stelle</p>
• \- <a name=“idp8612528” id=“idp8612528” title=“idp8612528” class=“indexterm”></a> <p>markiert mögliche Trennstelle, im restlichen Wort ist keine Trennung mehr möglich</p>
• ”- <a name=“idp8616112” id=“idp8616112” title=“idp8616112” class=“indexterm”></a> <p>Trennvorschlag, der Rest des Wortes kann noch automatisch getrennt werden</p>
• ”“ <a name=“idp8619648” id=“idp8619648” title=“idp8619648” class=“indexterm”></a> <p>Trennvorschlag, bei dem bei einer Trennung kein Bindestrich eingefügt wird</p>
• ”~ <a name=“idp8623264” id=“idp8623264” title=“idp8623264” class=“indexterm”></a> <p>Bindestrich, an dem nicht getrennt werden darf</p>
• ”= <a name=“idp8626768” id=“idp8626768” title=“idp8626768” class=“indexterm”></a> <p>Bindestrich, an dem getrennt werden darf</p>
• \dq <a name=“idp8630224” id=“idp8630224” title=“idp8630224” class=“indexterm”></a> <p>erzeugt ein nicht-typographisches gerades Anführungszeichen</p> <pre class=“programlisting”>\texttt{\dq} </pre>
• < <a name=“idp8634496” id=“idp8634496” title=“idp8634496” class=“indexterm”></a> <p>oder \dq ergibt das Zoll-Zeichen</p>

<a name=“idp8640048” id=“idp8640048” title=“idp8640048”></a><a name=“idp8640864” id=“idp8640864” title=“idp8640864”></a>

Look up details in grfguide.

<a name=“idp8645088” id=“idp8645088” title=“idp8645088”></a>

\includegraphics[]{picture-name}

File extensions of the graphics should be omitted, so it's easier to change the format (for example for pdf or ps output).

<a name=“idp8649072” id=“idp8649072” title=“idp8649072”></a>

\graphicspath{dir-list}

dir-list is a list of absolute or relative paths, where the command <a href=”#includegraphics” title=“3.6.1 \includegraphics”>\includegraphics{}</a> searches for the graphic files:

\graphicspathtiff would cause the system to look in the subdirectories eps and tiff of the current directory. This is unix syntax, on a Mac it would be:

\graphicspathtiff

Under Windows/DOS use also the slash / to separate directories. Not all tex installations can handle filenames with spaces. So it's better to avoid them.

<a name=“idp8660512” id=“idp8660512” title=“idp8660512”></a><a name=“idp8661584” id=“idp8661584” title=“idp8661584”></a>

For more infos read in the book LaTeX Web Companion or Mit LaTeX ins Web.

• 4 <a name=“idp8667776” id=“idp8667776” title=“idp8667776” class=“indexterm”></a> <p>use Acrobat 4 features (default: false).</p>
• a4paper, a5paper, b5paper, legalpaper, letterpaper, executivepaper <a name=“idp8672048” id=“idp8672048” title=“idp8672048” class=“indexterm”></a><a name=“idp8673952” id=“idp8673952” title=“idp8673952” class=“indexterm”></a><a name=“idp8675856” id=“idp8675856” title=“idp8675856” class=“indexterm”></a><a name=“idp8677760” id=“idp8677760” title=“idp8677760” class=“indexterm”></a><a name=“idp8679664” id=“idp8679664” title=“idp8679664” class=“indexterm”></a><a name=“idp8681568” id=“idp8681568” title=“idp8681568” class=“indexterm”></a> <p>use the specified paper size.</p>
• anchorcolor <a name=“idp8685088” id=“idp8685088” title=“idp8685088” class=“indexterm”></a> <p>set color of anchors (default: black).</p>
• backref <a name=“idp8689328” id=“idp8689328” title=“idp8689328” class=“indexterm”></a> <p>do bibliographical back references (default: false).</p>
• baseurl <a name=“idp8693584” id=“idp8693584” title=“idp8693584” class=“indexterm”></a> <p>set base URL for document (default: empty).</p>
• bookmarks <a name=“idp8697840” id=“idp8697840” title=“idp8697840” class=“indexterm”></a> <p>make bookmarks (default: true).</p>
• bookmarksnumbered <a name=“idp8702128” id=“idp8702128” title=“idp8702128” class=“indexterm”></a> <p>put section numbers in bookmarks (default: false).</p>
• bookmarksopen <a name=“idp8706384” id=“idp8706384” title=“idp8706384” class=“indexterm”></a> <p>open up bookmark tree (default: false).</p>
• bookmarksopenlevel <a name=“idp8710672” id=“idp8710672” title=“idp8710672” class=“indexterm”></a> <p>level to which bookmarks are open (default: \maxdimen).</p>
• bookmarkstype <a name=“idp8714928” id=“idp8714928” title=“idp8714928” class=“indexterm”></a> <p>to specify which `toc' file to mimic toc.</p>
• breaklinks <a name=“idp8718512” id=“idp8718512” title=“idp8718512” class=“indexterm”></a> <p>allow links to break over lines (default: false).</p>
• citebordercolor <a name=“idp8722816” id=“idp8722816” title=“idp8722816” class=“indexterm”></a> <p>color of border around cites (default: 0 1 0).</p>
• citecolor <a name=“idp8727072” id=“idp8727072” title=“idp8727072” class=“indexterm”></a> <p>color of citation links (default: green).</p>
• colorlinks <a name=“idp8731312” id=“idp8731312” title=“idp8731312” class=“indexterm”></a> <p>color links (default: false).</p>
• debug <a name=“idp8735600” id=“idp8735600” title=“idp8735600” class=“indexterm”></a> <p>provide details of anchors defined (same as verbose, default: false).</p>
• draft <a name=“idp8739888” id=“idp8739888” title=“idp8739888” class=“indexterm”></a> <p>do not do any hyper linking (default: false).</p>
• dvipdf, dvipdfm, dvips, dvipsone, dviwindo, hypertex, latex2html, pdftex, tex4ht, textures, ps2pdf, vtex <a name=“idp8744624” id=“idp8744624” title=“idp8744624” class=“indexterm”></a><a name=“idp8746528” id=“idp8746528” title=“idp8746528” class=“indexterm”></a><a name=“idp8748432” id=“idp8748432” title=“idp8748432” class=“indexterm”></a><a name=“idp8750336” id=“idp8750336” title=“idp8750336” class=“indexterm”></a><a name=“idp8752240” id=“idp8752240” title=“idp8752240” class=“indexterm”></a><a name=“idp8754144” id=“idp8754144” title=“idp8754144” class=“indexterm”></a><a name=“idp8756048” id=“idp8756048” title=“idp8756048” class=“indexterm”></a><a name=“idp8757952” id=“idp8757952” title=“idp8757952” class=“indexterm”></a><a name=“idp8759856” id=“idp8759856” title=“idp8759856” class=“indexterm”></a><a name=“idp8761760” id=“idp8761760” title=“idp8761760” class=“indexterm”></a><a name=“idp8763664” id=“idp8763664” title=“idp8763664” class=“indexterm”></a> <p>use the specified backend.</p>
• extension <a name=“idp8767184” id=“idp8767184” title=“idp8767184” class=“indexterm”></a> <p>suffix of linked files (default: dvi).</p>
• filebordercolor <a name=“idp8771392” id=“idp8771392” title=“idp8771392” class=“indexterm”></a> <p>color of border around file links (default: 0 .5 .5).</p>
• filecolor <a name=“idp8775648” id=“idp8775648” title=“idp8775648” class=“indexterm”></a> <p>color of file links (default: cyan).</p>
• frenchlinks <a name=“idp8779888” id=“idp8779888” title=“idp8779888” class=“indexterm”></a> <p>use small caps instead of color for links (default: false).</p>
• hyperfigures <a name=“idp8784160” id=“idp8784160” title=“idp8784160” class=“indexterm”></a> <p>make figures hyper links (default: false).</p>
• hyperindex <a name=“idp8788416” id=“idp8788416” title=“idp8788416” class=“indexterm”></a> <p>set up hyperlinked indices (default: true).</p>
• hypertexnames <a name=“idp8792672” id=“idp8792672” title=“idp8792672” class=“indexterm”></a> <p>use guessable names for links (default: true).</p>
• implicit <a name=“idp8796928” id=“idp8796928” title=“idp8796928” class=“indexterm”></a> <p>redefine LaTeX internals (default: true).</p>
• linkbordercolor <a name=“idp8801616” id=“idp8801616” title=“idp8801616” class=“indexterm”></a> <p>color of border around links (default: 1 0 0).</p>
• linkcolor <a name=“idp8805872” id=“idp8805872” title=“idp8805872” class=“indexterm”></a> <p>color of links (default: red).</p>
• linktocpage <a name=“idp8810128” id=“idp8810128” title=“idp8810128” class=“indexterm”></a> <p>make page number, not text, be link on TOC, LOF and LOT (default: false).</p>
• menubordercolor <a name=“idp8814416” id=“idp8814416” title=“idp8814416” class=“indexterm”></a> <p>color of border around menu links (default: 1 0 0).</p>
• menucolor <a name=“idp8818672” id=“idp8818672” title=“idp8818672” class=“indexterm”></a> <p>color for menu links (default: red).</p>
• naturalnames <a name=“idp8822880” id=“idp8822880” title=“idp8822880” class=“indexterm”></a> <p>use LaTeX-computed names for links (default: false).</p>
• nesting <a name=“idp8827584” id=“idp8827584” title=“idp8827584” class=“indexterm”></a> <p>allow nesting of links (default: false).</p>
• pageanchor <a name=“idp8831824” id=“idp8831824” title=“idp8831824” class=“indexterm”></a> <p>put an anchor on every page (default: true).</p>
• pagebackref <a name=“idp8836080” id=“idp8836080” title=“idp8836080” class=“indexterm”></a> <p>backreference by page number (default: false).</p>
• pagebordercolor <a name=“idp8840336” id=“idp8840336” title=“idp8840336” class=“indexterm”></a> <p>color of border around page links (default: 1 1 0).</p>
• pagecolor <a name=“idp8844592” id=“idp8844592” title=“idp8844592” class=“indexterm”></a> <p>color of page links (default: red).</p>
• pdfauthor <a name=“idp8848800” id=“idp8848800” title=“idp8848800” class=“indexterm”></a> <p>text for PDF Author field (default: empty).</p>
• pdfborder <a name=“idp8852336” id=“idp8852336” title=“idp8852336” class=“indexterm”></a> <p>width of PDF link border (default: 0 0 1; 0 0 0 for colorlinks)</p>
• pdfcenterwindow <a name=“idp8858032” id=“idp8858032” title=“idp8858032” class=“indexterm”></a> <p>position the document window center of the screen (default: false).</p>
• pdfcreator <a name=“idp8862304” id=“idp8862304” title=“idp8862304” class=“indexterm”></a> <p>text for PDF Creator field (default: LaTeX with hyperref package).</p>
• pdffitwindow <a name=“idp8866304” id=“idp8866304” title=“idp8866304” class=“indexterm”></a> <p>resize document window to fit document size (default: false).</p>
• pdfhighlight <a name=“idp8870576” id=“idp8870576” title=“idp8870576” class=“indexterm”></a> <p>set highlighting of PDF links (default: /I).</p>
• pdfkeywords <a name=“idp8874848” id=“idp8874848” title=“idp8874848” class=“indexterm”></a> <p>text for PDF Keywords field (default: empty).</p>
• pdfmenubar <a name=“idp8878384” id=“idp8878384” title=“idp8878384” class=“indexterm”></a> <p>make PDF viewer's menu bar visible (default: true).</p>
• pdfnewwindow <a name=“idp8882640” id=“idp8882640” title=“idp8882640” class=“indexterm”></a> <p>make links that open another PDF file start a new window (default: false).</p>
• pdfpagelayout <a name=“idp8886928” id=“idp8886928” title=“idp8886928” class=“indexterm”></a> <p>set layout of PDF pages (default: empty).</p>
• pdfpagemode <a name=“idp8890464” id=“idp8890464” title=“idp8890464” class=“indexterm”></a> <p>set default mode of PDF display (default: empty).</p>
• pdfpagescrop <a name=“idp8894016” id=“idp8894016” title=“idp8894016” class=“indexterm”></a> <p>set crop size of PDF document (default: empty).</p>
• pdfpagetransition <a name=“idp8897552” id=“idp8897552” title=“idp8897552” class=“indexterm”></a> <p>set PDF page transition style (default: empty).</p>
• pdfproducer <a name=“idp8901088” id=“idp8901088” title=“idp8901088” class=“indexterm”></a> <p>text for PDF Producer field (default: empty).</p>
• pdfstartpage <a name=“idp8904624” id=“idp8904624” title=“idp8904624” class=“indexterm”></a> <p>page at which PDF document opens (default: 1).</p>
• pdfstartview <a name=“idp8908848” id=“idp8908848” title=“idp8908848” class=“indexterm”></a> <p>starting view of PDF document (default: /Fit).</p>
• pdfsubject <a name=“idp8913104” id=“idp8913104” title=“idp8913104” class=“indexterm”></a> <p>text for PDF Subject field (default: empty).</p>
• pdftitle <a name=“idp8916640” id=“idp8916640” title=“idp8916640” class=“indexterm”></a> <p>text for PDF Title field(default: empty).</p>
• pdftoolbar <a name=“idp8920176” id=“idp8920176” title=“idp8920176” class=“indexterm”></a> <p>make PDF toolbar visible (default: true).</p>
• pdfview <a name=“idp8924432” id=“idp8924432” title=“idp8924432” class=“indexterm”></a> <p>PDF `view' when on link traversal (default: empty).</p>
• pdfwindowui <a name=“idp8927984” id=“idp8927984” title=“idp8927984” class=“indexterm”></a> <p>make PDF user interface elements visible (default: true).</p>
• plainpages <a name=“idp8932256” id=“idp8932256” title=“idp8932256” class=“indexterm”></a> <p>do page number anchors as plain arabic (default: true).</p>
• raiselinks <a name=“idp8936528” id=“idp8936528” title=“idp8936528” class=“indexterm”></a> <p>raise up links (for HyperTeX backend; default: false).</p>
• runbordercolor <a name=“idp8940800” id=“idp8940800” title=“idp8940800” class=“indexterm”></a> <p>color of border around run links (default: 0 .7 .7).</p>
• unicode <a name=“idp8945056” id=“idp8945056” title=“idp8945056” class=“indexterm”></a> <p>Unicode encoded pdf strings (default: true).</p>
• urlbordercolor <a name=“idp8949312” id=“idp8949312” title=“idp8949312” class=“indexterm”></a> <p>color of border around URL links (default: 0 1 1).</p>
• urlcolor <a name=“idp8953568” id=“idp8953568” title=“idp8953568” class=“indexterm”></a> <p>color of URL links (default: magenta).</p>
• verbose <a name=“idp8957808” id=“idp8957808” title=“idp8957808” class=“indexterm”></a> <p>be chatty (default: false).</p>

• \texorpdfstring{TeX-string}{pdf-string} <a name=“idp8964816” id=“idp8964816” title=“idp8964816” class=“indexterm”></a> <p>allows different texts for PDF or TeX creation.</p> <pre class=“programlisting”>\section{The role of \texorpdfstring{H$_2$O}{water}} </pre>
• <a name=“href” id=“href” title=“href”></a>\href{URL}{Text} <a name=“idp8970384” id=“idp8970384” title=“idp8970384” class=“indexterm”></a> <p>the text will be resolved into a URL. The URL must be complete, according to a base-url which might be defined in a \hyperbaseurl.</p> <pre class=“programlisting”>\href{http://www.karpfenteich.net/pit/}{Peter's input tips} </pre>
• <a name=“cmd-hyperbaseurl” id=“cmd-hyperbaseurl” title=“cmd-hyperbaseurl”></a>\hyperbaseurl{URL} <a name=“idp8976800” id=“idp8976800” title=“idp8976800” class=“indexterm”></a> <p>defines a base URL, which is preset to a given URL. This helps to make portable documents.</p>
• \hyperimage{image-URL} <a name=“idp8980784” id=“idp8980784” title=“idp8980784” class=“indexterm”></a> <p>includes the picture of the URL reference.</p>
• \hyperref{URL}{category}{name}{text}, \hyperref[mark]{text} <a name=“idp8985600” id=“idp8985600” title=“idp8985600” class=“indexterm”></a> <p>text is activated as a hyperlink to the point which is defined with a <a href=”#cmd-label-title” title=“2.3.2. \label{key}” class=“link”>\label</a> command with the symbolic name mark.</p>
• \hyperlink{name}{text}, \hyertarget{name}{text} <a name=“idp8993248” id=“idp8993248” title=“idp8993248” class=“indexterm”></a><a name=“idp8995152” id=“idp8995152” title=“idp8995152” class=“indexterm”></a> <p>\hyperlink creates an internal link to an object which is somewhere defined with a \hypertarget command.</p> <p>For HTML the command \hyperlink inserts a # character in front of each link. Thus it'll refer to the topical document, while \href will expect a complete URL.</p>
• \autoref{marker} <a name=“idp9003040” id=“idp9003040” title=“idp9003040” class=“indexterm”></a> <p>\autoref is a substitution for the standard \ref command. It inserts a context sensitive phrase.</p> <pre class=“programlisting”>see \autoref{foo} </pre> <p>for a \label in a section will output see section 3 for an example.</p> <p>There are macros to change the default output with the help of the \renewcommand:</p> <pre class=“programlisting”>\figurename \figurename \tablename \tablename \partname \partname \appendixname \appendixname \equationname \equationname \Itemname \Itemname \chaptername \chaptername \sectionname \sectionname \subsectionname \subsesctionname \subsubsectionname \subsubsectionname \paragraphname \paragraphname \Hfootnotename \Hfootnotename \AMSname \AMSname \theoremname \theoremname </pre>
• <a name=“cmd-nolinkurl” id=“cmd-nolinkurl” title=“cmd-nolinkurl”></a>\nolinkurl <a name=“idp9013472” id=“idp9013472” title=“idp9013472” class=“indexterm”></a> <p>Allows line breaks in a verbatim like environment like \url, but without the hyperlink function. This is useful to define own commands like this example:</p> <pre class=“programlisting”>\newcommand*{\urlw}[1]{\href{http://www.#1}% {\nolinkurl{www.#1}}} </pre> <p>This new defined command \urlw allows the user to typeset a linkable (this function is offered by \href) www.example.org address in the latex source like this:</p> <pre class=“programlisting”>\urlw{example.org} </pre> <p>This will produce the string www.example.org which is hyperlinked and breakable (when the driver like pdfTeX allows line breaks in links).</p>

<a name=“idp9025232” id=“idp9025232” title=“idp9025232”></a>

\usepackage[encoding name]{inputenc}

Allows to specify an input encoding for direct input of character codes > 127, e.g. accented characters.

Important encodings are:

• latin9, latin1 <p>Linux, Unix, VMS</p> <a name=“idp9030336” id=“idp9030336” title=“idp9030336” class=“indexterm”></a><a name=“idp9031152” id=“idp9031152” title=“idp9031152” class=“indexterm”></a>
• ansinew <p>Windows (codepage 1252)</p> <a name=“idp9033968” id=“idp9033968” title=“idp9033968” class=“indexterm”></a>
• cp850 <p>OS/2, MSDOS (codpage 850)</p> <a name=“idp9036864” id=“idp9036864” title=“idp9036864” class=“indexterm”></a>
• applemac <p>Apple Macintosh</p> <a name=“idp9039648” id=“idp9039648” title=“idp9039648” class=“indexterm”></a>

<a name=“idp9043184” id=“idp9043184” title=“idp9043184”></a><a name=“idp9044224” id=“idp9044224” title=“idp9044224”></a>

The KOMA-Script package has a very detailed and well written documentation. Read the scrguide for further information!

\typearea[BCOR]{DIV} <a name=“idp9050320” id=“idp9050320” title=“idp9050320”></a>

\areaset[BCOR]{Breite}{Höhe} <a name=“idp9052176” id=“idp9052176” title=“idp9052176”></a>

• headinclude, headexclude, footinclude, footexclude <a name=“idp9056720” id=“idp9056720” title=“idp9056720” class=“indexterm”></a><a name=“idp9057760” id=“idp9057760” title=“idp9057760” class=“indexterm”></a><a name=“idp9058832” id=“idp9058832” title=“idp9058832” class=“indexterm”></a><a name=“idp9059904” id=“idp9059904” title=“idp9059904” class=“indexterm”></a> <p>will determine if headers and footers are used in the calculation of the page size. Default is exclude. Include will make the text area smaller.</p>
• DIV <a name=“idp9062688” id=“idp9062688” title=“idp9062688” class=“indexterm”></a> <p>is a factor which determins how large the used page size is. This method takes care of good typography.</p> <p>Try values between 10 and 15. Higher values will cause smaller margins. An example would be: DIV12.</p>
• BCOR <a name=“idp9066640” id=“idp9066640” title=“idp9066640” class=“indexterm”></a> <p>Binding correction. Takes care of the loss of the visible paper size when the paper is cut and a book is bound.</p>

<a name=“idp9071024” id=“idp9071024” title=“idp9071024”></a>

This reference is based on the excellent scrguien.pdf from 2002-09-06.

<a name=“idp9074368” id=“idp9074368” title=“idp9074368”></a>

<a name=“idp9076960” id=“idp9076960” title=“idp9076960”></a>

• \KOMAoptions{options list} Use this to change options after loading the class. List single or multiple options, separated by commas.

<a name=“idp9082400” id=“idp9082400” title=“idp9082400”></a>

• paper=format Defines the paper format.
• BCOR=length, DIV=value, headlines=count Divisor, binding correction, and number of headlines.
• enlargefirstpage If true some more text would fit on the first page

<a name=“idp9093952” id=“idp9093952” title=“idp9093952”></a><a name=“idp9095856” id=“idp9095856” title=“idp9095856”></a>

• twoside Activate possibilities of a double-sided document, but stay with with the one-sided layout as far as possible.
• cleardoublepage=style <p>Inserted pages by \cleardoublepage get one of these page styles:</p> <p> <ul class=“itemizedlist”> <li class=“listitem”>empty</li> <li class=“listitem”>plain</li> <li class=“listitem”>standard</li> </ul> </p>
• headsepline, footsepline Insert a separator line below the head or above the foot.
• mpinclude, mpexclude These two options of the typearea package should not be used with scrlttr2.
• pagenumber=position <p>This option defines if and where a page number will be placed. Possible values are:</p> <p> <dl> bot, foot Page number in foot, horizontal position not changed botcenter, botcentered, botmiddle, footcenter, footcentered, footmiddle Page number infoot,centered botleft, footleft Page number in foot, left justified botrigth, footright Page number in foot, right justified center, centered, middle Page number centered horizontally, vertical position not changed false, no, off No page number head, top Page number in head, horizontal position not changed headcenter, headcentered, headmiddle, topcenter, topcentered, topmiddle Page number in head, centered headleft, topleft Page number in head, left justified headright, topright Page number in head, right justified left Page number left, vertical position not changed right Page number right, vertical position not changed </dl> </p> <p>Default is botcenter</p>
• parskip=value <p>Mark paragraphs alternatively by vertical skip. Possible values are:</p> <p> <dl> false, off Paragraph indentation instead of verticalk space full, on, true One line vertical space between paragraphs; at least 1 em free space in the last line. full* One line vertical space betwen paragraphs; at least a quarter of a line free space at the end of a paragraph. full+ One line vertical space betwen paragraphs; at least a third of aline free space at the end of a paragraph. full- One line vertical space betwen paragraphs; last line of a paragraph may be arbitrarily filled. half Half a line vertical space between paragraphs; at least 1 em free space in the last line. half* Half a line vertical space between paragraphs; at least a quarter of a line free space at the end of a paragraph. half+ Half a line vertical space between paragraphs; at least a third of a line free space at the end of a paragraph. half- One line vertical space between paragraphs; last line may be arbitrarily filled. </dl> </p> <p>Default is false.</p>

<a name=“idp9185392” id=“idp9185392” title=“idp9185392”></a>

• fontsize=size Font size of the document. Defaults to 12pt.

<a name=“idp9191520” id=“idp9191520” title=“idp9191520”></a>

• fromalign <p>Defines the placement of the from address in the letterhead. Possible values are:</p> <p> <dl> center, centered, middle Return address centered. false, no, off Standard design for return address. left Left justified return address. rigth Right justified return address. </dl> </p> <p>Default is left</p>
• fromrule <p>Allows to place a horizontal rule within return address. Possible values are:</p> <p> <dl> afteraddress, below, true, yes Line below return address aftername Line right below sender's name false, no, off No line. </dl> </p> <p>Default is false.</p>
• fromphone Defines whether the phone number will be part of the return address.
• fromfax Defines whether the facsimile number will be part of the return address.
• fromemail Defines whether the email address will be part of the return address.
• fromurl Defines whether the URL will be part of the return address.
• fromlogo Defines whether the logo will be part of the return address.
• addrfield Defines whether a return address field will be set.
• backaddress Defines whether a return address for window envelopes will be set.
• subject <p>Choose of your subject should have a title and if the subject should be set before or after the opening. Possible values are:</p> <p> <dl> afteropening Set subject after opening. beforeopening Set subject before opening. titled Add title to subject. untitled Do not add title to subject. </dl> </p> <p>Defaults are beforeopening and untitled.</p>
• locfield <p>Toggle between presets for the field width of additionbal sender attributes.</p> <p> <dl> narrow Small sender supplement field. wide Wide sender supplement field. </dl> </p> <p>Default is narrow.</p>
• foldmarks Activates fold marks.
• numericaldate Toggles between standard, language-dependent date presentation and a short, numerical one.
• refline Defines that the reference line may extend beyond the normal type area.

<a name=“idp9265264” id=“idp9265264” title=“idp9265264”></a>

• draft Toggles between the final and the draft version.

<a name=“idp9270688” id=“idp9270688” title=“idp9270688”></a>

• \LoadLetterOption{name} <p>Load a lco file. name is the filename without suffix.</p> <p>Predefined lco files:</p> <p> <dl> DIN For A4 size paper, complying with DIN 676. DINmtext For A4 size paper, complying with DIN 676, but using an alternate layout with more text on the first page. KOMAold Fo AQ4 paper size using a layout close to the obsolete scrlettr class. SN For Swiss letters with address field on the right side, according to SN 010 130 SNleft For Swiss letters with address field on the left side. </dl> </p>
• \LetterOptionNeedsPaperSize{option name}{paper size} Useful to be abel to emit warnings if the user selects a different paper size from the one the lco file is based on.

<a name=“idp9293136” id=“idp9293136” title=“idp9293136”></a>

<a name=“idp9295744” id=“idp9295744” title=“idp9295744”></a>

See also the section for Changing Fonts in KOMA-Script (still to be written).

• backaddress Back address for a window envelope
• descriptionlabel Label in a description environment
• fromaddress Sender's address in letterhead
• fromname Sender's address in letterhead if different from fromaddress
• pagefoot Footer, sometimes header of a page
• pagehead Header, sometimes footer of a page
• pagenumber Page number in footer or header
• subject Subject in the opening
• title Headline in the opening

<a name=“idp9319552” id=“idp9319552” title=“idp9319552”></a>

See also the section for Page Style in KOMA-Script (still to be written).

• empty Entirely empty headers and footers
• plain Empty head and and only page number in header or footer
• headings Automatic page headings
• myheadings Manual page headings

<a name=“idp9331952” id=“idp9331952” title=“idp9331952”></a>

The main difference between a command and a variable is that a command usually triggers an action whereas a variable only consists of plain text. Furthermore a variable can have an additional description.

$ \newkomavar[description]{name}, \newkomavar[description]{name}, \addtoreffields{name}: <a name=“idp9338848” id=“idp9338848” title=“idp9338848” class=“indexterm”></a><a name=“idp9340752” id=“idp9340752” title=“idp9340752” class=“indexterm”></a> <p>\newkomavar defines a new variable, addressed with name.</p> <p>The command \addtoreffields adds the variable name to the reference fields. See section <a href=”#scrlttr-business-line” title=“3.9.3. Business Line” class=“link”>Business Line</a>.</p> <p>The command \newkomavar works like \newkomavar with an additional call of the command \addtoreffields.</p>

Overview of all variables:

• backaddress <a name=“idp9352240” id=“idp9352240” title=“idp9352240” class=“indexterm”></a> <p>Back address for window envelopes</p>
• backaddressseparator <a name=“idp9356160” id=“idp9356160” title=“idp9356160” class=“indexterm”></a> <p>Separator within the back address</p>
• ccseparator <a name=“idp9360080” id=“idp9360080” title=“idp9360080” class=“indexterm”></a> <p>Separator between title of additional recipients and additional recipients</p>
• customer <a name=“idp9364048” id=“idp9364048” title=“idp9364048” class=“indexterm”></a> <p>Customer number</p>
• date <a name=“idp9367952” id=“idp9367952” title=“idp9367952” class=“indexterm”></a> <p>Date</p>
• emailseparator <a name=“idp9371856” id=“idp9371856” title=“idp9371856” class=“indexterm”></a> <p>Separator between e-mail name and e-mail address</p>
• enclseparator <a name=“idp9375808” id=“idp9375808” title=“idp9375808” class=“indexterm”></a> <p>Separator between title of enclosure and and enclosures</p>
• faxseparator <a name=“idp9379760” id=“idp9379760” title=“idp9379760” class=“indexterm”></a> <p>Separator between title of fax and fax number</p>
• fromaddress <a name=“idp9383712” id=“idp9383712” title=“idp9383712” class=“indexterm”></a> <p>Sender's address without its name</p>
• frombank <a name=“idp9387632” id=“idp9387632” title=“idp9387632” class=“indexterm”></a> <p>Sender's bank account</p>
• fromemail <a name=“idp9391536” id=“idp9391536” title=“idp9391536” class=“indexterm”></a> <p>Sender's e-mail</p>
• fromfax <a name=“idp9395440” id=“idp9395440” title=“idp9395440” class=“indexterm”></a> <p>Sender's fax number</p>
• fromlogo <a name=“idp9399344” id=“idp9399344” title=“idp9399344” class=“indexterm”></a> <p>Commands for inserting the sender's logo</p>
• fromname <a name=“idp9403280” id=“idp9403280” title=“idp9403280” class=“indexterm”></a> <p>Complete name of the sender</p>
• fromphone <a name=“idp9407200” id=“idp9407200” title=“idp9407200” class=“indexterm”></a> <p>Sender's telephone number</p>
• fromurl <a name=“idp9411120” id=“idp9411120” title=“idp9411120” class=“indexterm”></a> <p>URL of the sender</p>
• invoice <a name=“idp9415024” id=“idp9415024” title=“idp9415024” class=“indexterm”></a> <p>Invoice number</p>
• location <a name=“idp9418928” id=“idp9418928” title=“idp9418928” class=“indexterm”></a> <p>More details of the sender</p>
• myref <a name=“idp9422848” id=“idp9422848” title=“idp9422848” class=“indexterm”></a> <p>Sender's reference</p>
• place <a name=“idp9426752” id=“idp9426752” title=“idp9426752” class=“indexterm”></a> <p>Place</p>
• placeseparator <a name=“idp9430656” id=“idp9430656” title=“idp9430656” class=“indexterm”></a> <p>Separator between place and date</p>
• phoneseparator <a name=“idp9434576” id=“idp9434576” title=“idp9434576” class=“indexterm”></a> <p>Separator between title of telephone and telephone number</p>
• signature <a name=“idp9438528” id=“idp9438528” title=“idp9438528” class=“indexterm”></a> <p>Signature beneath the ending of the letter</p>
• specialmail <a name=“idp9442464” id=“idp9442464” title=“idp9442464” class=“indexterm”></a> <p>Special mail</p>
• subject <a name=“idp9446368” id=“idp9446368” title=“idp9446368” class=“indexterm”></a> <p>Subject</p>
• subjectseparator <a name=“idp9450272” id=“idp9450272” title=“idp9450272” class=“indexterm”></a> <p>Separator between title of subject and subject</p>
• title <a name=“idp9454224” id=“idp9454224” title=“idp9454224” class=“indexterm”></a> <p>Letter title</p>
• toname <a name=“idp9458128” id=“idp9458128” title=“idp9458128” class=“indexterm”></a> <p>Complete name of recipient</p>
• toaddress <a name=“idp9462048” id=“idp9462048” title=“idp9462048” class=“indexterm”></a> <p>Address of recipient without its name</p>
• yourmail <a name=“idp9465968” id=“idp9465968” title=“idp9465968” class=“indexterm”></a> <p>Date of recipient's mail</p>
• yourref <a name=“idp9469888” id=“idp9469888” title=“idp9469888” class=“indexterm”></a> <p>Recipient's reference</p>

$ \setkomavar{name}[description]{content}, \setkomavar{name}{description}: <a name=“idp9475408” id=“idp9475408” title=“idp9475408” class=“indexterm”></a> <p>\setkomavar sets the content of the variable name. The optional argument sets the description of the variable.</p> <p>\setkomavar only sets the description.</p>

$ \usekomavar[command]{name}, \usekomavar[command]{name}: <a name=“idp9484736” id=“idp9484736” title=“idp9484736” class=“indexterm”></a> <p>\usekomavar gives you access to the content of the variable name.</p> <p>\usekomavar gives you access to the description of the variable name.</p>

• \ifkomavarempty{name}{true}{false}, \ifkomavarempty*{name}{true}{false} <a name=“idp9494016” id=“idp9494016” title=“idp9494016” class=“indexterm”></a> <p>The true argument will be executed if the content or description is empty. Otherwise the false argument will be executed.</p> <p>The starred version handles the description of a variable, the variant without star the content.</p>

<a name=“idp9499584” id=“idp9499584” title=“idp9499584”></a>

• \@newplength{name} Defines a new pseudo length
• \useplength{name} Access value of pseudo length name
• \setlengthtoplength[factor]{length}{pseudo length} , \addtolengthplength[factor]{length}{pseudo length} Assign a multiple of pseudo length to a real length. Adds a multiple of pseudo length to length.
• \@setplength[factor]{pseudo length}{value} , \@addtoplength[factor]{pseudo length}{value} Assign a multiple of a value to a pseudo length. Adds value to pseudo length.

<a name=“idp9520240” id=“idp9520240” title=“idp9520240”></a>

<a name=“idp9522832” id=“idp9522832” title=“idp9522832”></a>

• firstheadvpos Distance between the top of the sheet and the letterhead.
• firstheadwidth Width of the letterhead.
• fromname, fromaddress, fromphone, fromfax, fromemail, fromurl, fromlogo This variables give all statements concerning the sender necessary to create the letterhead.
• phoneseparator, faxseparator, emailseparator, urlseparator Separators for variables in letterhead.
• \firsthead{construction} Create letterhead freely.

<a name=“idp9543760” id=“idp9543760” title=“idp9543760”></a>

• firstfootvpos Distance between footer and upper border of the sheet.
• firstfootwidth Width of letter's firstpage footer.
• \firstfoot{Construction} Set definition for first page's footer

<a name=“idp9553216” id=“idp9553216” title=“idp9553216”></a>

• toaddrvpos, toaddrhpos Distance between address window of a window envelope and the upper and left border of the sheet.
• toaddrwidth Width of the address window.
• toaddrindent Value of indentation for the address from the left border.
• backaddress, backaddressseparator, backaddrheight Double backslashes within return address will be exchanged with backaddressseparator. Height of the return address field.
• specialmail, specialmailindent, specialmailrightindent Optionally set between return address and addressee. specialmailindent and specialmailrightindent determine left and right indentation.
• toname, toaddress Usually not set directly by the user.
• \begin{letter}[options]{address} Major point of the letter class.
• \AtBeginLetter{command} Hook for commands run at begin of a letter.

<a name=“idp9580064” id=“idp9580064” title=“idp9580064”></a>

• locwidth Declares width of sender's extensions.
• location Content of sender's extension.

<a name=“idp9587888” id=“idp9587888” title=“idp9587888”></a>

• refvpos Distance between upper border of sheet and business line.
• refwidth Available width for the business line.
• refaftervskip Vertical space to be inserted beneath business line.
• place, placeseparator If all variables for business line are empty, the content of place and placeseparator will be set, followed by content of date.
• yourref, yourmail, myref, customer, invoice, date Typical fields for business lines.

<a name=“idp9608528” id=“idp9608528” title=“idp9608528”></a><a name=“idp9610432” id=“idp9610432” title=“idp9610432”></a>

• title Additional tile. Set centered beneath the business line.
• subject, subjectseparator Set the subject of the letter, optional prefixed by a label.

• tfoldmarkvpos, bfoldmarkvpos Position of upper and lower fold mark.
• foldmarkhpos Distance between fold marks and the sheet's left border.
• frombank Internally not used yet.
• \nexthead{construction}, \nextfoot{construction} Create letter head or foot for the following pages freely.

<a name=“idp9629920” id=“idp9629920” title=“idp9629920”></a>

<a name=“idp9632512” id=“idp9632512” title=“idp9632512”></a>

• \opening{opening} Set the opening of the letter.

<a name=“idp9637888” id=“idp9637888” title=“idp9637888”></a>

See section Footnotes in KOMA-Script (still to be written).

<a name=“idp9641376” id=“idp9641376” title=“idp9641376”></a>

See section Lists in KOMA-Script (still to be written).

<a name=“idp9644864” id=“idp9644864” title=“idp9644864”></a>

See section Margin Notes in KOMA-Script (still to be written).

<a name=“idp9648352” id=“idp9648352” title=“idp9648352”></a>

See section Logical Markup of Text in KOMA-Script (still to be written).

<a name=“idp9651840” id=“idp9651840” title=“idp9651840”></a>

<a name=“idp9654432” id=“idp9654432” title=“idp9654432”></a>

• signature Inlcudes an explanation for the inscription. Defaults to \usekomavar{fromname}.
• \closing{closing phrase} Typesets the colsing phrase follwoed by a vertical space and the contents fo variable signature.
• sigindent, sigbeforevskip, \raggedsignature Indentation of the box for closing phrase, inscription and signature (defaults to 0mm). Vertical space between closing phrase and signature (defaults to two lines). Alignment inside the box.

<a name=“idp9667216” id=“idp9667216” title=“idp9667216”></a><a name=“idp9669120” id=“idp9669120” title=“idp9669120”></a><a name=“idp9671024” id=“idp9671024” title=“idp9671024”></a>

• \ps Set a postscript.
• \cc{distribution list}, ccseparator Set a ddistribution list. If the contents of ccseparator isn't empty then the name and the content of the variable is inserted prior to distribution list.
• \encl{enclosures}, enclseparator Same structur as the distribution list.

<a name=“idp9682864” id=“idp9682864” title=“idp9682864”></a>

<a name=“idp9685456” id=“idp9685456” title=“idp9685456”></a>

• \captionenglish, \captionUSenglish, \captionamerican, \captionbritish, \captionUKenglish, \captiongerman, \captionngerman, \captionaustrian, \captionfrench, \captionitalian, \captionspanish, \captiondutch, \captioncroatian If the used language selection scheme does not support switching the language the above commands can be used directly.
• \dateenglish, \dateUSenglish, \dateamerican, \datebritish, \dateUKenglish, \dategerman, \datengerman, \dateaustrian, \datefrench, \dateitalian, \datespanish, \datedutch, \datecrotian Numerical date representation.

• \yourrefname, \youremailname, \myrefname, \customername, \invoicename, \subjectname, \ccname, \enclname, \headtoname, \headfromname, \datename, \pagename, \phonename, \faxname, \emailname, \wwwname, \bankname These defintions can be modified to support a new language of for private customization.

• \providecaptioname{language}{term}{definition}, \newcaptioname{language}{term}{defintion}, \renewcaptionname{language}{term}{definition} Assign a definition for a language to a term.

<a name=“idp9735696” id=“idp9735696” title=“idp9735696”></a><a name=“idp9737600” id=“idp9737600” title=“idp9737600”></a>

• \adrentry{Lastname}{Firstname}{Address}{Telephone}{F1}{F2}{Comment}{Key} Address entry for address files. The file extension has to be .adr!
• \addrentry{Lastname}{Firstname}{Address}{Telephone}{F1}{F2}{F3}{F4}{Key} This command supports four freely definable parameters for an address entry.
• \adrchar{initial letter}, \addrchar{initial letter} Separator for address entries. Ignored by scrlttr2.

<a name=“idp9751136” id=“idp9751136” title=“idp9751136”></a>

• \InputAddressFile{file name} <a name=“idp9754432” id=“idp9754432” title=“idp9754432” class=“indexterm”></a> <p>Read the contents of the given address file. Filename extension has to be .adr and has to be omitted in the argument.</p>
• \Name{Key}, \FirstName{Key}, \LastName{Key}, \Address{Key}, \Telephone{Key}, \FreeI{Key}, \FreeII{Key}, \Comment{Key}, \FreeIII{Key}, \FreeIV{Key} <a name=“idp9766496” id=“idp9766496” title=“idp9766496” class=“indexterm”></a><a name=“idp9768400” id=“idp9768400” title=“idp9768400” class=“indexterm”></a><a name=“idp9770304” id=“idp9770304” title=“idp9770304” class=“indexterm”></a><a name=“idp9772208” id=“idp9772208” title=“idp9772208” class=“indexterm”></a><a name=“idp9774112” id=“idp9774112” title=“idp9774112” class=“indexterm”></a><a name=“idp9776016” id=“idp9776016” title=“idp9776016” class=“indexterm”></a><a name=“idp9777920” id=“idp9777920” title=“idp9777920” class=“indexterm”></a><a name=“idp9779824” id=“idp9779824” title=“idp9779824” class=“indexterm”></a><a name=“idp9781728” id=“idp9781728” title=“idp9781728” class=“indexterm”></a><a name=“idp9783632” id=“idp9783632” title=“idp9783632” class=“indexterm”></a> <p>Access to the data in address file. \Name is a concatenation of \FirstName and \LastName.</p>
• AdrFreeIVempty, AdrFreeIVshow, AdrFreeIVwarn, AdrFreeIVstop Package warning options. Defaults to AdrFreeIVshow.

<a name=“idp9796432” id=“idp9796432” title=“idp9796432”></a><a name=“idp9797248” id=“idp9797248” title=“idp9797248”></a>

Math fonts for the use with the Palatino font.

<a name=“idp9800768” id=“idp9800768” title=“idp9800768”></a><a name=“idp9801584” id=“idp9801584” title=“idp9801584”></a>

Math fonts for the use with the Palatino font.

Package options are:

• [slantedGreek] <p>Uppercase Greek will be typeset slanted.</p>
• [noBBpl] <p>Do not use PazoMathBlackboardBold as (partial) blackboard bold font (e.g with \mathbb{R}).</p>
• [osf] <p>Make the font family pplj (Palatino with old style numerals) the default roman font, and use an alternative version of the virtual math italic fonts (zplmrj7m and zplmbj7m) with upright Palatino old style numerals for use with the \oldstylenums command.</p>
• [osfeqnnum] <p>Use old style numerals for equation numbering.</p>

<a name=“idp9818112” id=“idp9818112” title=“idp9818112”></a><a name=“idp9818928” id=“idp9818928” title=“idp9818928”></a>

Smarter version of the original latex2e <a href=”#cross-references” title=“2.3.2 Cross References”>cross reference commands</a>. Generated strings are customizable, Babel options are recognized (further info in the package documentation).

• <a name=“cmd-vref” id=“cmd-vref” title=“cmd-vref”></a>\vref, <a name=“cmd-vpageref” id=“cmd-vpageref” title=“cmd-vpageref”></a>\vpageref <a name=“idp9825344” id=“idp9825344” title=“idp9825344” class=“indexterm”></a><a name=“idp9826416” id=“idp9826416” title=“idp9826416” class=“indexterm”></a> <p>\vref is similar to \ref but adds an additional page reference, like on the facing page or on page 27 whenever the corresponding <a href=”#cmd-label-title” title=“2.3.2. \label{key}” class=“link”>\label</a> is not on the same page.</p> <p>\vpageref is a variation of \pageref with similar functionality.</p>
• \vrefrange, \vpagerefrange <a name=“idp9835776” id=“idp9835776” title=“idp9835776” class=“indexterm”></a><a name=“idp9836848” id=“idp9836848” title=“idp9836848” class=“indexterm”></a> <p>The \v…range commands take two labels as arguments and produce strings which depend on wether or not these labels fall onto a single page or on different pages.</p>
• \vref, \vpageref, \vpagerefrange* <p>Star * variants do not add any space before the generated text for situations like:</p> <pre class=“programlisting”>(\vref{foo} …) </pre>

<a name=“idp9845824” id=“idp9845824” title=“idp9845824”></a><a name=“idp9846640” id=“idp9846640” title=“idp9846640”></a><a name=“idp9847456” id=“idp9847456” title=“idp9847456”></a>

Must be loaded with the usual \usepackage command. Further info for a package to be found in the documentation (dvi, pdf, ps) or in the sty-file itself.

<a name=“idp9853888” id=“idp9853888” title=“idp9853888”></a><a name=“idp9854928” id=“idp9854928” title=“idp9854928”></a><a name=“idp9856384” id=“idp9856384” title=“idp9856384”></a>

Bold math symbols or equations with better spacing then the \boldsymbold command. <a name=“idp9858928” id=“idp9858928” title=“idp9858928”></a> If possible load after other packages which redefine the fonts. When no bold font is available for a certain char bm will use poor man's bold \pmb.

• <a name=“cmd-bm” id=“cmd-bm” title=“cmd-bm”></a>\bm <a name=“idp9864928” id=“idp9864928” title=“idp9864928” class=“indexterm”></a> <p>Produces bold math symbol or equation.</p>
• \unboldmath <a name=“idp9867984” id=“idp9867984” title=“idp9867984” class=“indexterm”></a> <p>Can be used to set parts of an equation unbold.</p>

<a name=“idp9872416” id=“idp9872416” title=“idp9872416”></a><a name=“idp9873456” id=“idp9873456” title=“idp9873456”></a>

Defines line breakable hyperlinked (uses <a href=“#hyperref” title=“3.7 hyperref”>hyperref</a> package) verbatim input for urls and e-mail addresses.

Example: \url{http://example.org} outputs http://example.org.

Related commands are \href and \nolinkurl.

<a name=“idp9884384” id=“idp9884384” title=“idp9884384”></a>

tbd.

<a name=“idp9888112” id=“idp9888112” title=“idp9888112”></a>

The idea behind the PSTricks package of Timothy van Zandt <a name=“idp9888528” id=“idp9888528” title=“idp9888528”></a> is to provide most of the PostScript language in LaTeX and TeX syntax.

<a name=“idp9896736” id=“idp9896736” title=“idp9896736”></a><a name=“idp9898832” id=“idp9898832” title=“idp9898832”></a><a name=“idp9900672” id=“idp9900672” title=“idp9900672”></a><a name=“idp9902576” id=“idp9902576” title=“idp9902576”></a>

$ \newgray{color}{num} , \newrgbcolor{color}{num1 num2 num3} , \newhsbcolor{color}{num1 num2 num3} , \newcmykcolor{color}{num1 num2 num3 num4}:

Note that these commands are obsolete for LaTeX. Load PSTricks with \usepackage{pstcol} and use the standard LaTeX color commands instead.

• \psset{par1=value1,par2=value2,…} <a name=“idp9915968” id=“idp9915968” title=“idp9915968” class=“indexterm”></a>

• \pssetlength{cmd}{dim} <a name=“idp9921952” id=“idp9921952” title=“idp9921952” class=“indexterm”></a>
• unit=dim, xunit=dim, yunit=dim, yunit=dim <a name=“idp9925776” id=“idp9925776” title=“idp9925776” class=“indexterm”></a><a name=“idp9927728” id=“idp9927728” title=“idp9927728” class=“indexterm”></a><a name=“idp9929632” id=“idp9929632” title=“idp9929632” class=“indexterm”></a><a name=“idp9931536” id=“idp9931536” title=“idp9931536” class=“indexterm”></a> <p>Default: 1cm</p>
• \degrees[num] <a name=“idp9936352” id=“idp9936352” title=“idp9936352” class=“indexterm”></a>
• \radians <a name=“idp9940096” id=“idp9940096” title=“idp9940096” class=“indexterm”></a>

• linewidth=dim <a name=“idp9945952” id=“idp9945952” title=“idp9945952” class=“indexterm”></a> <p>Default: .8pt</p>
• linecolor=color <a name=“idp9950800” id=“idp9950800” title=“idp9950800” class=“indexterm”></a> <p>Default: black</p>
• showpoints=true/false <a name=“idp9955648” id=“idp9955648” title=“idp9955648” class=“indexterm”></a> <p>Default: false</p>

• linearc=dim <a name=“idp9962688” id=“idp9962688” title=“idp9962688” class=“indexterm”></a> <p>Default: 0pt</p>
• framearc=num <a name=“idp9967504” id=“idp9967504” title=“idp9967504” class=“indexterm”></a> <p>Default: 0</p>
• cornersize=relative/absolute <a name=“idp9972336” id=“idp9972336” title=“idp9972336” class=“indexterm”></a> <p>Default: relative</p>
• \psline*[par]{arrows}(x0,y0)(x1,y1)…(xn,yn) <a name=“idp9977264” id=“idp9977264” title=“idp9977264” class=“indexterm”></a>
• \qline(coor0)(coor1) <a name=“idp9981056” id=“idp9981056” title=“idp9981056” class=“indexterm”></a>
• \pspolygon*[par](x0,y0)(x1,y1)(x2,y2)…(xn,yn) <a name=“idp9984880” id=“idp9984880” title=“idp9984880” class=“indexterm”></a>
• \psframe*[par](x0,y0)(x1,y1) <a name=“idp9988640” id=“idp9988640” title=“idp9988640” class=“indexterm”></a>

• \pscircle*[par](x0,y0){radius} <a name=“idp9994544” id=“idp9994544” title=“idp9994544” class=“indexterm”></a>
• \qdisk(coor){radius} <a name=“idp9998288” id=“idp9998288” title=“idp9998288” class=“indexterm”></a>
• \pswedge*[par](x0,y0){radius}{angle1}{angle2} <a name=“idp10002064” id=“idp10002064” title=“idp10002064” class=“indexterm”></a>
• \psellipse*[par](x0,y0)(x1,y1) <a name=“idp10005824” id=“idp10005824” title=“idp10005824” class=“indexterm”></a>
• \psarc*[par]{arrows}(x,y){radius}{angleA}{angleB} <a name=“idp10009600” id=“idp10009600” title=“idp10009600” class=“indexterm”></a>
• \psarcn*[par]{arrows}(x,y){radius}{angleA}{angleB} <a name=“idp10013376” id=“idp10013376” title=“idp10013376” class=“indexterm”></a>
• arcsep=dim, arcsepA=dim, arcsepB=dim <a name=“idp10017184” id=“idp10017184” title=“idp10017184” class=“indexterm”></a><a name=“idp10019088” id=“idp10019088” title=“idp10019088” class=“indexterm”></a><a name=“idp10020992” id=“idp10020992” title=“idp10020992” class=“indexterm”></a> <p>Default: 0pt</p>

• \psbezier*[par]{arrows}(x0,y0)(x1,y1)(x2,y2)(x3,y3) <a name=“idp10028080” id=“idp10028080” title=“idp10028080” class=“indexterm”></a>
• \parabola*[par]{arrows}(x0,y0)(x1,y1) <a name=“idp10031840” id=“idp10031840” title=“idp10031840” class=“indexterm”></a>
• \pscurve*[par]{arrows}(x1,y1)…(xn,yn) <a name=“idp10035600” id=“idp10035600” title=“idp10035600” class=“indexterm”></a>
• \psecurve*[par]{arrows}(x1,y1)…(xn,yn) <a name=“idp10039376” id=“idp10039376” title=“idp10039376” class=“indexterm”></a>
• \psccurve*[par]{arrows}(x1,y1)…(xn,yn) <a name=“idp10043152” id=“idp10043152” title=“idp10043152” class=“indexterm”></a>
• curvature=num1 num2 num3 <a name=“idp10046960” id=“idp10046960” title=“idp10046960” class=“indexterm”></a> <p>Default: 1 .1 0</p>

• \psdots*[par](x1,y1)(x2,y2)…(xn,yn) <a name=“idp10053920” id=“idp10053920” title=“idp10053920” class=“indexterm”></a>
• dotstyle=style <a name=“idp10057664” id=“idp10057664” title=“idp10057664” class=“indexterm”></a> <p>Default: *</p> <p>Dots: , o, +, triangle, triangle, square, square, pentagon, pentagon, |</p>
• dotscale=num1 num2 <a name=“idp10063424” id=“idp10063424” title=“idp10063424” class=“indexterm”></a> <p>Default: 1</p>
• dotangle=angle <a name=“idp10068240” id=“idp10068240” title=“idp10068240” class=“indexterm”></a> <p>Default: 0</p>

• \psgrid(x0,y0)(x1,y1)(x2,y2) <a name=“idp10075104” id=“idp10075104” title=“idp10075104” class=“indexterm”></a>
• gridwidth=dim <a name=“idp10078848” id=“idp10078848” title=“idp10078848” class=“indexterm”></a> <p>Default: .8pt</p>
• gridcolor=color <a name=“idp10083568” id=“idp10083568” title=“idp10083568” class=“indexterm”></a> <p>Default: black</p>
• griddots=num <a name=“idp10088288” id=“idp10088288” title=“idp10088288” class=“indexterm”></a> <p>Default: 0</p>
• gridlabels=dim <a name=“idp10092976” id=“idp10092976” title=“idp10092976” class=“indexterm”></a> <p>Default: 10pt</p>
• gridlabelcolor=color <a name=“idp10097696” id=“idp10097696” title=“idp10097696” class=“indexterm”></a> <p>Default: black</p>
• subgriddiv=int <a name=“idp10102416” id=“idp10102416” title=“idp10102416” class=“indexterm”></a> <p>Default: 5</p>
• subgridwidth=dim <a name=“idp10107104” id=“idp10107104” title=“idp10107104” class=“indexterm”></a> <p>Default: .4pt</p>
• subgridcolor=color <a name=“idp10111824” id=“idp10111824” title=“idp10111824” class=“indexterm”></a> <p>Default: gray</p>
• subgriddots=num <a name=“idp10116544” id=“idp10116544” title=“idp10116544” class=“indexterm”></a> <p>Default: 0</p>

• \fileplot*[par]{file} <a name=“idp10123424” id=“idp10123424” title=“idp10123424” class=“indexterm”></a>
• \dataplot*[par]{commands} <a name=“idp10127184” id=“idp10127184” title=“idp10127184” class=“indexterm”></a>
• \savedata{command}[data] <a name=“idp10130944” id=“idp10130944” title=“idp10130944” class=“indexterm”></a>
• \readdata{command}{file} <a name=“idp10134704” id=“idp10134704” title=“idp10134704” class=“indexterm”></a>
• \listplot*[par]{list} <a name=“idp10138448” id=“idp10138448” title=“idp10138448” class=“indexterm”></a>
• \psplot*[par]{xmin}{xmax}{function} <a name=“idp10142208” id=“idp10142208” title=“idp10142208” class=“indexterm”></a>
• \parametricplot*[par]{tmin}{tmax}{function} <a name=“idp10145984” id=“idp10145984” title=“idp10145984” class=“indexterm”></a>
• plotstyle=style <a name=“idp10149728” id=“idp10149728” title=“idp10149728” class=“indexterm”></a> <p>Default: line</p>
• plotpoints=int <a name=“idp10154448” id=“idp10154448” title=“idp10154448” class=“indexterm”></a> <p>Default: 50</p>

• origin={coor} <a name=“idp10161504” id=“idp10161504” title=“idp10161504” class=“indexterm”></a> <p>Default: 0pt,0pt</p>
• swapaxes=true <a name=“idp10166224” id=“idp10166224” title=“idp10166224” class=“indexterm”></a> <p>Default: false</p>

• linestyle=style <a name=“idp10173168” id=“idp10173168” title=“idp10173168” class=“indexterm”></a> <p>Default: solid</p>
• dash=dim1 dim2 <a name=“idp10177888” id=“idp10177888” title=“idp10177888” class=“indexterm”></a> <p>Default: 5pt 3pt</p>
• dotsep=dim <a name=“idp10182608” id=“idp10182608” title=“idp10182608” class=“indexterm”></a> <p>Default: 3pt</p>
• border=dim <a name=“idp10187296” id=“idp10187296” title=“idp10187296” class=“indexterm”></a> <p>Default: 0pt</p>
• bordercolor=color <a name=“idp10191984” id=“idp10191984” title=“idp10191984” class=“indexterm”></a> <p>Default: white</p>
• doubleline=true/false <a name=“idp10196704” id=“idp10196704” title=“idp10196704” class=“indexterm”></a> <p>Default: false</p>
• doublesep=dim <a name=“idp10201424” id=“idp10201424” title=“idp10201424” class=“indexterm”></a> <p>Default: 1.25\pslinewidth</p>
• doublecolor=color <a name=“idp10206192” id=“idp10206192” title=“idp10206192” class=“indexterm”></a> <p>Default: white</p>
• shadow=true/false <a name=“idp10210912” id=“idp10210912” title=“idp10210912” class=“indexterm”></a> <p>Default: false</p>
• shadowsize=dim <a name=“idp10215632” id=“idp10215632” title=“idp10215632” class=“indexterm”></a> <p>Default: 3pt</p>
• shadowangle=angle <a name=“idp10220320” id=“idp10220320” title=“idp10220320” class=“indexterm”></a> <p>Default: -45</p>
• shadowcolor=color <a name=“idp10225056” id=“idp10225056” title=“idp10225056” class=“indexterm”></a> <p>Default: darkgray</p>
• dimen=outer/inner/middle <a name=“idp10229792” id=“idp10229792” title=“idp10229792” class=“indexterm”></a> <p>Default: outer</p>

• fillstyle=style <a name=“idp10236736” id=“idp10236736” title=“idp10236736” class=“indexterm”></a> <p>Default: none</p>
• fillcolor=color <a name=“idp10241456” id=“idp10241456” title=“idp10241456” class=“indexterm”></a> <p>Default: white</p>
• hatchwidth=dim <a name=“idp10246176” id=“idp10246176” title=“idp10246176” class=“indexterm”></a> <p>Default: .8pt</p>
• hatchsep=dim <a name=“idp10250896” id=“idp10250896” title=“idp10250896” class=“indexterm”></a> <p>Default: 4pt</p>
• hatchcolor=color <a name=“idp10255584” id=“idp10255584” title=“idp10255584” class=“indexterm”></a> <p>Default: black</p>
• hatchangle=rot <a name=“idp10260304” id=“idp10260304” title=“idp10260304” class=“indexterm”></a> <p>Default: 45</p>

• arrows=style <a name=“idp10267264” id=“idp10267264” title=“idp10267264” class=“indexterm”></a> <p>Default: -</p> <p>Arrows: -, ↔, >-<, «→>, »-«, |-|, |-|, [-], (-), o-o, -, oo-oo, *-*, c-c, cc-cc, C-C</p>
• arrowsize=dim num <a name=“idp10273280” id=“idp10273280” title=“idp10273280” class=“indexterm”></a> <p>Default: 2pt 3</p>
• arrowlength=num <a name=“idp10278000” id=“idp10278000” title=“idp10278000” class=“indexterm”></a> <p>Default: 1.4</p>
• arrowinset=num <a name=“idp10282688” id=“idp10282688” title=“idp10282688” class=“indexterm”></a> <p>Default: .4</p>
• tbarsize=dim num <a name=“idp10287376” id=“idp10287376” title=“idp10287376” class=“indexterm”></a> <p>Default: 2pt 5</p>
• bracketlength=num, rbracketlength=num <a name=“idp10292112” id=“idp10292112” title=“idp10292112” class=“indexterm”></a><a name=“idp10294016” id=“idp10294016” title=“idp10294016” class=“indexterm”></a> <p>Default: .15</p>
• dotsize=dim num <a name=“idp10298752” id=“idp10298752” title=“idp10298752” class=“indexterm”></a> <p>Default: .5pt 2.5</p>
• arrowscale=num1 num2 <a name=“idp10303472” id=“idp10303472” title=“idp10303472” class=“indexterm”></a> <p>Default: 1</p>

• \newpsobject{name}{object}{par1=value1,…} <a name=“idp10310176” id=“idp10310176” title=“idp10310176” class=“indexterm”></a>
• \newpsstyle{name}{par1=value1,…} <a name=“idp10313984” id=“idp10313984” title=“idp10313984” class=“indexterm”></a>

• \pscustom*[par]{commands} <a name=“idp10319888” id=“idp10319888” title=“idp10319888” class=“indexterm”></a>

• linetype=int <a name=“idp10325856” id=“idp10325856” title=“idp10325856” class=“indexterm”></a> <p>Default: 0</p>

• liftpen=0/1/2 <a name=“idp10332752” id=“idp10332752” title=“idp10332752” class=“indexterm”></a> <p>Default: 0</p>

• \newpath <a name=“idp10339616” id=“idp10339616” title=“idp10339616” class=“indexterm”></a>
• \moveto(coor) <a name=“idp10343360” id=“idp10343360” title=“idp10343360” class=“indexterm”></a>
• \closepath <a name=“idp10347104” id=“idp10347104” title=“idp10347104” class=“indexterm”></a>
• \stroke[par] <a name=“idp10350848” id=“idp10350848” title=“idp10350848” class=“indexterm”></a>
• \fill[par] <a name=“idp10354592” id=“idp10354592” title=“idp10354592” class=“indexterm”></a>
• \gsave <a name=“idp10358336” id=“idp10358336” title=“idp10358336” class=“indexterm”></a>
• \grestore <a name=“idp10362080” id=“idp10362080” title=“idp10362080” class=“indexterm”></a>
• \translate(coor) <a name=“idp10365824” id=“idp10365824” title=“idp10365824” class=“indexterm”></a>
• \scale{num1 num2} <a name=“idp10369568” id=“idp10369568” title=“idp10369568” class=“indexterm”></a>
• \rotate{angle} <a name=“idp10373312” id=“idp10373312” title=“idp10373312” class=“indexterm”></a>
• \swapaxes <a name=“idp10377088” id=“idp10377088” title=“idp10377088” class=“indexterm”></a>
• \msave <a name=“idp10380768” id=“idp10380768” title=“idp10380768” class=“indexterm”></a>
• \mrestore <a name=“idp10384512” id=“idp10384512” title=“idp10384512” class=“indexterm”></a>
• \openshadow[par] <a name=“idp10388256” id=“idp10388256” title=“idp10388256” class=“indexterm”></a>
• \closedshadow[par] <a name=“idp10392000” id=“idp10392000” title=“idp10392000” class=“indexterm”></a>
• \movepath(coor) <a name=“idp10395744” id=“idp10395744” title=“idp10395744” class=“indexterm”></a>

• \lineto(coor) <a name=“idp10401616” id=“idp10401616” title=“idp10401616” class=“indexterm”></a>
• \rlineto(coor) <a name=“idp10405360” id=“idp10405360” title=“idp10405360” class=“indexterm”></a>
• \curveto(x1,y1)(x2,y2)(x3,y3) <a name=“idp10409120” id=“idp10409120” title=“idp10409120” class=“indexterm”></a>
• \rcurveto(x1,y1)(x2,y2)(x3,y3) <a name=“idp10412880” id=“idp10412880” title=“idp10412880” class=“indexterm”></a>

• \code{code} <a name=“idp10418768” id=“idp10418768” title=“idp10418768” class=“indexterm”></a>
• \dim{dim} <a name=“idp10422512” id=“idp10422512” title=“idp10422512” class=“indexterm”></a>
• \coor(x1,y1)(x2,y2)…(xn,yn) <a name=“idp10426272” id=“idp10426272” title=“idp10426272” class=“indexterm”></a>
• \rcoor(x1,y1)(x2,y2)…(xn,yn) <a name=“idp10430032” id=“idp10430032” title=“idp10430032” class=“indexterm”></a>
• \file{file} <a name=“idp10433776” id=“idp10433776” title=“idp10433776” class=“indexterm”></a>
• \arrows{arrows} <a name=“idp10437520” id=“idp10437520” title=“idp10437520” class=“indexterm”></a>
• \setcolor{color} <a name=“idp10441264” id=“idp10441264” title=“idp10441264” class=“indexterm”></a>

• \pspicture*[baseline](x0,y0)(x1,y1) <a name=“idp10447104” id=“idp10447104” title=“idp10447104” class=“indexterm”></a>
• \endpspicture <a name=“idp10450848” id=“idp10450848” title=“idp10450848” class=“indexterm”></a>

• \rput*[refpoint]{rotation}(x,y){stuff} <a name=“idp10456704” id=“idp10456704” title=“idp10456704” class=“indexterm”></a>
• \uput*{labelsep}[refangle]{rotation}(x,y){stuff} <a name=“idp10460480” id=“idp10460480” title=“idp10460480” class=“indexterm”></a>
• \pslabelsep <a name=“idp10464224” id=“idp10464224” title=“idp10464224” class=“indexterm”></a>
• labelsep=dim <a name=“idp10467968” id=“idp10467968” title=“idp10467968” class=“indexterm”></a> <p>Default: 5pt</p>

• \multirput*[refpoint]{angle}(x0,y0)(x1,y1){int}{stuff} <a name=“idp10475008” id=“idp10475008” title=“idp10475008” class=“indexterm”></a>
• \multips{angle}(x0,y0)(x1,y1){int}{graphics} <a name=“idp10478784” id=“idp10478784” title=“idp10478784” class=“indexterm”></a>

<a name=“idp10482784” id=“idp10482784” title=“idp10482784”></a>

• \psaxes*[par]{arrows}(x0,y0)(x1,y1)(x2,y2) <p> <table border=“0”> <tbody> <tr> <td align=“left”> Horizontal </td> <td align=“left”> Vertical </td> <td align=“left”> Dflt </td> <td align=“justify”> Description </td> </tr> <tr> <td align=“left”>Ox=num</td> <td align=“left”>Oy=num</td> <td align=“left”>0</td> <td align=“justify”>Label at origin.</td> </tr> <tr> <td align=“left”>Dx=num</td> <td align=“left”>Dy=num</td> <td align=“left”>1</td> <td align=“justify”>Label increment.</td> </tr> <tr> <td align=“left”>dx=dim</td> <td align=“left”>oy=dim</td> <td align=“left”>0pt</td> <td align=“justify”>Dist btwn labels.</td> </tr> </tbody> </table> </p>
• labels=all/x/y/none <a name=“idp10502928” id=“idp10502928” title=“idp10502928” class=“indexterm”></a> <p>Default: all</p>
• showorigin=true/false <a name=“idp10507840” id=“idp10507840” title=“idp10507840” class=“indexterm”></a> <p>Default: true</p>
• ticks=all/x/y/none <a name=“idp10512688” id=“idp10512688” title=“idp10512688” class=“indexterm”></a> <p>Default: all</p>
• tickstyle=full/top/bottom <a name=“idp10517520” id=“idp10517520” title=“idp10517520” class=“indexterm”></a> <p>Default: full</p>
• ticksize=dim <a name=“idp10522416” id=“idp10522416” title=“idp10522416” class=“indexterm”></a> <p>Default: 3pt</p>
• \psxlabel, \psylabel <a name=“idp10527232” id=“idp10527232” title=“idp10527232” class=“indexterm”></a><a name=“idp10529136” id=“idp10529136” title=“idp10529136” class=“indexterm”></a>
• axesstyle=axes/frame/none <a name=“idp10532944” id=“idp10532944” title=“idp10532944” class=“indexterm”></a> <p>Default: axes</p>

• framesep=dim <a name=“idp10539984” id=“idp10539984” title=“idp10539984” class=“indexterm”></a> <p>Default: 3pt</p>
• boxsep=true/false <a name=“idp10544800” id=“idp10544800” title=“idp10544800” class=“indexterm”></a> <p>Default: true</p>
• \psframebox*[par]{stuff} <a name=“idp10549664” id=“idp10549664” title=“idp10549664” class=“indexterm”></a>
• \psdblframebox*[par]{stuff} <a name=“idp10553424” id=“idp10553424” title=“idp10553424” class=“indexterm”></a>
• \psshadowbox*[par]{stuff} <a name=“idp10557184” id=“idp10557184” title=“idp10557184” class=“indexterm”></a>
• \pscirclebox*[par]{stuff} <a name=“idp10560944” id=“idp10560944” title=“idp10560944” class=“indexterm”></a>
• \cput*[par]{angle}(x,y){stuff} <a name=“idp10564704” id=“idp10564704” title=“idp10564704” class=“indexterm”></a>
• \psovalbox*[par]{stuff} <a name=“idp10568496” id=“idp10568496” title=“idp10568496” class=“indexterm”></a>

• \clipbox[dim]{stuff} <a name=“idp10574288” id=“idp10574288” title=“idp10574288” class=“indexterm”></a>
• \psclip{graphics} … \endpsclip <a name=“idp10578048” id=“idp10578048” title=“idp10578048” class=“indexterm”></a>

• \rotateleft{stuff} <a name=“idp10583952” id=“idp10583952” title=“idp10583952” class=“indexterm”></a>
• \rotateright{stuff} <a name=“idp10587696” id=“idp10587696” title=“idp10587696” class=“indexterm”></a>
• \rotatedown{stuff} <a name=“idp10591440” id=“idp10591440” title=“idp10591440” class=“indexterm”></a>
• \scalebox{num1 num2}{stuff} <a name=“idp10595248” id=“idp10595248” title=“idp10595248” class=“indexterm”></a>
• \scaleboxto(x,y){stuff} <a name=“idp10598992” id=“idp10598992” title=“idp10598992” class=“indexterm”></a>

• \rnode[refpoint]{name}{stuff} <a name=“idp10604832” id=“idp10604832” title=“idp10604832” class=“indexterm”></a>
• \Rnode(x,y){name}{stuff} <a name=“idp10608592” id=“idp10608592” title=“idp10608592” class=“indexterm”></a>
• \RnodeRef <a name=“idp10612336” id=“idp10612336” title=“idp10612336” class=“indexterm”></a>
• \pnode(x,y){name} <a name=“idp10616080” id=“idp10616080” title=“idp10616080” class=“indexterm”></a>
• \cnode*[par](x,y){radius}{name} <a name=“idp10619840” id=“idp10619840” title=“idp10619840” class=“indexterm”></a>
• \circlenode*[par]{name}{stuff} <a name=“idp10623600” id=“idp10623600” title=“idp10623600” class=“indexterm”></a>
• \cnodeput*[par]{angle}(x,y){name}{stuff} <a name=“idp10627376” id=“idp10627376” title=“idp10627376” class=“indexterm”></a>
• \ovalnode*[par]{name}{stuff} <a name=“idp10631136” id=“idp10631136” title=“idp10631136” class=“indexterm”></a>

• nodesep=dim <a name=“idp10637104” id=“idp10637104” title=“idp10637104” class=“indexterm”></a> <p>Default: 0</p>
• offset=dim <a name=“idp10641968” id=“idp10641968” title=“idp10641968” class=“indexterm”></a> <p>Default: 0</p>
• arm=dim <a name=“idp10646784” id=“idp10646784” title=“idp10646784” class=“indexterm”></a> <p>Default: 10pt</p>
• angle=angle <a name=“idp10651648” id=“idp10651648” title=“idp10651648” class=“indexterm”></a> <p>Default: 0</p>
• arcangle=angle <a name=“idp10656512” id=“idp10656512” title=“idp10656512” class=“indexterm”></a> <p>Default: 8</p>
• ncurv=num <a name=“idp10661328” id=“idp10661328” title=“idp10661328” class=“indexterm”></a> <p>Default: .67</p>
• loopsize=dim <a name=“idp10666192” id=“idp10666192” title=“idp10666192” class=“indexterm”></a> <p>Default: 1cm</p>
• \ncline*[par]{arrows}{nodeA}{nodeB} <a name=“idp10671072” id=“idp10671072” title=“idp10671072” class=“indexterm”></a>
• \ncLine*[par]{arrows}{nodeA}{nodeB} <a name=“idp10674832” id=“idp10674832” title=“idp10674832” class=“indexterm”></a>
• \nccurve*[par]{arrows}{nodeA}{nodeB} <a name=“idp10678592” id=“idp10678592” title=“idp10678592” class=“indexterm”></a>
• \ncarc*[par]{arrows}{nodeA}{nodeB} <a name=“idp10682352” id=“idp10682352” title=“idp10682352” class=“indexterm”></a>
• \ncbar*[par]{arrows}{nodeA}{nodeB} <a name=“idp10686112” id=“idp10686112” title=“idp10686112” class=“indexterm”></a>
• \ncdiag*[par]{arrows}{nodeA}{nodeB} <a name=“idp10689920” id=“idp10689920” title=“idp10689920” class=“indexterm”></a>
• \ncdiagg*[par]{arrows}{nodeA}{nodeB} <a name=“idp10693680” id=“idp10693680” title=“idp10693680” class=“indexterm”></a>
• \ncangle*[par]{arrows}{nodeA}{nodeB} <a name=“idp10697440” id=“idp10697440” title=“idp10697440” class=“indexterm”></a>
• \ncangles*[par]{arrows}{nodeA}{nodeB} <a name=“idp10701200” id=“idp10701200” title=“idp10701200” class=“indexterm”></a>
• \ncloop*[par]{arrows}{nodeA}{nodeB} <a name=“idp10704960” id=“idp10704960” title=“idp10704960” class=“indexterm”></a>
• \nccircle*[par]{arrows}{node}{radius} <a name=“idp10708720” id=“idp10708720” title=“idp10708720” class=“indexterm”></a>
• \pcline*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10712528” id=“idp10712528” title=“idp10712528” class=“indexterm”></a>
• \pccurve*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10716288” id=“idp10716288” title=“idp10716288” class=“indexterm”></a>
• \pcarc*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10720048” id=“idp10720048” title=“idp10720048” class=“indexterm”></a>
• \pcbar*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10723808” id=“idp10723808” title=“idp10723808” class=“indexterm”></a>
• \pcdiag*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10727616” id=“idp10727616” title=“idp10727616” class=“indexterm”></a>
• \pcangle*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10731376” id=“idp10731376” title=“idp10731376” class=“indexterm”></a>
• \pcloop*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10735136” id=“idp10735136” title=“idp10735136” class=“indexterm”></a>

• \lput*[refpoint]{rotation}(pos){stuff} <a name=“idp10741040” id=“idp10741040” title=“idp10741040” class=“indexterm”></a>
• \aput*[labelsep]{angle}(pos){stuff} <a name=“idp10744848” id=“idp10744848” title=“idp10744848” class=“indexterm”></a>
• \bput*[labelsep]{angle}(pos){stuff} <a name=“idp10748608” id=“idp10748608” title=“idp10748608” class=“indexterm”></a>
• \mput*[refpoint]{stuff} <a name=“idp10752352” id=“idp10752352” title=“idp10752352” class=“indexterm”></a>
• \Aput*[labelsep]{stuff} <a name=“idp10756096” id=“idp10756096” title=“idp10756096” class=“indexterm”></a>
• \Bput*[labelsep]{stuff} <a name=“idp10759840” id=“idp10759840” title=“idp10759840” class=“indexterm”></a>

• \pscoil*[par]{arrows}(x0,y0)(x1,y1) <a name=“idp10765776” id=“idp10765776” title=“idp10765776” class=“indexterm”></a>
• \psCoil*[par]{angle1}{angle2} <a name=“idp10769536” id=“idp10769536” title=“idp10769536” class=“indexterm”></a>
• \pszigzag*[par]{arrows}(x0,y0)(x1,y1) <a name=“idp10773296” id=“idp10773296” title=“idp10773296” class=“indexterm”></a>
• coilwidth=dim <a name=“idp10777040” id=“idp10777040” title=“idp10777040” class=“indexterm”></a> <p>Default: 1cm</p>
• coilheight=num <a name=“idp10781856” id=“idp10781856” title=“idp10781856” class=“indexterm”></a> <p>Default: 1</p>
• coilarm=dim <a name=“idp10786672” id=“idp10786672” title=“idp10786672” class=“indexterm”></a> <p>Default: .5cm</p>
• coilaspect=angle <a name=“idp10791568” id=“idp10791568” title=“idp10791568” class=“indexterm”></a> <p>Default: 45</p>
• coilinc=angle <a name=“idp10796384” id=“idp10796384” title=“idp10796384” class=“indexterm”></a> <p>Default: 10</p>
• \nccoil*[par]{arrows}{nodeA}{nodeB} <a name=“idp10801264” id=“idp10801264” title=“idp10801264” class=“indexterm”></a>
• \nczigzag*[par]{arrows}{nodeA}{nodeB} <a name=“idp10805024” id=“idp10805024” title=“idp10805024” class=“indexterm”></a>
• \pccoil*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10808832” id=“idp10808832” title=“idp10808832” class=“indexterm”></a>
• \pczigzag*[par]{arrows}(x1,y1)(x2,y2) <a name=“idp10812592” id=“idp10812592” title=“idp10812592” class=“indexterm”></a>

\SpecialCoor <a name=“idp10817680” id=“idp10817680” title=“idp10817680”></a>

<a name=“table-special-coordinates” id=“table-special-coordinates” title=“table-special-coordinates”></a>

Table 1.12. Special coordinates and angles

<table summary=“Special coordinates and angles” border=“0”> <tbody> <tr> <td align=“left”> Coordinate </td> <td align=“left”> Example </td> <td align=“justify”> Description </td> </tr> <tr> <td align=“left”>(x,y)</td> <td align=“left”>(3,4)</td> <td align=“justify”>Cartesian coordinate.</td> </tr> <tr> <td align=“left”>(r;a)</td> <td align=“left”>(3;110)</td> <td align=“justify”>Polar coordinate.</td> </tr> <tr> <td align=“left”>(node)</td> <td align=“left”>(A)</td> <td align=“justify”>Center of node.</td> </tr> <tr> <td align=“left”>([par]node)</td> <td align=“left”>([angle=45]A)</td> <td align=“justify”>Relative to node.</td> </tr> <tr> <td align=“left”>(ps)</td> <td align=“left”>(5 3.3 2 exp)</td> <td align=“justify”>Raw PostScript.</td> </tr> <tr> <td align=“left”>(coor1|coor2)</td> <td align=“left”>(A|1in;30)</td> <td align=“justify”>Combination.</td> </tr> </tbody> </table> <table summary=“Special coordinates and angles” border=“0”> <tbody> <tr> <td align=“left”> </td> <td> </td> <td> </td> </tr> <tr> <td align=“left”> Angle </td> <td align=“left”> Example </td> <td align=“justify”> Description </td> </tr> <tr> <td align=“left”>num</td> <td align=“left”>45</td> <td align=“justify”>Angle.</td> </tr> <tr> <td align=“left”>(coor)</td> <td align=“left”>(-1,1)</td> <td align=“justify”>Coordinate (vector).</td> </tr> <tr> <td align=“left”>ps</td> <td align=“left”>33 sqrt</td> <td align=“justify”>Raw PostScript.</td> </tr> </tbody> </table>

\NormalCoor <a name=“idp10852096” id=“idp10852096” title=“idp10852096”></a>

• \overlaybox stuff\endoverlaybox <a name=“idp10857664” id=“idp10857664” title=“idp10857664” class=“indexterm”></a>
• \psoverlay{string} <a name=“idp10861408” id=“idp10861408” title=“idp10861408” class=“indexterm”></a>
• \putoverlaybox{string} <a name=“idp10865200” id=“idp10865200” title=“idp10865200” class=“indexterm”></a>
• gradbegin=color <a name=“idp10868944” id=“idp10868944” title=“idp10868944” class=“indexterm”></a> <p>Default: gradbegin</p>
• gradend=color <a name=“idp10873792” id=“idp10873792” title=“idp10873792” class=“indexterm”></a> <p>Default: gradend</p>
• gradlines=int <a name=“idp10878640” id=“idp10878640” title=“idp10878640” class=“indexterm”></a> <p>Default: 500</p>
• gradmidpoint=num <a name=“idp10883504” id=“idp10883504” title=“idp10883504” class=“indexterm”></a> <p>Default: .9</p>
• gradangle=angle <a name=“idp10888320” id=“idp10888320” title=“idp10888320” class=“indexterm”></a> <p>Default: 0</p>

• \pstextpath[pos](x,y){graphics object}{text} <a name=“idp10895264” id=“idp10895264” title=“idp10895264” class=“indexterm”></a>

• \pscharpath*[par]{text} <a name=“idp10901216” id=“idp10901216” title=“idp10901216” class=“indexterm”></a>
• \pscharclip*[par]{text} … \endpscharclip <a name=“idp10905040” id=“idp10905040” title=“idp10905040” class=“indexterm”></a>

• \TeXtoEPS … \endTeXtoEPS <a name=“idp10910928” id=“idp10910928” title=“idp10910928” class=“indexterm”></a>
• \PSTtoEPS[par]{file}{graphics objects} <a name=“idp10914688” id=“idp10914688” title=“idp10914688” class=“indexterm”></a>
• bbllx=dim <a name=“idp10918432” id=“idp10918432” title=“idp10918432” class=“indexterm”></a> <p>Default: -1pt</p>
• bblly=dim <a name=“idp10923280” id=“idp10923280” title=“idp10923280” class=“indexterm”></a> <p>Default: -1pt</p>
• bburx=dim <a name=“idp10928128” id=“idp10928128” title=“idp10928128” class=“indexterm”></a> <p>Default: 1pt</p>
• bbury=dim <a name=“idp10932992” id=“idp10932992” title=“idp10932992” class=“indexterm”></a> <p>Default: 1pt</p>
• headerfile=file <a name=“idp10937808” id=“idp10937808” title=“idp10937808” class=“indexterm”></a> <p>Default: s</p>
• headers=none/all/user <a name=“idp10942624” id=“idp10942624” title=“idp10942624” class=“indexterm”></a> <p>Default: none</p>

• \psmathboxtrue, \psmathboxfalse <a name=“idp10949632” id=“idp10949632” title=“idp10949632” class=“indexterm”></a><a name=“idp10951536” id=“idp10951536” title=“idp10951536” class=“indexterm”></a>
• \everypsbox{commands} <a name=“idp10955280” id=“idp10955280” title=“idp10955280” class=“indexterm”></a>
• \pslongbox{name}{cmd} <a name=“idp10959024” id=“idp10959024” title=“idp10959024” class=“indexterm”></a>
• \psverbboxtrue, \psverbboxfalse <a name=“idp10962784” id=“idp10962784” title=“idp10962784” class=“indexterm”></a><a name=“idp10964688” id=“idp10964688” title=“idp10964688” class=“indexterm”></a>

• \pslbrace, \psrbrace <a name=“idp10970576” id=“idp10970576” title=“idp10970576” class=“indexterm”></a><a name=“idp10972480” id=“idp10972480” title=“idp10972480” class=“indexterm”></a>

• <a target=“_top” href=“ftp://ftp.dante.de/pub/tex/graphics/pstricks/contrib/psgo/” class=“ulink”>psgo</a> Draw Go diagrams
• <a target=“_top” href=“ftp://ftp.dante.de/pub/tex/graphics/pstricks/contrib/pst-blur/” class=“ulink”>pst-blur</a> PSTricks package for “blurred” shadows
• <a target=“_top” href=“http://dominique.rodriguez.9online.fr/pst-eucl/” class=“ulink”>pst-euc</a> Géométrie en LaTeX et PSTricks
• <a target=“_top” href=“http://www.tug.org/applications/PSTricks/More/pst-fr3d.tar.gz” class=“ulink”>pst-fr3d</a> Three dimensional framed Boxes
• <a target=“_top” href=“ftp://ftp.dante.de/pub/tex/graphics/pstricks/contrib/pst-ghsb/” class=“ulink”>pst-ghsb</a> PSTricks package for HSB Gradients
• <a target=“_top” href=“ftp://ftp.dante.de/pub/tex/graphics/pstricks/contrib/pst-gr3d/” class=“ulink”>pst-gr3d</a> PSTricks package for 3D grids
• <a target=“_top” href=“http://members.aol.com/ManuelLuque2/optique.htm” class=“ulink”>pst-lens</a> Optique géométrique
• <a target=“_top” href=“ftp://ftp.dante.de/tex-archive/graphics/pstricks/generic/” class=“ulink”>pst-node</a> PSTricks package for nodes
• <a target=“_top” href=“http://members.aol.com/Mluque5130/pst-ob3d.tar.gz” class=“ulink”>pst-ob3d</a> A PSTricks package for three dimensional basic objects
• <a target=“_top” href=“http://www.tug.org/applications/PSTricks/Physics/Oscilloscopes/” class=“ulink”>pst-osci</a> Oscilloscopes with PSTricks
• <a target=“_top” href=“ftp://ftp.dante.de/pub/tex/graphics/pstricks/contrib/pst-poly/” class=“ulink”>pst-poly</a> Polygons with PSTricks
• <a target=“_top” href=“ftp://ftp.dante.de/tex-archive/graphics/pstricks/generic/” class=“ulink”>pst-tree</a> PSTricks package for trees
• <a target=“_top” href=“http://www.ensta.fr/~diam/latex/pst-uml/” class=“ulink”>pst-uml</a> Draw easily diagrams with UML notation
• <a target=“_top” href=“http://perso.enst.fr/~lombardy/Vauc/” class=“ulink”>vaucansom.sty</a> Drawing automata

<a name=“idp11015344” id=“idp11015344” title=“idp11015344”></a>

tbd.

<a name=“idp11018448” id=“idp11018448” title=“idp11018448”></a><a name=“idp11019456” id=“idp11019456” title=“idp11019456”></a>

ConTeXt is based on PlainTeX and MetaPost and gets controlled with some Perl scripts. It's mainly targeted towards layout oriented users and especially useful for presentations. It's extensible by the use of modules and has in it's base distribution already a large amount of functionality. The preferred output format is PDF, but DVI is possible too.

Some of the unique features of ConTeXt are:

• Inline XML (including MathML, ChemML, and PhysML)
• really good XML support in general
• inline MetaPost

<a name=“idp11029360” id=“idp11029360” title=“idp11029360”></a>

tbd.

Table of Contents $ [[#pdftex-options|1 Options]]: $ 1.18 --version: $ 2 Environment: <a name=“idp11033552” id=“idp11033552” title=“idp11033552”></a>

The contents of this section was taken from pdftex(1).

<a name=“idp11037392” id=“idp11037392” title=“idp11037392”></a>

pdfTeX understands the following command line options.

<a name=“idp11041584” id=“idp11041584” title=“idp11041584”></a>

Print error messages in the form file:line:error which is similar to the way many compilers format them.

<a name=“idp11046592” id=“idp11046592” title=“idp11046592”></a>

Use format as the name of the format to be used, instead of the name by which pdfTeX was called or a %& line.

<a name=“idp11052960” id=“idp11052960” title=“idp11052960”></a>

Print help message and exit.

<a name=“idp11057184” id=“idp11057184” title=“idp11057184”></a>

Be pdfinitex, for dumping formats; this is implicitly true if the program is called as pdfinitex.

<a name=“idp11062864” id=“idp11062864” title=“idp11062864”></a>

Sets the interaction mode. The mode can be one of batchmode, nonstopmode, scrollmode, and errorstopmode. The meaning of these modes is the same as that of the corresponding \commands.

<a name=“idp11070624” id=“idp11070624” title=“idp11070624”></a>

Send DVI or PDF output to a socket as well as the usual output file. Whether this option is available is the choice of the installer.

<a name=“idp11074912” id=“idp11074912” title=“idp11074912”></a>

As –ipc, and starts the server at the other end as well. Whether this option is available is the choice of the installer.

<a name=“idp11080000” id=“idp11080000” title=“idp11080000”></a>

Use name for the job name, instead of deriving it from the name of the input file.

<a name=“idp11085056” id=“idp11085056” title=“idp11085056”></a>

Sets path searching debugging flags according to the bitmask. See the Kpathsea manual for details.

<a name=“idp11090128” id=“idp11090128” title=“idp11090128”></a>

Enable mktexfmt, where fmt must be one of tex or tfm.

<a name=“idp11097264” id=“idp11097264” title=“idp11097264”></a>

Disable mktexfmt, where fmt must be one of tex or tfm.

<a name=“idp11104304” id=“idp11104304” title=“idp11104304”></a>

Use string for the DVI file comment instead of the date.

<a name=“idp11109360” id=“idp11109360” title=“idp11109360”></a>

If the first line of the main input file begins with %& parse it to look for a dump name or a –translate-file option.

<a name=“idp11115088” id=“idp11115088” title=“idp11115088”></a>

Pretend to be program name. This affects both the format used and the search paths.

<a name=“idp11120080” id=“idp11120080” title=“idp11120080”></a>

Enable the filename recorder. This leaves a trace of the files opened for input and output in a file with extension .fls.

<a name=“idp11125200” id=“idp11125200” title=“idp11125200”></a>

Enable the \write18{command} construct. The command can be any Bourne shell command. This construct is normally disallowed for security reasons.

<a name=“idp11130240” id=“idp11130240” title=“idp11130240”></a>

Use the tcxname translation table.

<a name=“idp11135264” id=“idp11135264” title=“idp11135264”></a>

Print version information and exit.

<a name=“idp11139008” id=“idp11139008” title=“idp11139008”></a>

See the Kpathsearch library documentation (the `Path specifications' node) for the details of how the environment variables are used when searching. The kpsewhich utility can be used to query the values of the variables.

One caveat: In most pdfTeX formats, you cannot use ~ in a filename you give directly to pdfTeX, because ~ is an active character, and hence is expanded, not taken as part of the filename. Other programs, such as Metafont, do not have this problem.

• TEXMFOUTPUT <a name=“idp11145520” id=“idp11145520” title=“idp11145520” class=“indexterm”></a> <p>Normally, pdfTeX puts its output files in the current directory. If any output file cannot be opened there, it tries to open it in the directory specified in the environment variable TEXMFOUTPUT. There is no default value for that variable. For example, if you say pdftex paper and the current directory is not writable, if TEXMFOUTPUT has the value /tmp, pdfTeX attempts to create /tmp/paper.log (and /tmp/paper.pdf, if any output is produced.)</p>
• TEXINPUTS <a name=“idp11155600” id=“idp11155600” title=“idp11155600” class=“indexterm”></a> <p>Search path for \input and \openin files. This should probably start with ``., so that user files are found before system files. An empty path component will be replaced with the paths defined in the texmf.cnf file. For example, set TEXINPUTS to “.:/home/usr/tex:” to prepend the current direcory and ``/home/user/tex to the standard search path.</p>
• TEXFONTS <a name=“idp11164384” id=“idp11164384” title=“idp11164384” class=“indexterm”></a> <p>earch path for font metric (.tfm) files.</p>
• TEXFORMATS <a name=“idp11169312” id=“idp11169312” title=“idp11169312” class=“indexterm”></a> <p>Search path for format files.</p>
• TEXPOOL <a name=“idp11173520” id=“idp11173520” title=“idp11173520” class=“indexterm”></a> <p>Search path for pdfinitex internal strings.</p>
• TEXEDIT <a name=“idp11178448” id=“idp11178448” title=“idp11178448” class=“indexterm”></a> <p>Command template for switching to editor. The default, usually vi, is set when pdfTeX is compiled.</p>

<a name=“idp11185248” id=“idp11185248” title=“idp11185248”></a>

tbd.

Table of Contents $ [[#metapost-options|1 Options]]: $ 1.14 --version: $ 2 Environment: <a name=“idp11188624” id=“idp11188624” title=“idp11188624”></a>

The contents of this section was taken from mpost(1).

MetaPost is a programming language much like Knuth's Metafont except that it outputs PostScript programs instead of bitmaps. Borrowed from Metafont are the basic tools for creating and manipulating pictures. These include numbers, coordinate pairs, cubic splines, affine transformations, text strings, and boolean quantities. Additional features facilitate integrating text and graphics and accessing special features of PostScript such as clipping, shading, and dashed lines. Another feature borrowed from Metafont is the ability to solve linear equations that are given implicitly, thus allowing many programs to be written in a largely declarative style. By building complex operations from simpler ones, MetaPost achieves both power and exibility.

<a name=“idp11193728” id=“idp11193728” title=“idp11193728”></a>

MetaPost understands the following command line options.

<a name=“idp11197536” id=“idp11197536” title=“idp11197536”></a>

Print error messages in the form file:line:error which is similar to the way many compilers format them.

<a name=“idp11202496” id=“idp11202496” title=“idp11202496”></a>

Print help message and exit.

<a name=“idp11206784” id=“idp11206784” title=“idp11206784”></a>

Be inimpost, for dumping bases; this is implicitly true if the program is called as inimpost.

<a name=“idp11212576” id=“idp11212576” title=“idp11212576”></a>

Sets the interaction mode. The mode can be one of batchmode, nonstopmode, scrollmode, and errorstopmode. The meaning of these modes is the same as that of the corresponding commands.

<a name=“idp11219744” id=“idp11219744” title=“idp11219744”></a>

Use name for the job name, instead of deriving it from the name of the input file.

<a name=“idp11224848” id=“idp11224848” title=“idp11224848”></a>

Sets path searching debugging flags according to the bitmask. See the Kpathsea manual for details.

<a name=“idp11229904” id=“idp11229904” title=“idp11229904”></a>

Use mem as the name of the mem to be used, instead of the name by which MetaPost was called or a %& line.

<a name=“idp11235872” id=“idp11235872” title=“idp11235872”></a>

If the first line of the main input file begins with %& parse it to look for a dump name or a –translate-file option.

<a name=“idp11241680” id=“idp11241680” title=“idp11241680”></a>

Pretend to be program name. This affects both the format used and the search paths.

<a name=“idp11246672” id=“idp11246672” title=“idp11246672”></a>

Enable the filename recorder. This leaves a trace of the files opened for input and output in a file with extension .fls.

<a name=“idp11251520” id=“idp11251520” title=“idp11251520”></a>

Produce TROFF output.

<a name=“idp11255760” id=“idp11255760” title=“idp11255760”></a>

Use the tcxname translation table.

<a name=“idp11260768” id=“idp11260768” title=“idp11260768”></a>

As -T.

<a name=“idp11265040” id=“idp11265040” title=“idp11265040”></a>

Print version information and exit.

<a name=“idp11268736” id=“idp11268736” title=“idp11268736”></a>

See the Kpathsearch library documentation (the `Path specifications' node) for the details of how the environment variables are use when searching. The kpsewhich utility can be used to query the values of the variables.

If the environment variable TEXMFOUTPUT is set, MetaPost attempts to put its output files in it, if they cannot be put in the current directory.

Here is a list of the environment variables which affect the behavior of MetaPost:

• MPINPUTS <a name=“idp11274864” id=“idp11274864” title=“idp11274864” class=“indexterm”></a> <p>Search path for input files.</p>
• MFINPUTS <a name=“idp11278784” id=“idp11278784” title=“idp11278784” class=“indexterm”></a> <p>Auxiliary search path for input files with .mf extensions.</p>
• MPSUPPORT <a name=“idp11283456” id=“idp11283456” title=“idp11283456” class=“indexterm”></a> <p>Directory for various tables for handling included TeX and troff.</p>
• MPXCOMMAND <a name=“idp11287856” id=“idp11287856” title=“idp11287856” class=“indexterm”></a> <p>The name of a shell script that converts embedded typesetting commands to a form that MetaPost understands. Defaults: makempx for TeX and troffmpx for troff.</p>
• TEX <a name=“idp11293744” id=“idp11293744” title=“idp11293744” class=“indexterm”></a> <p>The version of TeX - or LaTeX - to use when processing btex and verbatimtex commands. Default TeX. This version of MetaPost allows you to use a `%&format' line instead.</p>
• TROFF <a name=“idp11301216” id=“idp11301216” title=“idp11301216” class=“indexterm”></a> <p>The troff pipeline for btex and verbatimtex commands. Default eqn -d\$\$ | troff</p>
• MPEDIT <a name=“idp11307136” id=“idp11307136” title=“idp11307136” class=“indexterm”></a> <p>A command template for invoking an editor.</p>

A .mem file is a binary file that permits fast loading of macro packages. MetaPost reads the default plain.mem unless another .mem file is specified at the start of the first line with an & just before it. There is also an mfplain.mem that simulates plain Metafont so that MetaPost can read .mf fonts. (Plain Metafont is described in The Metafontbook).

Experts can create .mem files by invoking inimpost and giving macro definitions followed by a dump command.

The MetaPost language is similar to Metafont, but the manual A User's Manual for MetaPost assumes no knowledge of Metafont. MetaPost does not have bitmap output commands or Metafont's online display mechanism.

Table of Contents

• 3 bib files $ 3.5 Field Types:
• 4 bst files $ 4.5 UNSRT.BST:

<a name=“idp11320656” id=“idp11320656” title=“idp11320656”></a>

The contents of this section was taken from the HTML helppages for BibTeX of Norman Walsh (Version 1.0, 12 Apr 94).

Invokes the BibTeX utility to compile a bibliography file for LaTeX. Full details can be found in “LaTeX: A Document Preparation System” by Leslie Lamport.

<a name=“idp11325504” id=“idp11325504” title=“idp11325504”></a>

bibliography-file-spec

Specifies the name of the bibliography database file to be compiled by BibTeX. If the file specification does not include a file type, BibTeX assumes a default type of BIB.

<a name=“idp11330496” id=“idp11330496” title=“idp11330496”></a>

/BIBINPUTS /BIBINPUTS=(name,…)

Specify directories containing input files, and the order in which they will be searched to locate each input file. A null value in the list indicates the current directory. The search procedure TeX uses to locate input files is to first search your default directory and then search each of the directories specified by the /BIBINPUTS option.

Default is /BIBINPUTS=(TEX_BIB:); TeX looks in the directory associated with the logical name TEX_BIB.

/STATS /STATS /NOSTATS [D]

This qualifier is used while debugging .BST files to determine BIBTEX memory usage.

/TEXINPUTS /TEXINPUTS=(name,…)

Specify directories containing input files, and the order in which they will be searched to locate each input file. A null value in the list indicates the current directory. The search procedure TeX uses to locate input files is to first search your default directory and then search each of the directories specified by the /TEXINPUTS option.

Default is /TEXINPUTS=(TEX_INPUTS); TeX looks in the directory associated with the logical name TEX_INPUTS.

/TRACE /TRACE /NOTRACE [D]

This qualifier is used while debugging .BST files to follow program flow.

<a name=“idp11347408” id=“idp11347408” title=“idp11347408”></a>

This help entry contains the same information as Appendix B of the LaTeX manual. It describes the format of a bibliography database (.BIB) file.

A bibliography database file may contains two types of entry - an abbreviation definition or a reference entry for citation.

<a name=“idp11353072” id=“idp11353072” title=“idp11353072”></a>

The @STRING command is used to define abbreviations for use by BibTeX within the bibliography database file. The command

 @string{jgg1 = "Journal of Gnats and Gnus, Series~1"} 

defines 'jgg1' to be the abbreviation for the string “Journal of Gnats and Gnus, Series~1”. Parentheses can be used in place of the outermost braces in the @string command, and braces can be used instead of the quotation marks. The text must have matching braces.

The case of letters is ignored in an abbreviation as well as in the command name @string, so the command above could have been written:

 @STRING{JgG1 = "Journal of Gnats and Gnus, Series~1"}  

A @string command can appear anywhere before or between entries in a bibliography database file. However, it must come before any use of the abbreviation, so a sensible place for @string commands is at the beginning of the file. A @string command in the bibliography database file takes precedence over a definition made by the bibliography style, so it can be used to change the definition of an abbreviation such as 'Feb'.

<a name=“idp11363136” id=“idp11363136” title=“idp11363136”></a>

A bibliography database file contains a series of reference entries like the following:

 @BOOK{kn:gnus,        AUTHOR = "Donald E. Knudson",        TITLE  = "1966 World Gnus Almanac",        PUBLISHER = {Permafrost Press},        ADDRESS = {Novisibirsk}             } 

The @BOOK states that this is an entry of type book. various entry types are described below. The 'kn:gnus' is the citation key, as it appears in the argument of a \cite command referring to the entry.

This entry has four fields, named AUTHOR, TITLE, PUBLISHER and ADDRESS. The meanings of these and other fields are described below. A field consists of the name, an '=' character with optional space around it, followed by its text. The text of a field is a string of characters, with no unmatched braces, surrounded by either a pair of braces or a pair of '“' characters. Entry fields are separated from one another, and from the citation key, by commas. A comma may have optional space around it.

The outermost braces that surround the entire entry may be replaced by parentheses. As in TeX input files, an end-of-line character counts as a space and one space is equivalent to many spaces. Unlike TeX, BibTeX ignores the case of letters in the entry type, citation key and field names. The above entry could have been typed as follows:

@BOOK(kn:gnus, author = {Donald E. Knudson},       TITLE  = "1966 World Gnus Almanac",       PUBLISHER = {Permafrost Press},       ADDRESS = {Novisibirsk}             ) 

However, the case of letters does matter to LaTeX, so the citation key (“kn:gnus” in the example above) should appear exactly the same in all \cite commands in the LaTeX input file.

The quotes or braces can be omitted around text consisting entirely of numerals. The following two fields are equivalent:

Volume = "27"           Volume = 27 

<a name=“idp11379680” id=“idp11379680” title=“idp11379680”></a>

When entering a reference in the bibliography database, the first thing to decide is what type of entry it is. No fixed classification scheme can be complete, but BibTeX provides enough entry types to handle almost any reference reasonably well.

References to different types of publications contain different information; a reference to a journal might include the volume and number of the journal, which is usually not meaningful for a book. Therefore, database entries of different types have different fields for each entry type, the fields are divided into three classes:

• Required <p>omitting the field will produce an error message and may result in a badly formatted bibliography entry. If the required information is not meaningful, you are using the wrong entry type.</p>
• Optional <p>the field's information will be used if present, but can be omitted without causing any formatting problems. A reference should contain any available information that might help the reader, so you should include the optional field if it is applicable.</p>
• Ignored <p>the field is ignored. BibTeX ignores any field that is not required or optional, so you can include any fields you want in a bibliography entry. It's often a good idea to put all relevant information about a reference in its bibliography entry - even information that may never appear in the bibliography. For example, if you want to keep an abstract of a paper in a computer file, put it in an 'abstract' field in the paper's bibliography entry. The bibliography database file is likely to be as good a place as any for the abstract, and it is possible to design a bibliography style for printing selected abstracts.</p>

BibTeX ignores the case of letters in the entry type.

<a name=“idp11392048” id=“idp11392048” title=“idp11392048”></a>

An article from a journal or magazine.

Format:

@ARTICLE{citation_key,          required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-journal“ title=“3.5.10 journal field”>journal</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-volume“ title=“3.5.22 volume field”>volume</a>, <a href=”#bibtex-field-types-number“ title=“3.5.14 number field”>number</a>, <a href=”#bibtex-field-types-pages“ title=“3.5.16 pages field”>pages</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11407168” id=“idp11407168” title=“idp11407168”></a>

A book with an explicit publisher.

Format:

@BOOK{citation_key,       required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a> or <a href=”#bibtex-field-types-editor“ title=“3.5.7 editor field”>editor</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-publisher“ title=“3.5.17 publisher field”>publisher</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-volume“ title=“3.5.22 volume field”>volume</a>, <a href=”#bibtex-field-types-series“ title=“3.5.19 series field”>series</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-edition“ title=“3.5.6 edition field”>edition</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11423488” id=“idp11423488” title=“idp11423488”></a>

A work that is printed and bound, but without a named publisher or sponsoring institution.

Format:

@BOOKLET{citation_key,          required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>

Optional fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-howpublished“ title=“3.5.8 howpublished field”>howpublished</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11435968” id=“idp11435968” title=“idp11435968”></a>

An article in the proceedings of a conference. This entry is identical to the 'inproceedings' entry and is included for compatibility with another text formatting system.

Format:

@CONFERENCE{citation_key,             required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-booktitle“ title=“3.5.4 booktitle field”>booktitle</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-editor“ title=“3.5.7 editor field”>editor</a>, <a href=”#bibtex-field-types-pages“ title=“3.5.16 pages field”>pages</a>, <a href=”#bibtex-field-types-organization“ title=“3.5.15 organization field”>organization</a>, <a href=”#bibtex-field-types-publisher“ title=“3.5.17 publisher field”>publisher</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11452080” id=“idp11452080” title=“idp11452080”></a>

A part of a book, which may be a chapter and/or a range of pages.

Format:

@INBOOK{citation_key,         required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a> or <a href=”#bibtex-field-types-editor“ title=“3.5.7 editor field”>editor</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-chapter“ title=“3.5.5 chapter field”>chapter</a> and/or <a href=”#bibtex-field-types-pages“ title=“3.5.16 pages field”>pages</a>, <a href=”#bibtex-field-types-publisher“ title=“3.5.17 publisher field”>publisher</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-volume“ title=“3.5.22 volume field”>volume</a>, <a href=”#bibtex-field-types-series“ title=“3.5.19 series field”>series</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-edition“ title=“3.5.6 edition field”>edition</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11469776” id=“idp11469776” title=“idp11469776”></a>

A part of a book with its own title.

Format:

@INCOLLECTION{citation_key,               required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-booktitle“ title=“3.5.4 booktitle field”>booktitle</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-editor“ title=“3.5.7 editor field”>editor</a>, <a href=”#bibtex-field-types-pages“ title=“3.5.16 pages field”>pages</a>, <a href=”#bibtex-field-types-organization“ title=“3.5.15 organization field”>organization</a>, <a href=”#bibtex-field-types-publisher“ title=“3.5.17 publisher field”>publisher</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11485600” id=“idp11485600” title=“idp11485600”></a>

An article in the proceedings of a conference.

Format:

@INPROCEEDINGS{citation_key,                required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-booktitle“ title=“3.5.4 booktitle field”>booktitle</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-editor“ title=“3.5.7 editor field”>editor</a>, <a href=”#bibtex-field-types-pages“ title=“3.5.16 pages field”>pages</a>, <a href=”#bibtex-field-types-organization“ title=“3.5.15 organization field”>organization</a>, <a href=”#bibtex-field-types-publisher“ title=“3.5.17 publisher field”>publisher</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11501392” id=“idp11501392” title=“idp11501392”></a>

Technical documentation.

Format:

@MANUAL{citation_key,         required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>

Optional fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-organization“ title=“3.5.15 organization field”>organization</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-edition“ title=“3.5.6 edition field”>edition</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11514608” id=“idp11514608” title=“idp11514608”></a>

A Master's thesis.

Format:

@MASTERSTHESIS{citation_key,                required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-school“ title=“3.5.18 school field”>school</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11526992” id=“idp11526992” title=“idp11526992”></a>

Use this type when nothing else seems appropriate.

Format:

@MISC{citation_key,       required_fields [, optional_fields] } 

Required fields: none

Optional fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-howpublished“ title=“3.5.8 howpublished field”>howpublished</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11538592” id=“idp11538592” title=“idp11538592”></a>

A PhD thesis.

Format:

@PHDTHESIS{citation_key,            required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-school“ title=“3.5.18 school field”>school</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11550944” id=“idp11550944” title=“idp11550944”></a>

The proceedings of a conference.

Format:

@PROCEEDINGS{citation_key,              required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-editor“ title=“3.5.7 editor field”>editor</a>, <a href=”#bibtex-field-types-publisher“ title=“3.5.17 publisher field”>publisher</a>, <a href=”#bibtex-field-types-organization“ title=“3.5.15 organization field”>organization</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11564128” id=“idp11564128” title=“idp11564128”></a>

A report published by a school or other institution, usually numbered within a series.

Format:

@TECHREPORT{citation_key,             required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-institution“ title=“3.5.9 institution field”>institution</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>

Optional fields: <a href=”#bibtex-field-types-type“ title=“3.5.21 type field”>type</a>, <a href=”#bibtex-field-types-number“ title=“3.5.14 number field”>number</a>, <a href=”#bibtex-field-types-address“ title=“3.5.1 address field”>address</a>, <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11578432” id=“idp11578432” title=“idp11578432”></a>

A document with an author and title, but not formally published.

Format:

@UNPUBLISHED{citation_key,              required_fields [, optional_fields] } 

Required fields: <a href=”#bibtex-field-types-author“ title=“3.5.3 author field”>author</a>, <a href=”#bibtex-field-types-title“ title=“3.5.20 title field”>title</a>, <a href=”#bibtex-field-types-note“ title=“3.5.13 note field”>note</a>

Optional fields: <a href=”#bibtex-field-types-month“ title=“3.5.12 month field”>month</a>, <a href=”#bibtex-field-types-year“ title=“3.5.23 year field”>year</a>, <a href=”#bibtex-field-types-key“ title=“3.5.11 key field”>key</a>

<a name=“idp11589168” id=“idp11589168” title=“idp11589168”></a>

The text of the field is enclosed in braces or double quote characters. A part of the text is said to be enclosed in braces if it lies inside a matching pair of braces other than the ones enclosing the entire entry or the entire field text.

BibTeX manipulates the case of letters in the field text as described in the subtopics below.

<a name=“idp11593664” id=“idp11593664” title=“idp11593664”></a>

The text of an author or editor field represents a list of names. The bibliography style determines the format in which the name is printed: whether the first name or last name appears first, if the full first name or just the first initial is used, etc. The bibliography file entry simply tells BibTeX what the name is.

You should type an author's complete name and let the bibliography style decide what to abbreviate. (But an author's complete name may be “Donald~E. Knuth” or even “J.~P.~Morgan”; you should type it the way the author would like it to appear, if that's known.)

Most names can be entered in the obvious way, either with or without a comma, as in the following examples:

“John Paul Jones” “Jones, John Paul” “Ludwig von Beethoven” “von Beethoven, Ludwig”

Some people have multiple last names - for example, Per Brinch Hansen's last name is Brinch~Hansen. His name should be typed with a comma:

“Brinch Hansen, Per”

To understand why, you must understand how BibTeX handles names (for what follows, a “name” corresponds to a person).

Each name consists of four parts: First, von, Last, and~Jr; each part consists of a (possibly empty) list of name-tokens. For example the First part of Per Brinch~Hansen's name has the single token “Per”; the Last part has two, “Brinch” and “Hansen”; and the von and Jr parts are empty. If you had typed

“Per Brinch Hansen”

instead, BibTeX would erroneously think “Brinch” were a First-part token, just as “Paul” is a First-part token in “John~Paul Jones”.

Here's another example:

“Charles Louis Xavier Joseph de la Vallee Poussin”

This name has four tokens in the First part, two in the von, and two in the Last. Here BibTeX knows where one part ends and the other begins because the tokens in the von part begin with lower-case letters.

If you want BibTeX to consider something a single token, enclose it in braces. You should do this, for example, if a comma is part of a name:

”{Barnes and Noble, Inc.}“ ”{Barnes and} {Noble, Inc.}“ ”{Barnes} {and} {Noble,} {Inc.}“

The braces surrounding the comma keep “Inc.” from being interpreted as a First token; this name has only a Last part, with either one, two, or four tokens (there must be a space separating the tokens in the second and third forms). Probably the second form is slightly more meaningful, but don't lose sleep over this since only rarely will an institution be an author or editor.

So the two names

“von Beethoven, Ludwig” ”{von Beethoven}, Ludwig“

are considered by BibTeX to be different names. In the first, “Beethoven” is the Last part and “von” is the von part; in the second, which in this case happens to be incorrect, the Last part has a single token and there's no von part. The bibliography style will probably print both the same, but it may alphabetize and label them differently.

“Juniors” pose a special problem. Most people having “Jr.” in their name precede it with a comma. Such a name should be entered as follows:

“Ford, Jr., Henry”

However, a few people do not use a comma. They are handled by considering the “Jr.” to be part of the last Last token:

”{Steele Jr.}, Guy L.“ “Guy L. {Steele Jr.}”

This name has no Jr part.

To summarize, you may type a name in one of three forms:

“First von Last” “von Last, First” “von Last, Jr, First”

You may almost always use the first form; you shouldn't if either there's a Jr part or the Last part has multiple tokens but there's no von part.

If there are multiple authors or editors, their names must be separated by the word “and”, surrounded by spaces, not enclosed in braces:

AUTHOR = “Ralph Alpher and Bethe, Hans and George Gamow”

Since BibTeX interprets commas as separating parts of a name and “and” as separating names themselves, this example has three coauthors: Ralph Alpher, Hans Bethe, and George Gamow. If the word “and” appears as part of a name, it must be enclosed in braces, as in the example of “Barnes and Noble,~Inc.” given above. If you have too many names to list in a field, you can end the list with “and others”; the standard styles appropriately append an “et al.”

BibTeX's rules are actually a bit more complicated than indicated here, but this description will suffice for most names.

<a name=“idp11617216” id=“idp11617216” title=“idp11617216”></a>

The bibliography style determines whether or not a title is capitalized; the titles of books usually are, the title of articles usually are not. You type a title the way it should appear if it is capitalized (you should capitalize everything but articles and unstressed conjunctions and prepositions, and even these should be capitalized as the first word or the first after a colon):

TITLE = “The Agony and the Ecstasy”

BibTeX will change uppercase letters to lowercase if appropriate. Uppercase letters that should not be changed are enclosed in braces. The following two titles are equivalent; the “A” of “Africa” will not be made lowercase.

“The Gnats and Gnus of {Africa}” “The Gnats and Gnus of {A}frica”

<a name=“idp11622960” id=“idp11622960” title=“idp11622960”></a>

Instead of an ordinary text string, the text of a field can be replaced by an abbreviation for it. An abbreviation is a string of characters that starts with a letter and does not contain a space or any of the following ten characters:

” # % ' ( ) , = { }

The abbreviation is typed in place of the text field, with no braces or quotation marks. If 'jgg1' is an abbreviation for

Journal of Gnats and Gnus, Series~1

then the following are equivalent:

JOURNAL = jgg1 JOURNAL = “Journal of Gnats and Gnus, Series~1”

Some abbreviations are predefined by the bibliography style. These always include the usual 3 letter abbreviations for the month: jan, feb, mar etc.

Bibliography styles usually contain abbreviations for the names of commonly referenced journals. Consult the Local Guide for a list of the predefined abbreviations for the bibliography styles available.

You can define your own abbreviations by using BibTeX's @STRING command.

<a name=“idp11632416” id=“idp11632416” title=“idp11632416”></a>

Below is a list of all fields recognized by the standard bibliography styles. An entry can also contain other fields, which are ignored by those styles.

BibTeX ignores the case of letters in the field names.

<a name=“idp11636800” id=“idp11636800” title=“idp11636800”></a>

Publisher's address. For major publishing houses, just the city is given. For small publishers, you can help the reader by giving the complete address.

Format:

ADDRESS = field_text 

<a name=“idp11641632” id=“idp11641632” title=“idp11641632”></a>

An annotation, used only for annotated bibliography styles (which are not among the standard ones).

Format:

ANNOTE = field_text 

<a name=“idp11646416” id=“idp11646416” title=“idp11646416”></a>

The name(s) of the author(s).

Format:

AUTHOR = field_text 

<a name=“idp11651120” id=“idp11651120” title=“idp11651120”></a>

Title of a book, part of which is being cited.

Format:

BOOKTITLE = field_text 

<a name=“idp11655840” id=“idp11655840” title=“idp11655840”></a>

A chapter number.

Format:

CHAPTER = field_text 

<a name=“idp11660528” id=“idp11660528” title=“idp11660528”></a>

The edition of a book - for example, “second”.

Format:

EDITION = field_text 

<a name=“idp11665248” id=“idp11665248” title=“idp11665248”></a>

Name(s) of editor(s). If there is also an “author” field, then the “editor” field gives the editor of the book or collection in which the reference appears.

Format:

EDITOR = field_text 

<a name=“idp11670096” id=“idp11670096” title=“idp11670096”></a>

How something strange has been published.

Format:

HOWPUBLISHED = field_text 

<a name=“idp11674832” id=“idp11674832” title=“idp11674832”></a>

The institution that published the work.

Format:

INSTITUTION = field_text 

<a name=“idp11679504” id=“idp11679504” title=“idp11679504”></a>

A journal name. Abbreviations are provided for many journals; see the Local Guide.

Format:

JOURNAL = field_text 

<a name=“idp11684240” id=“idp11684240” title=“idp11684240”></a>

Used for alphabetizing and creating a label when the “author” and “editor” fields are missing. This field should not be confused with the citation key that appears in the \cite command and at the beginning of the entry.

Format:

KEY = field_text 

<a name=“idp11689792” id=“idp11689792” title=“idp11689792”></a>

The month in which the work was published or, for an unpublished work, in which it was written.

Format:

MONTH = field_text 

<a name=“idp11694544” id=“idp11694544” title=“idp11694544”></a>

Any additional information that can help the reader.

Format:

NOTE = field_text 

<a name=“idp11699280” id=“idp11699280” title=“idp11699280”></a>

The number of a journal, magazine, or technical report. An issue of a journal or magazine is usually identified by its volume and number; the organization that issues a technical report usually gives it a number.

Format:

NUMBER = field_text 

<a name=“idp11704192” id=“idp11704192” title=“idp11704192”></a>

The organization sponsoring a conference.

Format:

ORGANIZATION = field_text 

<a name=“idp11708928” id=“idp11708928” title=“idp11708928”></a>

A page number or range of numbers such as “42–111”; you may also have several of these, separating them with commas: “7,41,73–97”. The standard styles convert a single dash to a double. >

Format:

PAGES = field_text 

<a name=“idp11714016” id=“idp11714016” title=“idp11714016”></a>

The publisher's name.

Format:

PUBLISHER = field_text 

<a name=“idp11718720” id=“idp11718720” title=“idp11718720”></a>

The name of the school where a thesis was written.

Format:

SCHOOL = field_text 

<a name=“idp11723376” id=“idp11723376” title=“idp11723376”></a>

The name of a series or set of books. When citing an entire book, the the “title” field gives its title and an optional “series” field gives the name of a series in which the book is published.

Format:

SERIES = field_text 

<a name=“idp11728256” id=“idp11728256” title=“idp11728256”></a>

The work's title.

Format:

TITLE = field_text 

<a name=“idp11732912” id=“idp11732912” title=“idp11732912”></a>

The type of a technical report - for example, “Research Note”.

Format:

TYPE = field_text 

<a name=“idp11737648” id=“idp11737648” title=“idp11737648”></a>

The volume of a journal or multivolume book work.

Format:

VOLUME = field_text 

<a name=“idp11742336” id=“idp11742336” title=“idp11742336”></a>

The year of publication or, for an unpublished work, the year it was written. This field's text should contain only numerals.

Format:

YEAR = field_text 

<a name=“idp11747376” id=“idp11747376” title=“idp11747376”></a>

Bibliography style files define the style of a bibliography source list.

The standard bibliography style files are <a href=“#bibtex-bst-plain” title=“4.3 PLAIN.BST”>PLAIN</a>, <a href=“#bibtex-bst-unsrt” title=“4.5 UNSRT.BST”>UNSRT</a>, <a href=“#bibtex-bst-alpha” title=“4.2 ALPHA.BST”>ALPHA</a> and <a href=“#bibtex-bst-abbr” title=“4.1 ABBRV.BST”>ABBRV</a>.

If you want to make a bibliography style of your own, look at <a href=“#bibtex-bst-sample” title=“4.4 SAMPLE.BST”>SAMPLE.BST</a>.

<a name=“idp11760016” id=“idp11760016” title=“idp11760016”></a>

This style is the same as the style defined in PLAIN.BST, except that entries are more compact because first names, month names and journal names are abbreviated.

<a name=“idp11765088” id=“idp11765088” title=“idp11765088”></a>

This style is the same as the style defined in PLAIN.BST except that entry labels like “Knu66”, formed from the author's name and the year of publication, are used.

<a name=“idp11770096” id=“idp11770096” title=“idp11770096”></a>

This style is formatted more or less as suggested by Mary-Claire van Leunen in “A Handbook for Scholars” (Alfred A. Knopf, New York, 1979). Entries are sorted alphabetically and are labelled with numbers.

<a name=“idp11774448” id=“idp11774448” title=“idp11774448”></a>

This is a sample bibliography style file meant to help you construct a new style. It creates a bibliography in which entries appear as follows:

[Jones79] Jones, R. L. and Richards, P. Q. The Birds and the Bees. {\it Journal of Irreproducible Results 4}, 2 (Jan. 1979), 27-33.

[Jones82a] Jones, P. G. The Bees and the Trees … (1982).

[Jones82b] Jones, R. L. The Trees and the Peas … (1982).

[Krist74] Kristofferson, R. P. Peopl and Places … (1974)

It should illustrate how you write a style file. The functions are described in an informal Pascal-like style in comments. Because of the way while loops and if-then-else statements must use functions, the following convention is used. If a while loop is labeled 'foo' in the informal description, then its test and body are the functions named 'foo.test' and 'foo.body'. If an if statement is labeled 'foo', then its two clauses are the functions named 'foo.then' and 'foo.else'. (Null clauses just use the 'skip$' function.) Note that because functions have to be defined in terms of already-defined functions, the actual function definitions are given in a 'bottom-up' order.

<a name=“idp11782576” id=“idp11782576” title=“idp11782576”></a>

This style is that same as PLAIN.BST except that entries appear in the order of their first citation.

Table of Contents $ [[#makeindex-options|1 Options]]: $ 1.12 -T: $ [[#makeindex-style-file|2 Style File]]: $ 2.2 Output Style Specifiers: $ 5 Special Effects: <a name=“idp11787888” id=“idp11787888” title=“idp11787888”></a>

The contents of this section was taken from the HTML helppages for Make-Index of Norman Walsh (Version 1.0, 12 Apr 94).

Some obvious errors in this documentation have been corrected according to makeindex(1L).

Additional information was taken from makeindex(1L) and the program source files as found in teTeX 2.0.2.

Make-Index is a general purpose index processor. It takes one or more raw index files (normally generated by a formatter), sorts the entries, and produces the actual index file. It is not dependent on any particular format of raw index file, although the .idx file generated by LaTeX is the default. Up to three levels (0, 1, and 2) of subitem nesting within the same entry is supported. The input format may be redefined in a style file so that raw index or glossary output from other formatters may be processed. The style file also defines the style of output index file. Unless specified otherwise, the file name base of the first input file (idx0) is used to determine other related input/output files. The default input file type is .idx.

<a name=“idp11798992” id=“idp11798992” title=“idp11798992”></a>

Make-Index is a Unix program, and therefore has a Unix-style command line. Instead of qualifiers delimited with a slash (/), Make-Index options are delimited with a hyphen (-).

<a name=“idp11804992” id=“idp11804992” title=“idp11804992”></a>

Enable blank compression. By default every blank counts in the index key. The -c option ignores leading and trailing blanks and tabs and compresses intermediate ones to a single space.

<a name=“idp11810096” id=“idp11810096” title=“idp11810096”></a>

Employ German word ordering in the index, in accord with rules set forth in DIN 5007. The quote character must be redefined in a style file (for example, redefine quote as '+'). If the quote character is not redefined, Make-Index will produce an error message and abort.

<a name=“idp11815760” id=“idp11815760” title=“idp11815760”></a>

Use stdin as the input file. When this option is specified and the -o is not, output is written to stdout.

<a name=“idp11822112” id=“idp11822112” title=“idp11822112”></a>

Use letter ordering. Default is word ordering (explained in the <a href=“#makeindex-ordering” title=“4 Ordering”>Ordering</a> section).

<a name=“idp11827360” id=“idp11827360” title=“idp11827360”></a>

Quiet mode, send no messages to stderr. By default progress and error messages are sent to stderr as well as the transcript file. The -q option disables the stderr messages.

<a name=“idp11834496” id=“idp11834496” title=“idp11834496”></a>

Disable implicit page range formation. By default three or more successive pages will be automatically abbreviated as a range (e.g. 1–5). The -r option disables it, making the explicit range operators the only way to create page ranges (see the <a href=“#makeindex-special-effects” title=“5 Special Effects”>Special Effects</a> section below).

<a name=“idp11840640” id=“idp11840640” title=“idp11840640”></a>

Take sty as the style file. There is no default for the style file name. The environment variable INDEXSTYLE defines the path where the style file should be found.

<a name=“idp11845744” id=“idp11845744” title=“idp11845744”></a>

Take ind as the output index file. By default the file name base of the first input file idx0 concatenated with the extension .ind is used as the output file name.

<a name=“idp11852208” id=“idp11852208” title=“idp11852208”></a>

Take log as the transcript file. By default the file name base of the first input file idx0 concatenated with the extension .ilg is used as the transcript file name.

<a name=“idp11858672” id=“idp11858672” title=“idp11858672”></a>

Set the starting page number of the output index file to be no. This is useful when the index file is to be formatted separately. Other than pure numbers, three special cases are allowed for no: any, odd, and even. In these special cases, the starting page number is determined by retrieving the last page number from the source log file. The source log file name is determined by concatenating the file name base of the first raw index file (idx0) with the extension .log. The last source page is obtained by searching backward in the log file for the first instance of a number included in […]. If a page number is missing or the log file is not found, no attempt will be made to set the starting page number. The meaning of each of these cases follows:

• any <p>The starting page is the last source page number plus 1.</p>
• odd <p>The starting page is the first odd page following the last source page number.</p>
• even <p>The starting page is the first even page following the last source page number.</p>

<a name=“idp11873904” id=“idp11873904” title=“idp11873904”></a>

Sort based on locale settings. String comparisons for sorting are done using strcoll(3), which compares strings according to the current locale category LC_COLLATE.

Not available on all systems (depends on compile time settings).

<a name=“idp11880048” id=“idp11880048” title=“idp11880048”></a>

Special support for Thai documents.

Not available on all systems (depends on compile time settings).

<a name=“idp11884224” id=“idp11884224” title=“idp11884224”></a>

The style file format is very simple. It is a list of <specifier, attribute> pairs. There are two types of specifiers (input and output). The pairs don't have to obey any particular order in the file. A line lead by `%' is a comment. The following is a list of all the specifiers and their respective arguments where <string> is an arbitrary string delimited by double quotes (“…”), <char> is a single letter embraced by single quotes ('…'), and <number> is a nonnegative integer. The maximum length of a <string> is 144. Notice that a backslash must be escaped (by an extra backslash) in the string quotation. Anything not specified in the style file will be assigned a default value, which is shown on a separate line. This file can reside anywhere in the path defined by the environment variable INDEXSTYLE.

<a name=“idp11894064” id=“idp11894064” title=“idp11894064”></a>

<a name=“idp11896704” id=“idp11896704” title=“idp11896704”></a>

Default: @

The symbol which indicates that the next entry is to appear in the actual index file.

<a name=“idp11901376” id=“idp11901376” title=“idp11901376”></a>

Default: }

This is the closing delimiter for the index entry argument.

<a name=“idp11906208” id=“idp11906208” title=“idp11906208”></a>

Default: {

This is the opening delimiter for the index entry argument.

<a name=“idp11910752” id=“idp11910752” title=“idp11910752”></a>

Default: |

The symbol which indicates that the rest of the argument list is to be used as the encapsulating command for the page number.

<a name=“idp11915408” id=“idp11915408” title=“idp11915408”></a>

Default:

The symbol which escapes the next letter, unless its preceding letter is escape. In other words, quote is used to escape the letter which immediately follows it. But if it is preceded by escape, it does not escape anything.

Notice that the two symbols must be distinct.

<a name=“idp11920576” id=“idp11920576” title=“idp11920576”></a>

Default: “\\indexentry”

This is the command which tells Make-Index that its argument is an index entry.

<a name=“idp11925648” id=“idp11925648” title=“idp11925648”></a>

Default: !

The delimiter which denotes a new level of subitem.

<a name=“idp11930176” id=“idp11930176” title=“idp11930176”></a>

Default: “

quote is used to escape the letter which immediately follows it, but if it is preceded by escape, it is treated as a ordinary character. These two symbols must be distinct.

<a name=“idp11935456” id=“idp11935456” title=“idp11935456”></a>

Default: )

The closing delimiter indicating the end of an explicit page range.

<a name=“idp11939984” id=“idp11939984” title=“idp11939984”></a>

Default: (

The opening delimiter indicating the beginning of an explicit page range.

<a name=“idp11944672” id=“idp11944672” title=“idp11944672”></a>

<a name=“idp11947360” id=“idp11947360” title=“idp11947360”></a>

Default: ”-“

This specifier is used to separate a range of page numbers.

Officially undocumented!

<a name=“idp11952416” id=“idp11952416” title=“idp11952416”></a>

Default: “\\begin{theindex}\n”

The preamble of actual index file.

<a name=“idp11957040” id=“idp11957040” title=“idp11957040”></a>

Default: “\n\n\\end{theindex}\n”

The postamble of actual index file.

<a name=“idp11961680” id=“idp11961680” title=“idp11961680”></a>

Default: “\n \\setcounter{page}{”

The prefix of the command which sets the starting page number.

<a name=“idp11966320” id=“idp11966320” title=“idp11966320”></a>

Default: ”}\n“

The suffix of the command which sets the starting page number.

<a name=“idp11970992” id=“idp11970992” title=“idp11970992”></a>

Default: “\n\n \\indexspace\n”

The vertical space to be inserted before a new group begins.

<a name=“idp11975616” id=“idp11975616” title=“idp11975616”></a>

Default: ”“

The header prefix to be inserted before a new letter begins.

<a name=“idp11980256” id=“idp11980256” title=“idp11980256”></a>

Default: ”“

The header suffix to be inserted before a new letter begins.

<a name=“idp11984848” id=“idp11984848” title=“idp11984848”></a>

Default: 0

The flag indicating the condition of inserting new letter header. Default is 0, which means no header. Positive means insert an uppercase letter between prefix and suffix. Negative means insert a lowercase letter.

<a name=“idp11989600” id=“idp11989600” title=“idp11989600”></a>

Default: “Symbols”

Heading for symbols to be inserted if headings_flag is positive.

<a name=“idp11994928” id=“idp11994928” title=“idp11994928”></a>

Default: “symbols”

Heading for symbols to be inserted if headings_flag is negative.

<a name=“idp12000304” id=“idp12000304” title=“idp12000304”></a>

Default: “Numbers”

Heading for numbers to be inserted if headings_flag is positive.

<a name=“idp12005680” id=“idp12005680” title=“idp12005680”></a>

Default: “numbers”

Heading for numbers to be inserted if headings_flag is negative.

<a name=“idp12010960” id=“idp12010960” title=“idp12010960”></a>

Default: “\n \\item ”

The command to be inserted between two primary (level 0) items.

<a name=“idp12015584” id=“idp12015584” title=“idp12015584”></a>

Default: “\n \\subitem ”

The command to be inserted between two secondary (level 1) items.

<a name=“idp12020208” id=“idp12020208” title=“idp12020208”></a>

Default: “\n \\subsubitem ”

The command to be inserted between two level 2 items.

<a name=“idp12024896” id=“idp12024896” title=“idp12024896”></a>

Default: “\n \\subitem ”

The command to be inserted between a level 0 item and a level 1 item.

<a name=“idp12029520” id=“idp12029520” title=“idp12029520”></a>

Default: “\n \\subitem ”

The command to be inserted between a level 0 item and a level 1 item. The difference between this and previous is that in this case the level 0 item doesn't have any page numbers.

<a name=“idp12034256” id=“idp12034256” title=“idp12034256”></a>

Default: “\n \\subsubitem ”

The command to be inserted between a level 1 item and a level 2 item.

<a name=“idp12038928” id=“idp12038928” title=“idp12038928”></a>

Default: “\n \\subsubitem ”

The command to be inserted between a level 1 item and a level 2 item. The difference between this and previous is that in this case the level 1 item doesn't have any page numbers.

<a name=“idp12043712” id=“idp12043712” title=“idp12043712”></a>

Default: ”, “

The delimiter to be inserted between a level 0 key and its first page number. Default is a comma followed by a blank.

<a name=“idp12048368” id=“idp12048368” title=“idp12048368”></a>

Default: ”, “

The delimiter to be inserted between a level 1 key and its first page number. Default is a comma followed by a blank.

<a name=“idp12053040” id=“idp12053040” title=“idp12053040”></a>

Default: ”, “

The delimiter to be inserted between a level 2 key and its first page number. Default is a comma followed by a blank.

<a name=“idp12057696” id=“idp12057696” title=“idp12057696”></a>

Default: ”, “

The delimiter to be inserted between two page numbers for the same key in any level. Default is a comma followed by a blank.

<a name=“idp12062368” id=“idp12062368” title=“idp12062368”></a>

Default: ”–“

The delimiter to be inserted between the starting and ending page numbers of a range.

<a name=“idp12067056” id=“idp12067056” title=“idp12067056”></a>

Default: ”“

The delimiter to be inserted at the end of a page list. This delimiter has no effect on entries which have no associated page list.

<a name=“idp12071776” id=“idp12071776” title=“idp12071776”></a>

Default: “\\”

The prefix for the command which encapsulates the page number.

<a name=“idp12076448” id=“idp12076448” title=“idp12076448”></a>

Default: ”{“

The prefix for the command which encapsulates the page number.

<a name=“idp12081136” id=“idp12081136” title=“idp12081136”></a>

Default: ”}“

The suffix for the command which encapsulates the page number.

<a name=“idp12085808” id=“idp12085808” title=“idp12085808”></a>

Default: 72

The maximum length of a line in the output beyond which a line wraps around.

<a name=“idp12090464” id=“idp12090464” title=“idp12090464”></a>

Default: “\t\t”

The space to be inserted in front of a wrapped line. Default is two tabs.

<a name=“idp12095104” id=“idp12095104” title=“idp12095104”></a>

Default: 16

The length of indent_space. In the default case this is 16 (for 2 tabs).

<a name=“idp12099792” id=“idp12099792” title=“idp12099792”></a>

Default: ”“

Delimiter to replace the range delimiter and the second page number of a two page list. When present, it overrides delim_r.

<a name=“idp12105168” id=“idp12105168” title=“idp12105168”></a>

Default: ”“

Delimiter to replace the range delimiter and the second page number of a three page list. When present, it overrides delim_r and suffix_mp.

<a name=“idp12111264” id=“idp12111264” title=“idp12111264”></a>

Default: ”“

Delimiter to replace the range delimiter and the second page number of a multiple page list (three or more pages). When present, it overrides delim_r.

<a name=“idp12116912” id=“idp12116912” title=“idp12116912”></a>

The following example shows a style file called book.isty which defines a stand-alone index for a book. By stand-alone, we mean it can be formatted independent of the main source.

preamble "\\documentstyle[12pt]{book} \\begin{document} \\begin{theindex} {\\small\n"  postamble "\n\n} \\end{theindex} \\end{document}\n" 

Suppose a particular book style requires the index (as well as any chapters) to start from an odd page number. Given foo.idx as the raw index file, the following command line produces an index in file foo-.ind.

makeindex  -s book.isty  -o foo-.ind  -p odd  foo 

The reason to use a non-default output file name is to avoid clobbering the source output (presumably foo.dvi) because if the index is in file foo.ind, its output will also be in foo.dvi as a result of separate formatting using . In the example the index is in foo-.ind, its output will be in foo-.dvi and thus introduces no confusion.

<a name=“idp12129248” id=“idp12129248” title=“idp12129248”></a>

By default makeindex assumes word ordering. The -l option turns it into letter ordering. The only difference is whether a blank is treated as an effective letter or not. In word ordering, a blank precedes any letter in the alphabet, whereas in letter ordering, it doesn't count at all. This is best illustrated by the following example:

Numbers are sorted in numeric order. For instance,

Letters are first sorted with uppercase and lowercase considered identical; then, within identical words the uppercase letter precedes its lowercase counterpart.

Patterns lead by a special symbol precede numbers, which precede patterns lead by a letter. The symbol here refers to anything not in the union of digits and English alphabet. This includes those which follow 'z' in the ASCII chart. As a special case, anything started with a digit but mixed with non-digits is considered a symbol-leading pattern instead of a number.

<a name=“idp12149520” id=“idp12149520” title=“idp12149520”></a>

In the normal case entries such as

\indexentry{alpha}{1}   \indexentry{alpha!beta}{3}   \indexentry{alpha!beta!gamma}{10} 

in the raw index file will be converted to

\item alpha, 1    \subitem beta, 3      \subsubitem gamma, 10 

in the output index file by Make-Index. Notice that the level symbol () is used to delimit levels of nesting.

It is possible to make an item appear in a designated form by using the actual (@) operator. For instance,

\indexentry{alpha@{\it alpha\/}}{1}  

will become

\item {\it alpha\/} 1 

after the conversion. The idea is that the pattern preceding @ is used as sort key, whereas the one following it is put in the actual result. However, the same key with and without the actual part are regarded as distinct entries.

It is also possible to encapsulate a page number with a designated command using the encap (|) operator. For example, in the default case,

\indexentry{alpha|bold}{1} 

will be converted to

\item alpha \bold{1} 

where \bold{n} will expand to {\bf n}. This allows the encap operator to be used to set pages in different fonts, thereby conveying more information about whatever being indexed. For instance, given the same key the page where its definition appears can be in one font while where its primary example is given can be in another, with other ordinary appearances in a third. Notice that in this example, the three output attributes associated with page encapsulation encap_prefix, encap_infix, and encap_suffix correspond respectively to backslash, left brace, and right brace. If this is to be formatted by languages other than , they would be defined differently.

By the same token, the encap operator can be used to make cross references in the index. For instance,

\indexentry{alpha|see{beta}}{1} 

will become

\item alpha \see{beta}{1} 

in the output index file after the conversion, where

\see{beta}{1} 

will expand to

{\it see\/} beta 

Notice that in a cross reference like this the page number disappears. Therefore, where to insert such a command in the source is immaterial.

A pair of encap concatenated with range_open (|() and with range_close (|)) creates an explicit page range. That is,

\indexentry{alpha|(}{1}   \indexentry{alpha|)}{5} 

will become

\item alpha, 1--5 

Intermediate pages indexed by the same key will be merged into the range implicitly. This is especially useful when an entire section about a particular subject is to be indexed, in which case only the range opening and closing operators need to be inserted at the beginning and end of the section, respectively.

This explicit page range formation can also include an extra command to set the page range in a designated font. Thus

\indexentry{alpha|(bold}{1}   \indexentry{alpha|)}{5} 

will become

\item alpha, \bold{1--5} 

A couple of special cases are worth mentioning here. First, entries like

\indexentry{alpha|(}{1}   \indexentry{alpha|bold}{3}   \indexentry{alpha|)}{5}  

will be interpreted as

\item alpha, \bold{3}, 1--5 

but with a warning message in the transcript about the encounter of an inconsistent page encapsulator. Secondly, an explicit range beginning in a Roman page number and ending in Arabic is considered an error. In a case like this the range is broken into two subranges, if possible, one in Roman, the other in Arabic. For instance,

\indexentry{alpha|(}{i} \indexentry{alpha}{iv} \indexentry{alpha}{3} \indexentry{alpha|)}{7} 

will be turned into

\item alpha, 1--iv, 3--7 

with a warning message in the transcript complaining about the illegal range formation.

Finally, every special symbol mentioned in this section may be escaped by the quote operator (”). Thus

\indexentry{alpha"@beta}{1}  

will actually become

\item alpha@beta, 1 

as a result of executing Make-Index. However, if quote is preceded by escape (\), its following letter is not escaped. That is,

\indexentry{f\"ur}{1}  

means

\item f\"ur, 1 

which represents umlaut accented u to the family of processors.

Table of Contents

• 1 Command List $ 1.3 Raw Index Interface:
• 2 Invoking xindy $ 2.2 Search Path:

<a name=“idp12189360” id=“idp12189360” title=“idp12189360”></a>

The content of this section was taken from the original documentation of xindy V2.1 (Doc/manual*.html).

xindy means fle x ible ind exing s y stem. It is an indexing system that can be used to generate book-like indexes for arbitrary document preparation systems. This term includes systems such as TeX and LaTeX, the Nroff-family or SGML-based systems (e.g. HTML) that process some kind of text and generate indexing information. It is not fixed to any specific system, but can be configured for a wide variety of purposes.

<a name=“idp12196448” id=“idp12196448” title=“idp12196448”></a>

Here is the complete list of xindy's commands that may be used in the index style. The symbol name always refers to a string. We separate the commands into the processing and markup commands. The commands are listed in alphabetical order.

The parenthesis [ and ] denote optional parts of the syntax and { and } denote the grouping of elements. A vertical bar indicates alternatives. However, the enclosing round braces are part of the syntax and must be supplied.

<a name=“idp12204304” id=“idp12204304” title=“idp12204304”></a>

<a name=“idp12207424” id=“idp12207424” title=“idp12207424”></a> <pre>(define-alphabet name string-list) </pre>

Defines name to be the alphabet consisting of all elements of the string-list. Examples:

(define-alphabet "example-alphabet" ("An" "Example" "Alphabet")) 

defines an alphabet consisting of exactly three symbols. For the successor relationship holds: succ(“An”)=“Example” and succ(“Example”)=“Alphabet”. The built-in alphabet digits is defined as follows:

(define-alphabet "digits"                  ("0" "1" "2" "3" "4" "5" "6" "7" "8" "9")) 

<a name=“idp12217408” id=“idp12217408” title=“idp12217408”></a> <pre>(define-attributes attribute-list) </pre>

Defines all attributes the raw index may contain. Parameter attribute-list is a list of list of strings. The nesting level must not be more than 2. So (..(..)..) is allowed, whereas (..(..(..)..)..) is not.

The list has two kinds of elements: strings and list of strings. A single string is treated as if it were a single element list. So the lists (“definition”) and ( (“definition”) ) are equivalent. All elements forming a list are a so-called attribute group. The members of a group are written to the output file before any member of the following groups are written.

Examples of valid attributes lists are:

(“definition” “usage”) defines two attribute groups. The first one contains all references with the attribute definition and the second one all with the attribute usage.

¹⁾ </pre>

Defines the order for the different sorting phases. The currently implemented orientations are forward and backward. This command must precede all sort-rule commands in an index style. It defines the orientations and implicitly sets the maximum number of sorting phases performed.

For further descriptions on the sorting model refer to the command sort-rule.

<a name=“idp12319808” id=“idp12319808” title=“idp12319808”></a> <pre>(merge-rule pattern replacement [:again] [:bregexp | :eregexp | :string]) </pre>

Defines a keyword mapping rule that can be used to generate the merge key from the main key of an index entry. This mapping is necessary to map all keywords that are differently written but belong to the same keyword to the same canonical keyword.

The parameter pattern can be a POSIX-compliant regular expression or an ordinary string. The implementation uses the GNU Rx regular expression library which implements the POSIX regular expressions. Regular expressions (REs) can be specified as basic regular expressions (BREs) or extended regular expressions (EREs). You can use the switch :bregexp to force the interpretation of the pattern as a BRE, or :eregexp to interpret it as an ERE. If you want xindy to interpret the pattern literally, use the switch :string. If none of these switches is selected, xindy uses an auto-detection mechanism to decide, if the pattern is a regular expression or not. If it recognizes the pattern as a RE, it interprets it as an ERE by default.

The parameter replacement must be a string possibly containing the special characters & (substitutes for the complete match) and \1 ,…, \9 (substituting for the n -th submatch. Examples:

(merge-rule "A" "a") 

replaces each occurrence of the uppercase letter `A' with its lowercase counterpart.

(merge-rule "\~"([AEOUaeou])" "\1") 

transforms the TeX umlaut-letters into their stripped counterparts, such that `\“A ' is treated as an `A' afterwards.

The following sequences have a special meaning:

• ` ~n ' <p>End of line symbol ( linefeed).</p>
• ` ~b ' <p>The ISO-Latin character with the lowest ordinal number.</p>
• ` ~e ' <p>The ISO-Latin character with the highest ordinal number.</p>
• ` ~~ ' <p>The tilde character.</p>
• ` ~” ' <p>The double quote character.</p>

Tilde characters and double quotes have to be quoted themselves with a tilde character. The special characters ` ~b ' and ` ~e ' allow the definition of arbitrary sorting orders by rules. In connection with an additional character every position in the alphabet can be described. E.g. ` m~e ' is lexicographically placed between `m' and `n'.

Due to efficiency, rules that just exchange characters or substitute constant character sequences are not treated as regular expressions. Therefore, instead of using the rule

(merge-rule "[A-Z]" "&") 

it is more efficient (though less comfortable) to use

(merge-rule "A" "Ax") (merge-rule "B" "Bx") ... (merge-rule "Z" "Zx") 

Usually rules are applied in order of their definition. Rules with a special prefix precede those that begin with a class of characters, so that the search pattern `alpha' is checked before `.*', but `auto' and `a.*' are checked in order of their definition.

The first rule from a style file that matches the input is applied and the process restarts behind the substituted text. If no rule could be applied, the actual character is copied from the input and the process continues with the next character.

Sometimes it is necessary to apply rules anew to the result of a transformation. By specifying the keyword argument :again in the merge rule the rule is marked as mutable, which means that after using this rule the transformation process shall restart at the same place. E.g. the rule

(merge-rule "\$(.*)\$" "\1" :again) 

deletes all surrounding `$ ' symbols from the input.

See also command sort-rule.

<a name=“idp12364256” id=“idp12364256” title=“idp12364256”></a> <pre>(merge-to attr-from attr-to [:drop]) </pre>

A merge rule says that the attribute attr-from can be used to build ranges in attr-to. Both attributes must name valid attribute names. The switch :drop indicates, that the original location reference with attribute attr-from has to be dropped (removed), if a successful range was built with location references in attribute attr-to. A detailed description is given in the section about processing phases.

<a name=“idp12372992” id=“idp12372992” title=“idp12372992”></a> <pre>(require filename) </pre>

This command allows to load more index style modules. The module is searched in the directories defined in the search path. The file is read in and processing of the current file continues. The argument filename must be a string. This allows to decompose the index style into several modules that can be included into the topmost index style file. Example:

(require "french/alphabet.xdy") (require "french/sort-rules.xdy") (require "tex/locations.xdy") (require "tex/markup.xdy") 

Submodules can load other submodules as well. If a file is required that was already loaded, the require command is simply ignored and processing continues without including this file twice. See also command searchpath.

<a name=“idp12380720” id=“idp12380720” title=“idp12380720”></a> <pre>(searchpath {path-string | path-list}) </pre>

This command adds the given paths to the list of paths, xindy searches for index style files. The argument path-string must be a colon-separated string of directory names. If this path ends with a colon the default search path is added to the end of the path list. Example:

(searchpath ".:/usr/local/lib/xindy:/usr/local/lib/xindy/english:") 

adds the specified directories to the search path. Since the last path ends with a colon, the built-in search path is added at the end. Specifying

(searchpath ("."              "/usr/local/lib/xindy"              "/usr/local/lib/xindy/english"              :default)) 

yields exactly the same result as the example above. Here path-list must be a list of strings and/or the keyword(s) :default and :last. The keyword :default signifies that the default pathnames are to be inserted at the specified position in the list. The keyword :last allows to insert the currently active paths at the indicated position. Since this allows to insert the built-in paths at any position and incrementally adding new paths to the search path, this version of the command ist more flexible than the first version.

<a name=“idp12392352” id=“idp12392352” title=“idp12392352”></a> <pre>(sort-rule pattern replacement [:run level] [:again]) </pre>

Defines a keyword mapping rule that can be used to generate the sort key of an index entry from the merge key. This key is used to sort the index entries lexicographically after they have been merged using the merge key.

The argument :run indicates that this rule is only in effect a the specified level (default is level 0). For a detailed discussion on the definition of sort rules for different layers refer to the documentation about the new sorting scheme (new-sort-rules) that comes with this distribution.

See command merge-rule for more information about keyword rules.

<a name=“idp12402016” id=“idp12402016” title=“idp12402016”></a> <pre>(use-rule-set [:run phase] [:rule-set ( <rule-set>… )) </pre>

This command instantiates the gives rule sets to be in effect at sorting phase phase. The order of the rule sets given with argument :rule-set is significant. Rule set entries of rule set appearing at the beginning of the list override entries in rule sets at the end of the list.

The following example declares that in phase 0 the rule sets din5007 and isolatin1-tolower should be active, whereas in phase 2 the other rule sets have to be applied.

(use-rule-set :run 0               :rule-set ("din5007" "isolatin1-tolower"))  (use-rule-set :run 1               :rule-set ("resolve-umlauts"                          "resolve-sharp-s"                          "isolatin1-tolower"                         )) 

For a discussion on rule sets refer to command define-rule-set.

<a name=“idp12412576” id=“idp12412576” title=“idp12412576”></a>

The following commands can be used to define the markup of the index. They don't have any influence on the indexing process. Since the markup scheme is characterized by the concept of environments, the syntax and naming scheme of all commands follows a simple structure.

The commands can be separated into environment and list-environment commands. All commands of the first group support the keyword arguments :open and :close, whereas the second group additionally supports the keyword argument :sep. If one of these keyword arguments is missing, the default markup tag is always the empty tag. The :open tag is always printed before the object itself and the :close tag is always printed after the object has been printed. If a list is printed the :sep tag is printed between two elements of the list but not before the first element, or after the last one. All commands dealing with a list have the suffix `-list' as part of their command name.

Since the number of commands and the heavy usage of default and specialized tags makes the markup somehow complex (but very powerful) we have added a mechanism to trace the markup tags xindy omits during its markup phase with the command markup-trace.

Here follows the list of markup commands in alphabetical order with some of the commands grouped together.

(markup-attribute-group-list [:open string] [:close string]                              [:sep string])  (markup-attribute-group      [:open string] [:close string]                              [:group group-num]) 

Location class groups consist of lists of attribute groups. The markup of this list can be defined with the command markup-attribute-group-list.

To allow different markup for different attribute groups the command markup-attribute-group can be specialized on the group number with the keyword argument :group which must be an integer number. E.g., given are the groups (“definition” “theorem”) and (“default”) with group numbers 0 and 1, then

(markup-attribute-group :open "<group0>" :close </group0>"                         :group 0)  (markup-attribute-group :open "<group1>" :close "</group1>"                         :group 1) 

can be used to assign different markup for both groups in a SGML-based language.

(markup-crossref-list       [:open string] [:close string]                             [:sep string]                             [:class crossref-class])  (markup-crossref-layer-list [:open string] [:close string]                             [:sep string]                             [:class crossref-class])  (markup-crossref-layer      [:open string] [:close string]                             [:class crossref-class]) 

A crossref class group contains cross references of the same class. The separator between the classes is defined with the (markup-locclass-list :sep)-parameter. A list of cross references can be tagged with the command markup-crossref-list that specializes on the :class argument.

Each cross reference is determined by a list of layers indicating the target of the cross reference. To define a suitable markup for such a list the command markup-crossref-layer-list can be used.

Each layer of a cross reference can be assigned two tags that specialize on the class of the reference, like all other commands.

A suitable markup for a cross reference class see within LaTeX2e could look like that:

(markup-crossref-list :class "see" :open "\emph{see} "                                    :sep  "; ") (markup-crossref-layer-list :class "see" :sep ",") (markup-crossref-layer :class "see"                                    :open "\textbf{" :close "}") 

An example output could look like … see house; garden,winter; greenhouse

(markup-index [:open string] [:close string]               [ :flat | :tree | :hierdepth depth ]) 

Defines the markup tags that enclose the whole index via the :open and :close parameters. Examples:

(markup-index :open  "Here comes the index~n"               :close "That's all folks!~n") 

defines that the :open string is printed before the rest of the index and the :close string appears after the index is printed.

Additionally one can specify the form of the generated index. It is possible to produce flat indexes by specifying the switch :flat, to generate a tree with the :tree switch or any kind of mixture between both by specifying the depth up to which trees shall be built with the parameter :hierdepth. Its argument depth is the number of layers that can be formed into a tree. Therefore :flat is an abbrevation of :hierdepth 0 and :tree is an abbrevation of :hierdepth max-depth, with max-depth being the maximum number of layers a keyword has. An example: the keywords

("tree" "binary" "AVL") ("tree" "binary" "natural") 

can be transformed in the following ways:

A flat index (:flat or :hierdepth 0)

tree binary AVL tree binary natural 

with :hierdepth 1

tree    binary  AVL    binary  natural 

and a tree (:tree or :hierdepth > 1)

tree    binary       AVL       natural 

Most often one will create tree-like indexes or ones that are flat.

(markup-indexentry-list [:open string] [:close string]                         [:sep string]  [:depth integer])  (markup-indexentry      [:open string] [:close string]                         [:depth integer]) 

Letter groups consists of a list of index entries. The command markup-indexentry-list defines the markup of these lists. The markup can be specialized on the depth if the index is hierarchically organized. The command

(markup-indexentry-list :open  "\begin{IdxentList}"                         :close "\end{IdxentList}"                         :sep   "~n") 

defines that the index entries of all layers are wrapped into the given markup tags. If additionally

(markup-indexentry-list :open  "\begin{IdxentListII}"                         :close "\end{IdxentListII}"                         :sep   "~n"                         :depth 2) 

is defined, all index entry lists of all layers (except layer 2) are tagged according to the first specification, and the index entry list within depth 2 are tagged according to the second rule.

The command markup-indexentry defines the markup of an index entry at a given depth. Since index entries may also contain subentries and the markup for subentries may be different in different layers, the optional keyword argument :depth can be used to assign different markup for different layers. If depth is ommited the default markup for all possible depths is defined. The top-most index entries have depth 0.

(markup-indexentry :open  "\begin{Indexentry}"                    :close "\end{Indexentry}") 

defines that the index entries of all layers are wrapped into the given markup tags. If additionally

(markup-indexentry :open  "\begin{IndexentryII}"                    :close "\end{IndexentryII}"                    :depth 2) 

is defined, all index entries of all layers (except layer 2) are tagged according to the first specification, and the index entries with depth 2 are tagged according to the second rule.

(markup-keyword-list [:open string] [:close string]                      [:sep string] [:depth integer])  (markup-keyword      [:open string] [:close string]                      [:depth integer]) 

The print key of an index entry consists of a list of strings. The markup of this list can be defined with the command markup-keyword-list. The keyword argument :depth may be specified to define the markup of the list at a particular depth.

The keyword of an index entry consists of a list of strings. Each of these components is tagged with the strings defined with the command markup-keyword. Since we maybe need different markup for different layers, the optional keyword argument can be used to specialize this markup for some depth.

(markup-letter-group-list [:open string] [:close string]                           [:sep string])  (markup-letter-group  [:open string] [:close string] [:group group-name]                       [:open-head string] [:close-head string]                       [:upcase | :downcase | :capitalize]) 

The first command defines the markup of the letter group with name group-name. Since the markup of letter groups often contains the name of the letter group as a part of it, the other keyword arguments allow an additional markup for this group name. If one of the parameters :open-head and :close-head is specified additional markup is added as can be described as follows:

<OPEN>    IF (:open-head OR :close-head)      <OPEN-HEAD>        transformer-of(<GROUP-NAME>)      <CLOSE-HEAD>    FI    <INDEXENTRIES...> <CLOSE> 

Here, transformer-of is a function that possibly transforms the string representing the group name into another string. The transformers we currently support can be specified with the switches :upcase, :downcase and :capitalize which result in the corresponding string conversions. If none of them is specified no transformation is done at all.

The command markup-letter-group defines the markup of the list of letter groups.

(markup-locclass-list [:open string] [:close string]                       [:sep string]) 

Each index entry contains a list of location class groups. This markup command can be used to define the markup of this list.

(markup-locref [:open string] [:close string]                [:class locref-class]                [:attr  attribute]                [:depth integer]) 

The markup tags of a location reference can be specialized on the three arguments :class, :attr and additionally, if sub-references are used, :depth. Most often one will only use a tag depending on the attribute. For example, all location references with the attribute definition should appear in a font series like bold, emphasizing the importance of this location reference; those with the attribute default in font shape italic. The markup in this case would not specialize on the depth or any particular class. A valid definition, suitable for a usage within HTML, could look like this.

(markup-locref :open "<B>" :close "</B>" :attr "definition") (markup-locref :open "<I>" :close "</I>" :attr "default") 

(markup-locref-class [:open string] [:close string]                      [:class locref-class]) 

All location references of a particular location reference class can be wrapped into the tags defined by this command. It specializes on the keyword argument :class.

(markup-locref-layer      [:open string] [:close string]                           [:depth integer] [:layer integer]                           [:class locref-class])  (markup-locref-layer-list [:open string] [:close string]                           [:sep string]                           [:depth integer]                           [:class locref-class]) 

A location reference contains a list of location reference layers. The second markup command can be used to markup this list. It specializes on the class of the location references and the depth (if sub-references are used).

The first command allows to tag the elements of a layer list differently. The first element of this list can is specialisable with :layer 0, the next element with :layer 1, etc. See the next example for an example.

(markup-locref-list [:open string] [:close string] [:sep string]                     [:depth integer] [:class locref-class]) 

An attribute group contains a list of location references and/or ranges. Additionally a layered location reference itself may contain sub-references that are stored as a list of location references. We specialize the markup for these lists on the location class they belong to with the keyword argument :class, and on :depth that specializes on the different subentry levels when using location references with sub-references.

Given is a list of location references that have the class description

(define-location-class "Appendix"                        ("ALPHA" :sep "-" "arabic-numbers")                        :hierdepth 2) 

This location class has instances like A-1, B-5, etc. The keyword argument :hierdepth 2 informs xindy to markup these location references in a hierarchical form. With the commands

(markup-locref-list            :sep "; "                      :depth 0  :class "Appendix") (markup-locref-list  :open " " :sep ","                      :depth 1  :class "Appendix") (markup-locref-layer :open "{\bf " :close "}" :layer 0                      :depth 0  :class "Appendix") 

we obtain a markup sequence for some example data that could look like

 \bf A} 1,2,5; {\bf B} 5,6,9; {\bf D} 1,5,8; ... 

(markup-range [:open string] [:close string] [:sep string]               [:class locref-class]               [:length num] [:ignore-end]) 

A range consists of two location references. Markup can be specified with the :open and :close arguments and one separator given by the argument :sep.

Since both location references are tagged with markup defined by the command markup-locref a specialization on attributes or depth is not necessary. Specialization is allowed on the class they belong to, because the separator between two location refences may be different for each location class. Argument :length can be used to define different markup for different lengths. In conjunction with :length is may be useful not to print the second location reference at all. For example, one wishes to markup ranges of length 1 in the form Xf. instead of X–Y. This can be accomplished with the switch :ignore-end.

The markup tags for a range (X,Y) can be described as follows:

<OPEN>   Markup of location reference X <SEP>   IF (not :ignore-end)      Markup of location reference Y   FI <CLOSE> 

The following tags can be used to define a range of page numbers (given in a location class page-numbers) without considering the open and close parameters:

(markup-range :sep "-" :class "page-numbers") 

Location ranges then appear separated by a hyphen in a form like this:

   ..., 5-8, 19-23, ... 

This command can be used to activate the tracing of all markup commands xindy executes. The switch :on activates the trace. If :on is omitted, the command line flag -t can be used as well. All tags which are emitted but not yet defined explicitly by the user are tagged with a symbolic notation indicating the commands that must be used to define this tag. The defaults for the keyword argument :open is `<' and for :close is `>'. The beginning of an example output could look like:

<INDEX:OPEN>   <LETTER-GROUP-LIST:OPEN>     <LETTER-GROUP:OPEN ["a"]>       <INDEXENTRY-LIST:OPEN [0]>         <INDEXENTRY:OPEN [0]>           <KEYWORD-LIST:OPEN [0]>             <KEYWORD:OPEN [0]>  ... 

We use a simple indentation scheme to make the structure of the tags visible. The symbolic tag <LETTER-GROUP:OPEN [“a”]> for example indicates that the tag that can be specified with the command

(markup-letter-group :open "XXX" :group "a" ... ) 

is emitted at this point in the markup process. By incrementally adding markup commands to the index, more and more tags can be defined until the whole markup is defined. This general mechanism should allow everyone understand the markup process. The best is to start with a small index, define the complete markup and afterwards process the whole index. Additionally one can enclose the symbolic tags into an environment that is neutral to the document preparation system, such as a comment. For TeX this could be

(markup-trace :open "%%" :close "~n") 

or a definition in the TeX document like

\def\ignore#1{} 

combined with the command

(markup-trace :open "\ignore{" :close "}") 

<a name=“idp12553152” id=“idp12553152” title=“idp12553152”></a>

This section can be skipped if the reader is not interested in adapting xindy to a new document preparation system.

The raw index is the file that represents the index that is to be processed. Since many different document preparation systems may use different forms of index representations, their output must be transformed in a form readable by xindy. We also could have written an configurable parser performing this task, but usually a tool written with some text processing tools such as perl, sed or awk can achieve the same task as well. Therefore, adapting xindy to a completely different system can mostly be done by writing an appropriate raw index filter.

The format of the raw index interface of xindy is defined as follows:

(indexentry { :key string-list [:print string-list]             | :tkey list-of-layers }             [:attr string]             { :locref string  [:open-range | :close-range]             | :xref string-list } ) 

The pseudo variable string is a sequence of characters surrounded by double quotes, e.g.

"Hi, it's me"  "one"  "a string with two \"double quotes\"" 

are three examples of valid strings. If you need to include a double quote as a literal character, you must quote it itself with a backslash as shown in the third example. A string list is simply a list of strings separated by whitespaces and surrounded by round braces. An example of a string list is

("This" "is" "a" "list" "of" "strings") 

So far about the syntax. The semantics of the different elements are described here.

$ :key: <p>The argument //string list// defines the keyword of the index entry. It must be a list of strings, since the keyword may consist of different layers such as ("heap" "fibonacci").</p> $ :print: <p>The optional print key defines the way the keyword has to be printed in the markup phase.</p> $ :tkey: <p>Another possibility to define the keys of an index entry is with the :tkey keyword argument. It can be used instead of the :key and :print arguments. Instead of specifying separately the key and the corresponding print key, we define the keyword by its layers. Each layer consist of a list of one or two strings. The first string will be interpreted as the main key, whereas the second one will become the print key. If the print key is ommited, the main key is taken instead. So the definition</p> <pre class="programlisting">:tkey (("This") ("is") ("a") ("bang" "BANG !!")) </pre> <p>is equivalent to</p> <pre class="programlisting">:key ("This" "is" "a" "bang") :print ("This" "is" "a" "BANG !!") </pre> $ :locref: <p>The reference an index entry describes can be a location reference or a cross reference. The switch :locref describes a location reference. Its optional arguments are :open-range and :close-range. The string that must be supplied must somehow encode the location reference. It might look like the string “25” representing the page number 25, or “Appendix-I” representing the first appendix numbered in uppercase roman numerals.</p> $ :open-range,:close-range: <p>These are switches that do not take any arguments. They describe the beginning and ending of a range, starting or ending from the location reference that is given by the argument :locref. If they are supplied, the location reference may have influence on the way ranges are build.</p>

• :xref <p>These arguments choose the second alternative. The argument string list of parameter :xref describes where the index entry should point to.</p>
• :attr <p>This parameter may be used to tag a location reference with a certain attribute or it names the class of a cross reference. It may also used to associate different markup for different attributes in the markup phase. If this parameter is omitted or is the empty string, the indexentry is declared to have the attribute default.</p>

Some examples:

(indexentry :key ("airplane") :locref "25" :attr "default") 

defines an index entry with the key airplane' indexed on page 25'. This index entry has the attribute default.

(indexentry :key ("house") :xref("building") :attr "see") 

defines a cross reference with the key house pointing to the term building. This cross reference belongs to the cross reference class see.

(indexentry :key ("house") :xref("building") :open-range) 

is an invalid specification, since :open-range mustn't be used together with cross references.

<a name=“idp12602032” id=“idp12602032” title=“idp12602032”></a>

<a name=“idp12604624” id=“idp12604624” title=“idp12604624”></a>

The following command line options are accepted:

xindy  [-h] [-t] [-v] [-l logfile] [-o outfile]        [-L n] [-f filterprog]        indexstyle raw-index 

The argument indexstyle names a file, containing the index style description. The argument raw-index names a file, containing the raw index. Both arguments are mandatory.

• -h <p>Gives a short summary of all command line options.</p>
• -l <p>Writes helpful information into the specified logfile. For example, the keyword mappings are written into this file, so one can check if the intended mappings were actually performed this way.</p>
• -o <p>Explicitly defines the name of the output file. If not given, the name of the raw-index is used with its extension changed to .ind (or added, if it had no extension at all).</p>
• -t <p>Enters tracing mode of the symbolic markup tags. The format of the emitted tags can be defined with the command markup-trace.</p>
• -L <p>Set the xindy logging-level to n.</p>
• -f <p>Run filterprog on raw-index before reading. The program must act as a filter reading from stdin and writing to stdout. The most obvious use of this option in conjunction with TeX is to run -f tex2xindy on the index file prior to reading the entries into xindy.</p>
• -v <p>Shows the version number of xindy.</p>

Errors and warnings are reported to stdout and additionally to the logfile if -l was specified.

<a name=“idp12632752” id=“idp12632752” title=“idp12632752”></a>

The system uses the concept of a search path for finding the index style files and modules. The searchpath can be set with the environment variable XINDY_SEARCHPATH which must contain a list of colon-separated directories. If it ends with a colon, the built-in searchpath is added to the entire searchpath. See the command <a href=“#xindy-command-list-processing-searchpath” title=“1.1.12 searchpath”>searchpath</a> for further details.

Table of Contents $ Index:

<a name=“idp12640688” id=“idp12640688” title=“idp12640688”></a>

• PDF <p>A PDF file is no longer supported.</p>
• Texinfo <p>Currently we don't know any working solution to convert DocBook XML to Texinfo (at least not for a complex document). Anyone who wants to work on this issue is highly welcome. A starting point could be the docbook2X project at <a target=“_top” href=“http://docbook2x.sourceforge.net” class=“ulink”>http://docbook2x.sourceforge.net</a>.</p>
• vim-help <p>Quite a few poeple are asking for a version in vim-help format. <a target=“_top” href=“<mailto:srinath@eecs.berkeley.edu>” class=“ulink”>Srinath Avadhanula</a> has already done some work on this.</p>

<a name=“idp12651216” id=“idp12651216” title=“idp12651216”></a>

The source format of this document is <a target=“_top” href=“http://www.oasis-open.org/committees/docbook/”>DocBook XML (V4.3)</a>.

The various output formats were generated using:

• <a target=“_top” href=“http://xmlsoft.org/XSLT/” class=“ulink”>xsltproc (libxml2-2.6.26/libxslt-1.1.26)</a> as XSLT processor
• <a target=“_top” href=“http://sourceforge.net/projects/docbook” class=“ulink”>DocBook XSL Stylesheets (V1.77.1)</a> for HTML and Epub

You'll always find the newest version of this document at <a target=“_top” href=“http://www.miwie.org/tex-refs/”>http://www.miwie.org/tex-refs/</a>.

• V0.4.0 12-12-02 <p> <ul class=“itemizedlist”> <li class=“listitem”>Minor changes for Epub output</li> <li class=“listitem”>Added missing IDs on some sections and tables</li> </ul> </p>
• V0.3.9 05-05-14 <p> <ul class=“itemizedlist”> <li class=“listitem”>Consistent naming scheme of IDs to ease the use of this reference for other projects</li> <li class=“listitem”>Added new section <a href=“#float” title=“3.3 float” class=“link”>float</a> in chapter <a href=“#latex” title=“2 LaTeX” class=“link”>LaTeX</a></li> </ul> </p>
• V0.3.8 04-10-28 <p> <ul class=“itemizedlist”> <li class=“listitem”>Minor changes in <a href=“#page-styles” title=“2.3.15 Page Styles” class=“link”>\maketitle</a></li> </ul> </p>
• V0.3.7 04-08-26 <p> <ul class=“itemizedlist”> <li class=“listitem”>Corrected typos and markup errors in chapter <a href=“#bibtex” title=“Chapter 5. BibTeX” class=“link”>BibTeX</a></li> <li class=“listitem”>Switched to DocBook XML V4.3</li> <li class=“listitem”>Added new section <a href=“#opt-latex” title=“2.1 Options” class=“link”>Options</a> in chapter <a href=“#latex” title=“2 LaTeX” class=“link”>LaTeX</a></li> </ul> </p>
• V0.3.6 04-06-21 <p> <ul class=“itemizedlist”> <li class=“listitem”>Added a note in chapter <a href=“#latex” title=“2 LaTeX” class=“link”>LaTeX</a> with the copyright and permission notice of the original file latex2.texi</li> <li class=“listitem”>Corrected typos and added missing hyperlinks in chapter <a href=“#xindy” title=“Chapter 7. xindy” class=“link”>xindy</a></li> <li class=“listitem”>PDF file optimized/linearized and some finetuning</li> </ul> </p>
• V0.3.5 04-05-01 <p> <ul class=“itemizedlist”> <li class=“listitem”>Added content to chapters <a href=“#metapost” title=“Chapter 4. MetaPost” class=“link”>MetaPost</a> and <a href=“#pdftex” title=“Chapter 2. pdfTeX” class=“link”>pdfTeX</a></li> <li class=“listitem”>Enhanced index for chapter <a href=“#metapost” title=“Chapter 4. MetaPost” class=“link”>Make-Index</a></li> </ul> </p>
• V0.3.4 04-04-24 <p> <ul class=“itemizedlist”> <li class=“listitem”>Version control system changed from CVS to SVN</li> <li class=“listitem”>Added missing entries to chapter <a href=“#makeindex” title=“Chapter 6. Make-Index” class=“link”>Make-Index</a></li> </ul> </p>
• V0.3.3 04-01-26 <p> <ul class=“itemizedlist”> <li class=“listitem”>Corrected again section <a href=“#makeindex-output-style-specs” title=“2.2 Output Style Specifiers” class=“link”>Output Style Specifiers</a> and <a href=“#makeindex-style” title=“2.1 Input Style Specifiers” class=“link”>Input Style Specifiers</a> of chapter <a href=“#makeindex” title=“Chapter 6. Make-Index” class=“link”>Make-Index</a></li> <li class=“listitem”>Corrected some symbols in the index</li> </ul> </p>
• V0.3.2 04-01-16 <p> <ul class=“itemizedlist”> <li class=“listitem”>Corrected sections <a href=“#makeindex-output-style-specs” title=“2.2 Output Style Specifiers” class=“link”>Output Style Specifiers</a> and <a href=“#makeindex-style” title=“2.1 Input Style Specifiers” class=“link”>Input Style Specifiers</a> of chapter <a href=“#makeindex” title=“Chapter 6. Make-Index” class=“link”>Make-Index</a></li> <li class=“listitem”>Enhanced index in PDF</li> </ul> </p>
• V0.3.1 04-01-06 <p> <ul class=“itemizedlist”> <li class=“listitem”>More work on PDF</li> <li class=“listitem”>Modularized XSL stylesheet files</li> <li class=“listitem”>Corrected some typos</li> </ul> </p>
• V0.3.0 03-12-25 <p> <ul class=“itemizedlist”> <li class=“listitem”>Changed document root to book </li> <li class=“listitem”>More work on PDF version</li> <li class=“listitem”>Using new XSL stylesheets V1.64.1</li> <li class=“listitem”>Minor fixes</li> </ul> </p>
• V0.2.6 03-10-27 <p> <ul class=“itemizedlist”> <li class=“listitem”>Rearranged appendix</li> <li class=“listitem”>Work on PDF version</li> </ul> </p>
• V0.2.5 03-10-17 <p> <ul class=“itemizedlist”> <li class=“listitem”>Added contents of <a href=“#gfdl” title=“4 GNU Free Documentation License” class=“link”>GNU FDL</a> in appendix</li> <li class=“listitem”>Using new XSL stylesheets V1.62.4</li> <li class=“listitem”>Switched to <a target=“_top” href=“http://xmlsoft.org/XSLT/” class=“ulink”>xsltproc</a> as XSLT-processor</li> <li class=“listitem”>Reedited some deeply nested sections</li> <li class=“listitem”>Changed colors in CSS</li> </ul> </p>
• V0.2.4 03-09-06 <p> <ul class=“itemizedlist”> <li class=“listitem”>Added subsection <a href=“#dcolumn” title=“3.2 dcolumn” class=“link”>dcolumn</a></li> <li class=“listitem”>Subsection <a href=“#fontenc” title=“3.4 fontenc” class=“link”>fontenc</a> translated into english</li> <li class=“listitem”>Corrected typo in <a href=“#cmd-sbox” title=“2.3.17. \sbox” class=“link”>\sbox</a></li> </ul> </p>
• V0.2.3 03-04-12 <p> <ul class=“itemizedlist”> <li class=“listitem”>Provide PDF output using <a target=“_top” href=“http://www.pragma-ade.com/” class=“ulink”>ConTeXt</a> and <a target=“_top” href=“http://www.hobby.nl/~scaprea/context/index.html” class=“ulink”>DocBook In ConTeXt</a> (still experimental)</li> <li class=“listitem”>Reedited (beautified) sections LaTeX / Commands / <a href=“#counters” title=“2.3.1 Counters” class=“link”>Counters</a> | <a href=“#cross-references” title=“2.3.2 Cross References” class=“link”>Cross References</a> | <a href=“#definitions” title=“2.3.3 Definitions” class=“link”>Definitions</a> | <a href=“#layout” title=“2.3.5 Layout” class=“link”>Layout</a> | <a href=“#env-latex” title=“2.3.6 Environments” class=“link”>Environments</a> | <a href=“#footnotes” title=“2.3.7 Footnotes” class=“link”>Footnotes</a></li> </ul> </p>
• V0.2.2 03-01-26 <p> <ul class=“itemizedlist”> <li class=“listitem”>Added bzip2 compressed version of source and outfiles tarball</li> <li class=“listitem”>Using new XSL stylesheets V1.60.1</li> <li class=“listitem”>Eliminated more spurious  characters in HTML output</li> </ul> </p>
• V0.2.1 03-01-18 <p> <ul class=“itemizedlist”> <li class=“listitem”>Using new XSL stylesheets V1.59.2</li> <li class=“listitem”>Eliminated spurious  characters</li> </ul> </p>
• V0.2.0 03-01-11 <p> <ul class=“itemizedlist”> <li class=“listitem”>Using new XSL stylesheets V1.58.1</li> <li class=“listitem”>Minor changes to CSS file</li> <li class=“listitem”>License changed to <a target=“_top” href=“http://www.gnu.org/licenses/fdl.html” class=“ulink”>GNU Free Documentation License</a></li> <li class=“listitem”>Added subsection <a href=“#pstricks-commands” title=“4.2.2 Commands and Parameters” class=“link”>Commands and Parameters</a> to section <a href=“#pstricks” title=“4.2 PSTricks” class=“link”>PSTricks</a></li> <li class=“listitem”>Reworked <a href=“#inputenc” title=“3.8 inputenc” class=“link”>inputenc</a> section</li> </ul> </p>
• V0.1.3 02-10-17 <p> <ul class=“itemizedlist”> <li class=“listitem”>Started rework of <a href=“#komascript” title=“3.9 KOMA-Script” class=“link”>KOMA-Script</a> section</li> <li class=“listitem”>Added subsection <a href=“#pstricks-add-packages” title=“4.2.3 List of Additional PSTricks Packages” class=“link”>Additional PSTricks Packages</a></li> <li class=“listitem”>Using new XSL stylesheets V1.56.1</li> </ul> </p>
• V0.1.2 02-10-01 <p> <ul class=“itemizedlist”> <li class=“listitem”>Reworked <a href=“#hyperref” title=“3.7 hyperref” class=“link”>hyperref</a> section</li> </ul> </p>
• V0.1.1 02-09-19 <p> <ul class=“itemizedlist”> <li class=“listitem”>Added template sections for <a href=“#pictex” title=“4.1 PiCTeX (tbd.)” class=“link”>PiCTeX</a> and <a href=“#texinfo” title=“7 Texinfo (tbd.)” class=“link”>Texinfo</a></li> <li class=“listitem”>Added subsection <a href=“#release-news” title=“3 Release News” class=“link”>Release News</a> in appendix <a href=“#about” title=“2 About this Document” class=“link”>About this Document</a></li> <li class=“listitem”>Using new XSL stylesheets V1.55.0</li> <li class=“listitem”>Added missing CSS file to outfiles tarball</li> <li class=“listitem”>Corrected wrong FPI</li> </ul> </p>
• V0.1.0 02-08-20 <p> <ul class=“itemizedlist”> <li class=“listitem”>Eliminated trailing '.' in numbered sections</li> <li class=“listitem”>Minor markup errors corrected</li> <li class=“listitem”>Reworked CSS file</li> </ul> </p>
• V0.0.5 02-08-10 <p> <ul class=“itemizedlist”> <li class=“listitem”>Switched to DocBook XML 4.2</li> <li class=“listitem”>Sections 'Bibindex' and 'xindy' completed</li> </ul> </p>
• V0.0.4 02-07-25 <p> <ul class=“itemizedlist”> <li class=“listitem”>Section 'Makeindex' completed</li> </ul> </p>
• V0.0.3 02-07-13 <p> <ul class=“itemizedlist”> <li class=“listitem”>New XSL stylesheets solve bug in creating index (no other changes)</li> </ul> </p>
• V0.0.2 02-07-05 <p> <ul class=“itemizedlist”> <li class=“listitem”>New (template) sections 'fontinst', 'Bibtex', 'Makeindex', and 'xindy'</li> <li class=“listitem”>New section 'Special Symbols'</li> <li class=“listitem”>Added information for 'german' package</li> <li class=“listitem”>Registered as a new project (tex-refs) on freshmeat.net</li> </ul> </p>
• V0.0.1 02-06-21 <p> <ul class=“itemizedlist”> <li class=“listitem”>First official announcement</li> </ul> </p>

<pre> Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document “free” in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”. Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 3. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. H. Include an unaltered copy of this License. I. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. M. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version. N. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section. O. Preserve any Warranty Disclaimers. If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties–for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. 5. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements”. 6. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. 8. TRANSLATION Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. ADDENDUM: How to use this License for your documents To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: Copyright © YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with…Texts.” line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. </pre>

$ _, Math Formulae:

$ Author, for titlepage, Page Styles:

$ BibTeX, [[#bibtex|BibTeX]]: $ bib files, bib files: $ Field Types, [[#bibtex-field-types|Field Types]]: $ bst files, bst files: $ UNSRT.BST, [[#bibtex-bst-unsrt|UNSRT.BST]]: $ Entry Types: $ unpublished entry, [[#bibtex-entry-types-unpublished|unpublished entry]]: $ Field Text: $ Titles, [[#bibtex-field-text-titles|Titles]]: $ Field Types: $ year field, [[#bibtex-field-types-year|year field]]: $ using, Environments: $ Boxes, Spaces & Boxes:

$ Cross referencing using section number, Cross References:

$ Document Classes, Document Classes:

$ exponent, Math Formulae:

$ float, [[#float|float]]: $ \restylefloat, float: $ Formulae, maths, Math Formulae:

$ german, [[#german|german]]: $ \grqq, german: $ Greek Letters, Special Symbols:

$ hyperref, [[#hyperref|hyperref]]: $ commands: $ \texorpdfstring, [[#hyperref-commands|Commands]]: $ options: $ vtex, Options:

$ Hyphenation, forcing, Line & Page Breaking:

$ itemize, Environments:

$ Justification, ragged right, Environments:

$ KOMA-Script, [[#komascript|KOMA-Script]]: $ scraddr, Address Files with scraddr: $ \Telephone{}, [[#komascript-scraddr|Address Files with scraddr]]: $ scrlttr2, Letter Class scrlttr2: $ \usekomavar, Letter Class scrlttr2:

$ LaTeX: $ Options, Options: $ -version, -version:

$ lrbox, Spaces & Boxes:

$ Make-Index, [[#makeindex|Make-Index]]: $ Input Style Specifiers, Input Style Specifiers: $ range_open, [[#makeindex-range-open|range_open <char>]]: $ Options, Options: $ -t log, [[#makeindex-option-t-log|-t log]]: $ Output Style Specifiers, Output Style Specifiers: $ symhead_positive, [[#makeindex-output-symhead-positive|symhead_positive <string>]]: $ Style File, Style File: $ MetaPost, [[#metapost|MetaPost]]: $ Environment, Environment: $ TROFF, [[#metapost-environment|Environment]]: $ Options, Options: $ -T, -T:

$ Multicolumn text, Layout:

$ Notes in the margin, Margin Notes:

$ Operators: $ Relational, Special Symbols: $ Overview of LaTeX, Overview of LaTeX and Local Guide:

$ Packages: $ varioref, varioref: $ pdfTeX, [[#pdftex|pdfTeX]]: $ Environment, Environment: $ TEXPOOL, [[#pdftex-environment|Environment]]: $ Options, Options: $ [-no]-maketex=FMT, opt-latex-no-maketex][[-no]-maketex=FMT:

$ People: $ Voss, Herbert, Credits: $ PSTricks, [[#pstricks|PSTricks]]: $ commands: $ \uput, [[#placing|Placing and rotating whatever]]: $ parameter: $ yunit, Dimensions, coordinates and angles:

$ Quoted text, displaying, Environments:

$ Right-justifying text, environment for, Environments:

• Symbols, Math Formulae $ Special, Special Symbols:

$ Typefaces, Typefaces:

$ Using BibTeX, Environments:

$ Vertical space, inserting, Spaces & Boxes:

• xindy, xindy $ Command List, [[#xindy-command-list|Command List]]: $ Raw Index Interface, Raw Index Interface: $ Invoking, [[#xindy-invoking|Invoking xindy]]: $ Search Path, Search Path: $ Processing Commands, [[#xindy-command-list-processing|Processing Commands]]: $ use-rule-set, use-rule-set: