diff options
author | Karl Berry <karl@freefriends.org> | 2009-08-16 23:33:14 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2009-08-16 23:33:14 +0000 |
commit | 1d678c9b24a56c664c9c27a350038656c8b49073 (patch) | |
tree | 56e390ac04c7958d1361e281649989f8355c6e06 /Master/texmf/scripts | |
parent | d0d7124586683746bbc2a57dc417b86eac77f341 (diff) |
support disabling of maps/formats/hyphenations in local conf files
git-svn-id: svn://tug.org/texlive/trunk@14715 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf/scripts')
-rwxr-xr-x | Master/texmf/scripts/texlive/tlmgr.pl | 58 |
1 files changed, 41 insertions, 17 deletions
diff --git a/Master/texmf/scripts/texlive/tlmgr.pl b/Master/texmf/scripts/texlive/tlmgr.pl index 5728eec155c..fca9a6b8668 100755 --- a/Master/texmf/scripts/texlive/tlmgr.pl +++ b/Master/texmf/scripts/texlive/tlmgr.pl @@ -4347,29 +4347,53 @@ Live installer and C<tlmgr> routinely call I<generate> for them. For C<updmap>, however, neither the installer nor C<tlmgr> use C<generate>, because the result would be to disable all maps which have been manually installed via S<C<updmap-sys --enable>>, e.g., for -proprietary or local fonts. Only the changes in the C<--localcfg> file -mentioned below are incorporated by I<generate>. Furthermore, C<tlmgr> -updates and maintains the final C<updmap.cfg> in C<TEXMFSYSCONFIG> (the -others use C<TEXMFSYSVAR>) because that is the location that -C<updmap-sys> (via C<tcfmgr>) uses. +proprietary or local fonts. The I<generate> action only incorporates +the changes in the C<--localcfg> file mentioned below. Furthermore, +C<tlmgr> updates and maintains the final C<updmap.cfg> in +C<TEXMFSYSCONFIG> (while the other files are in C<TEXMFSYSVAR>), because +that is the location that C<updmap-sys> (via C<tcfmgr>) uses. Notwithstanding the above, if you only use the fonts and font packages -within TeX Live, and maintain your local fonts (if any) with the local -config file, there is nothing wrong with using C<generate updmap>. -Indeed, we use it ourselves to generate the C<updmap.cfg> file that is -maintained in the live source repository. +within TeX Live, and maintain your local fonts (if any) using +C<updmap-local.cfg>, there is nothing wrong with using C<generate +updmap>. Indeed, we use it ourselves to generate the C<updmap.cfg> file +that is maintained in the live source repository. In more detail: C<generate> remakes any of the four config files C<language.dat>, C<language.def>, C<fmtutil.cnf>, and C<updmap.cfg> from -the information present in the local TLPDB. If the files -C<language-local.dat>, C<language-local.def>, C<fmtutil-local.cnf>, or -C<updmap-local.cfg> are present under C<TEXMFLOCAL> in the respective -directories, their contents will be simply merged into the final files, -with no error checking of any kind. +the information present in the local TLPDB, plus locally-maintained +files. + +The locally-maintained files are C<language-local.dat>, +C<language-local.def>, C<fmtutil-local.cnf>, or C<updmap-local.cfg>, +searched for in C<TEXMFLOCAL> in the respective directories. If they +are present, the final file is made by starting with the main file, +omitting any entries that the local file specifies to be disabled, and +finally appending the local file. + +Local files specify entries to be disabled with a comment line like this: + + #!NAME + %!NAME + +where C<fmtutil.cnf> and C<updmap.cfg> use C<#>, and C<language.dat> and +C<language.def> use C<%>. In any case, the I<name> is the respective +format name, map file name (include the C<.map> extension),or +hyphenation pattern identifier. Examples: + + #!pdflatex + #!lm.map + %!german + +(Of course, you're not likely to actually want to disable those +particular items. They're just examples.) + +After such a disabling line, the local file can include another entry +for the same item, if a different definition is desired. The form C<generate language> recreates both the C<language.dat> and the -C<language.def> files, while the forms with extension only recreates -the given file. +C<language.def> files, while the forms with extension recreates only +the given language file. Options: @@ -4423,7 +4447,7 @@ Currently this option only applies to the L<update|/"update "end-of-updates" other output from post actions, not in machine readable form -The header section current has two fields: C<location-url> (the +The header section currently has two fields: C<location-url> (the repository source from which updates are being drawn), and C<total-bytes> (the total number of bytes to be downloaded). |