\documentclass{entcs} \usepackage{entcsmacro}
\usepackage{graphicx}

% The following is enclosed to allow easy detection of differences in
% ascii coding.
% 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        =3D           Greater than >          Question mark ?
% At            @           Left bracket [          Backslash     \
% Right bracket ]           Circumflex   ^          Underscore    _
% Grave accent  `           Left brace   {          Vertical bar  |
% Right brace   }           Tilde        ~

% A couple of exemplary definitions:

\newcommand{\Nat}{{\mathbb N}}
\newcommand{\Real}{{\mathbb R}}
\def\lastname{My Lastname}
\begin{document}
\begin{frontmatter}
  \title{An Example Paper} \author{My
    Name\thanksref{ALL}\thanksref{myemail}}
  \address{My Department\\ My University\\
    My City, My Country} \author{My Co-author\thanksref{coemail}}
  \address{My Co-author's Department\\My Co-author's University\\
    My Co-author's City, My Co-author's Country} \thanks[ALL]{Thanks
    to everyone who should be thanked} \thanks[myemail]{Email:
    \href{mailto:myuserid@mydept.myinst.myedu} {\texttt{\normalshape
        myuserid@mydept.myinst.myedu}}} \thanks[coemail]{Email:
    \href{mailto:couserid@codept.coinst.coedu} {\texttt{\normalshape
        couserid@codept.coinst.coedu}}}
\begin{abstract} This is a short
  example to show the basics of using the ENTCS style macro files.
  Ample examples of how files should look may be found on the ENTCS
  Home Page \href{http://www.elsevier.nl/locate/entcs}
  {\tt http://www.elsevier.nl/locate/entcs}.
\end{abstract}
\end{frontmatter}

\section{Introduction}\label{intro}
This short note provides a guide to using the ENTCS macro package for
preparing papers for publication in your conference
\emph{Proceedings}. The \emph{Proceedings} may be printed and hard
copies distributed to participants at the meeting; this is an option
to Conference Organizers may choose to exercise.  The
\emph{Proceedings} also will be a volume in the series
\emph{Electronic Notes in Theoretical Computer Science} (ENTCS), which
is published under the auspices of Elsevier Science B.~V., the
publishers of \emph{Theoretical Computer Science}.

The ENTCS macro package consists of two files:
\begin{description}
\item[\texttt{entcs.cls},] the basic style file, and
\item[\texttt{entcsmacro.sty},] a macro file containing the
  definitions of some of the theorem-like environments and a few other
  tidbits.
\end{description}
Additional macro files can be added using \verb+\usepackage{...}+.
The file \texttt{entcs\-macro.sty} \emph{must} be included in the
list, as is done at the start of the source file for this paper.

The formatting these style files impose should \emph{not} be altered
-- the reason for using them is to attain a uniform format for all
papers in the \emph{Proceedings} of which your paper is a part.

The file \texttt{instraut.dvi} contains information about the macro
package \texttt{elsart.sty} and \texttt{elsart12.sty}, from which the
files \texttt{entcs.sty} and \texttt{entcs12.sty} are derived. Reading
this file should answer most of the basic questions that might arise.
It also gives some basic rules about using the macro package.

\section{Frontmatter}
The biggest difference between a ``usual'' \LaTeX\ style such as
\texttt{article.sty} and the ENTCS package is that the ENTCS macro
package requires the title, author's name or names, abstract and
``thanks'' all to be included within the \texttt{frontmatter}
environment.  At the beginning of the source file for this paper,
you'll notice this.  Also, you'll notice that the usual
\verb+\maketitle+ is absent; it no longer is needed.  The ENTCS
style package automatically generates the title, author's name
and address, and related material at the beginning of the paper.

The ENTCS macro package provides two alternatives to listing
authors names and addresses.  These are described in detail in
the file \texttt{instraut.dvi}.  Basically, listing each author
and his or her address in turn, is the simplest method.  But, if
there are several authors and two or more share the same address
(but not all authors are at this address), then the method of
listing authors first, and then the addresses, and of referencing
addresses to authors should be used.

Also, notice that acknowledgment of support (the contents of
\verb+\thanks+) should be done by a separate listing of
\verb+\thanks[NSF]{To the NSF}+ with the optional argument --
\verb+[NSF]+ -- being used for \verb+\thanksref+ which is
attached to those authors acknowledging such support.  It is
important that the \verb+\thanks+ not be included within the
scope of \verb+\author{}+ or of \verb+\title{}+, but it must be
within the scope of the environment \texttt{frontmatter}.

More details about added terms such as \verb+\collab+ can be
found in \texttt{inst.dvi}, if they are needed.

Also, notice that the command \verb+\lastname{My Lastname}+ has
been included \emph{before} the \texttt{frontmatter} begins.  This
command should contain the last names of the authors of the
paper.  If there are no more than three authors, then they should
be listed with the word ``and'' between the last two; if more
than three authors collaborated on the paper, then the first
author only should be listed, together with \verb+\emph{et al}+.
This command creates the headline for each page after page 1.

Finally, please be sure to include an abstract for your paper.

\section{Sectioning and Environments}
Since ENTCS is published through the auspices of Elsevier Science
B.~V., their style files have been used to create the ENTCS macro
package.  Here's a proof that this package is not much different than
most of the ones one encounters:

\begin{definition}
  A file is \emph{derived} from another if it is obtained with only a
  few modifications from the original file.
\end{definition}

\begin{theorem}
  The file \texttt{\normalshape entcs.cls} is derived from
  \texttt{\normalshape elsart.sty}.
\end{theorem}
\begin{proof}
  This is clear from the similarity of the output to the output from
  Elsevier's style files.
\end{proof}

If one wants to start a proof with a descriptive word, such as
``sketch'', then one can use the \verb+\begin{proof*}...\end{proof*}+
environment, as in

\begin{proof*}{Proof (Sketch)}
  This can be derived from simple observations.
\end{proof*}

The main differences between the file \texttt{entcs.cls} and the ones
created by Elsevier are the more precise format we use -- Elsevier's
generic files are meant for preliminary editing, and more precise
formatting is imposed using a macro file designed for the specific
Elsevier journal in which the paper will eventually appear. The
\texttt{entcs.cls} and \texttt{entcsmacro.sty} files format papers
uniformly so that they all are easily recognizable as being from the
series \emph{Electronic Notes in Theoretical Computer Science}.

All of the usual features of \LaTeX\ are available with these
style files -- it is only the formatting that has been rigorously
defined. Thus, one has available the sectioning commands
\verb+\section,\subsection, \paragraph+ and \verb+\subparagraph.+
The numbering scheme used is one under which Theorem 1.2.3 is the
third numbered item in second subsection of the first section of
the paper.  In order to facilitate cross-references, all of the
named environments given below are numbered, and all use the same
number scheme.

The file \texttt{entcsmacro.sty} contains additional information that
is needed to typeset a paper.  It also has the definitions of the
$\cal AMS$ \texttt{euler} and \texttt{blackboard bold} fonts builtin.
If you want to use symbols for the natural numbers, the reals, etc.,
then we prefer that you use the blackboard bold fonts, and not plain
bold fonts. This is accomplished by using the \verb+\mathbb+ font, as
in $\Nat$ or $\Real$.

The names of theorem-like environments are provided in
\texttt{entcsmacro.sty}.  With the exception of the environment
Algorithm, the names of all of these are full name, rather than a
shortened version. The environments provided and their names are
\begin{itemize}
\item \verb+\begin{theorem} ... \end{theorem}+ for Theorems,
\item \verb+\begin{lemma} ... \end{lemma}+ for Lemmas,
\item \verb+\begin{corollary} ... \end{corollary}+ for Corollaries,
\item \verb+\begin{proposition} ... \end{proposition}+ for
  Propositions,
\item \verb+\begin{criterion} ... \end{criterion}+ for Criteria,
\item \verb+\begin{alg} ... \end{alg}+ for Algorithms,
\item \verb+\begin{definition} ... \end{definition}+ for Definitions,
\item \verb+\begin{conjecture} ... \end{conjecture}+ for Conjectures,
\item \verb+\begin{example} ... \end{example}+ for Examples,
\item \verb+\begin{problem} ... \end{problem}+ for Problems,
\item \verb+\begin{remark} ... \end{remark}+ for Remarks,
\item \verb+\begin{note} ... \end{note}+ for Notes,
\item \verb+\begin{claim} ... \end{claim}+ for Claims,
\item \verb+\begin{summary} ... \end{summary}+ for Summary,
\item \verb+\begin{case} ... \end{case}+ for Cases, and
\item \verb+\begin{ack} ... \end{ack}+ for Acknowledgements.
\end{itemize}

For example,

\begin{algorithm}[h]
\begin{alg}
  Step 1:  Write the paper\\
  Step 2: Format it with the ENTCS macro package\\
  Step 3:  Ship the whole thing to the Guest Editors\\
\end{alg}
\end{algorithm}

\section{References and Cross-references}
All the cross-referencing facilities of \LaTeX\ are supported, so one
can use \verb+\ref{}+ and \verb+\cite{}+ for cross-references within
the paper and for references to bibliographic items.  As is done in
this note, the {\bf References} section~\ref{bibliography} can be
composed with \verb+\begin{thebibliography}...\end{thebibliography}+.
Alternatively, Bib\TeX\ can be used to compile the bibliography.
Whichever one is used, the references are to be numbered
consecutively, rather than by author-defined acronyms.  Of course you
can use your own acronyms for easy reference to each of the items in
the bibliography, as has been done with the listing for this short
note.

However, note that the references should \emph{not} be started with a
new \verb+\section+ command.

The package \texttt{hyperref} is automatically loaded by
entcs.cls, and this makes all the cross-references within the
document ``active'' when the file is viewed with \texttt{xdvi}.
The format for including a link is simple: simply insert
\verb+\href{URL}+ \verb+{text}+ where \emph{URL} is the URL to
which you want the link to point, and \emph{text} is the text you
want to be highlighted, which when clicked upon will bring up the
desired web page. \LaTeX\ appears to have problems dealing with
the cross-references embedded within the \texttt{frontmatter}
section, but the complaints appear to be harmless, and simply
pushing \LaTeX\ to run through them appears to work. We are
working on the problem -- if some \LaTeX pert figures out how to
cure it (other than the \emph{unacceptable} method of disabling
\texttt{hyperref}), we would appreciate hearing about it.


\subsection{Particulars about {\normalshape \texttt{.pdf} files}}
In addition to PostScript$^{\tiny \copyright}$ files of final
versions of papers appearing ENTCS, we also require that
\texttt{.pdf} files be provided for publication online. A
\texttt{.pdf} file is viewable by Adobe's Acrobat$^{\tiny
\copyright}$ viewer, which can be configured to load
automatically within a browser. Viewing a properly formatted
\texttt{.pdf} file with Acrobat$^{\tiny \copyright}$ allows the
cross-references and links to URLs to be active. In fact, we have
decided to utilize \texttt{.pdf} files in order to take better
advantage of the web's capabilities. There are two methods for
producing \texttt{.pdf} files.

\paragraph{The \texttt{DVIPDFM} utility}
Probably the easiest method for producing acceptable
\texttt{.pdf} files is via the utility \texttt{dvipdfm}. This
utility is included in distributions of Mik\TeX, which runs on
Windows machines, but it probably needs to be added to your
te\TeX\ distribution, if you are running \LaTeX\ on a UNIX
machine. The utility and precise information about installing it
on your system can be found at the web page
\href{http://gaspra.kettering.edu/dvipdfm/}{\tt
http://gaspra.kettering.edu/dvipdfm/}. In essence, this utility
converts a \texttt{.dvi} file into a \texttt{.pdf} file. So, one
can first prepare the \texttt{.dvi} file using \LaTeX, and then
apply the utility \texttt{dvipdfm} to produce the needed
\texttt{.pdf} file.\footnote{ \emph{Beware}! The utility
\texttt{dvipdf} does \emph{not} produce acceptable \texttt{.pdf}
files, and should not be used. Only \texttt{dvipdfm} should be
used to produce \texttt{.pdf} files.} This utility makes
inclusion of graphics particularly simple -- those that are
included in the \LaTeX\ source file are simply converted to the
\texttt{.pdf} format. As we note below, things are not so simple
with the second alternative, which is to use pdf\LaTeX.

\paragraph{pdf\LaTeX}
An alternative to using \texttt{dvipdfm} to produce \texttt{.pdf}
files is to process the source file with pdf\LaTeX. This format is
available from the standard CTAN sites
\href{http://www.ctan.org}{\tt http://www.ctan.org}. It appears
that pdf\LaTeX\ and \texttt{hyperref} have some problems when
used together. It is necessary to use pdf\LaTeX\ version 14d or
later in order to minimize these issues. If your system has an
earlier version (most te\TeX\ distributions have version 13d),
then you can update your system by retrieving the latest version
of pdf\LaTeX\ from
\href{ftp://ftp.cstug.cz/pub/tex/local/cstug/thanh/pdftex/}{\tt
ftp://ftp.cstug.cz/pub/tex/local/cstug/thanh/pdftex/}. Even if
the recent versions are used, pdf\LaTeX\ has the same dealing
with references embedded with the \texttt{frontmatter} section
described above for \LaTeX.

There is one aspect of using pdf\LaTeX\ that bears mention. Many
authors want to include EPS\footnote{EPS stands for \emph{embedded
    PostScript}, which affords a mechanism for including pre-prepared
  PostScript files within a \LaTeX\ document.} files within their
papers. While this is fairly straightforward with \LaTeX, there are a
couple of points to note when attempting this with pdf\LaTeX.

To include a PostScript image in a \texttt{.pdf} file produced
with pdf\LaTeX, you first have to convert the image to a
\texttt{.pdf} file, and then it can be included using the same
command sequence as above. The conversion can be accomplished
most easily using Ghostscript; you can simply view the file in
Ghostview and then print the image to a \texttt{.pdf} file using
the \verb+pdfwriter+ option within Ghostview. The result for a
standard chess board that is part of the Ghostview distribution
is the following image:

\begin{center}
  \includegraphics[height=3truein,width=3truein]{chess.eps}
\end{center}

Here as well is a copy of a color image. While pdf\LaTeX\ can
handle image files in other formats, \LaTeX\ can only handle
\texttt{.eps} images reliably.

\begin{center}
  \includegraphics[height=3.5truein,width=3truein]{tigre.eps}
\end{center}

It also should be noted that you need to have two separate source
files -- one for \LaTeX\ and one for pdf\LaTeX\ -- \emph{only} in case
you wish to insert graphics images in your final paper. If your paper
does not include such images, then the same source file can be
formatted by both \LaTeX\ and by pdf\LaTeX.

Some versions of \texttt{xdvi} can view PostScript files, but often it
is necessary to convert the \texttt{.dvi} file to a PostScript file in
order to view such images. Even for those versions of \texttt{xdvi}
that support embedded PostScript images, the files themselves are
binary, and hence can suffer corruption when transferred over the net.
Moreover, Ghostview does not support active links at this time, so the
advantages of the \texttt{hyperref} package are lost in this case.
This explains why we are moving to \texttt{.pdf} files for ENTCS.

\section{Summary}  The ENTCS macro package should be easy to use
and should provide a uniform layout for all the papers in the
Proceedings.

\begin{problem}
  Finish your paper and get it to your Program Chairman on time!
\end{problem}

When you have finished preparing your paper, send a copy of the
\emph{source file}, together with any macro files that are needed to
your Program Chairman.  If the files are extensive, you can place
copies in the \texttt{pub/incoming} sub-directory of the ftp directory
on the machine indicated by your Program Chairman using anonymous ftp.
If you do this, please send me email to alert me that the file(s) are
here.

\section{Bibliographical references}\label{references}
ENTCS employs the \texttt{plain} style of bibliographic references in
which references are listed in alphabetical order, according the the
first author's last name, and are sequentially numbered. Please
utilize this style. We have a Bib\TeX\ style file, for those who wish
to use it. It is the file \texttt{entcs.bst} which can be found in the
directory containing the macro files for ENTCS. The basic rules we
have employed are the following:
\begin{itemize}
\item Authors' names should be listed in alphabetical order, with the
  first author's last name being the first listing, followed by the
  author's initials or first name, and with the other
  authors names listed as \emph{first name, last name}.
\item Titles of articles in journals should be in \emph{emphasized} type.
\item Titles of books, monographs, etc.\ should be in quotations.
\item Journal names should be in plain roman type.
\item Journal volume numbers should be in boldface type, with the year
  of publication immediately following in roman type, and enclosed in
  parentheses.
\item References to URLs on the net should be ``active'' and the URL
  itself should be in typewriter font.
\item Articles should include page numbers.
\end{itemize}
These are illustrated in the following.

\begin{thebibliography}{10}\label{bibliography}
\bibitem{cy} Civin, P., and B. Yood, \emph{Involutions on Banach
    algebras}, Pacific J. Math. \textbf{9} (1959), 415--436.

\bibitem{cp} Clifford, A. H., and G. B. Preston, ``The Algebraic
  Theory of Semigroups,'' Math. Surveys \textbf{7}, Amer. Math. Soc.,
  Providence, R.I., 1961.

\bibitem{f} Freyd, Peter, Peter O'Hearn, John Power, Robert Tennent
  and Makoto Takeyama, \emph{Bireflectivity}, Electronic Notes in
  Theoretical Computer Science {\bf 1} (1995), URL:
  \href{http://www.elsevier.nl/locate/entcs/volume1.html}
  {\texttt{http://www.elsevier.nl/locate/entcs/volume1.html}}.

\bibitem{em2} Easdown, D., and W. D. Munn, \emph{Trace functions on
    inverse semigroup algebras}, U. of Glasgow, Dept. of Math.,
  preprint 93/52.


\bibitem{r} Roscoe, A. W., ``The Theory and Practice of Concurrency,''
  Prentice Hall Series in Computer Science, Prentice Hall Publishers,
  London, New York (1198), 565pp. With associated web site
  \href{http://www.comlab.ox.ac.uk/oucl/publications/books/concurrency/}
  {\texttt{http://www.comlab.ox.ac.uk/oucl/} \texttt{
      publications/books/concurrency/}}.

\bibitem{s} Shehadah, A. A., ``Embedding theorems for semigroups with
  involution, `` Ph.D.  thesis, Purdue University, Indiana, 1982.

\bibitem{w} Weyl, H., ``The Classical Groups,'' 2nd Ed., Princeton U.
  Press, Princeton, N.J., 1946.

\end{thebibliography}

\end{document}
