AMS Style Guide PDF
AMS Style Guide PDF
AMS Style Guide PDF
www.ams.org/authors
Contents
Introduction
This handbook is designed to help authors who are preparing books or articles
for publication or copublication by the American Mathematical Society (AMS).
In recent years, computer technology has transformed publishing. The advent of
electronic submissions and digitally created illustrations has made the author a full
partner in the production process. To ensure that your submission is published
in the format needed for your intended publication, please carefully read over this
introduction and the relevant sections of this guide.
The AMS, one of the world’s largest publishers of research literature in the
mathematical sciences, uses LATEX to typeset its publications. The AMS offers
TEX-related support software, such as AMS-LATEX and AMS-TEX, that provides
easy ways to code manuscripts containing mathematical expressions. To encourage
the use of AMS-LATEX and AMS-TEX, the AMS has developed publication-specific
author packages. These author packages contain instructions and style files per-
taining to the publication in question, as well as general graphics guidelines. Thus,
authors submitting work to Graduate Studies in Mathematics would use a different
package than those submitting to the Journal of the American Mathematical Soci-
ety. (You will find a complete list of packages in the section AMS Author Packages
later in this handbook.)
Although the AMS will accept submissions in a number of forms, including non-
electronic manuscripts, authors are strongly encouraged to use the author packages
whenever possible. This will speed up the publishing process, and dramatically
reduce the number of manuscript errors, as well as time required for proofread-
ing. Using the author packages is the best way to make sure that your article or
monograph flows smoothly through the production process.
General resources
For general advice on writing mathematics, see [SHSD] and [Hi]. For infor-
mation of a more specific nature including selecting notation, rules for spacing and
breaking mathematical expressions, English usage, the appropriate format for ref-
erences, a list of mathematical symbols, and the symbols used in proofreading, see
[Sw] and [Hi]. In your bibliography, use the abbreviations given in [ASMR].
Permissions
Authors are responsible for obtaining written permission to use another per-
son’s work—including text, graphics, photos, tables, and other art—whether or not
it has been previously published. If the work has been previously published, the
publisher is usually empowered to grant permission, but that is not always the case;
the author or an heir sometimes retains such rights. Permissions must be granted
free of any restrictions which may limit the AMS’s ability to produce, publish, pro-
mote, and distribute your monograph, in print or electronic format. Permissions
that include restrictions may result in the material being omitted.
Permission is not necessary for use of work in the public domain (such as U.S.
government publications or works for which the copyright has expired), but credit
should be given, in any case, to the originator of the work.
Authors are advised to begin writing for permissions as soon as a manuscript
has been accepted for publication by an editor or editorial committee, using the
AMS permission form (see www.ams.org/authors/permission-form). The AMS
will assist an author in obtaining permissions if such assistance is requested at least
eight weeks before the final submission is due to the AMS. A copy of the letter(s)
granting permission must be sent to the AMS with the submission.
Graphics
Detailed instructions on preparing graphics are provided in the AMS graphics
guidelines.
Electronic graphics. Figures may be submitted to the AMS in an electronic
format. The AMS recommends that graphics be created electronically at 100%
and saved in Encapsulated PostScript (EPS) format. This includes graphics origi-
nated via a graphics application as well as scanned photographs or other computer-
generated images.
Many popular graphics applications under a Macintosh, Windows, or Unix
environment allow files to be saved in EPS format (fonts should be embedded or
saved as outlines). However, if your package does not support EPS output, save
your graphics file in one of the standard graphics formats—such as TIFF, PICT,
GIF, JPEG, etc.—rather than in an application-dependent format. For example, if
you are using SuperPaint on a Macintosh, do not send files in SuperPaint format.
Instead, save the file in PICT format from SuperPaint and send the PICT files
to the AMS. Graphics files submitted in an application-dependent format are not
likely to be used. No matter what method was used to produce the graphic, it is
3
4 MONOGRAPHS
necessary to provide a reference copy (print or PDF) to the AMS for confirmation
purposes.
Please make sure that the version of the file submitted in electronic form is the
same as the version submitted as the reference copy. Authors sometimes submit
an electronic file that does not exactly match the reference copy submitted. This
is not acceptable, and will delay publication.
For electronic graphics submitted as part of an electronic manuscript, do not
include the caption or page number in the graphics file; the caption should be
typeset from the source file.
Create graphics at 100% of the size at which they will be printed. Do not
exceed the dimensions of the print area for the publication in which the figure is
to appear. If you must scale a figure before sending it to us, remember that line
weights also scale. Bear in mind that the thinnest line weight which will reproduce
clearly at high resolution is 0.5pt at 100%. Do NOT specify “hairline” weight, as
this will be nearly invisible at high resolution and will disappear in the printing
process. If a rule line is gray or colored, its weight should be no thinner than 1
point.
Graded line weights should increase in increments of at least 0.5pt. Increments
less than this are insufficiently distinguishable at high resolution.
Screened fills should be screened not less than 15% (less will print as white)
and not greater than 85% (greater will print as black).
Ideally, text included in graphics files should be font outlines rather than
bitmaps, because the AMS typesets its publications on a high-resolution image-
setter, not a laser printer. Text or lines in graphics that are bitmaps at 300dpi or
less (which may look fine next to your laser-printed output of your article) may
appear poor in quality next to the high-resolution text of AMS publications. If
bitmaps of characters are part of bitmapped line art files, output will be ideal if
the bitmapped characters are at 1200dpi.
Equations
Check displayed equations carefully, making sure they are broken and aligned
following the guidelines in [Sw, pp. 38–41], and that they do not exceed the width
of the page for the publication in which they are to appear. For multi-line displays,
use the structures defined in the amsmath user’s guide [ALG] or [Sp].
Indexes
Ideally, indexes should be prepared by including index terms directly in the
TEX file(s) for the document, to ensure correct page references. The output re-
sulting from TEXing the file should conform to the rules of MakeIndex. Use of the
MakeIndex program is described in [MG, chapter 11]. Output of this program is
processable only by LATEX.
If you are using AMS-TEX, please contact AMS Technical Support for assis-
tance.
Answers to some common questions about indexes are given in the AMS Author
FAQ [FAQ].
Initial submission
Electronic submissions. Send two proof copies or a PDF file of your mono-
graph to the Acquisitions Department. You should state your intention to submit
your work electronically, but the electronic version of the source file(s) should not
accompany the proof copy.
Nonelectronic submissions. Send two proof copies of your monograph to
the Acquisitions Department. Include any artwork.
Monograph Author Checklist
General resources
For general advice on writing mathematics, see [SHSD] and [Hi]. For infor-
mation of a more specific nature including selecting notation, rules for spacing and
breaking mathematical expressions, English usage, the appropriate format for ref-
erences, a list of mathematical symbols, and the symbols used in proofreading, see
[Sw] and [Hi]. In your bibliography, use the abbreviations given in [ASMR].
Permissions
Authors are responsible for obtaining written permission to use another per-
son’s work—including text, graphics, photos, tables, and other art—whether or not
it has been previously published. If the work has been previously published, the
publisher is usually empowered to grant permission, but that is not always the case;
the author or an heir sometimes retains such rights. Permissions must be granted
free of any restrictions which may limit the AMS’s ability to produce, publish, pro-
mote, and distribute your article, in print or electronic format. Permissions that
include restrictions may result in the material being omitted.
Permission is not necessary for use of work in the public domain (such as U.S.
government publications or works for which the copyright has expired), but credit
should be given, in any case, to the originator of the work.
Authors are advised to begin writing for permissions as soon as a manuscript
has been accepted for publication by an editor or editorial committee, using the
AMS permission form (see www.ams.org/authors/permission-form). The AMS
will assist an author in obtaining permissions if such assistance is requested at least
eight weeks before the final submission is due to the AMS. A copy of the letter(s)
granting permission must be sent to the AMS with the submission.
Use proper coding to link citations and cross references for optimum function-
ality on the web. Use \cite for all citations; this will enable linking between the
citation and the bibliographic item. Use \label and \ref or \eqref (LATEX only)
to automatically cross-reference sections, equations, theorems and theorem-like en-
vironments, tables, figures, etc. Use only numbers, letters, and colons within these
commands; other characters including spaces may fail to link properly when the
hyperref package is used, and may have to be replaced by AMS staff.
Graphics
Detailed instructions on preparing graphics are provided in the AMS graphics
guidelines.
Ideally, text included in graphics files should be font outlines rather than
bitmaps, because the AMS typesets its publications on a high-resolution image-
setter, not a laser printer. Text or lines in graphics that are bitmaps at 300dpi or
less (which may look fine next to your laser-printed output of your article) may
appear poor in quality next to the high-resolution text of AMS publications. If
bitmaps of characters are part of bitmapped line art files, output will be ideal if
the bitmapped characters are at 1200dpi.
Nonelectronic graphics. These graphics should be drawn in black ink with
clean, unbroken lines on nonabsorbent paper. Whenever possible, fonts used in
graphics should match those used in the text. Authors’ original graphics are used
whenever possible in AMS publications.
Send the originals of photographs or electronic artwork to the AMS. A photo-
copy of such an image can be used to identify it. To avoid damage to photographic
images, do not use paper clips or staples, and do not tape them to a sheet of paper.
Use cardboard backing in the mailing package for support and do not fold.
For a color image (whether it is to be converted to a black and white image or
is to appear in color), submit one of the following (listed in order of preference):
• glossy color photograph,
• color transparency or interneg,
• color slide.
Color graphics. The AMS normally does not include color graphics in its
proceedings, except in special circumstances. When the Editor and Publisher mu-
tually agree that color graphics are warranted, all graphics should be submitted in
EPS (Encapsulated PostScript) format.
• Color
Bitmap graphics: These should be at least 300dpi at 100% (i.e., un-
scaled) and in CMYK color space. TIFF and JPG (maximum quality)
are also acceptable.
Vector graphics: These should be in CMYK color space.
• Gray (e.g., black and white photographs) should be in gray or CMYK color
space.
Equations
Check displayed equations carefully, making sure they are broken and aligned
following the guidelines in [Sw, pp. 38–41], and that they do not exceed the width
of the page for the publication in which they are to appear. For multi-line displays,
use the structures defined in the amsmath user’s guide [ALG] or [Sp].
Initial submission
Electronic submissions. Send two proof copies or a PDF file of your article to
the Acquisitions Department. You should state your intention to submit your work
electronically, but the electronic version of the source file(s) should not accompany
the proof copy.
Nonelectronic submissions. Send two proof copies of your article to the
Acquisitions Department. Include any artwork.
Proceedings Volumes and Collections
Author Checklist
Most proceedings volumes and collections are published both in print and
on line. In order to expedite processing, the following restrictions are placed
on articles:
– Only “public” macro packages (packages available from CTAN, the
Comprehensive TEX Archive Network) may be used.
– Other macro definitions must be embedded in the preamble of the file.
Electronic files must be able to be processed independently with all
macros (not entire macro files) included.
– Macros should be defined with \newcommand (or \define if using AMS-
TEX), not with \def.
Do not redefine any existing LATEX, AMS-LATEX, or AMS-TEX commands.
The hyperref package will be added by AMS staff at the appropriate stage of
the production process and will be applied to internal cross-references and
external URLs.
Preliminary papers, abstracts, and summaries are not accepted for pub-
lication in AMS proceedings volumes.
Use the template supplied in the author package for your particular pub-
lication and the appropriate document style.
Use only “public” packages available from CTAN (the Comprehensive TEX
Archive Network).
Do not modify page sizes or other dimensions. Page sizes must conform
to the specifications for the book series for which you are preparing your
manuscript.
For electronic manuscripts, do not use author-defined macros in author
names, titles, abstracts, section headings, or references.
The first page of an article must contain a descriptive title. This title should
be short, but informative; avoid useless or vague phrases such as “some
remarks about” or “concerning”.
In article titles, the first and last words of the title and all nouns, pronouns,
adjectives, adverbs, and verbs should be capitalized; articles, conjunctions,
and prepositions should be lowercased except for the first and last words of
the title. Supply a shortened form of the title if the full title is too long for
the running head.
Avoid the use of math in the title. Titles are provided to on-line biblio-
graphic services for indexing. Use of TEX math coding (especially dollar
signs) will result in inaccurate bibliographic listings.
The running heads on the left-hand (even-numbered) pages should have
the name(s) of the author(s) in uppercase letters. Names in running heads
should match the names as given on the first page. Shortened forms must be
provided if necessary to fit on one line, leaving room for the page number.
Uppercasing will be applied automatically if you are using AMS style files.
10
PROCEEDINGS VOLUMES AND COLLECTIONS AUTHOR CHECKLIST 11
General resources
For general advice on writing mathematics, see [SHSD] and [Hi]. For infor-
mation of a more specific nature including selecting notation, rules for spacing and
breaking mathematical expressions, English usage, the appropriate format for ref-
erences, a list of mathematical symbols, and the symbols used in proofreading, see
[Sw] and [Hi]. In your bibliography, use the abbreviations given in [ASMR].
Note: Although the Memoirs series is available by subscription like a journal,
file creation is similar to that of a monograph. Authors should always read this
section completely, use the Memoirs author package, and follow the Memoirs author
checklist.
Permissions
Authors are responsible for obtaining written permission to use another per-
son’s work—including text, graphics, photos, tables, and other art—whether or not
it has been previously published. If the work has been previously published, the
publisher is usually empowered to grant permission, but that is not always the case;
the author or an heir sometimes retains such rights. Permissions must be granted
free of any restrictions which may limit the AMS’s ability to produce, publish, pro-
mote, and distribute your article, in print or electronic format. Permissions that
include restrictions may result in the material being omitted.
Permission is not necessary for use of work in the public domain (such as U.S.
government publications or works for which the copyright has expired), but credit
should be given, in any case, to the originator of the work.
Authors are advised to begin writing for permissions as soon as a manuscript
has been accepted for publication by an editor or editorial committee, using the
AMS permission form (see www.ams.org/authors/permission-form). The AMS
will assist an author in obtaining permissions if such assistance is requested at least
eight weeks before the final submission is due to the AMS. A copy of the letter(s)
granting permission must be sent to the AMS with the submission.
that are redefined must be manually replaced, one by one, by AMS staff; this is
both time consuming and error prone.
Use proper coding to link citations and cross references for optimum function-
ality on the web. Use \cite for all citations; this will enable linking between the
citation and the bibliographic item. The submitted bibliography will be available
on the article’s web page; it will be replaced in the file by an enhanced bibliogra-
phy with data from MathSciNet. Use \label and \ref or \eqref (LATEX only) to
automatically cross-reference sections, equations, theorems and theorem-like envi-
ronments, tables, figures, etc. Use only numbers, letters, and colons within these
commands; other characters including spaces may fail to link properly when the
hyperref package is used, and may have to be replaced by AMS staff.
Graphics
Detailed instructions on preparing graphics are provided in the AMS graphics
guidelines.
Electronic graphics. Figures may be submitted to the AMS in an electronic
format. The AMS recommends that graphics be created electronically at 100%
and saved in Encapsulated PostScript (EPS) format. This includes graphics origi-
nated via a graphics application as well as scanned photographs or other computer-
generated images.
Many popular graphics applications under a Macintosh, Windows, or Unix
environment allow files to be saved in EPS format (fonts should be embedded or
saved as outlines). However, if your package does not support EPS output, save
your graphics file in one of the standard graphics formats—such as TIFF, PICT,
GIF, JPEG, etc.—rather than in an application-dependent format. For example, if
you are using SuperPaint on a Macintosh, do not send files in SuperPaint format.
Instead, save the file in PICT format from SuperPaint and send the PICT files
to the AMS. Graphics files submitted in an application-dependent format are not
likely to be used. No matter what method was used to produce the graphic, it is
necessary to provide a reference copy (print or PDF) to the AMS for confirmation
purposes.
Please make sure that the version of the file submitted in electronic form is the
same as the version submitted as the reference copy. Authors sometimes submit
an electronic file that does not exactly match the reference copy submitted. This
is not acceptable, and will delay publication.
For electronic graphics submitted as part of an electronic manuscript, do not
include the caption or page number in the graphics file; the caption should be
typeset from the source file.
Create graphics at 100% of the size at which they will be printed. Do not
exceed the dimensions of the print area for the publication in which the figure is
to appear. If you must scale a figure before sending it to us, remember that line
weights also scale. Bear in mind that the thinnest line weight which will reproduce
clearly at high resolution is 0.5pt at 100%. Do NOT specify “hairline” weight, as
this will be nearly invisible at high resolution and will disappear in the printing
process. If a rule line is gray or colored, its weight should be no thinner than 1
point.
Graded line weights should increase in increments of at least 0.5pt. Increments
less than this are insufficiently distinguishable at high resolution.
14 JOURNALS
Screened fills should be screened not less than 15% (less will print as white)
and not greater than 85% (greater will print as black).
Ideally, text included in graphics files should be font outlines rather than
bitmaps, because the AMS typesets its publications on a high-resolution image-
setter, not a laser printer. Text or lines in graphics that are bitmaps at 300dpi or
less (which may look fine next to your laser-printed output of your article) may
appear poor in quality next to the high-resolution text of AMS publications. If
bitmaps of characters are part of bitmapped line art files, output will be ideal if
the bitmapped characters are at 1200dpi.
Color graphics. The AMS normally does not include color graphics in the
print version of its journals, except in special circumstances. (Note, however, that
color graphics that appear in black and white in the print version will appear in color
in the electronic version as submitted.) When the Editor and Publisher mutually
agree that color graphics are warranted, all graphics should be submitted in EPS
(Encapsulated PostScript) format.
• Color
Bitmap graphics: These should be at least 300dpi at 100% (i.e., un-
scaled) and in CMYK color space. TIFF and JPG (maximum quality)
are also acceptable.
Vector graphics: These should be in CMYK color space.
• Gray (e.g., black and white photographs) should be in gray or CMYK color
space.
Equations
Check displayed equations carefully, making sure they are broken and aligned
following the guidelines in [Sw, pp. 38–41], and that they do not exceed the width
of the page for the publication in which they are to appear. For multi-line displays,
use the structures defined in the amsmath user’s guide [ALG] or [Sp].
Initial submission
Electronic submissions. For AMS journals, see initial submission instruc-
tions on the web at www.ams.org/peer-review-submission.
INITIAL SUBMISSION 15
Most AMS journals are published both in print and on line. In order to
expedite processing, the following restrictions are placed onjournal articles:
– Only “public” macro packages (packages available from CTAN, the
Comprehensive TEX Archive Network) may be used.
– Other macro definitions must be embedded in the preamble of the ar-
ticle file. Electronic files must be able to be processed independently
with all macros (not entire macro files) included.
– Macros should be defined with \newcommand (or \define if using AMS-
TEX), not with \def.
Do not redefine any existing LATEX, AMS-LATEX, or AMS-TEX commands.
The hyperref package will be added by AMS staff at the appropriate stage of
the production process and will be applied to internal cross-references and
external URLs.
Use the template supplied in the author package for your particular pub-
lication and the appropriate document style.
For electronic manuscripts, do not use author-defined macros in author
names, titles, abstracts, section headings, or references.
The first page of an article must contain a descriptive title. This title should
be short, but informative; avoid useless or vague phrases such as “some
remarks about” or “concerning”.
In article titles, only the first word and proper nouns should be capitalized.
Supply a shortened form of the title if the full title is too long for the running
head.
Avoid the use of math in the title. Titles are provided to on-line biblio-
graphic services for indexing. Use of TEX math coding (especially dollar
signs) will result in inaccurate bibliographic listings.
The running heads on the left-hand (even-numbered) pages should have
the name(s) of the author(s) in uppercase letters. Names in running heads
should match the names as given on the first page. Shortened forms must be
provided if necessary to fit on one line, leaving room for the page number.
Uppercasing will be applied automatically if you are using AMS style files.
All AMS journal articles (except book reviews) must contain an abstract.
The main purpose of the abstract is to enable readers to take in the nature
and results of the article quickly. Zentralblatt publishes authors’ abstracts
instead of reviews, so the abstract may also appear there. The abstract
should contain no text references to the bibliography unless the bibliographic
reference is fully supplied. For example, [3] is meaningless to the reader once
the abstract is separated from the article. The abstract may comprise mul-
tiple paragraphs and include displayed material if appropriate. The length
of the abstract depends primarily on the length of the article itself and on
the difficulty of summarizing the material, but an upper limit of about 150
words for short articles and 300 words for long articles is suggested.
16
JOURNAL AUTHOR CHECKLIST 17
18
MEMOIRS AUTHOR CHECKLIST 19
Each of the author packages developed by the AMS produces the style of a
specific publication using a standard set of command sequences (see the lists of
commands later in this handbook). The AMS strongly encourages authors to pre-
pare their articles and monographs using the appropriate author package. By using
the appropriate author package, you will help reduce the cost of publication and
could shorten the time needed to publish your work.
Author packages contain sample articles(s) or chapter(s), templates for coding
topmatter (including some recommendations for packages), an electronic copy of
this handbook, instructions for using the package, and style files that produce
the style of a specific publication. Instructions for obtaining author packages are
included in the next section.
Each author package is designed to work with the most recent versions of the
base software. If you use older versions of LATEX, TEX, or AMS-created macro
packages, you may run into problems such as bugs that have been fixed in a later
version of the software you are running.
To use an author package, you will need the current version of AMS-LATEX
(preferred) or AMS-TEX as appropriate. See the next section for instructions on
how to obtain this software.
20
Obtaining and Using AMS Author Packages
A complete and up-to-date list of available author packages is on the AMS web
server at
• www.ams.org/authors/monopackages for monographs,
• www.ams.org/authors/procpackages for proceedings volumes and
collections, or
• www.ams.org/authors/journalpackages for journals.
Author packages should be retrieved via links from those pages. A list also appears
in the AMS Author Packages list later in this handbook.
Every author package is available bundled into a .zip file. If you are unable
to use a .zip file, be sure to retrieve every file for the author package you have
selected.
21
Quick Start for Obtaining and Using
AMS Author Packages
The purpose of this ‘Quick Start’ is to help you get an author package and start
using it as quickly as possible. To use an author package, you need to have the
most recent version of AMS-LATEX or AMS-TEX already installed. Retrieve author
packages from the AMS web server for monographs, for proceedings volumes and
collections, or for journals. Select the author package for the specific publication
from the list provided. Every author package is available bundled into a .zip file.
If you are unable to use a .zip file, be sure to retrieve every file for the author
package you have selected.
If you will be getting more than one author package, complete Step 3 before
getting another package; otherwise, files you have already downloaded may be over-
written in Step 2. In Steps 1 through 3, you will retrieve an author package from
the AMS web server and install it on your system. The lists of AMS-LATEX and
AMS-TEX commands in this handbook will help you use the package to prepare
your files so the time needed to publish your work is shortened.
STEP 1: Access the AMS web server
Using a web browser, link to www.ams.org/authors/monopackages for mono-
graphs, to www.ams.org/authors/procpackages for proceedings volumes and
collections, or to www.ams.org/authors/journalpackages for journals.
STEP 2: Get author package
1. Determine the journal or series in which your article or monograph will ap-
pear. If you are uncertain of the specific publication, select an appropriate
“generic” package.
2. Choose AMS-LATEX (preferred) or AMS-TEX. (Some packages are avail-
able only for AMS-LATEX.)
3. AMS author packages are posted both in bundled form (a .zip file) and
as separate files. If you choose to retrieve separate files, download every
file for the author package you have selected.
STEP 3: Install AMS-LATEX class files or AMS-TEX style files in the project-
specific directory, where your *.tex files are located. (Most current TEX distri-
butions are now updated in such a way that everything in the main “library”
area is removed and replaced, so if you install .cls or .sty files for an au-
thor package in the same directory as the underlying ams*.cls (AMS-LATEX)
or amsppt.sty (AMS-TEX) files, and upgrade your system while you are still
working on your document, the package-specific files would disappear.)
STEP 4: TEX and Print
1. Print the README file and follow the instructions for tailoring the sample
*.tex files and the *-template.tex file.
2. TEX the sample *.tex files in the package and print the output.
3. Print the .pdf files unless you already have copies.
STEP 5: Read the Checklist for electronic submissions in this handbook and the
Instructions you printed in Step 4; use the *-template.tex file as the basis for
your article or book, and use the sample *.tex files only as examples.
22
QUICK START FOR OBTAINING AND USING AMS AUTHOR PACKAGES 23
STEP 6: Coding
• AMS style files contain commands to identify all the important features
of mathematical articles and monographs; use these commands, not ones
you define yourself. Quick reference lists of the most important structuring
commands are given on the following pages.
• Do not use \def to define any command. For AMS-LATEX, use \newcommand,
and for AMS-TEX, use \define to warn you if the command name you are
using already exists. If the name already exists, do not redefine it without
explicit instructions to do so; choose another name instead.
• Do not modify page sizes or other dimensions.
• Put definitions for frequently occurring mathematical expressions together
in the preamble section, before the start of the text of the manuscript.
Once a macro is created for an expression, you should use it consistently
for every occurrence of that expression.
• Use TEX coding for special fonts (e.g., boldface or italic) only within the
text of the manuscript; do not use such coding for any headings or prede-
fined environments, e.g., theorems, etc.
STEP 7: Proofread your work carefully. Publications in some book series and in
Memoirs will not be given an editorial proofreading.
STEP 8: Verify the items in the Checklist for electronic submissions to be sure
your files are ready to be submitted.
STEP 9: Submit your files following the instructions in Appendix A, Submitting
Accepted Electronic Files and Graphics.
Basic AMS-LATEX Structure Commands
The commands listed here are for use in the body of your article or book.
The commands required for the top matter are presented in the template that is
included in the author package.
Code Comments
\specialsection{} Use only if sections are grouped
into parts.
\section{} First-level head (sections).
\section*{} etc. Unnumbered form.
\subsection{} Second-level head (subsections).
\subsubsection{} Third-level head (subsubsections).
\begin{xca} \end{xca} Exercises in body of text.
\begin{xcb} \end{xcb} Exercises at end of chapter
(available only for monographs).
\begin{figure} These five lines of code
\includegraphics{filename} insert a figure reference,
\caption{} print caption,
\label{} provide a cross-reference,
\end{figure} and close the insert.
\cite{} Cite a reference.
\begin{enumerate} \end{enumerate} Use for numbered lists.
\begin{itemize} \end{itemize} Use for bulleted lists.
\textup{} Use to get roman fences, i.e.,
( ), [ ], { },
and roman punctuation, i.e.,
: (colon)
; (semicolon)
, (comma)
‘‘ ’’ (quotation marks)
in the text of proclamations.
Theorems and similar structures are treated as environments in LATEX. Three
different theorem styles are provided by AMS-LATEX: plain, definition, and
remark. By referring to these styles and using the \newtheorem command, an
author can build a complement of theorem environments appropriate for any article
or monograph. The use of these commands is described in the manual Using the
amsthm Package [ATH]. All \newtheorem specifications should be included in the
preamble.
The following list summarizes the types of structures that are appropriate for
use with each theorem style.
The commands listed here are for use in the body of your article or monograph.
The commands required for the top matter are presented in the template that is
included in the author package.
Code Comments
\specialhead \endspecialhead Use only if sections are grouped
into parts.
\head \endhead First-level head (sections).
\subhead \endsubhead Second-level head (subsections).
\subsubhead \endsubsubhead Third-level head (subsubsections).
\proclaim{ } \endproclaim Theorem, Lemma, Corollary,
Proposition, Conjecture, Criterion,
Assertion.
\demo{ } \enddemo Proof.
\definition{ } \enddefinition Definition, Condition, Problem,
Algorithm, Question, Axiom,
Property, Assumption, Hypothesis.
\remark{ } \endremark Remark, Note, Notation, Claim,
Summary, Acknowledgment, Case,
Conclusion.
\example{ } \endexample Example.
\xca{ } \endxca Exercises in body of text.
\xcb{ } \endxcb Exercises at end of chapter
(available only for monographs).
\topinsert These four lines of code
\vspace #in create space for a figure,
\botcaption{ } \endcaption print caption,
\endinsert and close the insert.
\cite{ } Cite a reference.
\roster \endroster Use for lists.
\rom{ } Use to get roman fences, i.e.,
( ), [ ], { },
and roman punctuation, i.e.,
: (colon)
; (semicolon)
, (comma)
‘‘ ’’ (quotation marks)
in the text of proclamations.
25
AMS Author Packages
The packages listed here are available from the AMS web server. A complete,
up-to-date list for monographs is located at www.ams.org/authors/monopackages,
for proceedings volumes and collections at www.ams.org/authors/procpackages,
and for journals at www.ams.org/authors/journalpackages. Some packages are
available only for AMS-LATEX.
If you are not certain to which publication you will be submitting your article
or monograph, use the appropriate generic package, gen-*. These generic packages
are compatible with those for specific publications, allowing your manuscript to be
converted with minimal intervention.
Note: If you are the editor of a proceedings volume or collection, you should
obtain our Editor’s Package (www.ams.org/authors/editpkg), which will assist in
preparing the volume front matter.
Generic packages
gen-j Generic journal
gen-m Generic monograph
gen-p Generic proceedings
Journal packages
Code Full Journal Name
bull Bulletin (New Series) of the American Mathematical Society
ecgd Conformal Geometry and Dynamics
jag Journal of Algebraic Geometry
jams Journal of the American Mathematical Society
mcom Mathematics of Computation
memo Memoirs of the American Mathematical Society 1
noti Notices of the American Mathematical Society 2
qam Quarterly of Applied Mathematics
proc Proceedings of the American Mathematical Society
ert Representation Theory
spmj St. Petersburg Mathematical Journal
suga Sugaku Expositions
tpms Theory of Probability and Mathematical Statistics
tran Transactions of the American Mathematical Society
mosc Transactions of the Moscow Mathematical Society
Notes:
1. Although the Memoirs series is available by subscription like a journal, file
creation is similar to that of a monograph. Authors should always use the
Memoirs author package, and follow the Memoirs author checklist.
2. See also www.ams.org/notices/authors.html.
26
PACKAGES FOR PROCEEDINGS VOLUMES AND COLLECTIONS 27
Monograph packages
Code Full Series Name
cbms CBMS Regional Conference Series in Mathematics (Monograph)
coll Colloquium Publications
cmim Clay Mathematics Monographs
crmm CRM Monograph Series
gsm Graduate Studies in Mathematics
hmath History of Mathematics
surv Mathematical Surveys and Monographs
mawrld Mathematical World
amstext Pure and Applied Undergraduate Texts
smf SMF/AMS Texts and Monographs
stml Student Mathematical Library
mmono Translations of Mathematical Monographs
mmono-s Translations of Mathematical Monographs (Iwanami Series)
ulect University Lecture Series
Submitting Accepted
Electronic Files and Graphics
Use the commands provided by AMS style files to identify the important fea-
tures of mathematical articles and monographs (sections, theorems, etc.), not
commands you define.
Do not use \def to define commands. With LATEX use \newcommand, and with
AMS-TEX use \define. Do not redefine any plain TEX, LATEX, AMS-LATEX, or
AMS-TEX command.
Do not modify page sizes or other dimensions. Dimensions are publication-
specific.
Do not use TEX coding to control line and page breaks. Lines and pages may
break differently in the published article from the way they break in the file
you submit. If you insert TEX coding for line and page breaks, it will have
to be removed for production. That work could offset any time saved by your
keyboarding the manuscript, and any change to your TEX file creates a small
chance of additional errors being introduced.
Avoid explicit horizontal and vertical spacing commands for the same reason.
Put definitions for frequently occurring mathematical expressions together in the
preamble section, before the start of the text of the manuscript. Once a macro
is created for an expression, use it for every occurrence of that expression.
For a journal or proceedings article, or book chapters created using AMS-TEX,
include all relevant command definitions and all bibliographic items in the main
source file; input only “public” macro packages from CTAN. Every file should
be able to be processed independently. For an AMS-LATEX monograph, use a
driver file and put the source code for each chapter in a separate file, using
\include to pull them together into a single document.
Use only standard commands in section or theorem headings; do not hard-code
font changes or use commands that you have defined. Use TEX coding for special
fonts (e.g., boldface or italic) only within the text of the manuscript.
Use \cite to indicate citations in the manuscript.
Include all available information for references; use the abbreviations of journals
and book series from [ASMR], either in print or on the web.
Include the research address or institutional affiliation and current address (if
different) of each author. Email addresses and URLs may be included optionally.
Email addresses will appear in articles posted on line; URLs will not; both will
appear in print.
Check that all graphics meet specification requirements given in the AMS graph-
ics guidelines. Verify that graphics do not extend into the margins.
Proofread your article thoroughly and carefully. Publications in some book
series and in Memoirs will not be given an editorial proofreading.
Verify that submitted reference copy matches the accepted files.
28
ELECTRONIC MAIL SUBMISSIONS 29
Submission guidelines
Upon acceptance of your article or book, the source file(s) should be sent to
the AMS office (this includes the TEX (AMS-LATEX or AMS-TEX) source file(s) and
any graphics files). Send only the files that are needed to process your submission
or archive it for future reference.
Before sending the source file(s), be sure you have proofread your article or
monograph carefully. The files that you send must be the EXACT files used to
generate the proof copy that was accepted for publication. In order to avoid any
possible production problems, before sending the files, be sure to verify all items in
the Checklist for electronic submissions section above. Be sure that any necessary
forms are sent along with your submission.
For all publications, authors are required to send in a printed reference copy
or PDF file of their article that exactly matches the submitted file along with any
graphics that will appear in the article. For books, authors should send the printed
reference copy or PDF file to the Acquisitions Department. For journals, the process
is handled automatically through EditFlow.
If your submission consists of multiple files, we recommend that you bundle
them using the Zip utility; this can be obtained (free) for most platforms from
freecode.com. Bundling means that only one (compressed) file needs to be sent,
lessening the chance of name conflicts or file corruption.
Instructions for submitting electronic monographs or articles to be published
in AMS books and journals are found at www.ams.org/authors/submit-article.
Files that are bundled may be submitted by any acceptable method. The preferred
method is via the AMS web server; other acceptable methods are email (bundled
and source files only), FTP, or on CD.
FTP submissions
Files (source, EPS, and PDF) can be transferred over the Internet by FTP to
the AMS FTP server ftp.ams.org using the following instructions. The AMS FTP
server is a Unix environment; therefore file and directory names are case-sensitive.
Directory names on the server are lowercase.
At a system prompt, type ftp ftp.ams.org <return>. When you see a mes-
sage indicating that a connection has been opened, log in as follows. If your version
of FTP is now prompting you for a Name or Username, type anonymous <return>.
Otherwise, type login anonymous <return>. You will be asked to enter a pass-
word; enter your email address here and press <return>.
Once logged in, connect to the directory “incoming”:
cd incoming <return>
This is the only directory in the FTP area that is open to write access. Be sure to
set your mode to binary before you transfer your file(s) (see Sample FTP session
below). Please use a unique filename, for example, grey.zip. If the author name is
a common name, please include something to make it unique, such as first initials.
(If a file by the same name already exists in the incoming area, your transfer
will not be permitted.) After the transfer is complete, you must send mail to
pub-submit@ams.org to inform the AMS staff of the transfer. In your message tell
us the name of the file(s) you transferred, the publication for which it is intended,
and the name of the editor of the volume (if applicable).
Submissions on CD
Files (source, EPS, and PDF) can be sent on CD to the Acquisitions Depart-
ment for books, or to the Electronic Prepress Department for journals. CDs of any
standard format appropriate for either Windows or Macintosh are acceptable. The
CD should be labelled with your name, the title of your article or monograph, and
the publication for which it is intended.
A package containing a CD should be clearly marked “Electronic media. Do not
fold or bend. Do not expose to electric motors or other magnetic fields.” Mailers
designed for CD shipment are available from many sources; if you do not use a
special mailer, cardboard or some other stiffener should be enclosed in the package
for protection.
Files received on CD will be acknowledged as soon as possible after they are
received. If you have not received an acknowledgment within a reasonable amount
of time (two weeks if you are located in North America; three weeks if in Europe,
Australia, Japan, or South America; a month if you are in Eastern Europe, Asia or
Africa), please inquire, writing to the same address to which you sent the CD.
Sample FTP and email sessions
Sample FTP session. In the sample FTP session shown below, the files
grey.tex, grey.dvi, and grey-fig1.eps are transferred as a .zip file to the
AMS FTP server. Computer messages and prompts are shown in italic text, and
the commands that you will enter are shown in typewriter text. Note: Different
implementations of FTP work slightly differently, so the messages and prompts you
see will not necessarily be identical to the ones listed here.
homei ftp ftp.ams.org
Connected to ftp.ams.org.
220 130.44.204.20 FTP server ready
SAMPLE FTP AND EMAIL SESSIONS 31
Name: anonymous
331 Anonymous login ok, send your complete email address as your password.
Password:
230 Anonymous access granted, restrictions apply.
Remote system type is UNIX.
ftpi binary
200 Type set to I
ftpi cd incoming
250 CWD command successful.
ftpi pwd
257 00 /incoming 00 is current directory.
ftpi mput grey.zip
200 PORT command successful.
150 Opening data connection for grey.zip
226 Transfer complete.
local: grey.zip remote: grey.zip
nnn bytes sent in mmm seconds (NNN Kbytes/s)
ftpi quit
221 Goodbye.
Sample email session. The final step of the FTP submission process is to
send email to pub-submit@ams.org notifying the AMS that the files have been
transferred. The following is a sample subject line and message of an email message
notifying the AMS of the submission by FTP of an article to appear in a volume
of the Proceedings of Symposia in Pure Mathematics.
Subject : PSPUM/Greene
I have submitted the following file into /incoming on the FTP server:
grey.zip
for PSPUM edited by Robert Greene.
This zip file contains the following two files:
grey.tex
grey-fig1.eps
APPENDIX B
Resources
TEX Resources
LATEX and TEX are available on the web free of charge. There are also several
commercial TEX implementations. AMS web pages devoted to TEX information
can be accessed starting at www.ams.org/tex. The first of these pages has links to
other pages that identify the various sources for the TEX program.
LATEX is the most popular of the free front ends designed for use with TEX, the
basic typesetting program. Whereas plain TEX defines basic macros, LATEX defines
stylistic packages, setting up styles for a monograph, journal article, and article in
a proceedings collection, which you can then alter to your own specifications.
AMS-LATEX is a collection of LATEX extensions that make various kinds of math-
ematical constructions easier to produce, and take more care with certain finer de-
tails in order to yield publication-quality results. The macro package AMS-TEX,
from which AMS-LATEX inherited many of its parts, provides similar facilities in
a non-LATEX context. For both AMS-LATEX and AMS-TEX there are companion
design setup packages (variously referred to as ‘documentclass’ or ‘documentstyle’
or ‘style’ files) that enable authors writing a monograph or article to get largely the
same visual appearance in their preliminary drafts as in a final publication with the
AMS. AMS-LATEX files are included in the canonical LATEX distribution; updates
can be obtained directly from the AMS web server or from CTAN.
The book Math into LATEX [Gr] is written from the point of view of a math-
ematician using AMS-LATEX, and contains many examples. The Guide to LATEX,
fourth edition [KD], is a good general introduction to LATEX. The original and au-
thoritative manual for LATEX is the LATEX User’s Guide & Reference Manual [La].
For AMS-TEX the complete reference is The Joy of TEX [Sp]. And for plain TEX,
the original reference is The TEXbook [Kn].
Both AMS-LATEX and AMS-TEX require the installation of TEX. AMS-LATEX
requires the additional installation of LATEX. (See the section Author Package
Recommendations.)
AMS-LATEX and AMS-TEX are available from the AMS web server starting
from www.ams.org/tex. Distributions of AMS-LATEX, AMS-TEX, and AMSFonts
each include a copy of the relevant User’s Guide and related documentation. Each
guide provides important information including installation procedures and coding
examples. An electronic version of each of these guides is available as part of the
distribution packages on the AMS web server.
Another source of information on TEX and LATEX is the TEX Users Group
(TUG). They can be contacted at:
TEX Users Group
P. O. Box 2311
Portland, OR 97208-2311
(503) 223-9994, FAX: (206) 203-3960
office@tug.org
TUG also distributes the TEX Live collection, which includes ready-to-run imple-
mentations of TEX for Windows and Unix platforms, as well as LATEX, AMS-TEX,
and an extensive selection of packages, all freeware.
32
AMS RESOURCES 33
The AMS is not equipped to handle questions about specific platforms. Links
to sites providing such support, as well as addresses for discussion lists and links
for on-line forums, are given on this AMS web page.
AMS Resources
All written correspondence should be sent to the appropriate department at
the American Mathematical Society:
or by FAX to 401-331-3842.
For books, questions concerning what you need to prepare your manuscript
should be directed to:
Acquisitions Department
Phone: 800-321-4267, ext. 4051 or 401-455-4051
Email: acquisitions@ams.org
All documentation for AMS TEX-related products is available in PDF form from
the AMS web server as indicated below. If you are reading this handbook on-line,
the links for each item should be “live”.
[AFG] User’s Guide to AMSFonts, version 2.2d, Amer. Math. Soc., Providence,
RI, 2002. Link at www.ams.org/tex/amsfonts
[ALG] User’s Guide for the amsmath Package, version 2.0, Amer. Math. Soc.,
Providence, RI, 2002. Link at www.ams.org/tex/amslatex
[ASMR] Abbreviations of names of serials [reviewed in Mathematical Reviews],
Amer. Math. Soc., Providence, RI. www.ams.org/msnhtml/serials.pdf
[ATG] User’s Guide to AMS-TEX , version 2.2, Amer. Math. Soc., Providence,
RI, 2001. Link at www.ams.org/tex/amstex
[ATH] Using the amsthm Package, version 2.20, Amer. Math. Soc., Providence,
RI, 2004. Link at www.ams.org/tex/amslatex
[FAQ] Frequently Asked Questions for AMS Authors, www.ams.org/authors/
author-faq.
[INL] Instructions for Preparation of Papers and Monographs: AMS-LATEX ,
version 2.20, Amer. Math. Soc., Providence, RI, 2004. Link at www.ams.
org/tex/amslatex
[INT] Instructions for Preparation of Papers and Monographs: AMS-TEX , ver-
sion 2.2b, Amer. Math. Soc., Providence, RI, 2002. Link at www.ams.
org/tex/amstex