% 00inst.txt
%
% (c) Copyright 1995 J"org Knappen
% (c) Copyright 1990, 1992 Norbert Schwarz
%
% This file is part of dcfonts version 1.2
%
% Please read the files 00readme.txt, 00inst.txt, 00error.txt, and
% copyrite.txt for further information
%
% You find some documentation in dcdoc.tex (needs LaTeX2e)
%
             How to install the dc and tc fonts


To install the dc and tc fonts from the sources, take the following steps:

1) Generate the driver files

$ tex dcstdedt
$ tex tcstdedt

There are no driver files distributed, instead they are generated by 
running plain TeX on dcstdedt.tex and tcstdedt.tex. The unchanged version
of these files gives you a standard set of Fonts, if you want other sizes
you can add them by editing dcstdedt.tex and tcstdedt.tex.

The driver files are very simple and look like:

     % This is dcr1000.mf in text format as of June, 16,  1995
     if unknown dxbase: input dxbase fi;
     gensize:=10;
     generate dcr

2) Run METAFONT on the driver files to generate the metric (tfm) files
and the generic font files (gf files).

$ mf "\mode=localfont; input dcr1000"

Running METAFONT on the driver files produces you the metric file
(suffix .tfm) and the generic font file (suffix .%%%gf, where %%% is the 
resolution of your device). Only the plain base is needed, the file dxbase 
will be loaded on demand. On small and slow machines, you may want to 
dumb dxbase first and to call METAFONT with dxbase preloaded, but this is 
not a necessary step.

Note however, that you should NOT use a METAFONT with cmbase preloaded, 
because of incompatibility.

3) Pack the generic font files

$ gftopk dcr1000.%%%gf

gftopk packs the generic font file to a packed font file, which is the 
standard form accepted by all dvi drivers. Note, that you can't create 
a .pxl file (obsolete as they are) from the dc fonts, since the pxl file
format is limited to 128 characters.

4) Copy the tfm files to a place, where TeX and the dvi-drivers find them

This place is traditionally given by the environment variable TEXFONTS
(or something similar, like TEX_FONTS). Within the proposed TeX Directory 
Structure (TDS), the proper place is

TEXMF/fonts/tfm/dcfonts/

5) Copy the pk files to a place where the dvi drivers find them

This place is traditionally given by the environment variable TEXPK
(or something similar, like TEX_PKDIR). Within the proposed TeX Directory 
Structure (TDS), the proper place is

TEXMF/fonts/pk/<device>/dcfonts/<resolution>/

(Note: There was a long and engaged dispute over the latter place. It may 
change, or local needs may enforce a different structure. Regard it as a 
suggestion, not as a prescription)

6) Put the .mf files (including the generated driver files) at a place,
where METAFONT finds them 

The rationale of this step is to allow autmatic font genration on demand,
e.g. by maketexpk or similar tools.

This place is traditionally given by the environment variable MFINPUTS
(or something similar, like MF_INPUTS). Within the proposed TeX Directory 
Structure (TDS), the proper place is

TEXMF/fonts/source/mf/dcfonts

(I have to get used to such a path. Under my VMS installation, it is simply
TEX_ROOT:[MF.DCFONTS])

7) Delete unneeded files

The following files are no longer needed and can be deleted:

*.log (on VMS: *.lis) log files
*.*gf generic font files
dcstdedt.dvi
tcstdedt.dvi

--J"org Knappen