Installing Type I fonts in Windows XP

[Ulrich Dirr]

David Ireland wrote:
> This is my understanding of how it should work:
>
> My document.tex is structured
> \documentclass{book}
> \usepackage{pnb}  %To specify the font to be used throughout
> \begin{document} Text....
> \end{document}

You missed something like \usepackage[LY1]{fontenc} before loading
pnb.sty (below you define that your Baskerville fonts have LY1
encoding, therefore TeX should know this too).

> which looks at the font definition file (copied from the Y&Y CD)
> ly1pnb.fd: %%%%%%%%%%%%
> \ProvidesFile{ly1pnc.fd}
>    [1997/02/26  LY1/pnc (NewBaskerville) with Karl Berry file names.
> (LV)] \DeclareFontFamily{LY1}{pnb}{}
> \DeclareFontShape{LY1}{pnb}{m}{n}{<-> pnbr8y}{}
> \DeclareFontShape{LY1}{pnb}{m}{it}{<-> pnbri8y}{}
> \DeclareFontShape{LY1}{pnb}{b}{n}{<-> pnbb8y}{}
> \DeclareFontShape{LY1}{pnb}{b}{it}{<-> pnbbi8y}{}
> % We silently treat bold extended as bold
> \DeclareFontShape{LY1}{pnb}{bx}{n}{<->ssub * pnb/b/n}{}
> \DeclareFontShape{LY1}{pnb}{bx}{it}{<->ssub * pnb/b/it}{} \endinput
> %%%%%%%%%%%%%%
>
> Now, I have files pnbr8[x].fd, where x = t, c or r but not y.  Can I
> convert them into 'y's and, if so, will this mean that ly1pnb.fd
will
> find the files and my DVI file will look all lovely in New
> Baskerville?   (DVI font encoding set to TeXnANSI, hence the need
for
> 'y' files)

Your're probably confused here. The file ly1pnc.fd should be enough
unless you want osf/sc. The pnbr8[x].fd files are in principle the
same as ly1pnc.fd---just with another encoding (the file names reflect
the Berry nameing scheme, look at the doc for fontname if you want to
get the whole picture).

But what the hell does, e.g., \DeclareFontShape{LY1}{pnb}{m}{n}{<->
pnbr8y}{} mean?
You tell TeX to use 'LY1' encoding, 'pnb' as font family, 'm' as font
series (medium I presume), 'n' as font shape. And for the
metrics---which TeX needs to do the actual typesetting---look at
pnbr8y.tfm ('<->' is for all sizes in contrast to, e.g., <8-12>). You
can also do other fancy things here, which is all described in detail
in the LaTeX companion or in fntguide.[dvi/pdf] from the base LaTeX
distribution.

> One other point; the files provided by Adobe were of the form NBR,
> NBI, NBBR, NBBI, but I don't have atm files with 'pnb' names. Should
> there be? Or do I somehow need to link the NB* files to pnb ones?
>
> And where do the afm, pfm, pfb and tfm files come in to all this?
> Are they all to enable DVIWindo to display the fonts correctly?

With the above in mind it should now be clear that TeX is looking for
pnb*8y.tfm files but the actual fonts (the pfm and pfb) which DVIWindo
needs (and which are installed with ATM or OS) have NB*.[pfm/pfb] file
names. These should be consistent.

Summary: In your TeX file you select a font encoding and a font
family. TeX then needs TFM ('TeX font metrics') files for typesetting.
Your output device (DVIWindo/DVIPSONE etc.) needs the 'real' font
(normally the pfm ('printer font metrics') and pfb ('printer font
binary') files) for displaying/printing. The PFMs are more or less the
same for windows as TFM files are for TeX, whereas PFB files have the
actual character descriptions inside (in Type-1 format). The AFM
('Adobe Font Metric') is just an ASCII (human readable) file with
metrics and kerning information inside. It's used for generation of
TFM files.

Best regards,
Ulrich Dirr