======================================================================= Using `PostScript' fonts with DVIPS (dvipsfnt.txt) ======================================================================= Copyright (C) 1995-1996 Y&Y, Inc. All Rights Reserved The documentation that comes with DVIPS is `sparse' when it comes to instructions on using fonts in Adobe Type 1 format (also referred to as `PostScript fonts' or `ATM fonts'). First consult DVIPS.TEX, which comes with DVIPS, and DVIPS.DOC written by G. Sawade. If you have emTeX these will be in \emtex\doc\dvips\dvips.tex and \emtex\doc\dvips\dvips.doc respectively. On CTAN, look for `dvips.doc' in the tex-archive/systems/msdos/dviware/dvips/dvips558.pc directory. Section 11. `PSNFSS and DVIPS' of DVIPS.DOC, shows how complex this can be. You may find that the method discussed here is simpler --- you don't neccessarily need all those `.vf', `.map', `.tfm', `.sty', and `.fd' files. Here is what you have to do to use fonts in Adode Type 1 format with DVIPS. Short Summary: ------------- (0) Make sure you have a recent copy of DVIPS. Handling of Type 1 fonts and font encoding has changed several times over the last few years. (1) Tell DVIPS where it can find the PFB files. In the `config.ps' file, edit the line that starts with `H' (header), and add the proper path. (2) Tell DVIPS how to map TFM file names into corresponding PostScript FontNames. A good way to do this is to use p+ at the end of `config.ps' to link to any new `map' files (psfonts.lb, psfonts.mt, psfonts.ams etc). (3) If your Type 1 fonts (`PostScript fonts') are set up for a different encoding schemes than that assumed by TeX (true for anything other than the Computer Modern fonts!), then you have to tell DVIPS to reencode the fonts. (4) If your system needs `virtual fonts' to use Type 1 fonts (always true on Unix and on Macintosh) then you need the corresponding VF files. In this case you have to edit the line in `config.ps' that starts with V (virtual fonts) to add the proper path. (5) Make sure that your TFM files are set up for the encoding you are using. (6) Make sure that your TeX source code is set up for the same font encoding. Note that the LaTeX 2e PSNFSS package provides extensive support for fonts. This support includes TeX macro files such as `lucida.dtx' and `lucida.ins.' This may be *all* you need on a TeX system with strong scalable font support. On systems using virtual fonts, you will *also* need files from another part of the TeX Archive hierarchy which includes VF, TFM, FD, and other files. In these notes reference is made to various configuration files. Where these file are depends on your particular directory structure. Since there is no standardization, only general guidelines can be given. Often settings of environment variables (like TEXMF) give important clues. Setting up the psfonts.map file: -------------------------------- (1) First of all, DVIPS needs to know that a font is a Type 1 font so it will not look for a bitmapped PK font file (or try and create one!). It also needs to know the relationship between the name used for a font in TeX (i.e. the name of the TFM file) and the PostScript FontName. The mapping between these two names is given in the file `psfonts.map' (which may be in some directory like /usr/lib/texmf/dvips). This file lists TeX TFM file names and corresponding PS FontNames. e.g.: tir Times-Roman Fonts made for use with TeX (such as LucidaBright and MathTime) come with ready-made add-on files with names that typically start with `psfonts...' (psfonts.lb, psfonts.lbe, psfonts.mt, psfonts.cm, psfonts.ams, psfonts.ltx). For other fonts, file names and PS FontNames are given by the font foundry in its documentation for the font set. You can also look near the beginning of the AFM (or PFA) file for the `FontName' entry. You can add new lines for Type 1 fonts either directly to the end of an existing `psfonts.map' file, or, more conveniently, in another file that is called in at the end of the `config.ps' file, using something like: p +psfonts.lb You can append multiple files in this statement (use commas to separate). Put the `psfonts.xxx' files in the same directory as `config.ps' (2) Next --- if the font is not printer resident --- you have to ask DVIPS to actually include it in the PostScript file it produces. DVIPS can handle font files in the compact binary PFB, as well as the `ASCII' PFA format. You ask DVIPS to include the font file using `<' and the file name, e.g. tirsc Times-RomanSC