% 00inst.txt
%
% (c) Copyright 1995, 1996 J"org Knappen
%
% This file is part of dcfonts version 1.3
%
% 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

Running TeX on dcstdedt and tcstdedt also generates a batch file in the
style of missfont.log. You may edit the line starting with \BatchFile
to get the appropriate result for your operating system.

2) Run plain 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 dump dxbase first and to call 
METAFONT with dxbase preloaded. Use the file dxbase.ini_mf to generate
a base file in this case. 

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/jknappen/dc/

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>/jknappen/dc/<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 automatic font generation 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/jknappen/dc

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

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

8) Hints and possible problems

a) Problems with font generation

You need an up-to-date installation of METAFONT (at least version 2.0, 
current is 2.718), plain.mf (version 2.71 is required, 2.0 does not work)
modes.mf (3.0 is required, if you want to generate the dc fonts for a 
write-white device) to generate the dc and tc fonts successfully. 

dxbase checks for the most common errors and gives an error message.


b) Installation under LaTeX

Note that the LaTeX format preloads some fonts. In order to use the 
new fonts under LaTeX2e, you'll need to regenerate the LaTeX format after 
installing the fonts.

c) Write-white devices

The handling of write-white devices with older modes (distributed in 
modes.mf 2.*) was incompatible with dxbase. Get modes.mf 3.0 if you
have a write-white device for which you want to generate the dc fonts.

d) Conflicting versions of the dc fonts

It is strongly recommended that you delete all older versions of the dc 
fonts after backing them up. 

Some times, you may have documents in dvi format with older dc fonts, but 
no TeX source available, in this case you can use generally the new dc 
fonts without too much problems (of course, checksum errors occur).

If you still have very old versions, the following correspondences beetween
old and new names hold:

old:    new:          old:        new:
...5    ...0500       dccsc...    dccc...
...6    ...0600       dcbxti...   dcbi...
...7    ...0700       dctcsc...   dctc...
...8    ...0800       dcvtt...    dcvt...
...9    ...0900       dcsltt...   dcst...
...10   ...1000       dcdunh...   dcdh...
...12   ...1200       dcssbx...   dcsx...
...14   ...1440       dcssi...    dcsi...
...17   ...1728       dcbom...    dcbm...
                      dcitt...    dcit...

--J"org Knappen