diff options
Diffstat (limited to 'Master/texmf-dist/doc/man/man1/updmap.1')
| -rw-r--r-- | Master/texmf-dist/doc/man/man1/updmap.1 | 196 |
1 files changed, 53 insertions, 143 deletions
diff --git a/Master/texmf-dist/doc/man/man1/updmap.1 b/Master/texmf-dist/doc/man/man1/updmap.1 index 5a7518996d8..c72ae139fec 100644 --- a/Master/texmf-dist/doc/man/man1/updmap.1 +++ b/Master/texmf-dist/doc/man/man1/updmap.1 @@ -1,60 +1,33 @@ -.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4. -.TH UPDMAP "1" "May 2017" "TeX Live" "User Commands" +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.45.1. +.TH UPDMAP "1" "May 2014" "TeX Live" "User Commands" .SH NAME updmap \- manage TeX font maps, per-user .br updmap-sys \- manage TeX font maps, system-wide .SH SYNOPSIS .B updmap -[\fI\,-user|-sys\/\fR] [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR] -.br -.B updmap-user [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR] .br .B updmap-sys [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR] .SH DESCRIPTION -updmap version r44149 (2017\-05\-02 11:57:51 +0200) +updmap version svn33988 (2014\-05\-12 15:39:32 +0900) .PP -Update the default font map files used by pdftex (pdftex.map), dvips -(psfonts.map), and dvipdfm(x), and optionally pxdvi, as determined by -all configuration files updmap.cfg (the ones returned by running -"kpsewhich \fB\-\-all\fR updmap.cfg", but see below). +Update the default font map files used by pdftex, dvips, and dvipdfm(x), +and optionally pxdvi, as determined by all configuration files updmap.cfg +(the ones returned by running "kpsewhich \fB\-\-all\fR updmap.cfg", but see below). .PP Among other things, these map files are used to determine which fonts should be used as bitmaps and which as outlines, and to determine which -font files are included, typically subsetted, in the PDF or PostScript output. +font files are included in the PDF or PostScript output. .PP -updmap\-sys (or updmap \fB\-sys\fR) is intended to affect the system\-wide -configuration, while updmap\-user (or updmap \fB\-user\fR) affects personal -configuration files only, overriding the system files. -As a consequence, once updmap\-user has been run, even a single time, +updmap\-sys is intended to affect the system\-wide configuration, while +updmap affects personal configuration files only, overriding the system +files. As a consequence, once updmap has been run, even a single time, running updmap\-sys no longer has any effect. (updmap\-sys issues a warning in this situation.) .PP -See http://tug.org/texlive/scripts\-sys\-user.html for details. -.PP By default, the TeX filename database (ls\-R) is also updated. -.PP -The updmap system is regrettably complicated, for both inherent and -historical reasons. A general overview: -.PP -\- updmap.cfg files are mainly about listing other files, namely the -.IP -font\-specific .maps, in which each line gives information about a -different TeX (.tfm) font. -.PP -\- updmap reads the updmap.cfg files and then concatenates the -.IP -contents of those .map files into the main output files: psfonts.map -for dvips and pdftex.map for pdftex and dvipdfmx. -.PP -\- The updmap.cfg files themselves are created and updated at package -.IP -installation time, by the system installer or the package manager or -by hand, and not (by default) by updmap. -.PP -Good luck. .SH OPTIONS .TP \fB\-\-cnffile\fR FILE @@ -92,9 +65,6 @@ do not run texhash \fB\-\-sys\fR affect system\-wide files (equivalent to updmap\-sys) .TP -\fB\-\-user\fR -affect personal files (equivalent to updmap\-user) -.TP \fB\-n\fR, \fB\-\-dry\-run\fR only show the configuration, no output .TP @@ -135,46 +105,20 @@ add "Map MAPFILE" to updmap.cfg disable MAPFILE, of whatever type .TP \fB\-\-listmaps\fR -list all maps (details below) +list all active and inactive maps .TP \fB\-\-listavailablemaps\fR -list available maps (details below) +same as \fB\-\-listmaps\fR, but without +unavailable map files .TP \fB\-\-syncwithtrees\fR disable unavailable map files in updmap.cfg .PP -The main output: -.IP -The main output of updmap is the files containing the individual font -map lines which the drivers (dvips, pdftex, etc.) read to handle fonts. -.IP -The map files for dvips (psfonts.map) and pdftex and dvipdfmx -(pdftex.map) are written to TEXMFVAR/fonts/map/updmap/{dvips,pdftex}/. -.IP -In addition, information about Kanji fonts is written to -TEXMFVAR/fonts/map/updmap/dvipdfmx/kanjix.map, and optionally to -TEXMFVAR/fonts/map/updmap/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. -.IP -If no option is given, so the invocation is just "updmap\-user" or -"updmap\-sys", these output files are always recreated. -.IP -Otherwise, if an option such as \fB\-\-enable\fR or \fB\-\-disable\fR is given, the -output files are recreated if the list of enabled map files (from -updmap.cfg) has changed. The \fB\-\-force\fR option overrides this, -always recreating the output files. -.PP -Explanation of the map types: -.IP -The normal type is Map. -.IP -The only difference between Map and MixedMap is that MixedMap entries -are not added to psfonts_pk.map. The purpose is to help users with -devices that render Type 1 outline fonts worse than mode\-tuned Type 1 -bitmap fonts. So, MixedMap is used for fonts that are available as -both Type 1 and Metafont. -.IP +Explanation of the map types: the (only) difference between Map and +MixedMap is that MixedMap entries are not added to psfonts_pk.map. +The purpose is to help users with devices that render Type 1 outline +fonts worse than mode\-tuned Type 1 bitmap fonts. So, MixedMap is used +for fonts that are available as both Type 1 and Metafont. KanjiMap entries are added to psfonts_t1.map and kanjix.map. .PP Explanation of the OPTION names for \fB\-\-showoptions\fR, \fB\-\-showoption\fR, \fB\-\-setoption\fR: @@ -199,19 +143,10 @@ true,false (default false) .IP Whether maps for pxdvi (Japanese\-patched xdvi) are under updmap's control. .TP -jaEmbed +kanjiEmbed (any string) .TP -jaVariant -(any string) -.TP -scEmbed -(any string) -.TP -tcEmbed -(any string) -.TP -koEmbed +kanjiVariant (any string) .IP See below. @@ -242,24 +177,21 @@ 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. .IP -The options jaEmbed and jaVariant (formerly kanjiEmbed and kanjiVariant) -specify special 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 -scEmbed, tcEmbed and koEmbed respectively. +The options kanjiEmbed and kanjiVariant specify special replacements +in the map lines. If a map contains the string @kanjiEmbed@, then +this will be replaced by the value of that option; similarly for +kanjiVariant. In this way, users of Japanese TeX can select different +fonts to be included in the final output. .SH ENVIRONMENT .PP Explanation of trees and files normally used: .IP -If \fB\-\-cnffile\fR is specified on the command line (can be given multiple -times), its value(s) is(are) used. Otherwise, updmap reads all the -updmap.cfg files found by running `kpsewhich \fB\-all\fR updmap.cfg', -in the order returned by kpsewhich (which is the order of trees -defined in texmf.cnf). +If \fB\-\-cnffile\fR is specified on the command line (possibly multiple +times), its value(s) are used. Otherwise, updmap reads all the +updmap.cfg files found by running `kpsewhich \fB\-all\fR updmap.cfg', in the +order returned by kpsewhich. .IP -In either case, if multiple updmap.cfg files are found, all the maps +In any case, if multiple updmap.cfg files are found, all the maps mentioned in all the updmap.cfg files are merged. .IP Thus, if updmap.cfg files are present in all trees, and the default @@ -273,7 +205,7 @@ TEXMFSYSVAR \fI\,$TEXLIVE/YYYY/texmf\-var/web2c/updmap.cfg\/\fP TEXMFLOCAL \fI\,$TEXLIVE/texmf\-local/web2c/updmap.cfg\/\fP TEXMFDIST \fI\,$TEXLIVE/YYYY/texmf\-dist/web2c/updmap.cfg\/\fP .IP -For updmap\-user: +For updmap: TEXMFCONFIG $HOME/.texliveYYYY/texmf\-config/web2c/updmap.cfg TEXMFVAR $HOME/.texliveYYYY/texmf\-var/web2c/updmap.cfg TEXMFHOME \fI\,$HOME/texmf/web2c/updmap.cfg\/\fP @@ -288,31 +220,25 @@ TEXMFDIST \fI\,$TEXLIVE/YYYY/texmf\-dist/web2c/updmap.cfg\/\fP According to the actions, updmap might write to one of the given files or create a new updmap.cfg, described further below. .PP -Where and which updmap.cfg changes are saved: -.IP -When no options are given, the updmap.cfg file(s) are only read, not -written. It's when an option \fB\-\-setoption\fR, \fB\-\-enable\fR or \fB\-\-disable\fR is -specified that an updmap.cfg needs to be updated. In this case: -.IP -1) If config files are given on the command line, then the first one -given is used to save any such changes. +Where changes are saved: .IP -2) If the config files are taken from kpsewhich output, then the -algorithm is more complex: +If config files are given on the command line, then the first one +given will be used to save any changes from \fB\-\-setoption\fR, \fB\-\-enable\fR +or \fB\-\-disable\fR. If the config files are taken from kpsewhich output, +then the algorithm is more complex: .IP -2a) If \fI\,$TEXMFCONFIG/web2c/updmap.cfg\/\fP or \fI\,$TEXMFHOME/web2c/updmap.cfg\/\fP +1) If \fI\,$TEXMFCONFIG/web2c/updmap.cfg\/\fP or \fI\,$TEXMFHOME/web2c/updmap.cfg\/\fP appears in the list of used files, then the one listed first by kpsewhich \fB\-\-all\fR (equivalently, the one returned by kpsewhich updmap.cfg), is used. .IP -2b) If neither of the above two are present and changes are made, a +2) If neither of the above two are present and changes are made, a new config file is created in \fI\,$TEXMFCONFIG/web2c/updmap.cfg\/\fP. .IP -In general, the idea is that if the user cannot write to a given -config file, a higher\-level one can be used. That way, the -distribution's settings can be overridden system\-wide using -TEXMFLOCAL, and system settings can be overridden again in a -particular user's TEXMFHOME. +In general, the idea is that if a given config file is not writable, a +higher\-level one can be used. That way, the distribution's settings +can be overridden for system\-wide using TEXMFLOCAL, and then system +settings can be overridden again for a particular using using TEXMFHOME. .PP Resolving multiple definitions of a font: .IP @@ -332,12 +258,8 @@ writing, e.g., or .IP #! MixedMap mapname.map -.TP -in the higher\-priority updmap.cfg file. -(The #! must be at the .IP -beginning of the line, with at least one space or tab afterward, and -whitespace between each word on the list.) +in the higher\-priority updmap.cfg file. .IP As an example, suppose you have a copy of MathTime Pro fonts and want to disable the Belleek version of the fonts; that is, @@ -350,26 +272,16 @@ Map mt\-yy.map .IP and call updmap. .PP -Listing of maps: -.IP -The two options \fB\-\-listmaps\fR and \fB\-\-listavailablemaps\fR list all maps -defined in any of the updmap.cfg files (for \fB\-\-listmaps\fR), and -only those actually found on the system (for \fB\-\-listavailablemaps\fR). -The output format is one line per font map, with the following -fields separated by tabs: map, type (Map, MixedMap, KanjiMap), -status (enabled, disabled), origin (the updmap.cfg file where -it is mentioned, or 'builtin' for the three basic maps). -.IP -In the case of \fB\-\-listmaps\fR there can be one additional fields -(again separated by tab) containing '(not available)' for those -map files that cannot be found. +updmap writes the map files for dvips (psfonts.map) and pdftex +(pdftex.map) to the TEXMFVAR/fonts/map/updmap/{dvips,pdftex}/ +directories. +.PP +The log file is written to TEXMFVAR/web2c/updmap.log. .PP -updmap\-user vs. updmap\-sys: -.IP When updmap\-sys is run, TEXMFSYSCONFIG and TEXMFSYSVAR are used -instead of TEXMFCONFIG and TEXMFVAR, respectively. This is the -primary difference between updmap\-sys and updmap\-user. -.IP +instead of TEXMFCONFIG and TEXMFVAR, respectively. This is the only +difference between updmap\-sys and updmap. +.PP Other locations may be used if you give them on the command line, or these trees don't exist, or you are not using the original TeX Live. .PP @@ -377,11 +289,9 @@ To see the precise locations of the various files that will be read and written, give the \fB\-n\fR option (or read the source). .SH EXAMPLES .PP -The log file is written to TEXMFVAR/web2c/updmap.log. -.PP For step\-by\-step instructions on making new fonts known to TeX, read http://tug.org/fonts/fontinstall.html. For even more terse -instructions, read the beginning of the main updmap.cfg file. +instructions, read the beginning of the main updmap.cfg. .SH FILES Configuration and input files: .IP "\fIupdmap\&.cfg\fP" @@ -459,6 +369,6 @@ of \fIpsfonts\&.map\fP\&. Loads \fIpsfonts_t1\&.map\fP instead of \fIpsfonts\&.map\fP\&. .SH "REPORTING BUGS" -Report bugs to: tex\-live@tug.org +Report bugs to: tex\-k@tug.org .br TeX Live home page: <http://tug.org/texlive/> |