% install.tex -- how to install Malvern fonts
% Copyright 1994 P. Damian Cugley
%%% @TeX-document {
%%% filename = "install.tex",
%%% version = "X",
%%% date = "pdc 1994.09.26",
%%% package = "Malvern 1.2",
%%% author = "P. Damian Cugley",
%%% email = "damian.cugley@comlab.ox.ac.uk",
%%% address = "Oxford University Computing Laboratory,
%%% Parks Road, Oxford OX1 3QD, UK",
%%% codetable = "USASCII",
%%% keywords = "Malvern, METAFONT, font, typefont, TeX",
%%% supported = "Maybe",
%%% abstract = "Installation summary for the Malvern
%%% font family.",
%%% dependencies = "none",
%%% }
% See the Malvern Handbook (maman.tex) for more info about Malvern.
% This software is available freely but without warranty.
% See the file COPYING for details.
% This document is written in plain TeX and has NO dependencies
% other than the fonts (of course) which are all standard CM fonts.
% The hope is that this way anyone will be able to TeX this file
% without it all going horribly wrong...
% To change the paper size, change the assignments to \hsize
% and \vsize below (after the definition of \margin).
\newdimen\margin \margin=25mm % size of margins
% Change the following two lines to select a different paper size:
\hsize=210mm \advance\hsize-2\margin
\vsize=297mm \advance\vsize-2\margin
% change the following 1 line if you do have the LOGO10 font:
\newif\iflogo \logofalse
\def\package{Malvern~1.2}
\def\ttpackage{Malvern-1.2}
% Adjust \vsize to be a multiple of baselineskip + topskip:
\baselineskip=14pt
\newcount\counta
\counta=\vsize \advance\counta-\topskip
\divide\counta\baselineskip
\vsize=\counta\baselineskip \advance\vsize\topskip
\hoffset=\margin \advance\hoffset-1in
\voffset=\margin \advance\voffset-1in
%
% FONTS
%
\def\fnt#1#2{\font#1=#2 \fontdimen3#1=0pt \fontdimen4#1=0pt }
\fnt\twelverm{cmr12} \def\rm{\twelverm\fam0 }
\fnt\twelvei{cmmi12}
\fnt\twelvesy{cmsy10 at 12pt}
\fnt\twelvebf{cmb10 at 12pt} \def\bf{\twelvebf\fam\bffam}
\fnt\twelveit{cmti12} \def\it{\twelveit\fam\itfam}
\fnt\twelvett{cmtt12} \def\tt{\twelvett\fam\ttfam}
\iflogo
\fnt\twelvemf{logo10 scaled 1200} \def\mf{\twelvemf}
\fi
\fnt\twelvermc{cmcsc10 scaled 1200} \def\sc#1{{\twelvermc \lowercase{#1}}}
% Add just enough maths stuff:
\textfont0=\twelverm \scriptfont0=\tenrm \scriptscriptfont0=\sevenrm
\textfont1=\twelvei \scriptfont1=\teni \scriptscriptfont1=\seveni
\textfont2=\twelvesy \scriptfont2=\tensy \scriptscriptfont2=\sevensy
\textfont\itfam=\twelveit \scriptfont\itfam=\tenit
\textfont\ttfam=\twelvett \scriptfont\ttfam=\tentt
\fnt\titlerm{cmss17}
\fnt\headingrm{cmss12 scaled 1200}
\fnt\headingit{cmssi12 scaled 1200}
\fnt\subheadingrm{cmss12}
\fnt\subheadingit{cmssi12}
\rm
\rightskip=0pt plus 2em
\tolerance=1000
\emergencystretch=3em
%
% MACROS
%
\def\.{\mathhexbox201}
\def\{$\langle\hbox{\it #1\/}\rangle$}
\def\allcapabbrev#1{{\the\scriptfont\fam #1}}
\iflogo
\def\MF{{\mf META}\-{\mf FONT}}
\else
\def\MF{\allcapabbrev{META}\-\allcapabbrev{FONT}}
\fi
\def\fontinst{{\tt font}\-{\tt inst}}
% No blank lines after section and subsection commands!
\newcount\seccount \seccount=0
\def\section#1%
{
\medbreak
\advance\seccount1 \subseccount=0
\begingroup \headingrm \let\it=\headingit
\rightskip=0pt plus 2em
\parskip=0pt \parindent=0pt
\the\seccount\enspace #1
\nobreak\smallskip
\endgroup
\noindent\ignorespaces
}
\newcount\subseccount
\def\subsection#1%
{
\smallbreak
\advance\subseccount1
\begingroup \subheadingrm \let\it=\subheadingit
\rightskip=0pt plus 2em
\parskip=0pt \parindent=0pt
\the\seccount\sfcdot\the\subseccount\enspace #1\quad
\endgroup
\ignorespaces
}
\def\sfcdot{\leavevmode\raise0.5ex\hbox{.}}
\def\begintable
{%
$$\vbox\bgroup\halign\bgroup
##\hfil&&\quad##\hfil\cr
\noalign{\hrule height 1pt \kern2\jot}%
}
\def\endtable
{%
\crcr
\noalign{\kern1.5\jot \hrule height 1pt}%
\egroup\egroup$$
\ignorespaces
}
\def\flushtop#1%
{{%
\setbox0=\hbox{#1}\setbox1=\hbox{X}%
\dimen0=\ht1 \advance\dimen0-\ht0
\raise\dimen0\box0
}}
\def\pt{\,{\rm pt}} \mathcode`.="0201
\def\La{L\kern-0.15em\flushtop{a}}
\def\LaTeX{\La\kern-0.05em \TeX}
%
% DOCUMENT PROPER STARTS HERE
%
\leftline{\titlerm Installing Malvern fonts}
\bigskip
% Print my address:
\rightline{\vbox{\halign{\strut#\hfil\cr
P. Damian Cugley\cr
\noalign{\smallskip}%
Oxford University Computing Laboratory\cr
Parks Road\cr
Oxford \sc{OX$\mit1\ 3$QD}\cr
UK\cr
\noalign{\smallskip}%
\tt Damian.Cugley@comlab.ox.ac.uk\cr
}}}
\bigskip
(Where this document and the corresponding chapter in the {\it
Handbook} differ, this version is probably the more up-to-date.)
\section{About Malvern}
Malvern is a font family designed and implemented in \MF. It is
a sanserif font intended mainly for non-technical documents. It
does not blend particularly well with the Computer Modern fonts.
\subsection{Generic driver file}
Malvern is unusual amongst \MF\ families in that it is supplied
with one {\it generic driver file} which could in theory be used
instead of having one driver file for each size and style the
family comes in.\footnote*{The package includes a selection of
driver files nevertheless.} The generic driver file ({\tt
ma.mf}) inspects the values of variables like {\it designsize}
and {\it weight} and gives the ad-hoc parameters appropriate
values, before reading the program files. On some UNIX systems
a small program called {\tt mff} can be used to generate fonts
using this system. Otherwise other measures will have to be
taken, described below.
\subsection{Malvern encodings}
Malvern uses a nonstandard encoding -- in fact a family of
encodings, for example, Malvern~A (latin alphabets) and
Malvern~G (Greek). To create fonts for use with \LaTeX~2e and
the NFSS~2 font selection macros, use Alan Jeffrey's {\tt
fontinst} package. This generates the {\tt fd} files and
virtual fonts so that Malvern fonts may be used in the same way
as other \LaTeX~2e families. (The glyphs needed to make fonts
with the Cork (T1) encoding are in Malvern~A and Malvern~B.)
This has already been done to make a selection of styles
available with both \TeX\ Text and T1 encodings.
\subsection{Malvern font names}
The Malvern fonts generated with \MF\ will have \TeX\ names of
the following form:
$$
\hbox{\tt ma \it style enc size}
$$
where the {\it style} is a two-digit style code (described
below), {\it enc} is one- or two-letter code identifying a
Malvern encoding (such as `{\tt a}' or `{\tt az}'), and {\it
size} is the size in points (e.g., `{\tt 12}' for $12\pt$, `{\tt
17p28}' for $17.28\pt$). Thus {\tt ma55a12} (12-pt Malvern 55,
encoding~A), {\tt ma56g12} (12-pt Malvern~56, Greek encoding).
The two-letter style codes are based on Adrien Frutiger's
system, devised for the Univers family. The first digit
specifies the weight, from 1 (ultra-light) to 9 (ultra-bold),
with 5 meaning medium and 7 bold. The second digit gives the
width: 5 or 6 is normal width, 7 or 8 is compressed, 3 or 4 is
expanded. An odd number means an upright font, an even number
italic. Thus Malvern~55 is roman, Malvern~56 is italic,
Malvern~75 boldface, Malvern~68 is demibold compressed italic.
\edef\refstylecodes{\S\thinspace\the\seccount\.\the\subseccount}
The \MF\ programs are also able to generate fonts named in Karl
Berry's system,\footnote\dag{Karl Berry, {\it File Names for \TeX\
Fonts}, version 1\.6 ({\tt
file:\allowbreak//ftp.cs.umb.edu\slash pub\slash tex\slash fontname}).}
starting with `{\tt fmv}'. The correspondance between Malvern's
style digits and weight, variant and expansion letters is given
in the tables below. The encoding used for these fonts is \TeX\
text, so for example {\tt fmvr12} and {\tt ma55s12} are names
for the same font. This is so that these fonts may be used in
plain-\TeX\ and \LaTeX-2\.09 documents without too much
confusion. NFSS~2 systems (indeed, any that use non-\TeX-text
encodings) will use virtual fonts.
As of October 1994, however, the font names standard does not
allow for combinations of more than two variants (where
`variants' includes encodings and slant) without breaking the
eight-character limit required by stupid filesystems like MS-DOS
and ISO~9960. As an extreme example, Malvern~58 with the
caps-and-small-caps, old-style-numerals variation of the \TeX\
Text encoding is {\tt fmvr9ci7tc12} (12 chars). The only
temporary solution I can offer is to extend the naming scheme
used for the `{\tt ma}-' fonts to include encoding codes for the
virtual fonts needed for plain \LaTeX, NFSS and NFSS~2 (e.g.,
{\tt ma58ab12}). Therefore, the ability to create {\tt fmv}-
fonts is not being used at present.
\section{Unpacking Malvern}
The Malvern distribution includes \MF\ source files, some \TeX\
files such as this documentation, and a few other miscellaneous
files.
All files have names that should work with MS-DOS and ISO-9960
filesystems.
\subsection{Source files ({\tt/source})}
On most \TeX\ systems, \MF\ fonts end up with their source files
stored in one directory. I~suggest that Malvern instead be
given its own file area. This avoids problems with different
font families having files with the same name, and makes it easy
to replace all the Malvern files in one go if you upgrade to a
newer version of Malvern.
With a new-style directory tree,\footnote*{At the time of
writing, the \TeX\ Directory Standard (TeDiouS) is still in
discussion.\break This is my best guess based on a \TeX\ system I
recently installed.} the {\tt\ttpackage} directory may be
placed in the `{\tt texmf/fonts/public}' directory, and the {\tt
source} directory and {\tt driver} directories merged and
renamed so that \MF\ can find them.
The files {\tt mff.rc} and {\tt fmv.mff} are input files for
{\tt mff} and may be ignored if you are not using {\tt mff} to
generate fonts. If the Malvern files are being mixed in with a
bunch of others, rename {\tt mff.rc} to {\tt ma.mff}.
\subsection{Driver files ({\tt/drivers})}
Fonts can be generated by including assignments on the \MF\
command line, but driver files are more convenient (unless you
have {\tt mff}). These are also used when assignments to the
generic driver file's parameters on the \MF\ command line is
impossible, such as when using the standard {\tt MakeTeXPK}
script. A driver file is included for each {\tt tfm} supplied.
\subsection{\TeX\ input files ({\tt/tex})}
These files belong in a system-wide \TeX\ inputs area. The
files ending -{\tt.fd} are font family description files, used
by NFSS~2.
On new-style directory trees, the best approach is probably to
link or rename the {\tt texmf/fonts/public/\ttpackage/tex}
directory to {\tt texmf/tex/\ttpackage}.
\subsection{Documentation files ({\tt/doc}, {\tt/dvi})}
Files ending in `{\tt.tex}' are plain \TeX\ documents, and will
not work with \LaTeX. Compiled ({\tt dvi}) files are supplied
to save the installer having to run \TeX. Read this document,
{\tt install.tex}, first. The Greek text encoding is described
in {\tt magrman.tex}.
Please do not install any of the macro files used to typeset the
documentation in the system-wide \TeX\ inputs area. They are
not supported, not necessarily generally useful, and very
nonstandard. Earlier releases of Malvern gave the macro files
generic enough names that they might clash with other macro
files. They have been renamed to start with `{\tt pdc}' in the
hope that this will avoid clashes if they are accidentally
installed.
\subsection{Virtual font files ({\tt/vf})}
These virtual fonts are generated using Alan Jeffrey's
\fontinst\ package, and are Malvern fonts with the Cork encoding
(and some of the trickier \TeX\ Text variations). With NFSS~2
they are used by specifying encoding `{\tt T1}' and family `{\tt
fmv}'.s
The virtual fonts may have the following encoding codes:
\begintable
\it Encoding&\it Code&\it Description\cr
\noalign{\kern\jot\hrule\kern1.5\jot}
OT1c& \tt aa&
\TeX\ text with caps\&small caps\cr
OT1c9& \tt ab&
ditto, with old-style numerals\cr
T1& \tt ar&
Cork\cr
T19& \tt as&
Cork, with old style numerals\cr
T1c& \tt at&
Cork, with caps\&small caps\cr
T1c9& \tt au&
Cork, with c\&sc and o.s. numerals\cr
\endtable
For example, {\tt ma55ar12} has encoding T1. Note that
replacing lower-case letters with small-capitals counts as a
different encoding scheme rather than a `font shape'.
\subsection{Font metric files ({\tt/tfm})}
A selection of precompiled font metric files, including those
for virtual fonts in {\tt /vf} and the actual fonts needed to
use them, as well as fonts needed to print the documentation in
{\tt/dvi}.
\section{Using mff to generate Malvern fonts}
First, install {\tt mff} and arrange that \MF\ fill be able to
find the {\tt mf} files. Then to create a Malvern font, for
example 12-pt Malvern~55 ({\tt ma55a12}), give the command:
$$
\hbox{\tt mff ma55a12}
$$
To generate Malvern~55 and 56 at magsteps 0, half and 1, for 300-dpi
and 1000-dpi printers, you would type:
$$
\hbox{\tt mff --magstep=0,h,1
--dpi=300,1000 ma55a10 ma56a10}
$$
If all goes well, the {\tt tfm} and {\tt pk} files generated
will be installed in the correct directories automatically.
\section{Generating Malvern fonts without mff}
This section presumes you know how to install a normal \MF\
font.
Create a driver file for each style of Malvern you want to be
able to use. It should have the following form:
\begintable
\tt \% \ -- generate \-pt Malvern \