is used to generate updmap(1) Ns 's and updmap-sys(8) Ns 's site-wide configuration file, /var/lib/texmf/web2c/updmap.cfg , or the per-user configuration file, TEXMFCONFIG/web2c/updmap.cfg , from the files with names ending in located in /etc/texmf/updmap.d/ .

The base TeX packages (tetex-bin or texlive-) provide files in /etc/texmf/updmap.d/ , which define the base contents of the to-be-generated /var/lib/texmf/web2c/updmap.cfg (general settings and base fonts), or the per-user file TEXMFCONFIG/web2c/updmap.cfg . With the underlying mechanism, system administrators can disable the map files they want by commenting their entries in the appropriate files under /etc/texmf/updmap.d/ . Such changes will be preserved if the package in question is removed (not purged) and then reinstalled.

Users without local administration rights can use to merge their local configuration and an updated site-wide configuration (see below). The local configuration files, unless specified otherwise, are expected in $TEXMFCONFIG/updmap.d , (that is ~/.texmf-config/updmap.d ), and the default output file is $TEXMFVAR/web2c/updmap.cfg (in other words, ~/.texmf-var/web2c/updmap.cfg ).

Thanks to , TeX-related font packages can have their own font map files referenced in /var/lib/texmf/web2c/updmap.cfg without having to edit that file. The packages simply have to ship their map files (e.g., foo.map ) in /etc/texmf/map/dvips/ and one or more file(s) under /etc/texmf/updmap.d/ (e.g., 10foo.cfg ) referencing the map files.

concatenates all the files under /etc/texmf/updmap.d/ provided that:

•

they do not contain the following pseudo-comment: # -_- DebPkgProvidedMaps -_- or;

•

they have this pseudo-comment and are listed in a file under /var/lib/tex-common/fontmap-cfg/ , meaning that the package shipping the file is installed. The name of the file is ignored (but should be the name of the package that installed it). The file should contain the names of the files in /etc/texmf/updmap.d/ that should be enabled, without the suffix, e.g. 10foo 12bar

The first case is for configuration files added by the local system administrator. Files that contain the magic pseudo-comment should be used by Debian packages. In this case, only the base name should appear in the file: for instance, for /etc/texmf/updmap.d/10foo.cfg ; please refer to the Debian TeX Policy for details.

Filenames should begin with two digits and must have the extension The order used to process the files is obtained by running sort() with the locale (for ordinary alphanumeric characters, it corresponds to the ASCII order). The result obtained by concatenating them is stored as the new updmap.cfg . Note that updmap(1) Ns and updmap-sys(8) Ns don't care about the order of entries, the sorting is just for the user's convenience.

If you want to be able to use updmap(1) Ns 's or updmap-sys(8) Ns 's option --enable and --setoption , some further apply to the filenames used and the way entries are distributed among these files. For --setoption to work, the options (like dvipsPreferOutline ) must be kept in a file named 00updmap.cfg , either in /etc/texmf/updmap.d/ as installed by the tex-common package, or in the conf-dir you specified. If you use --enable Map some.map and there is no mention of some.map in any file in /etc/texmf/updmap.d/ (and in conf-dir , if specified), then the Map line will be introduced in a file whose name matches *local*.cfg if it exists, or 99local.cfg will be created (in conf-dir if specified). For this to work, you cannot have more than one file that matches that name, except that you can use conf-dir/*local.cfg to supersede the site-wide file in /etc/texmf/updmap.d/ .

In order to enable a Map file that already is listed in your configuration files, it must be commented with the string '#! '. This is the sort of lines that will produce - see also updmap.cfg(5) Ns . If such a line occurs in more than one file, updmap(1) Ns will fail. Again the exception is a file in conf-dir that shadows entries in a site-wide file.

Although not strictly mandatory, it is wise to keep corresponding Map entries in files with the same name in conf-dir and the site-wide dir. Otherwise, the results may seem unpredictable.

If you want a different configuration for updmap(1) Ns than the setup at your site provides, you can place changed copies of the configuration files from /etc/texmf/updmap.d/ in a directory below $TEXMFCONFIG , or create additional files there. Per default, files are looked for in $TEXMFCONFIG/updmap.d , where $TEXMFCONFIG is ~/.texmf-config unless the configuration has been changed. When you call as a user, it will produce a user-specific updmap.cfg file as follows: if files with the same name exist in both directories, the version in ~/.texmf-config/updmap.d/ will be used; files with unique names will be used from either directory.

If you want to keep your files elsewhere, specify their location with options (see below).