1UPDMAP.CFG(20)                     TeX Live                     UPDMAP.CFG(20)
2
3
4

NAME

6       updmap.cfg  -  configuration  of  font  mapping/inclusion for dvips and
7       friends.
8

DESCRIPTION

10       The file updmap.cfg is the central font configuration file of  a  teTeX
11       system  and  is read by updmap(1). It describes if and how fonts should
12       be included (or not included) into PS-/PDF-files. This works  for  Out‐
13       line (Postscript Type1) and Bitmap Fonts (Postscript Type3) mostly com‐
14       ing from MetaFont.
15
16       updmap is a utility that creates font configuration files for dvips(1),
17       pdftex(1), xdvi(1), ps2pk(1), gsftopk(1), and dvipdfmx(1).  In an ideal
18       world, updmap would be unnecessary -- each of these programs would read
19       the  same  configuration file to learn what fonts are available and how
20       they should be treated.  As things stand, however, each of these  tools
21       has  subtly  different requirements and thereby needs its own font con‐
22       figuration file.  updmap creates font configuration files  for  all  of
23       these  programs  from  several sources, namely all updmap.cfg, allowing
24       you to easily keep all the different configuration files in sync.
25
26       Running "updmap --help" will output the main  documentation  for  using
27       updmap.
28
29       dvipsPreferOutline
30       Configures  if dvips (by default) should prefer bitmap fonts or outline
31       fonts if both are available? Independent of this setting, outlines  can
32       be  forced  by putting "p psfonts_t1.map" into a config file that dvips
33       reads. Bitmaps can be forced by putting "p psfonts_pk.map" into a  con‐
34       fig  file.  We provide such config files which can be enabled via dvips
35       -Poutline (resp. dvips -Ppk).
36       Valid settings for dvipsPreferOutline are true / false.
37
38       LW35
39       Which fonts of the "Basic 35 Laserwriter Fonts" do you want to use  and
40       how are the filenames chosen? Valid settings:
41       URW:     URW fonts with "vendor" filenames (e.g. n019064l.pfb)
42       URWkb:   URW fonts with "berry" filenames (e.g. uhvbo8ac.pfb)
43       ADOBE:   Adobe fonts with "vendor" filenames (e.g. hvnbo___.pfb)
44       ADOBEkb: Adobe fonts with  "berry" filenames (e.g. phvbo8an.pfb)
45
46       dvipsDownloadBase35
47       Configures if dvips (by default) should download the 35 base PostScript
48       fonts into the document (set true) or should these fonts be  used  from
49       the ps interpreter / printer (set false).
50       The  user  can  override  the  default by specifying dvips -Pdownload35
51       (resp. dvips -Pbuiltin35) to download the LW35  fonts  (resp.  use  the
52       built-in fonts).
53       Valid settings are true / false.
54
55       pdftexDownloadBase14
56       Should pdftex download the 14 base PDF fonts? Since some configurations
57       (ps / pdf tools / printers) use bad default fonts, it is safer to down‐
58       load the fonts. The pdf files get bigger, but that is the cost.
59       Valid  settings  are true (download the fonts) or false (don't download
60       the fonts). Adobe recommends embedding all fonts.
61
62       pxdviUse
63       Should special map files for pxdvi be created? pxdvi is an adaption  of
64       xdvi  with  support  for  reading and displaying files generated by the
65       ptex family of engines.
66       Valid  settings  are  true  (generate  configuration)  or  false.   See
67       http://www.tug.org/texlive/updmap-kanji.html for detailed discussion.
68
69       kanjiEmbed
70       kanjiVariant
71       The options kanjiEmbed and kanjiVariant specify special replacements in
72       the map lines.  In a map, the string "@kanjiEmbed@" will be replaced by
73       the  value  of  that  option; similarly for kanjiVariant.  In this way,
74       users of Japanese TeX can select different fonts to be included in  the
75       final output.
76
77       Map
78       Points  to a map file, which describes a mapping from a font (called in
79       the TeX document) to the pfb file containing the Postscript code.
80       Usage: Map filename.map
81
82       The syntax of map files is the same as dvips(1) uses, see  the  section
83       "psfonts.map" in the manual of dvips(1).
84
85       MixedMap
86       Similar  to  Map.  It  should  be used when there is Type1 and a bitmap
87       implementation of the font (the latter mostly  coming  from  MetaFont).
88       These  entries  will  not  be used in the default map of dvips if dvip‐
89       sPreferOutline is set to false.
90       Usage: MixedMap filename.map
91
92       KanjiMap
93       Similar to Map. This should be used for kanji fonts.
94       Usage: KanjiMap filename.map
95
96       The sign # precedes a comment.
97
98       Map files not to be used should be commented out using the string #! at
99       the  beginning  of  the  line. Such entries can be (de-)activated using
100       updmap with the options --enable and --disable, respectively.
101
102

AUTHOR

104       This manual page was written by  Hilmar  Preusse  <hille42@web.de>  and
105       extended  by  Norbert  Preining  <preining@logic.at>,  for  the  Debian
106       GNU/Linux system by simply copying the  comments  from  updmap.cfg  and
107       rewriting  some  of them. It may be used by other distributions without
108       contacting the author. Any mistakes or omissions in the manual page are
109       our fault; inquiries about or corrections to this manual page should be
110       directed to tex-live@tug.org.
111
112

SEE ALSO

114       updmap(1), dvips(1)
115
116

THANKS TO

118       Frank Kuester, Thomas Esser.
119
120
121
122TeX Live                         November 2012                  UPDMAP.CFG(20)
Impressum