# $Id: updmap-hdr.cfg 24398 2011-10-26 01:07:22Z preining $
# 
# The full updmap.cfg is generated by concatenating updmap-hdr.cfg with
# all the Map and MixedMap lines from an installation, possibly
# appending a local configuration file.
#
# To make local customizations to the map files, please use of the
# following methods:
#
# 1) call 
#       updmap-sys --enable Map=foo.map
#    for each map file.  (Or MixedMap instead of Map, if your font has
#    both Metafont and outline definitions.)  See the updmap --help
#    documentation.
#
# 2) add your local map entries to the file
#       TEXMFLOCAL/web2c/updmap-local.cfg
#    and then call
#       tlmgr generate updmap
#    which will concatenate updmap-local.cfg to the end of the final
#    updmap.cfg.  (You can override the local.cfg file location with the
#    --localcfg option; see tlmgr --help.)
#
# If you use either of these methods, your local adaptations will be
# preserved when tlmgr updates the installation or this config file.
# Manual edits to updmap.cfg may be lost on update.


################################################################
# OPTIONS
################################################################

#
# dvipsPreferOutline
#
# Should dvips (by default) prefer bitmap fonts or outline fonts
# if both are available? Independent of this setting, outlines
# can be forced by putting "p psfonts_t1.map" into a config file
# that dvips reads. Bitmaps (for the fonts in question) can
# be forced by putting "p psfonts_pk.map" into a config file.
# We provide such config files which can be enabled via
# dvips -Poutline ... resp. dvips -Ppk ...
#
# Valid settings for dvipsPreferOutline are true / false:
dvipsPreferOutline true

#
# LW35
#
# Which fonts for the "Basic 35 Laserwriter Fonts" do you want to use and
# how are the filenames chosen? Valid settings:
#   URW:     URW fonts with "vendor" filenames (e.g. n019064l.pfb)
#   URWkb:   URW fonts with "berry" filenames (e.g. uhvbo8ac.pfb)
#   ADOBE:   Adobe fonts with "vendor" filenames (e.g. hvnbo___.pfb)
#   ADOBEkb: Adobe fonts with  "berry" filenames (e.g. phvbo8an.pfb)
LW35 URWkb

#
# dvipsDownloadBase35
# 
# Should dvips (by default) download the standard 35 LaserWriter fonts
# with the document (then set dvipsDownloadBase35 true) or should these
# fonts be used from the ps interpreter / printer?
# Whatever the default is, the user can override it by specifying
# dvips -Pdownload35 ... resp. dvips -Pbuiltin35 ... to either download
# the LW35 fonts resp. use the built-in fonts.
#
# Valid settings are true / false:
dvipsDownloadBase35 true

#
# pdftexDownloadBase14
#
# Should pdftex download the base 14 pdf fonts? Since some configurations
# (ps / pdf tools / printers) use bad default fonts, it is safer to download
# the fonts. The pdf files will get bigger, though.
# Valid settings are true (download the fonts) or false (don't download
# the fonts). Adobe recommends embedding all fonts.
pdftexDownloadBase14 true

#
# dvipdfmDownloadBase14
#
# Should dvipdfm download the base 14 pdf fonts? Since some configurations
# (ps / pdf tools / printers) use bad default fonts, it is safer to download
# the fonts. The pdf files will get bigger, though.
# Valid settings are true (download the fonts) or false (don't download
# the fonts).
dvipdfmDownloadBase14 true

#
# kanjiEmbed
#
# updmap generates a file kanjix.map for usage with dvipdfmx. Using this
# option one can switch between not embedding any kanji font, and several
# available. 
# Valid setting is any string. At updmap run time the @kanjiEmbed@ substring
# in a map file name will be replaced with this settings, and the respective
# map file used.
kanjiEmbed noEmbed

#
# pxdviUse
# 
# This description is from 
# http://tutimura.ath.cx/ptexlive/?tlptexlive%A5%EA%A5%DD%A5%B8%A5%C8%A5%EA
# 
# Current updmap allows generation of xdvi-ptex.map (in TEXMF(SYS)VAR like 
# the other generated map files) if one sets the updmap.cfg option "pxdviUse" 
# to "true". 
# If "pxdviUse" to "true", xdvi-ptex.map is just copy of kanjix.map (a map 
# file for japanese fonts, used by dvipdfmx). Otherwise, one has to write his 
# own xdvi-ptex.map. The advantage of each setting is summerized as follows:
#   pxdviUse=true: the displaying image by pxdvi and the output pdf by 
#     dvipdfmx look similar. So, if one thinks that a pdf is the final output 
#     (and he use pxdvi only for previewing it), he should use this option.
#   pxdviUse=false: pxdvi can display fake bold fonts (with freetype) even if 
#     there is no real bold font.
# Note that no file is removed by setting "pxdviUse"; one has to remove old 
# xdvi-ptex.map. The copy of the original xdvi-ptex.map (included in the 
# pxdvi package) is located in texmf/xdvi/xdvi-ptex.map.sample.
pxdviUse true

################################################################
# Map files.
################################################################
#
# There are two possible entries: Map and MixedMap. Both have one additional
# argument: the filename of the map file. MixedMap ("mixed" means that
# the font is available as bitmap and as outline) lines will not be used
# in the default map of dvips if dvipsPreferOutline is false. Inactive
# Map files should be marked by "#! " (without the quotes), not just #.
#

