| 1 |
% 00inst.txt |
| 2 |
% |
| 3 |
% (c) Copyright 1995, 1996, 1997 J"org Knappen |
| 4 |
% |
| 5 |
% This file is part of ecfonts version 1.0 |
| 6 |
% |
| 7 |
% Please read the files 00readme.txt, 00inst.txt, 00error.txt, and |
| 8 |
% copyrite.txt for further information |
| 9 |
% |
| 10 |
% You find some documentation in dcdoc.tex (needs LaTeX2e) |
| 11 |
% |
| 12 |
How to install the ec and tc fonts |
| 13 |
|
| 14 |
|
| 15 |
To install the ec and tc fonts from the sources, take the following steps: |
| 16 |
|
| 17 |
1) Generate the driver files |
| 18 |
|
| 19 |
$ tex ecstdedt |
| 20 |
$ tex tcstdedt |
| 21 |
|
| 22 |
There are no driver files distributed, instead they are generated by |
| 23 |
running plain TeX on ecstdedt.tex and tcstdedt.tex. The unchanged version |
| 24 |
of these files gives you a standard set of Fonts, if you want other sizes |
| 25 |
you can add them by editing ecstdedt.tex and tcstdedt.tex. |
| 26 |
|
| 27 |
The driver files are very simple and look like: |
| 28 |
|
| 29 |
% This is ecrm1000.mf in text format as of January, 19, 1997 |
| 30 |
if unknown exbase: input exbase fi; |
| 31 |
gensize:=10; |
| 32 |
generate ecrm |
| 33 |
|
| 34 |
Running TeX on ecstdedt and tcstdedt also generates a batch file in the |
| 35 |
style of missfont.log. You may edit the line starting with \BatchFile |
| 36 |
to get the appropriate result for your operating system. |
| 37 |
|
| 38 |
2) Run plain METAFONT on the driver files to generate the metric (tfm) files |
| 39 |
and the generic font files (gf files). |
| 40 |
|
| 41 |
$ mf "\mode=localfont; input ecrm1000" |
| 42 |
|
| 43 |
Running METAFONT on the driver files produces you the metric file |
| 44 |
(suffix .tfm) and the generic font file (suffix .%%%gf, where %%% is the |
| 45 |
resolution of your device). Only the plain base is needed, the file exbase |
| 46 |
will be loaded on demand. |
| 47 |
|
| 48 |
You should NOT use a METAFONT with cmbase preloaded, because of |
| 49 |
incompatibility. In fact, using cmmf on the ec fonts will stop |
| 50 |
with an error message generated. |
| 51 |
|
| 52 |
3) Pack the generic font files |
| 53 |
|
| 54 |
$ gftopk ecrm1000.%%%gf |
| 55 |
|
| 56 |
gftopk packs the generic font file to a packed font file, which is the |
| 57 |
standard form accepted by all dvi drivers. Note, that you can't create |
| 58 |
a .pxl file (obsolete as they are) from the ec fonts, since the pxl file |
| 59 |
format is limited to 128 characters. |
| 60 |
|
| 61 |
4) Copy the tfm files to a place, where TeX and the dvi-drivers find them |
| 62 |
|
| 63 |
This place is traditionally given by the environment variable TEXFONTS |
| 64 |
(or something similar, like TEX_FONTS). Within the proposed TeX Directory |
| 65 |
Structure (TDS), the proper place is |
| 66 |
|
| 67 |
TEXMF/fonts/tfm/jknappen/ec/ |
| 68 |
|
| 69 |
5) Copy the pk files to a place where the dvi drivers find them |
| 70 |
|
| 71 |
This place is traditionally given by the environment variable TEXPK |
| 72 |
(or something similar, like TEX_PKDIR). Within the proposed TeX Directory |
| 73 |
Structure (TDS), the proper place is |
| 74 |
|
| 75 |
TEXMF/fonts/pk/<device>/jknappen/ec/<resolution>/ |
| 76 |
|
| 77 |
(Note: There was a long and engaged dispute over the latter place. It may |
| 78 |
change, or local needs may enforce a different structure. Regard it as a |
| 79 |
suggestion, not as a prescription) |
| 80 |
|
| 81 |
6) Put the .mf files (including the generated driver files) at a place, |
| 82 |
where METAFONT finds them. |
| 83 |
|
| 84 |
The rationale of this step is to allow automatic font generation on demand, |
| 85 |
e.g. by maketexpk or similar tools. |
| 86 |
|
| 87 |
This place is traditionally given by the environment variable MFINPUTS |
| 88 |
(or something similar, like MF_INPUTS). Within the proposed TeX Directory |
| 89 |
Structure (TDS), the proper place is |
| 90 |
|
| 91 |
TEXMF/fonts/source/jknappen/ec |
| 92 |
|
| 93 |
(I have to get used to such a path. Under my VMS installation, it is simply |
| 94 |
TEX_ROOT:[MF.EC]) |
| 95 |
|
| 96 |
7) Delete unneeded files |
| 97 |
|
| 98 |
The following files are no longer needed and can be deleted: |
| 99 |
|
| 100 |
*.log (on VMS: *.lis) log files |
| 101 |
*.*gf generic font files |
| 102 |
ecstdedt.dvi |
| 103 |
tcstdedt.dvi |
| 104 |
|
| 105 |
8) Hints and possible problems |
| 106 |
|
| 107 |
a) Problems with font generation |
| 108 |
|
| 109 |
You need an up-to-date installation of METAFONT (at least version 2.0, |
| 110 |
current is 2.718), plain.mf (version 2.71 is required, 2.0 does not work) |
| 111 |
modes.mf (3.0 is required, if you want to generate the ec fonts for a |
| 112 |
write-white device) to generate the ec and tc fonts successfully. |
| 113 |
|
| 114 |
exbase checks for the most common errors and gives an error message. |
| 115 |
|
| 116 |
|
| 117 |
b) Installation under LaTeX |
| 118 |
|
| 119 |
Note that the LaTeX format preloads some fonts. In order to use the |
| 120 |
new fonts under LaTeX2e, you'll need to regenerate the LaTeX format after |
| 121 |
installing the fonts. The ec fonts are supported beginning with |
| 122 |
LaTeX2e from 1996/12/01. |
| 123 |
|
| 124 |
c) Write-white devices |
| 125 |
|
| 126 |
The handling of write-white devices with older modes (distributed in |
| 127 |
modes.mf 2.*) was incompatible with exbase. Get modes.mf 3.0 if you |
| 128 |
have a write-white device for which you want to generate the ec fonts. |
| 129 |
|
| 130 |
d) dc fonts |
| 131 |
|
| 132 |
It is strongly recommended that you delete all older versions of the dc |
| 133 |
fonts after backing them up. |
| 134 |
|
| 135 |
The dc fonts have had several incompatible versions, which are now finally |
| 136 |
replaced by the ec fonts. It is suggested that you regenerate your dvi |
| 137 |
files from the LaTeX source files. |
| 138 |
|
| 139 |
There are now virtual dc fonts available, reconstructing the dc fonts as |
| 140 |
virtual fonts from the ec fonts. They can be used in two ways: |
| 141 |
|
| 142 |
* To display and print dvi files containing the older dc fonts |
| 143 |
|
| 144 |
* To migrate older dvi files directly to the ec fonts, using the program |
| 145 |
dvicopy on them. |
| 146 |
|
| 147 |
|
| 148 |
--J"org Knappen |