\documentclass[fleqn]{baskrep}

%\def\dings{\par\hrule\par}
%\let\Dings\dings

\BASKvol{7}
\BASKno{1}
\BASKed*{Kaveh Bazargan}% * for Guest editor
\BASKyear{1997}
\BASKmonth{September}
% Things this paper definitely needs
\usepackage{xspace}
\usepackage{relsize}
\usepackage{fancyvrb,amstext}
%\newcommand\ftp{\textsf{ftp}\xspace}
%\DeclareRobustCommand\cs[1]{\texttt{\char`\\#1}}
%
%\def\url#1{\texttt{#1}}

%\def\LyX{L\kern-.1667em\lower.25em\hbox{Y}\kern-.125emX\spacefactor1000}%

\begin{document}

  \begin{frontmatter}
    \section{Editorial}
We had fun trying to output this issue together. Because of the very nature
of Baskerville, being written by the {\TeX}perts, and pushing {\TeX} to its
limits, it is not the simplest publication to handle. Now we all like to do
things in the most elegant way possible but, having run a production
environment for a few years, we have learned to use the quick and dirty
method when it works. I thought some notes on the production of this issue
might be of interest. 

The work was done using Textures on a Power Computing Macintosh clone. The
initial problem came from (of all places) fonts. Textures uses a system of
font management different to other machines (in itself no bad thing). A
version of the Baskerville class file had to be chosen from the several that
were offered/located (actually a \verb|diff| was performed on them and the most
likely looking candiates were pinched into one big, mutated, class file---it
worked, so who are we to complain). Things went smoothly until Sebastian's
MetaPost article where the use of \verb|%*Font|, dvips specific, commands meant
that the \verb|.eps| files needed to be modified to run under Textures. The
following lines where added. (This is not a general solution and can be
quite dangerous, but it was quick.)
\begin{verbatim}
/cmsy10 /CMSY10 def
/cmr10  /CMR10  def
/cmmi10 /CMMI10 def
/fshow {exch findfont exch scalefont setfont
        show}bind def
\end{verbatim}
What it does is to make the text \verb|cmr10|, etc active (so no phrases like
`this figure uses cmr10' are allowed) and defines the \verb|fshow| command.
Unfortunately you must have access to \emph{all} the fonts locally on your
machine as they aren't embedded into the PostScript. Obviously we could have
run MetaPost on the original source codes, by adding a \verb|prologues := 1;|
command of course, but as both methods require us to change all the files
and the latter requires an extra processing step from {\MP} so the first
method was deemed acceptable.

Jeff Kingston is the author of the batch-processing document formatter
\textsf{lout}.  His paper was written while he was on sabbatical in the
\acro{UK}, and he was happy for it to be republished in \BV{} (after
translation to \LaTeX{}, of course).  The paper is over a year old,
but Jeff welcomes comments (other than those of the form ``if you did
this in \LaTeX{}, all your problems would go away''\dots).

The paper on standard \acro{DTD}s was first published in \acro{EPSIG} News 5
number 3, September 1992, pp\,10--19.  Permission was obtained from
the three authors to republish in \BV{}.

Despite the extreme age of this paper it contains much useful comment
and observation of the problems of encoding mathematical notations.
Two appendices have been omitted: `Existing mathematical notations'
and `Comparison between \acro{ISO} \acro{TR}~9573 and \acro{AAP} Math
\acro{DTD}s'.


Good luck to the next editor!
  \end{frontmatter}

\Dings

  \input{lout}

\Dings

  \input{dtd}

%\Dings

  \input{ltour3}

\Dings

  \def\textdegree{$^{\circ}$}
  \input{rahtz}

%  \input{lyx-intro}
%  \input{lyx}
\vfill
\Dings
\vfill
\clearpage

  \input{regul}
\end{document}