{
    "mode": "man",
    "parameter": "updmap-sys",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/updmap-sys/1/json",
    "generated": "2026-06-03T01:22:48Z",
    "synopsis": "updmap [-user|-sys] [OPTION] ... [COMMAND]\nupdmap-user [OPTION] ... [COMMAND]\nupdmap-sys [OPTION] ... [COMMAND]",
    "sections": {
        "NAME": {
            "content": "updmap - manage TeX font maps\nupdmap-sys - manage TeX font maps, system-wide\nupdmap-user - manage TeX font maps, per-user\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "updmap [-user|-sys] [OPTION] ... [COMMAND]\nupdmap-user [OPTION] ... [COMMAND]\nupdmap-sys [OPTION] ... [COMMAND]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "updmap version r59152 (2021-05-09 23:49:52 +0200)\n\nUpdate  the  default  font  map  files used by pdftex and dvipdfm(x) (pdftex.map), dvips (ps‐\nfonts.map), and optionally pxdvi, as determined by all configuration files  updmap.cfg  (usu‐\nally the ones returned by running \"kpsewhich --all updmap.cfg\", but see below).\n\nAmong  other things, these map files are used to determine which fonts should be used as bit‐\nmaps and which as outlines, and to determine which font files are included, typically subset‐\nted, in the PDF or PostScript output.\n\nupdmap-sys  (or  updmap  -sys) is intended to affect the system-wide configuration, while up‐\ndmap-user (or updmap -user) affects personal configuration files only, overriding the  system\nfiles.\n\nAs  a  consequence,  once updmap-user has been run, even a single time, running updmap-sys no\nlonger has any effect.  updmap-sys issues a warning about this, since it is rarely desirable.\nSee https://tug.org/texlive/scripts-sys-user.html for details.\n\nBy default, the TeX filename database (ls-R) is also updated.\n\nThe  updmap  system  is regrettably complicated, for both inherent and historical reasons.  A\ngeneral overview:\n\n- updmap.cfg files are mainly about listing other files, namely the\n\nfont-specific .maps, in which each line gives information about a different TeX (.tfm)\nfont.\n\n- updmap reads the updmap.cfg files and then concatenates the\n\ncontents  of  those  .map  files into the main output files: psfonts.map for dvips and\npdftex.map for pdftex and dvipdfmx.\n\n- The updmap.cfg files themselves are created and updated at package\n\ninstallation time, by the system installer or the package manager or by hand, and  not\n(by default) by updmap.\n",
            "subsections": []
        },
        "OPTIONS": {
            "content": "--cnffile FILE\nread FILE for the updmap configuration (can be given multiple times, in which case all\nthe files are used)\n\n--dvipdfmxoutputdir DIR\nspecify output directory (dvipdfm(x) syntax)\n\n--dvipsoutputdir DIR\nspecify output directory (dvips syntax)\n\n--pdftexoutputdir DIR\nspecify output directory (pdftex syntax)\n\n--pxdvioutputdir DIR\nspecify output directory (pxdvi syntax)\n\n--outputdir DIR\nspecify output directory (for all files)\n\n--copy cp generic files rather than using symlinks\n",
            "subsections": [
                {
                    "name": "--force",
                    "content": "recreate files even if config hasn't changed\n",
                    "long": "--force"
                },
                {
                    "name": "--nomkmap",
                    "content": "do not recreate map files\n",
                    "long": "--nomkmap"
                },
                {
                    "name": "--nohash",
                    "content": "do not run mktexlsr (a.k.a. texhash)\n\n--sys  affect system-wide files (equivalent to updmap-sys)\n\n--user affect personal files (equivalent to updmap-user)\n",
                    "long": "--nohash"
                },
                {
                    "name": "-n --dry-run",
                    "content": "only show the configuration, no output\n\n--quiet, --silent\nreduce verbosity\n",
                    "flag": "-n",
                    "long": "--dry-run"
                },
                {
                    "name": "Commands:",
                    "content": "--help show this message and exit\n"
                },
                {
                    "name": "--version",
                    "content": "show version information and exit\n\n--showoption OPTION\nshow the current setting of OPTION\n\n--showoptions OPTION\nshow possible settings for OPTION\n\n--setoption OPTION VALUE\nset OPTION to value; option names below\n\n--setoption OPTION=VALUE\nas above, just different syntax\n\n--enable MAPTYPE MAPFILE\nadd \"MAPTYPE MAPFILE\" to updmap.cfg, where MAPTYPE is Map, MixedMap, or KanjiMap\n\n--enable Map=MAPFILE\nadd \"Map MAPFILE\" to updmap.cfg\n\n--enable MixedMap=MAPFILE\nadd \"MixedMap MAPFILE\" to updmap.cfg\n\n--enable KanjiMap=MAPFILE\nadd \"KanjiMap MAPFILE\" to updmap.cfg\n\n--disable MAPFILE\ndisable MAPFILE, of whatever type\n",
                    "long": "--version"
                },
                {
                    "name": "--listmaps",
                    "content": "list all maps (details below)\n",
                    "long": "--listmaps"
                },
                {
                    "name": "--listavailablemaps",
                    "content": "list available maps (details below)\n",
                    "long": "--listavailablemaps"
                },
                {
                    "name": "--syncwithtrees",
                    "content": "disable unavailable map files in updmap.cfg\n\nThe main output:\n\nThe main output of updmap is the files containing the individual font map lines  which\nthe drivers (dvips, pdftex, etc.) read to handle fonts.\n\nThe map files for dvips (psfonts.map) and pdftex and dvipdfmx (pdftex.map) are written\nto TEXMFVAR/fonts/map/updmap/{dvips,pdftex}/.\n\nIn addition, information  about  Kanji  fonts  is  written  to  TEXMFVAR/fonts/map/up‐\ndmap/dvipdfmx/kanjix.map,      and      optionally      to      TEXMFVAR/fonts/map/up‐\ndmap/pxdvi/xdvi-ptex.map.  These are for Kanji only and are not like other map  files.\ndvipdfmx reads pdftex.map for the map entries for non-Kanji fonts.\n\nIf  no option is given, so the invocation is just \"updmap-user\" or \"updmap-sys\", these\noutput files are always recreated.\n\nOtherwise, if an option such as --enable or --disable is given, the output  files  are\nrecreated if the list of enabled map files (from updmap.cfg) has changed.  The --force\noption overrides this, always recreating the output files.\n\nExplanation of the map types:\n\nThe normal type is Map.\n\nThe only difference between Map and MixedMap is that MixedMap entries are not added to\npsfontspk.map.   The purpose is to help users with devices that render Type 1 outline\nfonts worse than mode-tuned Type 3 bitmap fonts.  So, MixedMap is used for fonts  that\nare available as both Type 1 and Metafont.\n\nKanjiMap entries are added to psfontst1.map and kanjix.map.\n\nExplanation of the OPTION names for --showoptions, --showoption, --setoption:\n\ndvipsPreferOutline\ntrue,false  (default true)\n\nWhether dvips uses bitmaps or outlines, when both are available.\n\ndvipsDownloadBase35\ntrue,false  (default true)\n\nWhether dvips includes the standard 35 PostScript fonts in its output.\n\npdftexDownloadBase14\ntrue,false   (default true)\n\nWhether pdftex includes the standard 14 PDF fonts in its output.\n\npxdviUse\ntrue,false  (default false)\n\nWhether maps for pxdvi (Japanese-patched xdvi) are under updmap's control.\n\njaEmbed\n(any string)\n\njaVariant\n(any string)\n\nscEmbed\n(any string)\n\ntcEmbed\n(any string)\n\nkoEmbed\n(any string)\n\nSee below.\n\nLW35   URWkb,URW,ADOBEkb,ADOBE  (default URWkb)\n\nAdapt the font and file names of the standard 35 PostScript fonts.\n\nURWkb  URW fonts with \"berry\" filenames    (e.g. uhvbo8ac.pfb)\n\nURW    URW fonts with \"vendor\" filenames   (e.g. n019064l.pfb)\n\nADOBEkb\nAdobe fonts with \"berry\" filenames  (e.g. phvbo8an.pfb)\n\nADOBE  Adobe fonts with \"vendor\" filenames (e.g. hvnbo.pfb)\n\nThese  options  are only read and acted on by updmap; dvips, pdftex, etc., do not know\nanything about them.  They work by changing the default map file  which  the  programs\nread,  so  they  can be overridden by specifying command-line options or configuration\nfiles to the programs, as explained at the beginning of updmap.cfg.\n\nThe options jaEmbed and jaVariant (formerly kanjiEmbed and kanjiVariant) specify  spe‐\ncial replacements in the map lines.  If a map contains the string @jaEmbed@, then this\nwill be replaced by the value of that option; similarly for jaVariant.  In  this  way,\nusers  of  Japanese TeX can select different fonts to be included in the final output.\nThe counterpart for Simplified Chinese, Traditional Chinese and Korean fonts are scEm‐\nbed, tcEmbed and koEmbed respectively.\n",
                    "long": "--syncwithtrees"
                }
            ]
        },
        "ENVIRONMENT": {
            "content": "Explanation of trees and files normally used:\n\nIf  --cnffile  is  specified  on  the  command line (can be given multiple times), its\nvalue(s) is(are) used.  Otherwise, updmap reads all the updmap.cfg files found by run‐\nning `kpsewhich -all updmap.cfg', in the order returned by kpsewhich (which is the or‐\nder of trees defined in texmf.cnf).\n\nIn either case, if multiple updmap.cfg files are found, all the maps mentioned in  all\nthe updmap.cfg files are merged.\n\nThus,  if updmap.cfg files are present in all trees, and the default layout is used as\nshipped with TeX Live on Debian, the following files are read, in the given order.\n\nFor updmap-sys:\nTEXMFSYSCONFIG /etc/texmf/web2c/updmap.cfg\nTEXMFSYSVAR    /var/lib/texmf/web2c/updmap.cfg\nTEXMFLOCAL     /usr/local/share/texmf/web2c/updmap.cfg\nTEXMFDEBIAN    /usr/share/texmf/web2c/updmap.cfg\nTEXMFDIST      /usr/share/texlive/texmf/web2c/updmap.cfg\n\nFor updmap-user:\nTEXMFCONFIG    $HOME/.texmf-config/web2c/updmap.cfg\nTEXMFVAR       $HOME/.texmf-var/web2c/updmap.cfg\nTEXMFHOME      $HOME/texmf/web2c/updmap.cfg\nTEXMFSYSCONFIG /etc/web2c/updmap.cfg\nTEXMFSYSVAR    /var/lib/texmf/web2c/updmap.cfg\nTEXMFLOCAL     /usr/local/share/texmf/web2c/updmap.cfg\nTEXMFDEBIAN    /usr/share/texmf/web2c/updmap.cfg\nTEXMFDIST      /usr/share/texlive/texmf/web2c/updmap.cfg\n\nAccording to the actions, updmap might write to one of the given files or create a new\nupdmap.cfg, described further below.\n\nWhere and which updmap.cfg changes are saved:\n\nWhen  no  options  are given, the updmap.cfg file(s) are only read, not written.  It's\nwhen an option --setoption, --enable or --disable  is  specified  that  an  updmap.cfg\nneeds to be updated.  In this case:\n\n1)  If config files are given on the command line, then the first one given is used to\nsave any such changes.\n\n2) If the config files are taken from kpsewhich output, then  the  algorithm  is  more\ncomplex:\n\n2a)  If  $TEXMFCONFIG/web2c/updmap.cfg  or  $TEXMFHOME/web2c/updmap.cfg appears in the\nlist of used files, then the one listed first by kpsewhich  --all  (equivalently,  the\none returned by kpsewhich updmap.cfg), is used.\n\n2b) If neither of the above two are present and changes are made, a new config file is\ncreated in $TEXMFCONFIG/web2c/updmap.cfg.\n\nIn general, the idea is that if the user cannot  write  to  a  given  config  file,  a\nhigher-level one can be used.  That way, the distribution's settings can be overridden\nsystem-wide using TEXMFLOCAL, and system settings can be overridden again in a partic‐\nular user's TEXMFHOME or TEXMFCONFIG.\n\nResolving multiple definitions of a font:\n\nIf  a  font  is defined in more than one map file, then the definition coming from the\nfirst-listed updmap.cfg is used.  If a font is defined multiple times within the  same\nmap file, one is chosen arbitrarily.  In both cases a warning is issued.\n\nDisabling maps:\n\nupdmap.cfg  files  with higher priority (listed earlier) can disable maps mentioned in\nlower priority (listed later) updmap.cfg files by writing, e.g.,\n\n#! Map mapname.map\n\nor\n\n#! MixedMap mapname.map\n\nin the higher-priority updmap.cfg file.\n(The #! must be at the\n\nbeginning of the line, with at least one space or tab afterward,  and  whitespace  be‐\ntween each word on the list.)\n\nAs  an  example, suppose you have a copy of MathTime Pro fonts and want to disable the\nBelleek version of the fonts; that is, disable the map belleek.map.   You  can  create\nthe file $TEXMFCONFIG/web2c/updmap.cfg with the content\n\n#! Map belleek.map Map mt-plus.map Map mt-yy.map\n\nand call updmap.\n\nListing of maps:\n\nThe two options --listmaps and --listavailablemaps list all maps defined in any of the\nupdmap.cfg files (for --listmaps), and only those actually found on  the  system  (for\n--listavailablemaps).   The output format is one line per font map, with the following\nfields separated by tabs: map, type (Map, MixedMap, KanjiMap), status  (enabled,  dis‐\nabled),  origin (the updmap.cfg file where it is mentioned, or 'builtin' for the three\nbasic maps).\n\nIn the case of --listmaps there can be one additional fields (again separated by  tab)\ncontaining '(not available)' for those map files that cannot be found.\n\nupdmap-user vs. updmap-sys:\n\nWhen updmap-sys is run, TEXMFSYSCONFIG and TEXMFSYSVAR are used instead of TEXMFCONFIG\nand TEXMFVAR, respectively.  This is the primary difference between updmap-sys and up‐\ndmap-user.\n\nOther locations may be used if you give them on the command line, or these trees don't\nexist, or you are not using the original TeX Live.\n\nTo see the precise locations of the various files that will be read and written, give the  -n\noption (or read the source).\n",
            "subsections": []
        },
        "EXAMPLES": {
            "content": "The log file is written to TEXMFVAR/web2c/updmap.log.\n\nFor    step-by-step    instructions    on    making    new   fonts   known   to   TeX,   read\nhttps://tug.org/fonts/fontinstall.html.  For even more terse instructions, read the beginning\nof the main updmap.cfg file.\n",
            "subsections": []
        },
        "FILES": {
            "content": "Configuration and input files:\n\nupdmap.cfg\nMain configuration file.  In texmf-dist/web2c by default, but may be located elsewhere\ndepending on your distribution.  Each texmf tree read should have its own updmap.cfg.\n\ndvips35.map\nMap file for standard 35 PostScript fonts for use with dvips(1).\n\npdftex35.map\nMap file for standard 35 PostScript fonts for use with pdftex(1).\n\nps2pk35.map\nMap file for standard 35 PostScript fonts for use with ps2pk(1).\n\nOutput files:\n\npsfonts.map\nFor dvips(1).  Same as psfontst1.map if option dvipsPreferOutline active, else as ps‐\nfontspk.map.\n\npsfontspk.map\nFor  dvips(1).   Without information from MixedMap files.  (Setting of dvipsPreferOut‐‐\nline ignored.)\n\npsfontst1.map\nFor dvips(1).  With information from MixedMap files.  (Setting  of  dvipsPreferOutline\nignored.)\n\ndownload35.map\nFor  dvips(1).   Always  downloads  the standard 35 fonts.  (Setting of dvipsDownload‐‐\nBase35 ignored.)\n\nbuiltin35.map\nFor dvips(1).  Never downloads the standard 35 fonts.  (Setting of dvipsDownloadBase35\nignored.)\n\npdftex.map\nFor pdftex(1).  Same as pdftexdl14.map if option pdftexDownloadBase14 active, else as\npdftexndl14.map.\n\npdftexdl14.map\nFor pdftex(1).  Always downloads the standard 14 fonts.\n\npdftexndl14.map\nFor pdftex(1).  Never downloads the standard 14 fonts.\n\nps2pk.map\nSimilar to psfonts.map file, but forces all fonts to be downloaded, so this  map  file\ncan be used with xdvi(1) and ps2pk(1).\n\nConfiguration files for dvips(1):\n\nconfig.builtin35\nLoads builtin35.map instead of psfonts.map.\n\nconfig.download35\nLoads download35.map instead of psfonts.map.\n\nconfig.outline\nLoads psfontst1.map instead of psfonts.map.\n\nconfig.pdf\nLoads psfontst1.map instead of psfonts.map and has additional settings for PDF gener‐\nation.\n\nconfig.pk\nLoads psfontspk.map instead of psfonts.map.\n\nconfig.www\nLoads psfontst1.map instead of psfonts.map.  (For compatibility with old versions.)\n\nconfig.gstopk\nLoads psfontst1.map instead of psfonts.map.\n",
            "subsections": []
        },
        "REPORTING BUGS": {
            "content": "Report bugs to: tex-live@tug.org\nTeX Live home page: <https://tug.org/texlive/>\n\n\n\nTeX Live                                      May 2021                                     UPDMAP(1)",
            "subsections": []
        }
    },
    "summary": "updmap - manage TeX font maps updmap-sys - manage TeX font maps, system-wide updmap-user - manage TeX font maps, per-user",
    "flags": [
        {
            "flag": "",
            "long": "--force",
            "arg": null,
            "description": "recreate files even if config hasn't changed"
        },
        {
            "flag": "",
            "long": "--nomkmap",
            "arg": null,
            "description": "do not recreate map files"
        },
        {
            "flag": "",
            "long": "--nohash",
            "arg": null,
            "description": "do not run mktexlsr (a.k.a. texhash) --sys affect system-wide files (equivalent to updmap-sys) --user affect personal files (equivalent to updmap-user)"
        },
        {
            "flag": "-n",
            "long": "--dry-run",
            "arg": null,
            "description": "only show the configuration, no output --quiet, --silent reduce verbosity"
        },
        {
            "flag": "",
            "long": "--version",
            "arg": null,
            "description": "show version information and exit --showoption OPTION show the current setting of OPTION --showoptions OPTION show possible settings for OPTION --setoption OPTION VALUE set OPTION to value; option names below --setoption OPTION=VALUE as above, just different syntax --enable MAPTYPE MAPFILE add \"MAPTYPE MAPFILE\" to updmap.cfg, where MAPTYPE is Map, MixedMap, or KanjiMap --enable Map=MAPFILE add \"Map MAPFILE\" to updmap.cfg --enable MixedMap=MAPFILE add \"MixedMap MAPFILE\" to updmap.cfg --enable KanjiMap=MAPFILE add \"KanjiMap MAPFILE\" to updmap.cfg --disable MAPFILE disable MAPFILE, of whatever type"
        },
        {
            "flag": "",
            "long": "--listmaps",
            "arg": null,
            "description": "list all maps (details below)"
        },
        {
            "flag": "",
            "long": "--listavailablemaps",
            "arg": null,
            "description": "list available maps (details below)"
        },
        {
            "flag": "",
            "long": "--syncwithtrees",
            "arg": null,
            "description": "disable unavailable map files in updmap.cfg The main output: The main output of updmap is the files containing the individual font map lines which the drivers (dvips, pdftex, etc.) read to handle fonts. The map files for dvips (psfonts.map) and pdftex and dvipdfmx (pdftex.map) are written to TEXMFVAR/fonts/map/updmap/{dvips,pdftex}/. In addition, information about Kanji fonts is written to TEXMFVAR/fonts/map/up‐ dmap/dvipdfmx/kanjix.map, and optionally to TEXMFVAR/fonts/map/up‐ dmap/pxdvi/xdvi-ptex.map. These are for Kanji only and are not like other map files. dvipdfmx reads pdftex.map for the map entries for non-Kanji fonts. If no option is given, so the invocation is just \"updmap-user\" or \"updmap-sys\", these output files are always recreated. Otherwise, if an option such as --enable or --disable is given, the output files are recreated if the list of enabled map files (from updmap.cfg) has changed. The --force option overrides this, always recreating the output files. Explanation of the map types: The normal type is Map. The only difference between Map and MixedMap is that MixedMap entries are not added to psfontspk.map. The purpose is to help users with devices that render Type 1 outline fonts worse than mode-tuned Type 3 bitmap fonts. So, MixedMap is used for fonts that are available as both Type 1 and Metafont. KanjiMap entries are added to psfontst1.map and kanjix.map. Explanation of the OPTION names for --showoptions, --showoption, --setoption: dvipsPreferOutline true,false (default true) Whether dvips uses bitmaps or outlines, when both are available. dvipsDownloadBase35 true,false (default true) Whether dvips includes the standard 35 PostScript fonts in its output. pdftexDownloadBase14 true,false (default true) Whether pdftex includes the standard 14 PDF fonts in its output. pxdviUse true,false (default false) Whether maps for pxdvi (Japanese-patched xdvi) are under updmap's control. jaEmbed (any string) jaVariant (any string) scEmbed (any string) tcEmbed (any string) koEmbed (any string) See below. LW35 URWkb,URW,ADOBEkb,ADOBE (default URWkb) Adapt the font and file names of the standard 35 PostScript fonts. URWkb URW fonts with \"berry\" filenames (e.g. uhvbo8ac.pfb) URW URW fonts with \"vendor\" filenames (e.g. n019064l.pfb) ADOBEkb Adobe fonts with \"berry\" filenames (e.g. phvbo8an.pfb) ADOBE Adobe fonts with \"vendor\" filenames (e.g. hvnbo.pfb) These options are only read and acted on by updmap; dvips, pdftex, etc., do not know anything about them. They work by changing the default map file which the programs read, so they can be overridden by specifying command-line options or configuration files to the programs, as explained at the beginning of updmap.cfg. The options jaEmbed and jaVariant (formerly kanjiEmbed and kanjiVariant) specify spe‐ cial replacements in the map lines. If a map contains the string @jaEmbed@, then this will be replaced by the value of that option; similarly for jaVariant. In this way, users of Japanese TeX can select different fonts to be included in the final output. The counterpart for Simplified Chinese, Traditional Chinese and Korean fonts are scEm‐ bed, tcEmbed and koEmbed respectively."
        }
    ],
    "examples": [
        "The log file is written to TEXMFVAR/web2c/updmap.log.",
        "For    step-by-step    instructions    on    making    new   fonts   known   to   TeX,   read",
        "https://tug.org/fonts/fontinstall.html.  For even more terse instructions, read the beginning",
        "of the main updmap.cfg file."
    ],
    "see_also": []
}