summaryrefslogtreecommitdiff
path: root/Build/source/texk/ttf2pk/dvidrv.doc
blob: f1ecc5b43cc763f7d34708c9103c7acbc63b27e7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
Using dvidrv.btm [emTeX for DOS and OS/2]
-------------------------------------------

This batch file does the same as MakeTeXPK does; it is a replacement for
dvidrv.exe of emTeX which can handle ttf2pk, hbf2gf, and ps2pk additionally
(the ps2pk part is untested yet; it uses ps2pkmfj of the 4allTeX
distribution and was basically copied from a similar script, also part of
4allTeX).

First of all, create and install a set of TFM files as described in the
previous section.

Then configure the following variables in dvidrv.btm:

    ps2pk       ... set it to `yes' if you want to use this program
    ttf2pk      ... ditto
    hbf2gf      ... ditto

    pkdir       ... the place where PK files created by ps2pk, ttf2pk,
                    or hbf2gf should go to. dvidrv.btm adds
                    `\modeless\XXXdpi' resp. `\modeless\dpiXXX' to this
                    string (depending on the variables `pre_dpi' and
                    `post_dpi')

    ttfonts     ... where the TrueType fonts files reside
    ttfcfg      ... where the auxiliary data files of ttf2pk reside

    hbfonts     ... where the HBF files reside
    hbfcfg      ... the place where the hbf2gf configuration files are

The last four variables in the above list support trailing `!' and `!!' for
recursive directory searching (see the dvidrv.doc of the emTeX package for
details).

Alternatively, you can set these variables in the environment; please note
that no spaces are allowed before and after the equal sign, e.g.

  set foo=bar

is OK, but

  set foo = bar

will fail.

Rename dvidrv.exe to dvidrv.ori or something similar and copy dvidrv.btm to
a directory in the path.

Don't forget to update the DVIDRVFONTS and TEXTFM environment variables if
necessary.

Under OS/2 dvips will call mfjob or hbf2gf itself; under DOS it will create
a batch file which must be called afterwards.


--- end of dvidrv.doc ---