PREPARING ARTICLES

WITH LATEX

INSTRUCTIONS TO AUTHORS
FOR PREPARING COMPUSCRIPTS

ELSEVIER
SCIENCE
PUBLISHERS B.V.
PREPARING ARTICLES
WITH LATEX

INSTRUCTIONS TO AUTHORS
FOR PREPARING COMPUSCRIPTS

ELSEVIER SCIENCE PUBLISHERS B.V.

 This publication was typeset using LATEX
TEX is a trademark of the American Mathematical Society
Copyright
c 1994 by Elsevier Science Publishers B.V.
All rights reserved
Contents

1 Introduction 5
2 Preparing a compuscript 6
2.1 Title and author 6
2.2 Simple text 7
2.3 Sectional units 8
2.4 Lists 8
2.5 Cross-references 8
2.6 Mathematical formulas 9
2.7 Theorems and denitions 11
2.8 Proofs 12
2.9 Literature references 12
2.10 Tables and gures 13
2.11 Programs and algorithms 13
2.12 Large articles 14
2.13 Private denitions 14
2.14 Layout 14
2.15 Deviations from standard document styles 15
2.16 Technical information, and versions of LATEX 15
3 Submitting a compuscript 17
3.1 Sending via electronic mail 17
3.2 Submission on diskette 18
4 Getting help 18
A Examples 20

3
4
1. Introduction

Nowadays, it is becoming more and more customary for authors to type their
manuscripts using some kind of electronic device and composing the result
with some text-processing system. Systems that are quite popular are TEX
and LATEX. In order to assist authors in preparing their papers for articles
published by Elsevier Science Publishers in such a way that their les can
be used to print the article from, we have developed LATEX document styles
for our journals. The following is a description of these document styles. For
best understanding, authors should be reasonably familiar with the LATEX
manual written by Leslie Lamport [1].
In order to enable the publisher to bring the article into the uniform layout
and style of the journal in which it will appear, authors are kindly requested
to follow the suggestions mentioned below. This has the advantage of keep-
ing editorial changes to a minimum, which will considerably speed up the
publication process.
Upon receipt of the compuscript, it is given to a technical editor, who prints
the compuscript on paper, reads it carefully and makes changes when nec-
essary. If sending proofs is part of the normal procedure for the particular
journal, a proof is sent to the author. If the author nds something in the
proof that should be changed, he/she should indicate this clearly in the mar-
gin, so that the technical editor can apply these corrections before making
the paper ready for publication.
For all journals that accept author-prepared LATEX articles we have docu-
ment styles. All these document styles, which are used for the actual pro-
duction of the journals, have the same commands. Furthermore, there is a
separate document style elsart that is fully compatible with the produc-
tion document styles. Authors can use this document style elsart to obtain
preprint output. When the article is prepared for publication, this document
style is replaced by a document style for the journal in which the article is
published.
This documentation contains a users guide, guidelines for submitting the
article for publication and information on where to get help in case problems
occur.

5
6

2. Preparing a compuscript

The documentstyle elsart, with which the article can be prepared and preprint
output can be obtained, is compatible with the standard document styles of
LATEX, except for the specication of the front matter, i.e. the title, author,
addresses and abstract.
In the following sections we will describe the dierences between normal
LATEX usage and the usage of the Elsevier document styles. Also, we will
summarize some of the important aspects of coding a compuscript with
LATEX.

2.1. Title and author

In the Elsevier document styles the commands \title, \author etc., have
been replaced by a more general frontmatter environment. Since the stan-
dard LATEX document styles do not dierentiate between author name and
address, extra mark-up instructions have been added to the Elsevier docu-
ment styles. Within the frontmatter environment, you should specify the
title, names and addresses of the authors, followed by the abstract and
in some cases a keyword abstract. 1 Title, author, collaboration, address,
abstract and keyword abstract should be indicated with the instructions
\title, \author, \collab and \address, and the abstract and keyword
environments, respectively. The instruction \maketitle has become obso-
lete in the Elsevier document style.
There are two types of authoraddress lists. These are illustrated by Exam-
ples 1 and 2 in Appendix A. The rst type of authoraddress list consists
of one or more groups of authors followed by an address (aliation). In this
type of list there is an implicit link between authors and addresses. The
second type of authoraddress list consists of one list of all authors, followed
by one list of all addresses (aliations), and with explicit links between
authors and addresses. The links are written as optional arguments to the
\author, \collab and \address commands and are usually formatted as
footnote-like symbols.
The \thanks command can be used to produce notes that are added to
the title, author or address. In the Elsevier document styles this command
should be written inside the frontmatter environment, but outside the
argument of \title, \author, \collab and \address; see also Examples 1
and 2. The modied \thanks command has an optional argument that can
be used to attach a label to a note:
\thanks[CAICYT]{Partially supported by CAICYT, Spain.}
1
Optional, not present in some journals.
 7

