\documentstyle[12pt]{article}

\newcommand{\BIBTeX}{{\sc Bib\hspace{-0.1em}\TeX}}
\newcommand{\LaTeXtwoe}{\LaTeX\kern.15em 2${}_{\textstyle\varepsilon}$}
\newcommand{\AmS}{${\protect\the\textfont2 A}\kern-.1667em\lower
         .5ex\hbox{\protect\the\textfont2 M}\kern
         -.125em{\protect\the\textfont2 S}$}
\newcommand{\ttbs}{\char`\\}

\begin{document}
\title{
  Instructions for Authors\\
  \emph{The Chicago Journal of\\ Theoretical Computer Science}\\
  The MIT Press
}

\author{
  Michael J.\ O'Donnell\\
  The University of Chicago\\
  \texttt{odonnell@cs.uchicago.edu}
}

\date{Revised 1 January 1997}

\maketitle

The \emph{Chicago Journal of Theoretical Computer Science} is a
peer-reviewed scholarly journal in theoretical computer
science. Articles are submitted and published in \LaTeX\ source form,
and distributed internationally over the InterNet. Articles are
augmented by refereed forward references to improvements and
subsequent related work. Readers may obtain articles through \emph{FTP}
and \emph{HTTP} (\emph{World Wide Web}).
Other widely used network tools
will be supported as they arise in the future. The \emph{Journal} is
committed to minimizing publication delays, and to promoting maximum
flexibility in the ways that readers use the journal for teaching,
research, and scholarship. Readers' license is limited only as
required to insure fair attribution to authors and the journal, and to
prohibit use in a competing commercial product.

\section{What is a Published Article?}
The definitive version of an article published in the \emph{Chicago
Journal of Theoretical Computer Science} is a \LaTeX\ source file
containing the text of the article, an accompanying \BIBTeX\ source
file containing the bibliography, and encapsulated PostScript files if
drawings \emph{cannot} be encoded in the \LaTeX\ source. The journal's
copy editors prepare the source files for each article to present the
logical structure of the article as clearly as possible, so as to
maximize portability of the text, and to facilitate future development
of browsing interfaces and information retrieval applications.
Precompiled PostScript translations are provided for readers who
cannot format \LaTeX, or do not wish to, but the \LaTeX\ source is the
definitive copy.

\subsection*{Reader-Powered Publication}
Electronically published journals have used a variety of different
publication formats, including bitmapped page images, PostScript page
layouts, typographical formats such as \LaTeX, plain ASCII, and
special proprietary formats closely integrated with browsing and
information-retrieval software. Each of these choices favors different
qualities of publication---for example, bitmaps, PostScript, and some
proprietary formats give authors and publishers maximum control over
the beauty of the final display, while plain ASCII requires the
minimum equipment and skill on the part of the reader, etc. The
publication format of the \emph{Chicago Journal} is intended to
maximize \emph{readers' power} to use articles in whatever ways they
find most productive. The problem is that we cannot anticipate
precisely what readers will do, but we should assume at least that
they display articles in a wide variety of typographical formats
suited to their equipment, their paper or screen size, and their
eyesight, and that they apply browsing and information-retrieval
software acquired from other suppliers than MIT Press. To stretch our
imaginations a bit, there is already experimental software providing
audio browsing of
\LaTeX\ documents.

The way to maximize the power of readers in the long run, without
precise knowledge of reader behavior, is to represent the logical
structure of articles in the most transparent and easily parsable way
that we can manage. SGML was designed precisely for this task, but it
can also be done satisfactorily with a disciplined use of
\LaTeX. Furthermore, \LaTeX\ supports the representation of
mathematical formulae fairly well, and most of our reader and author
community already has the software to typeset and display \LaTeX. But,
maximum power and flexibility for readers demands a certain amount of
standardization in the \emph{source} format of articles. Readers, and
particularly readers' software packages, must be able to parse
important components, such as sectional units, paragraphs, sentences,
displayed subtexts such as theorems, easily and unambiguously. To
provide this uniform clarity in the \LaTeX\ source, copy editors must
polish authors' manuscripts into a disciplined subset of \LaTeX. As an
author, you need not be concerned with the details of that disciplined
subset, but by following the guidelines below you may improve the
efficiency of the journal operation, avoid wasting your own effort on
idiosyncratic layout that is incompatible with the discipline required
for uniform clarity in the final published article, and minimize the
delay in presenting your article to readers.

\section{What Should You Submit?}
All contributions to the \emph{Chicago Journal of Theoretical Computer
Science} are submitted by electronic mail in \LaTeX\ (or \LaTeXtwoe)
source format. The remainder of these instructions are intended to
guide you in preparing a submission efficiently. The closer that you
follow these rules, the more quickly and easily your contribution can
be evaluated and published. When there are good reasons to use
structures other than the normal ones, you should negotiate changes
with the editors. But, when conventional forms are satisfactory, you
will help everyone's efficiency by following them.

To submit an article for consideration by the editors, choose a short
mnemonic \emph{name} for your contribution, and prepare the following
three files:
\begin{itemize}
  \item \mbox{\emph{name}\texttt{.doc}}, a plain ASCII file containing
    your name, as many ways of reaching you as possible (mail
    address, e-mail address, telephone number, FAX number), a list
    of the other files that you are submitting, and any special
    message that you would like to provide for the editors;
  \item \mbox{\emph{name}\texttt{.tex}}, a \LaTeX\ (or \LaTeXtwoe) source
    file containing the text of the article, formatted with the
    standard \texttt{article} style, using any of the \AmS-\LaTeX\ style
    options \texttt{amstex}, \texttt{amsbsy}, \texttt{amscd}, \texttt{amsfonts},
    \texttt{amssymb}, \texttt{amstext} that you need;
  \item \mbox{\emph{name}\texttt{.bib}}, a \BIBTeX\ source file containing
    bibliography for the article (\BIBTeX\ source includes a lot of
    useful markup of the components of bibliographical entries
    that is usually lost in \texttt{*.bbl} files or hand-coded
    bibliographies).
\end{itemize}
If you have a large \BIBTeX\ database, you may wish to use
\texttt{aux2bib} or the combination of \texttt{citetags} and
\texttt{citefind} (find them through the journal's network server) to
select the items relevant to your submitted article.

Please include all local macro definitions (everything not defined in
\TeX, plain \TeX, \LaTeX, the \texttt{article} style, the \AmS-\LaTeX\ 
options, or encapsulated PostScript support such as the \texttt{epsf}
style) in the preamble to \mbox{\emph{name}\texttt{.tex}}, rather than in
a separate file of macro definitions. If you have written your article
using other files of specialized macro definitions, you may find the
UNIX command \texttt{texexpand} helpful in folding those definitions in
to one file.

\subsection{Drawings}

I recommend \emph{strongly} that you prepare drawings with
\texttt{xfig}, export them in \texttt{eepic} format (but save the
\texttt{fig} sources as well), and include them in the \LaTeX\ 
source file with the rest of the article. This will make it
\emph{much} easier to revise the drawings, and keep them
consistent with various article formats. The main shortcoming of
textt{xfig} is that it does not format mathematical formulae and
text with the same fonts and the same style as your article. But, it
is reasonably easy to fix this by editing the \texttt{eepic}
output. This final editing is easiest if you use a single
\texttt{xfig} text entry for each piece of formatted text or formula,
rather than, e.g., placing superscripts and subscripts as separate
text elements in \texttt{xfig}. The actual text entry in \texttt{xfig}
does not need to look exactly like the final product: it only needs to
be easily recognizable when you are editing the \texttt{eepic}. Look
at the \LaTeX\ source of published articles for examples. If your
article is accepted, I will ask for the \texttt{fig} sources as well,
so that I can polish the figures during final production.

As a last resort, if \texttt{eepic} cannot support the drawings that
you need to convey your ideas, you may provide encapsulated
PostScript as follows:
\begin{itemize}
  \item \emph{name}\texttt{f}\emph{i}.\texttt{eps}, encapsulated
    PostScript file with a picture for Figure \emph{i}
  \item \emph{name}\texttt{t}\emph{j}.\texttt{eps}, encapsulated
    PostScript file with a picture for Table \emph{j}
\end{itemize}
The first two years of journal publication have shown that the
\texttt{xfig}/\texttt{eepic} method is \emph{much} more
efficient and effective than encapsulated PostScript.

\section{How Should You Submit?}
Submit your article by electronic mail to
\begin{quote}
  \mbox{\texttt{chicago-journal@cs.uchicago.edu}}
\end{quote}
If you are computing on a UNIX system, the best form of submission is
a single \texttt{shar} archive containing all of the files mentioned
above in one message. Use the mnemonic name of your article as the
\texttt{Subject} line of the message. The next best form is a separate
message for each file transmitted, using the file name as the
\texttt{Subject} line.

\section{Guidelines for Your \LaTeX\ Source}
Try to use the simplest, most direct expression of the structure of
your article in the main \mbox{\emph{name}\texttt{.tex}} file. For
example, mark sectional units with the standard \LaTeX\ sectional
commands \texttt{\ttbs section}, \texttt{\ttbs subsection}, etc., rather
than hand-coding your own headings. Do not try to achieve a beautiful
layout by clever use of \TeX\ and \LaTeX\ tricks: most of that layout
work will be lost during copy editing anyway. In particular, specific
font choices (except \texttt{\ttbs em} for emphasis, and special uses in
defining mathematical symbols), type size choices, spacing by
reference to absolute units (\texttt{in}, \texttt{cm}, \texttt{pc}, \texttt{pt}),
and page breaking will be lost in copy editing.  We are collecting
macros to aid you in preparing submissions in the file
\texttt{cjauthor.tex} (it has only one item so far). As this collection of
macros grows, please use it as much as possible to avoid wasted effort
on solved problems. You may contribute material for
\texttt{cjauthor.tex}, but it will be incorporated only if it contributes to
the efficiency of this journal. Use indentation and blank comment
lines to make your \LaTeX\ source file more readable.

To include encapsulated PostScript figures, use the command
\begin{quote}
  \mbox{\texttt{\ttbs epsfbox\{}\emph{filename}\texttt{\}}}
\end{quote}
which is normally defined in a file named \texttt{epsf.sty}.

Your contribution is a late draft, and you may decide to revise it in
light of the referees' comments. So, make full use of the \LaTeX\
features that support the maintenance of a sequence of drafts. Avoid
typing in absolute names and numbers for labels, cross-references, and
citations. Use the automatically numbered version of the sectioning
commands, floats, and theorem-like environments, as well as \texttt{\ttbs
label}, \texttt{\ttbs ref}, and \texttt{\ttbs cite}. In this way \texttt{latex}
will produce labels, cross-references, and citations automatically, and
correct them after revisions. You may leave the final publication
numbering scheme to the copy editors. Or, if you suggest a particular
numbering scheme (for example, hierarchical within sectional units, or
lemmas numbered hierarchically within the proofs that contain them)
the editors will use it as long as it is internally consistent and
compatible with the needs of readers for clear references into
articles.

\subsection*{Mathematical Formulae}
Mathematical formulae tend to blur the distinction between meaningful
text and aesthetic layout, so you may need to exercise closer control
of formatting than you do in normal English text. As much as possible,
define sensible macros that stand for mathematically meaningful
operations. Try to put all nitty-gritty typographical commands, such
as type style choices and spacing adjustments, inside such
macros. When you need to design special mathematical notation, use the
standard type styles \texttt{\ttbs rm}, \texttt{\ttbs it}, \texttt{\ttbs bf},
\texttt{\ttbs sl}, \texttt{\ttbs sf}, \texttt{\ttbs sc}, \texttt{\ttbs tt},
\texttt{\ttbs cal}, or type styles supported by fonts distributed by the
American Mathematical Society. Other type styles must be negotiated
with the editors in advance, and they must be implemented by fonts
that are available for free distribution to all readers. Use the
\texttt{\ttbs mathstyleclass} command in \texttt{cjauthor.tex} to declare new classes
of mathematical symbols using specific type styles.

\section{Reviewing and Revising}
Your contributed article will be assigned to a contact editor, who
will use anonymous referees to help review it.
After the review, the editors may decide to accept
the article for publication, decline it, or ask for revisions. When
revisions are required by the editors and referees, you should submit
a complete revised version of your article, along with comments on how
your revisions address the concerns of the editors and referees. Such
revisions may be submitted in the same form as your original
contribution, except that instead of the file
\mbox{\emph{name}\texttt{.doc}}, provide \mbox{\emph{name}\texttt{-resp1.tex}}
containing your response to the referees' comments, and mail the
revised version to your contact editor. The journal also provides a
way for the referees to communicate technical questions to you
directly but anonymously when appropriate to speed reviewing. You may
answer such queries in the normal way that you reply to network mail.

If your article is accepted for publication, it will be forwarded
immediately to the copy editors, who will correct stylistic problems
and edit your \LaTeX\ source into the disciplined form that we
designed to maximize readers' flexibility. Copy editing is not
intended to introduce substantive changes in your article, but since
the boundary between format and substance is not always simple, the
copy editors will need to communicate with you to ask questions and to
gain your approval of the final version. Please address all replies
directly to the copy editors. If you wish to propose any revisions
during copy editing, please describe the appropriate changes to the
copy editors, instead of submitting fresh versions of the complete
article. Copy editing requires 3 weeks. In order to maintain
this schedule, you need to respond to queries from the copy editor
within 3 working days.

\section{For More Information}
More information and various materials associated with the {\em
Chicago Journal} are available through
\begin{itemize}
  \item \emph{World Wide Web} to MIT Press (for example, using \emph{Mosaic})
    \begin{itemize}
      \item use URL \texttt{http://www-mitpress.mit.edu/jrnls-catalog/science-toc.html}
    \end{itemize}
    \emph{World Wide Web} to U.\ Chicago
    \begin{itemize}
      \item use URL \texttt{http://cs-www.uchicago.edu/publications/cjtcs}
    \end{itemize}
  \item Anonymous \emph{ftp} to MIT Press
    \begin{itemize}
      \item connect to \texttt{mitpress.mit.edu}
      \item login as \texttt{anonymous}
      \item change directory to \texttt{pub/CJTCS}
    \end{itemize}
    Anonymous \emph{ftp} to U.\ Chicago
    \begin{itemize}
      \item connect to \texttt{cs.uchicago.edu}
      \item login as \texttt{anonymous}
      \item change directory to \texttt{pub/publications/cjtcs}
    \end{itemize}
  \item Network mail to \texttt{chicago-journal@cs.uchicago.edu} and
    \texttt{journals-info@mit.edu}.
\end{itemize}

\appendix

\section{Approved \LaTeX\ Commands and Features}
You are especially encouraged to use the following \LaTeX\ features:
\begin{description}
  \item Commands: \texttt{\ttbs section}, \texttt{\ttbs subsection},
    \texttt{\ttbs subsubsection}, \texttt{\ttbs appendix}, \texttt{\ttbs title},
    \texttt{\ttbs author}, \texttt{\ttbs thanks}, \texttt{\ttbs maketitle},
    \texttt{\ttbs newtheorem}, \texttt{\ttbs caption}, \texttt{\ttbs
    bibliography}, \texttt{\ttbs em}, \texttt{\ttbs item}, \texttt{\ttbs
    \ttbs}, \texttt{\ttbs label}, \texttt{\ttbs ref}, \texttt{\ttbs cite},
    \texttt{\ttbs nocite}, \texttt{\ttbs text}, \texttt{\ttbs intertext}, all of the
    \LaTeX\ and \AmS-\LaTeX\ commands producing the usual textual and
    mathematical symbols.
  \item Environments: \texttt{document}, \texttt{abstract}, \texttt{itemize},
    \texttt{enumerate}, \texttt{description}, \texttt{math}, \texttt{displaymath},
    \texttt{equation}, \texttt{eqnarray}, theorem-like environments,
    \texttt{quote}, \texttt{figure}, \texttt{table}, \texttt{array},
    \texttt{tabular}, \texttt{cases}, \texttt{Sb}, \texttt{Sp}, \texttt{CD}, \texttt{align},
    \texttt{gather}, \texttt{alignat}, \texttt{multiline}, \texttt{split}.
  \item Document styles and options: \texttt{article}, \texttt{epsf},
    \texttt{amstex}, \texttt{amsbsy}, \texttt{amscd}, \texttt{amsfonts}, \texttt{amssymb},
    \texttt{amstext}.
\end{description}

\subsection{In Macros for Mathematical Formulae Only}
As much as possible, use \texttt{\ttbs mathstyleclass} from
\texttt{cjauthor.tex} and \texttt{\ttbs newcommand} to hide the type style
choices and spaciing commands below within macro definitions.
\begin{description}
  \item Commands: \texttt{\ttbs rm}, \texttt{\ttbs bf}, \texttt{\ttbs it},
    \texttt{\ttbs sl}, \texttt{\ttbs sf}, \texttt{\ttbs sc}, \texttt{\ttbs tt},
    \texttt{\ttbs cal}, \texttt{\ttbs !}, \texttt{\ttbs ,}, \texttt{\ttbs :},
    \texttt{\ttbs ;}, \texttt{\ttbs Bbb}, \texttt{\ttbs boldsymbol}, \texttt{\ttbs
    frak}, \texttt{\ttbs pmb}, \texttt{\ttbs smash}, \texttt{\ttbs
    operatorname}, \texttt{\ttbs operatornamewithlimits}.
\end{description}

\section{\LaTeX\ Commands and Features to Avoid}
Avoid the following \LaTeX\ features as much as possible. When you
really need them, try to embed them in meaningful macro definitions.
\begin{description}
  \item Commands: \texttt{\ttbs vspace}, \texttt{\ttbs noindent}, \texttt{\ttbs
    indent}, \texttt{\ttbs linebreak}, \texttt{\ttbs nolinebreak},
    \texttt{\ttbs nopagebreak}, \texttt{\ttbs samepage}, \texttt{\ttbs fill},
    \texttt{\ttbs stretch}, \texttt{\ttbs hspace}, \texttt{\ttbs vspace}, \texttt{\ttbs
    bigskip}, \texttt{\ttbs medskip}, \texttt{\ttbs smallskip}, \texttt{\ttbs
    addvspace}, \texttt{\ttbs sloppy}, \texttt{\ttbs fussy}, \texttt{\ttbs
    raisebox}.
  \item Environments: \texttt{tabbing}.
  \item Change style parameters: \texttt{\ttbs topsep}, \texttt{\ttbs
    partopsep}, \texttt{\ttbs itemsep}, \texttt{\ttbs parsep}, \texttt{\ttbs
    itemindent}, \texttt{\ttbs labelsep}, \texttt{\ttbs labelwidth},
    \texttt{\ttbs makelabel}, \texttt{\ttbs jot}, \texttt{\ttbs arraycolsep},
    \texttt{\ttbs tabcolsep}, \texttt{\ttbs arrayrulewidth}, \texttt{\ttbs
    doublerulesep}, \texttt{\ttbs arraystretch}.
  \item Read style parameters: all style parameters.
  \item Length units: \texttt{em}, \texttt{ex}.
\end{description}

\section{Prohibited \LaTeX\ Commands and Features}
You should not use the following \LaTeX\ features. If you think that
you really need them, please contact me.
\begin{description}
  \item Commands: \texttt{\ttbs pagenumbering}, \texttt{\ttbs pagestyle},
    \texttt{\ttbs thispagestyle}, \texttt{\ttbs pagebreak}, \texttt{\ttbs
    marginpar}, \texttt{\ttbs reversemarginpar}, \texttt{\ttbs
    normalmarginpar}, \texttt{\ttbs part}, \texttt{\ttbs chapter},
    \texttt{\ttbs markright}, \texttt{\ttbs markboth}, \texttt{\ttbs twocolumn},
    \texttt{\ttbs onecolumn}, \texttt{\ttbs clearpage}, \texttt{\ttbs verb},
    \texttt{\ttbs bibitem}, \texttt{\ttbs input}, \texttt{\ttbs include},
    \texttt{\ttbs typeout}, \texttt{\ttbs typein}.
  \item Environments: \texttt{titlepage}, \texttt{verbatim},
    \texttt{thebibiliography}, \texttt{theindex}
  \item Change style parameters: \texttt{\ttbs textwidth}, \texttt{\ttbs
    linewidth}, \texttt{parindent}, \texttt{\ttbs baselineskip}, \texttt{\ttbs
    baselinestretch}, \texttt{parskip}, \texttt{\ttbs footnotesep},
    \texttt{\ttbs footnoterule}, \texttt{secnumdepth}, \texttt{\ttbs tocdepth},
    \texttt{\ttbs bibindent}, \texttt{\ttbs columnsep}, \texttt{\ttbs
    columnseprule}, \texttt{\ttbs mathindent}, \texttt{\ttbs
    oddsidemanrgin}, \texttt{\ttbs evensidemargin}, \texttt{\ttbs
    marginparwidth}, \texttt{\ttbs marginparsep}, \texttt{\ttbs topmargin},
    \texttt{\ttbs headheight}, \texttt{\ttbs headsep}, \texttt{\ttbs
    textheight}, \texttt{\ttbs textwidth}, \texttt{\ttbs topskip},
    \texttt{\ttbs footheight}, \texttt{\ttbs footskip}, \texttt{\ttbs leftmargin},
    \texttt{\ttbs rightmargin}, \texttt{\ttbs listparindent}, \texttt{\ttbs
    mathindent}, \texttt{\ttbs abovedisplayskip}, \texttt{\ttbs
    belowdisplayskip}, \texttt{\ttbs abovedisplayshortskip}, \texttt{\ttbs
    belowdisplayshortskip}, \texttt{topnumber}, \texttt{\ttbs topfraction},
    \texttt{bottomnumber}, \texttt{\ttbs bottomfraction}, \texttt{totalnumber},
    \texttt{\ttbs textfraction}, \texttt{\ttbs floatpagefraction},
    \texttt{dbltopnumber}, \texttt{\ttbs dbltopfraction}, \texttt{\ttbs
    dblfloatpagefraction}, \texttt{\ttbs floatsep}, \texttt{\ttbs
    textfloatsep}, \texttt{\ttbs intextsep}, \texttt{\ttbs dblfloatsep},
    \texttt{\ttbs dbltextfloatsep}, \texttt{\ttbs marginparwidth},
    \texttt{\ttbs marginparsep}, \texttt{\ttbs marginparpush}, \texttt{\ttbs
    tabbingsep}, \texttt{\ttbs fboxrule}, \texttt{\ttbs fboxsep}.
  \item Length units: \texttt{cm}, \texttt{in}, \texttt{pc}, \texttt{pt}, \texttt{mm}.
  \item Document styles and options: all those not listed in Appendix~A.
\end{description}

\end{document}