Inside the argument of \title, \author, \collab and \address one can
refer to this note with the command \thanksref, which takes the label of
a \thanks command as argument:
\author{L.A. Fernandez\thanksref{CAICYT}}
The command \and has its usual meaning.
In some journals, authors of experimental papers have to add keyword ab-
stracts. These abstracts are specied by using an equivalent of the abstract
environment: the keyword environment. The following input gives an exam-
ple of the use of this environment.
\begin{keyword}
Radioactivity.
($\beta^+$, EC) [from Pt(p, $x$n)Au or ...
\end{keyword}
might generate this output
Keywords: Radioactivity. ( + , EC) [from Pt(p, xn)Au or ...

The proper position of the keyword environment is inside the frontmatter

environment, before or after the abstract environment.

2.2. Simple text

Text should be typed as usual. Hyphens are typed as -, number ranges are
typed as --. The en dash -- is also used, e.g., in Theorem of Cantor
SchroderBernstein.
Emphasized text is obtained with the command \em. In most cases this will
result in italic text representing emphasis. Italic text should be terminated
by an italic correction, i.e.
{\em heavy quarks\/}
unless the text in italics is immediately followed by a full stop (.) or comma
(,).
Extra or exceptional hyphenations are added to TEXs list of abbreviated
words by means of the command \hyphenation, which should be placed in
the preamble of the document. An example:
\hyphenation{caus-al min-i-mi-za-tion pro-ven}
Introduce macros (with care, see 2.13) for notations and abbreviations that
occur more than once, for example e.g. and i.e.. This facilitates changes in
notation. If you introduce macros for abbreviations, these are often param-
eterless macros, so you should be aware of TEXs behaviour with regard to
spaces following a parameterless macro. An instruction without parameters
should be dened and used as
8

\newcommand{\ie}{i.e.}
...
... extra particles, ... extra particles, i.e. parti-
\ie{} particles ... cles ...

Alternatives to \ie{} are \ie\3 and {\ie}. The \3 after \ie produces a
space, whereas \ie3particles will result in i.e.particles [1, p. 16].
Putting a space in the denition of \ie is not the right solution, since it can
result in a space before a punctuation mark, e.g.
\newcommand{\ie}{i.e. }
...
... extra particles, ... extra particles, i.e. , parti-
\ie, particles ... cles ...

2.3. Sectional units

Sectional units are obtained in the usual way, i.e. with the LATEX in-
structions \section, \subsection, \subsubsection, \paragraph and
\subparagraph.
A new environment ack see also Section 2.7 has been added to produce
an Acknowledgements section, which should be placed at the end of the
article, just before the references.

2.4. Lists
Lists of items are produced with the usual itemize and enumerate envi-
ronments. The itemize environment is used for unnumbered lists and the
enumerate environment for numbered lists. Even if the layout of these lists
is not precisely what you would like, we prefer lists to be coded this way
instead of by hand. This enables the document style for the specic journal
to determine the list layout.

2.5. Cross-references
Use \label and \ref for cross-references to equations, gures, tables, sec-
tions, subsections, etc., instead of plain numbers. For references to the lit-
erature list at the end of the article see Section 2.9.
Every numbered part to which one wants to refer, should be labelled with
the instruction \label. For example:
\begin{equation}
e^{i\pi} + 1 = 0 \label{eq:euler}
 9

\end{equation}
With the instruction \ref one can refer to a numbered part that has been
labelled:
..., see also eq. (\ref{eq:euler})
The \label instruction should be typed
immediately after (or one line below), but not inside the argument of
a number-generating instruction such as \section or \caption, e.g.:

\caption{Cross section} \label{fig:crosssec}

roughly in the position where the number appears, in environments
such as equation, e.g.:
\begin{equation}
e^{i\pi} + 1 = 0 \label{eq:euler}
\end{equation}

2.6. Mathematical formulas

For in-line formulas use \( ... \) or $ ... $. Avoid built-up construc-
tions, for example fractions and matrices, in in-line formulas.
For unnumbered displayed one-line formulas use the displaymath environ-
ment or the shorthand notation \[ ... \]. For numbered displayed one-
line formulas use the equation environment. Do not use $$ ... $$, but
only the LATEX environments, so that the document style determines the
formula layout. For example, the input for:


a
P+ (V b) = RT, (1)
V2

is:
\begin{equation}
\left( P + \frac{a}{V^2} \right) (V-b) = RT ,
\end{equation}
For displayed multi-line formulas use the eqnarray environment. For ex-
ample,
\begin{eqnarray}
f(x) & = & \sum_{n=1}^{\infty} a_n\cos(nx) +
b_n\sin(nx) \nonumber \\
& = & \sum_{n=-\infty}^{\infty}
c_n\exp(-\mathrm{i} xn)\, .
\end{eqnarray}
produces:
10


f (x) = an cos(nx) + bn sin(nx)
n=1

= cn exp(ixn) . (2)
n=

Angle brackets, which are used in, e.g., the inner product notation, the bra-
ket notation (physics), and in BNF (computer science), are obtained with
\langle and \rangle:
\langle x, y \rangle = 0 x, y = 0
\langle p|A|p \rangle = 0 p|A|p = 0
\langle \mbox{sign} \rangle
\longrightarrow + | - sign +|

Superscripts and subscripts that are words or abbreviations, as in low ,

should be typed as roman letters; this is done as follows:
\( \sigma_{\mathrm{low}} \) low

instead of
\( \sigma_{low} \) low

The most common symbols that are conventionally typeset in a roman type-
face, for example units, are listed below. For some of these, see also Table 1
on page 16.
The Euler number, for example, ex .
i when used as imaginary unit, e.g. a+bi or ei , etc. The Euler equation,
which was used as an example earlier, can therefore also be typed as
\begin{equation}
\mathrm{e}^{\mathrm{i}\pi} + 1 = 0
\label{eq:euler}
\end{equation}
Geometric functions, e.g. exp, sin, cos, tan, etc. LATEX provides macros
\sin, \cos, \tan for these and similar functions. These macros also
give the proper spacing in mathematical formulas.
The dierential operators, e.g. dx, and the operators Im and Re for
the imaginary and real parts of complex numbers, respectively. 2
Groups, for example SU(2) and SU(3).
Labels for atomic orbitals and atomic shells. Example: 4s, 4p, K, L.
2
The normal shape of Greek capital letters is upright. The slanted shape of, e.g., the
letter is obtained with \varDelta, as in AMS-LATEX: .
 11

Greek letters when used as a unit, e.g. for ohm.

Units in general. Example: cm, A, and b for barn.
Subscripts and superscripts that are used as an abbreviation. Exam-
ples: TC (Curie temperature), Tc (critical temperature), and C3v (iden-
tier of space group)
Operator or function names, or their abbreviatons, e.g. Ker, Im, Hom,
Re, etc.

Of the advanced features of TEX we mention the possibility to dene extra

symbols. Extra relation symbols can be dened as in the following example
(see also Section 2.13):

\newcommand{\leL}{\mathrel{\le_{\mathrm{L}}}}
\( a \leL b \)

produces the following result:

a L b

Extra log-like functions or operators can be dened as follows:

\newcommand{\re}{\mathop{\mathrm{Re}}}
\newcommand{\im}{\mathop{\mathrm{Im}}}
\( z + \bar{z} = 2 \re z, \quad
z - \bar{z} = 2 \mathrm {i} \im z \)

produces the following result:

z + z = 2 Re z, z z = 2i Im z

For more information on TEXs advanced mathematical features we refer

to chapters 1618 of the TEX book [3]. It is also possible to use the AMS-
LATEX package [4], which can be obtained from the AMS, from various TEX
archives, or from us (see Section 4).

2.7. Theorems and denitions

LATEX provides \newtheorem to create theorem environments. The Elsevier

document styles contain a set of pre-dened environments for theorems,
denitions, proofs, remarks and the like.

The following environments are dened (analogous to the example given in

the AMS-LATEX users guide [4, 31.5]):
12

Environment name Heading Environment name Heading

thm Theorem exmp Example
lem Lemma prob Problem
cor Corollary rem Remark
prop Proposition note Note
crit Criterion claim Claim
alg Algorithm summ Summary
defn Denition case Case
conj Conjecture ack Acknowledgement
To add theorem-type environments to an article, use the \newtheorem com-
mand see the LATEX user manual [1].

2.8. Proofs
The Elsevier document styles also provide a predened pf environment, and
a starred form pf*, for proofs. The pf environment produces the heading
Proof with appropriate spacing and punctuation. A Q.E.D. symbol,
,
can be appended at the end of a proof with the command \qed.
The starred form, pf*, of the proof environment takes an argument in curly
braces, which allows you to substitute a dierent name for the standard
Proof. If you want to substitute, say, Proof (suciency), then write
\begin{pf*}{Proof (sufficiency)}

2.9. Literature references

The list of literature references can be produced in two ways, by using
the environment thebibliography, or
BibTEX
Example 3 shows a bibliography produced with the thebibliography envi-
ronment.
If the references are collected in one, not too large, BibTEX le (.bib), it
would be appreciated if you would let us have this le as well. In a future
release we will include a BibTEX bibliography style in the author package
as well.
The instruction \cite should be used to obtain references to this list, i.e.
citations. The Elsevier document styles take care of the actual formatting
of the citation, e.g. as roman numbers between brackets, or as a superscript
number.
For multiple citations do not use \cite{Knuth}\cite{Lamport}, but use
\cite{Knuth,Lamport} instead. Consecutive numbers in a citation appear
as a range, i.e. [1,2,3] is automatically converted by the document style to
 13

[13]. For a note added to a citation use \cite[note]{key}, for example:

\cite[p. 217]{Knuth}.

2.10. Tables and gures

Put the tables and gures in the text with the table and figure environ-
ments, and position them near the rst reference of the table or gure in
the text. Do not put them at the end of the article.
A gure is obtained with
\begin{figure}
\vspace{30mm} % height of figure
\caption{ ... text below figure ... }
\end{figure}
Instead of the instruction \vspace{30mm} for the white space to be reserved
for a separate gure, you can insert diagrams. Simple diagrams can be drawn
with the picture environment; Feynman diagrams with the feynman pack-
age. Originals of separate gures should be sent via ordinary mail; sometimes
good-quality prints are also acceptable. These should be submitted in the
usual way. We can also process gures in PostScript form, but not in any
other electronic form.
A table is obtained with
\begin{table}
\caption{ ... text above table ... }
\begin{tabular}{ ... }
...
\end{tabular}
\end{table}
Please avoid long caption texts in gures and tables and vertical rules.

2.11. Programs and algorithms

Fragments of computer programs and descriptions of algorithms should be
prepared as if they were normal text. Use the same fonts for keywords,
variables, etc., as in the text; do not use small typeface sizes to make program
fragments and algorithms t within the margins set by the document style.
An example, with only the tabbing environment and one new denition:
\newcommand{\keyw}[1]{{\bf #1}}
\begin{tabbing}
\quad \=\quad \=\quad \kill
\keyw{for} each $x$ \keyw{do} \\
\> \keyw{if} extension$(p, x)$ \\
14

\> \> \keyw{then} $E:=E\cup\{x\}$\\

\keyw{return} $E$
\end{tabbing}
This produces the following:
for each x do
if extension(p, x)
then E := E {x}
return E

2.12. Large articles

A compuscript can be submitted as one or more les. If there is more than
one le, one of them should be a root le. The root le inputs the les that
constitute the entire article by means of \input or \include.

2.13. Private denitions

Private denitions should be placed in the preamble of the article, and not
at any other place in the document. Such private denitions, i.e. denitions
made using the commands \newcommand, \renewcommand, \newenvironment
or \renewenvironment, should be used with great care.
Sensible, restricted usage of private denitions is encouraged. Large macro
packages should be avoided. Denitions that are not used in the article
should be omitted. Do not change existing environments, commands and
other standard parts of LATEX. Denitions that are merely abbreviations for
keystrokes, such as \bt for \begin{theorem}, should be avoided (use the
facilities of your editor program to minimize keystrokes). A short description
of the various denitions, in the form of TEX comment lines, is appreciated.
Deviation from these rules may cause inaccuracies in the article or a delay in
publication, or may even result in the LATEX le being discarded altogether
so that the article is typeset conventionally.

2.14. Layout
The document style elsart, which is part of this package, can be used to
obtain preprint output. When the article is prepared for publication, this
document style is replaced by a document style for the journal in which the
article will be published.
The elsart style is compatible with all Elseviers journal styles, so that
preparation of the article for nal publication is straightforward.
In order to facilitate our processing of your article, please give easily identi-
able structure to the various parts of the text by making use of the usual
 15

LATEX commands or by your own commands dened in the preamble, rather

than by using explicit layout commands, such as \hspace, \vspace, \large,
\centering, etc. Also, do not redene the page-layout parameters.

2.15. Deviations from standard document styles

The document style elsart deviates from the standard document styles in
the following areas
specication of the front matter
extra commands
The document style denes several extra instructions. These are summarized
in Table 1.
The document style redenes the standard command \vec: it formats vector
symbols according to the layout of the journal, often italic boldface letters.
The command \pol produces the standard vector notation, i.e. with a small
right arrow on top of the argument.

2.16. Technical information, and versions of LATEX

In June 1994 a new version of LATEX was released, LATEX 2 ; Elsevier will
continue to support users of the old LATEX209 for the foreseeable future,
but would like authors to switch to LATEX 2 as soon as practical. It is
documented in the second edition of Lamports book [?], and described in
great detail in [2].
Our preprint style is available in two forms, as eslart.sty and eslart.cls.
The document style elsart.sty, with the corresponding elsart12.sty has
been designed for LATEX 2.09 (version of January 1992 or later). The doc-
ument class eslart.cls (no extra size le) has been designed for LATEX2e
(versions from June 1994).
It is also possible to use the document style or class in combination with
the AMS-LATEX package [4], in its LATEX209 or LATEX 2 version, and we
recommend this to authors who have more complex mathematical needs.
16

Table 1: Extra commands.

Front matter commands
\title{string} title of article
\author[key]{string} name of one author
\collab[key]{string} name of collaboration (group of authors)
\address[key]{string} address of author or collaboration
\thanks[key]{string} note to one of the above elements
\thanksref{key} reference to \thanks note
Case fractions
1
\half small 2
3
\threehalf small 2
1
\quart small 4
Theorem environments
see Sections 2.7 and 2.8
Extra mathematical operators
\d dierential d
\e base of natural logarithm
other operators see below
Blackboard bold symbols (AMSFonts version 2.1 must be present)
\Nset N, set of positive integer numbers
\Zset Z, set of integer numbers
\Qset Q, set of rational numbers
\Rset R, set of real numbers
\Cset C, set of complex numbers
\Hset H, set of quaternions
other letters use \Bbb{...} from amsfonts
Extra notations for physics
\nuc nuclides, \nuc{183}{Ir} produces 183Ir
\vec boldface vector
\pol polarization (right arrow on top of argument)
\FMslash small slash through letter (Feynman notation)
\FMSlash large slash through letter (Feynman notation)
 17

3. Submitting a compuscript

The guidelines for submission of compuscripts can be found on the inside

cover pages of the journal to which you would like to submit the article. If
submission via electronic mail is allowed, you will nd the network address
to which you can send your compuscript in those guidelines as well.
For passing a compuscript to the publisher for nal processing we give the
following guidelines.

3.1. Sending via electronic mail

Short articles (say, less than 30 pages) should be prepared as one LATEX le
and be sent via electronic mail as one message. Large les may be split into
several parts, which are input in the root le.
Send all les in separate messages; do not concatenate them together
in one large message.
Identify each part in the subject line as part m of n in addition to the
identication described above; note that without proper identication
the order of the parts will be lost in the mail.
If the article consists of more than ve les, we prefer submission on
diskette (see below) or via FTP. Please contact the publisher for more
information on the latter.
If you send your compuscript via electronic mail, prepare the le such that
no line is longer than 72 characters. This also prevents loss of information
in various networks. Include
1. name of sender,
2. journal identication and article number, and
3. name of the le
in the subject line of your electronic-mail message.
Also, include an ASCII table at the start of every le you send via electronic
mail. An ASCII table, lename ascii.tab, is part of the package authors
can obtain from the publisher. It contains the following:
% Upper-case A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
% Lower-case a b c d e f g h i j k l m n o p q r s t u v w x y z
% Digits 0 1 2 3 4 5 6 7 8 9
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
18

% At @ Left bracket [ Backslash \

% Right bracket ] Circumflex ^ Underscore _
% Grave accent Left brace { Vertical bar |
% Right brace } Tilde ~
If this is included, any distortion can be detected and removed from the
submitted les.

3.2. Submission on diskette

If you submit your compuscript on a diskette, prepare the le such that no
line is longer than 72 characters. Try to use as few diskettes as possible, and
put a label, with
1. name of sender, and
2. journal identication and article number
on each of them. Also add a le readme with a list of all the les on the
diskettes and a description of their contents.
The allowed diskette types are: MS-DOS 3.5 inch, MS-DOS 5.25 inch and
Macintosh, and for every diskette type all densities are possible.

4. Getting help

Although a lot of eort has been put in keeping the document style easy to
use and in obtaining a concise description of the most common aspects of
style, it is of course possible that authors encounter problems while using
it. Also authors might have suggestions for additions. In those cases they
should send their comments and suggestions to the address mentioned on
the inside cover of the journal.

References

[1] Leslie Lamport: LATEX, A document preparation system,

2nd edition, Addison-Wesley (Reading, Massachusetts, 1994)
[2] Michel Goossens, Frank Mittelbach and Alexander Samarin: The
LATEXCompanion, Addison-Wesley (Reading, Massachusetts, 1994)
[3] Donald E. Knuth: The TEX book
Addison-Wesley (Reading, Massachusetts, 1986)
[4] AMS-LATEX Version 1.1Users Guide, American Mathematical Soci-
ety, Providence, R.I., December 1990; distributed with the AMS-LATEX
package.
 19

[5] Frank Mittelbach and Rainer Schopf: The new font family selection
user interface to standard LATEX
TUGboat 11 (1990) 297305.
20

A. Examples

In this appendix we will show a few examples of the use of the docu-
ment style elsart: two examples of the front matter, and one example
of the bibliography environment. LATEX 2 users should simply substitute
\documentclass in place of \documentstyle.
 21

\documentstyle{elsart}

\begin{document}
\begin{frontmatter}
\title{Integrability in
random matrix models\thanksref{talk}}
\thanks[talk]{Expanded version of a talk
presented at the Singapore Meeting on
Particle Physics (Singapore, August 1990).}

\author{L. Alvarez-Gaum\{e}}
\address{Theory Division, CERN,
CH-1211 Geneva 23, Switzerland}
\author{C. Gomez\thanksref{SNSF}},
\address{D\{e}partment de Physique Th\{e}orique,
Universit\{e} de Gen\{e}ve,
CH-1211 Geneva 4, Switzerland}
\author{J. Lacki},
\address{School of Natural Sciences,
Institute for Advanced Study,
Princeton, NJ 08540, USA}
\thanks[SNSF]{Supported by the
Swiss National Science Foundation}

\begin{abstract}
We prove the equivalence between the recent matrix model
formulation of 2D gravity and lattice integrable models.
For even potentials this system is the Volterra hierarchy.
\end{abstract}
\end{frontmatter}

\section{Introduction}
Some aspects of the recently discovered non-perturbative
solutions to non-critical strings \cite{ref1} can be better
understood and clarified directly in terms of the
integrability properties of the random matrix model.
...

Example 1. Article opening with implicit links (input).

22

Integrability in random matrix models

L. Alvarez-Gaume

Theory Division, CERN, CH-1211 Geneva 23, Switzerland

C. Gomez1

Department de Physique Theorique, Universite de Geneve, CH-1211

Geneva 4, Switzerland

J. Lacki

School of Natural Sciences, Institute for Advanced Study, Princeton, NJ

08540, USA

Abstract
We prove the equivalence between the recent matrix model formulation of 2D grav-
ity and lattice integrable models. For even potentials this system is the Volterra
hierarchy.

1. Introduction

Some aspects of the recently discovered non-perturbative solutions to non-

critical strings [1] can be better understood and claried directly in terms
of the integrability properties of the random matrix model.
...


Expanded version of a talk presented at the Singapore Meeting on Particle Physics
(Singapore, August 1990).
1
Supported by the Swiss National Science Foundation

Example 1. Article opening with implicit links (output).

 23

\documentstyle{elsart}

\begin{document}
\begin{frontmatter}
\title{A renormalization group study of a gauge \\
theory: SU(3) at finite temperature}

\author[Madrid]{L.A. Fernandez\thanksref{CAICYT}},
\author[Pisa]{M.P. Lombardo},
\author[Rome]{R. Petronzio} and
\author[Zaragoza]{A. Tarancon\thanksref{CAICYT}}
\address[Madrid]{Departamento de F\{\i}sica Te\{o}rica,
Universidad Complutense de Madrid, E-28040 Madrid, Spain}
\address[Pisa]{INFN, Sezione di Pisa, I-56100 Pisa, Italy}
\address[Rome]{Dipartimento di Fisica,
Universit\{a} di Roma II Tor Vergata and
INFN, Sezione di Roma Tor Vergata,
Via O. Raimondo, I-00173 Rome, Italy}
\address[Zaragoza]{Departamento de F\{\i}sica Te\{o}rica,
Universidad de Zaragoza, E-50009 Zaragoza, Spain}
\thanks[CAICYT]{Partially supported by CAICYT, Spain.}

\begin{abstract}
We apply a finite size renormalization group method to the
study of the deconfining transition in pure gauge SU(3). By
constructing renormalized systems with $2^3$ and 2 variables
suitably defined we obtain a very accurate determination
of the transition point and of the thermal exponent $\nu$.
\end{abstract}
\end{frontmatter}

The pure gauge SU(3) system at finite temperature

undergoes a phase transition from the confined to
the deconfined phase associated to the spontaneous
breaking of the local Z(3) symmetry.
...

Example 2. Article opening with explicit links (input).

24

A renormalization group study of a gauge

theory: SU(3) at nite temperature

L.A. Fernandeza,1, M.P. Lombardob , R. Petronzioc, A. Tarancond,1

a
Departamento de Fsica Teorica, Universidad Complutense de Madrid,
E-28040 Madrid, Spain
b
INFN, Sezione di Pisa, I-56100 Pisa, Italy
c Dipartimento di Fisica, Universita di Roma II Tor Vergata and INFN,
Sezione di Roma Tor Vergata, Via O. Raimondo, I-00173 Rome, Italy
d
Departamento de Fsica Teorica, Universidad de Zaragoza, E-50009
Zaragoza, Spain

Abstract
We apply a nite size renormalization group method to the study of the decon-
ning transition in pure gauge SU(3). By constructing renormalized systems with
23 and 2 variables suitably dened we obtain a very accurate determination of the
transition point and of the thermal exponent .

The pure gauge SU(3) system at nite temperature undergoes a phase transi-
tion from the conned to the deconned phase associated to the spontaneous
breaking of the local Z(3) symmetry.
...
1
Partially supported by CAICYT, Spain.

Example 2. Article opening with explicit links (output).

 25

\begin{thebibliography}{9}
\bibitem{Robi66}
A. Robinson,
{\em Non-standard Analysis\/}
(North-Holland, Amsterdam, 1966).

\bibitem{Sand89a}
E. Sandewall,
Combining logic and differential equations
for describing real-world systems,
in: R.J. Brachmann, H. Levesque and R. Reiter, eds.,
{\em Proceedings First International Conference on
Principles of Knowledge Representation and Reasoning\/}
(Morgan Kaufmann, Los Altos, CA, 1989) 412--320.

\bibitem{Sand89b}
E. Sandewall,
Filter preferential treatment for the logic of action
in almost continuous worlds,
in: R.J. Brachmann, H. Levesque and R. Reiter, eds.,
{\em Proceedings IJCAI-89\/}
(Detroit, MI, 1989) 894--899.

\bibitem{Shoh88a}
Y.Shoham,
Chronological ignorance:
experiments in nonmonotonic temporal reasoning,
{\em Artif. Intell.\/} {\bf 36} (1988) 279--331.

\bibitem{Shoh88b}
Y.Shoham and D. McDermott,
Problems in formal temporal reasoning,
{\em Artif. Intell.\/} {\bf 36} (1988) 49--61.

\bibitem{Bent83}
J. van Benthem,
{\em The logic of time\/}
(Reidel, Dordrecht, 1983).
\end{thebibliography}

Example 3. Literature references (input).

26

References

[1] A. Robinson, Non-standard Analysis (North-Holland, Amsterdam, 1966).

[2] E. Sandewall, Combining logic and dierential equations for describing
real-world systems, in: R.J. Brachmann, H. Levesque and R. Reiter, eds.,
Proceedings First International Conference on Principles of Knowledge
Representation and Reasoning (Morgan Kaufmann, Los Altos, CA, 1989)
412320.
[3] E. Sandewall, Filter preferential treatment for the logic of action in al-
most continuous worlds, in: R.J. Brachmann, H. Levesque and R. Reiter,
eds., Proceedings IJCAI-89 (Detroit, MI, 1989) 894899.
[4] Y.Shoham, Chronological ignorance: experiments in nonmonotonic tem-
poral reasoning, Artif. Intell. 36 (1988) 279331.
[5] Y.Shoham and D. McDermott, Problems in formal temporal reasoning,
Artif. Intell. 36 (1988) 4961.
[6] J. van Benthem, The logic of time (Reidel, Dordrecht, 1983).

Example 3. Literature references (output).

Index

abbreviations enumerate, 8
macros for, 7 eqnarray environment, 9
abstract, 6, 7 equation, 9
abstract, 6 displayed, 9
acknowledgements, 8 in-line, 9
address, 6 multi-line, 9
\address, 6 equation environment, 9
optional argument of, 6 extra instructions, 15
algorithm, 13
\and, 7 figure environment, 13
angle brackets, 10 \label in, see \caption
author, 6 formula, 9
\author, 6 displayed, 9
optional argument of, 6 in-line, 9
multi-line, 9
bibliography front matter, 6, 7
made with BibTEX, 12
made with bibliography en- hyphen, 7
vironment, 12
\include, 14
BibTEX, 12
\input, 14
caption, 13 italic correction, 7
argument too long, 13 italics, 7
vertical rules, 13 itemize, 8
\caption, 13
keyword abstract, 6, 7
in combination with \label, 9
citation, 12 \label, 8
formatting the, 12 for equation number, 9
multiple, 13 for sectional unit, 9
with added note, 13 for table or gure caption, 9
\cite, 12 layout
collab, 6 explicit commands for, 15
\collab, 6 lists, 8
optional argument of, 6 literature references, 12
computer program, 13
cross-reference, 8 \maketitle, 6

dash, 7 notations
diagram, 13 macros for, 7
dierences with standard styles, 6 number ranges, 7

emphasized text, 7 parameterless macro, 7

27
28

picture, 13
preamble, 7
proof environment, 12

\ref, 9
roman typeface, 10
root le, 14

\section
in combination with \label, 9
sectional units, 8
space
explicit, 8
submitting a compuscript
on a diskette, 18
via electronic mail, 17
subscripts
abbreviations in, 10
words in, 10
superscripts
abbreviations in, 10
words in, 10

table environment, 13
\label in, see \caption
\thanks, 6
optional argument of, 6
\thanksref, 7
theorem environments, 11
title, 6
\title, 6

units, 10
user-dened
log-like functions, 11
operators, 11
relation symbols, 11

\vec, 15
vector, 15