summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/info/kpathsea.info
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2020-03-13 17:38:53 +0000
committerKarl Berry <karl@freefriends.org>2020-03-13 17:38:53 +0000
commiteaea0d35a703f47bc759ec85ecc1533c8aacc404 (patch)
tree343d24ac887960c960257a545f84767300909154 /Master/texmf-dist/doc/info/kpathsea.info
parent3166b3e1095114d49cbef65216417c43bcd932d7 (diff)
texinfo manual updates for 2020
git-svn-id: svn://tug.org/texlive/trunk@54279 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/info/kpathsea.info')
-rw-r--r--Master/texmf-dist/doc/info/kpathsea.info353
1 files changed, 211 insertions, 142 deletions
diff --git a/Master/texmf-dist/doc/info/kpathsea.info b/Master/texmf-dist/doc/info/kpathsea.info
index d5d49858ae5..2744e1176d4 100644
--- a/Master/texmf-dist/doc/info/kpathsea.info
+++ b/Master/texmf-dist/doc/info/kpathsea.info
@@ -1,9 +1,9 @@
-This is kpathsea.info, produced by makeinfo version 6.6 from
+This is kpathsea.info, produced by makeinfo version 6.7 from
kpathsea.texi.
This file documents the Kpathsea library for path searching.
- Copyright (C) 1996-2019 Karl Berry & Olaf Weber.
+ Copyright (C) 1996-2020 Karl Berry & Olaf Weber.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
@@ -37,7 +37,7 @@ Kpathsea library
****************
This manual documents the Kpathsea library for path searching. It
-corresponds to version 6.3.1, released in March 2019.
+corresponds to version 6.3.2, released in March 2020.
* Menu:
@@ -61,8 +61,8 @@ File: kpathsea.info, Node: Introduction, Next: unixtex.ftp, Prev: Top, Up: T
1 Introduction
**************
-This manual corresponds to version 6.3.1 of the Kpathsea library,
-released in March 2019.
+This manual corresponds to version 6.3.2 of the Kpathsea library,
+released in March 2020.
The library's fundamental purpose is to return a filename from a list
of directories specified by the user, similar to what shells do when
@@ -80,7 +80,7 @@ this library:
Other software that we do not maintain also uses it.
Kpathsea is now maintained as part of the TeX Live distribution
-(<http://tug.org/texlive>), which includes several more Kpathsea-using
+(<https://tug.org/texlive>), which includes several more Kpathsea-using
programs. For information on configuration, building, installing, and
more, *note (tlbuild)::.
@@ -95,7 +95,7 @@ changes you have made, and allow anyone to modify the library source and
distribute their modifications. It does not mean you have to distribute
the source to your program using the library, although we hope you will.
See accompanying files for the text of the GNU licenses, or
-<http2://www.gnu.org/licenses>.
+<https://gnu.org/licenses>.
If you know enough about TeX to be reading this manual, then you (or
your institution) should consider joining the TeX Users Group (if you're
@@ -201,24 +201,25 @@ File: kpathsea.info, Node: unixtex.ftp, Next: Security, Prev: Introduction,
2 'unixtex.ftp': Obtaining TeX
******************************
-This is <https://tug.org/tex/unixtex.ftp>, last updated 28 November
-2017. Email <tex-k@tug.org> with comments or questions.
+This is <ftp://tug.org/tex/unixtex.ftp>, a.k.a.
+<https://tug.org/unixtex.ftp>, last updated 29 February 2020. Email
+<tex-k@tug.org> with comments or questions.
The principal free TeX distribution for Unix-like systems is TeX
Live, on the web at <http://tug.org/texlive>. The pages there describe
-many ways to acquire and.or build TeX, over the Internet or on physical
+many ways to acquire and/or build TeX, over the Internet or on physical
media, both the sources and precompiled binaries for many systems,
either standalone or as part of various operating system distributions.
- Web2c, Kpathsea, Dvips, and Dviljk are no longer released as a
-separate packages. Their sources are now maintained as part of TeX
-Live.
+ Web2c, Kpathsea, Dvips, and Dviljk, among others, are no longer
+released as a separate packages. Their sources are now maintained as
+part of TeX Live.
The host ftp.cs.stanford.edu is the original source for the files for
which Donald Knuth is directly responsible: 'tex.web', 'plain.tex', etc.
However, unless you want to undertake the project of building your TeX
-installation from scratch, it is more reliable and less work to retrieve
-these files as part of a larger package.
+system from scratch, it is more reliable and less work to retrieve these
+files as part of a larger package.
In any case, the Stanford ftp site is not the canonical source for
anything except what was created as part of Knuth's original TeX, so do
@@ -291,8 +292,8 @@ This section describes the default installation hierarchy of the
distribution. It conforms to both the GNU coding standards and the TeX
directory structure (TDS) standard. For rationale and further
explanation, please see those documents. The GNU document is available
-from <http://www.gnu.org/prep/standards>. The TDS document is available
-from <http://www.mirror.ctan.org/tds> (*note unixtex.ftp::).
+from <https://gnu.org/prep/standards>. The TDS document is available
+from <http://mirror.ctan.org/tds> (*note unixtex.ftp::).
In short, here is a skeleton of the default directory structure,
extracted from the TDS document:
@@ -374,6 +375,11 @@ This chapter describes the generic path searching mechanism Kpathsea
provides. For information about searching for particular file types
(e.g., TeX fonts), see the next chapter.
+ This section, with minor differences, has been translated into
+several other languages (Chinese, Spanish, Russian, Japanese, French,
+German, ...) as part of the TeX Live guide; see
+<https://tug.org/texlive/doc.html> for links.
+
* Menu:
* Searching overview:: Basic scheme for searching.
@@ -467,7 +473,10 @@ File: kpathsea.info, Node: Path sources, Next: Path expansion, Prev: Searchin
A search path or other configuration value can come from many sources.
In the order in which Kpathsea looks for them:
- 1. A user-set environment variable, e.g., 'TEXINPUTS'. Environment
+ 1. A command-line option such as '--cnf-line', available in
+ 'kpsewhich' and most TeX engines. *Note Path searching options::.
+
+ A user-set environment variable, e.g., 'TEXINPUTS'. Environment
variables with an underscore and the program name appended
override; for example, 'TEXINPUTS_latex' overrides 'TEXINPUTS' if
the program being run is named 'latex'.
@@ -519,11 +528,11 @@ mentions most features. The format of 'texmf.cnf' files follows:
* Comments start with '%', either at the beginning of a line or
preceded by whitespace, and continue to the end of the line. That
- is, as with most shells, a '%' in the "middle" of a value does not
- start a comment. Examples:
+ is, similar to most shells, a '%' in the "middle" of a value does
+ not start a comment. Examples:
% this is a comment
- var = a%b % but the value of var will be "a%b".
+ var = a%b % but the value of var will be "a%b"
* Blank lines are ignored.
@@ -531,7 +540,7 @@ mentions most features. The format of 'texmf.cnf' files follows:
the next line is appended. Whitespace at the beginning of
continuation lines is not ignored.
- * Each remaining line must look like
+ * Each remaining line will look like:
VARIABLE [. PROGNAME] [=] VALUE
@@ -540,20 +549,27 @@ mentions most features. The format of 'texmf.cnf' files follows:
* The VARIABLE name may contain any character other than whitespace,
'=', or '.', but sticking to 'A-Za-z_' is safest.
- * If '.PROGNAME' is present, the definition only applies if the
- program that is running is named (i.e., the last component of
- 'argv[0]' is) PROGNAME or 'PROGNAME.{exe,bat,cmd,...}'. Most
- notably, this allows different flavors of TeX to have different
- search paths.
-
- * VALUE may contain any characters except '%' and '@'. (These
- restrictions are only necessary because of the processing done on
- 'texmf.cnf' at build time, so you can stick those characters in
- after installation if you have to.) The '$VAR.PROG' feature is not
- available on the right-hand side; instead, you must use an
- additional variable (see below for example). A ';' in VALUE is
- translated to ':' if running under Unix; this is useful to write a
- single 'texmf.cnf' which can be used under both Unix and Windows.
+ * If '.PROGNAME' is present (preceding spaces are ignored), the
+ definition only applies if the program that is running is named
+ (i.e., the last component of 'argv[0]' is) PROGNAME or
+ 'PROGNAME.{exe,bat,cmd,...}'. Most notably, this allows different
+ flavors of TeX to have different search paths. The PROGNAME value
+ is used literally, without variable or other expansions.
+
+ * Considered as strings, VALUE may contain any character. However,
+ in practice most 'texmf.cnf' values are related to path expansion,
+ and since various special characters are used in expansion, such as
+ braces and commas, they cannot be used in directory names.
+
+ The '$VAR.PROG' feature is not available on the right-hand side;
+ instead, you must use an additional variable (see below for
+ example).
+
+ A ';' in VALUE is translated to ':' if running under Unix, in order
+ to have a single 'texmf.cnf' that can support both Unix and Windows
+ systems. This translation happens with any value, not just search
+ paths, but fortunately in practice ';' is not needed in other
+ values.
* All definitions are read before anything is expanded, so you can
use variables before they are defined (like Make, unlike most other
@@ -569,12 +585,31 @@ Here is a configuration file fragment illustrating most of these points:
TEXINPUTS.latex2e = $latex2e_inputs
TEXINPUTS.latex = $latex2e_inputs
- This format has obvious similarities to Bourne shell scripts--change
-the comment character to '#', disallow spaces around the '=', and get
-rid of the '.NAME' convention, and it could be run through the shell.
-However, there seemed little advantage in this, since all the
-information would have to passed back to Kpathsea and parsed there
-anyway, since the 'sh' process couldn't affect its parent's environment.
+ This format has some similarity to Bourne shell scripts--change the
+comment character to '#', disallow spaces around the '=', and get rid of
+the '.NAME' convention, and it could be run through the shell. However,
+there seemed little advantage in this, since all the information would
+have to passed back to Kpathsea and parsed there anyway, since the 'sh'
+process couldn't affect its parent's environment.
+
+ The combination of spaces being ignored before the '.' of a program
+name qualifer and the optional '=' for the assignment has an unexpected
+consequence: if the value begins with a literal '.' and the '=' is
+omitted, the intended value is interpreted as a program name. For
+example, a line 'var .;/some/path' is taken as an empty value for 'var'
+running under the program named ';/some/path'. To diagnose this,
+Kpathsea warns if the program name contains a path separator or other
+special character. The simplest way to avoid the problem is to use the
+'='.
+
+ Exactly when a character will be considered special or act as itself
+depends on the context in which it is used. The rules are inherent in
+the multiple levels of interpretation of the configuration (parsing,
+expansion, search, ...) and so cannot be concisely stated,
+unfortunately. There is no general escape mechanism; in particular, '\'
+is not an "escape character" in 'texmf.cnf' files. When it comes
+choosing directory names for installation, it is safest to avoid them
+all.
The implementation of all this is in 'kpathsea/cnf.c'.
@@ -801,7 +836,7 @@ if the path specification is, say, '$TEXMF/fonts//pk//', then files in a
subdirectory '.../pk', even if it is a leaf, are checked. The reason
cannot be explained without reference to the implementation, so read
'kpathsea/elt-dirs.c' (search for 'may descend') if you are curious.
-And if you can find a way to _solve_ the problem, please let me know.
+And if you find a way to solve the problem, please let me know.
Subdirectory expansion is implemented in the source file
'kpathsea/elt-dirs.c'.
@@ -845,8 +880,8 @@ only to differences in case.
This same problematic scenario has always existed on Windows, but for
whatever reason, it has become much more common since Apple also went to
-a case-insensitive filesystem. Hence the move to change the Kpathsea
-behavior now.
+a case-insensitive filesystem. Hence the relatively late change to the
+Kpathsea behavior.
The fallback case-insensitive search is omitted at compile-time on
Windows, where (for practical purposes) all file names are
@@ -936,7 +971,7 @@ steps:
Sorry that it's annoyingly lengthy, but implementing this inside
Kpathsea would be a lot of error-prone trouble for something that is
only useful for debugging. If your 'find' does not support '-iname',
-you can get GNU Find from <https://www.gnu.org/software/findutils>.
+you can get GNU Find from <https://gnu.org/software/findutils>.
The casefolding search is implemented in the source file
'kpathsea/pathsearch.c'. Two implementation points:
@@ -961,7 +996,7 @@ File: kpathsea.info, Node: Filename database, Next: Invoking kpsewhich, Prev:
Kpathsea goes to some lengths to minimize disk accesses for searches
(*note Subdirectory expansion::). Nevertheless, in practice searching
-each possible directory in typical TeX installations takes an
+every possible directory in typical TeX installations takes an
excessively long time.
Therefore, Kpathsea can use an externally-built "filename database"
@@ -969,8 +1004,7 @@ file named 'ls-R' that maps files to directories, thus avoiding the need
to exhaustively search the disk.
A second database file 'aliases' allows you to give additional names
-to the files listed in 'ls-R'. This can be helpful to adapt to "8.3"
-filename conventions in source files.
+to the files listed in 'ls-R'.
The 'ls-R' and 'aliases' features are implemented in the source file
'kpathsea/db.c'.
@@ -1182,6 +1216,27 @@ filename, and returns the first file found.
case-insensitive, it merely means that Kpathsea does not do any
casefolding itself.
+'--cnf-line=STR'
+ Parse STR as if it were a line in the 'texmf.cnf' configuration
+ file (*note Config files::), overriding settings in the actual
+ configuration files, and also in the environment (*note Path
+ sources::). This is implemented by making any settings from STR in
+ the environment, overwriting any value already there. Thus, an
+ extra colon in a '--cnf-line' value will refer to the value from a
+ configuration file, not a user-set environment variable.
+
+ Furthermore, any variable set from STR will also be set with the
+ program name suffix. For example, 'pdftex
+ --cnf-line=TEXINPUTS=/foo:' will set both 'TEXINPUTS' and
+ 'TEXINPUTS_pdftex' in the environment (and the value will be '/foo'
+ followed by the setting from 'texmf.cnf', ignoring any user-set
+ 'TEXINPUTS').
+
+ This behavior is desirable because, in practice, many variables in
+ the distributed 'texmf.cnf' are program-specific, and the intuitive
+ behavior is for values set on the command line with '--cnf-line' to
+ override them.
+
'--dpi=NUM'
Set the resolution to NUM; this only affects 'gf' and 'pk' lookups.
'-D' is a synonym, for compatibility with Dvips. Default is 600.
@@ -1499,8 +1554,8 @@ Kpsewhich provides some features in addition to path lookup as such:
Unix-ish system) '.:/home/karl', supposing the latter is the
current user's home directory. Note that the ';' in the source
value, as commonly used in 'texmf.cnf', has changed to a ':', as
- the normal path separator on the current system. (On a Windows-ish
- system, the ';' would remain.)
+ the normal path separator on the current system. On a Windows-ish
+ system, the ';' would remain.
'--var-value=VARIABLE'
Outputs the value of VARIABLE (a simple identifier like
@@ -1514,7 +1569,8 @@ Kpsewhich provides some features in addition to path lookup as such:
default is not changed) '1'.
Example to contrast with '--var-brace-value': 'FOO='.;~' kpsewhich
- --var-value=FOO' outputs '.;~', i.e., the same as the input value.
+ --var-value=FOO' outputs '.;~', i.e., the same as the input value,
+ on all systems.

File: kpathsea.info, Node: Standard options, Prev: Auxiliary tasks, Up: Invoking kpsewhich
@@ -1596,14 +1652,14 @@ Auxiliary tasks::).
'bltxml'
(BibLaTeXML bibliography files for Biber,
- <http://ctan.org/pkg/biber>) 'BLTXMLINPUTS' suffix '.bltxml'.
+ <https://ctan.org/pkg/biber>) 'BLTXMLINPUTS' suffix '.bltxml'.
'bst'
(BibTeX style, *note Basic BibTeX style files: (web2c)Basic BibTeX
style files.) 'BSTINPUTS'; suffix '.bst'.
'clua'
- (dynamic libraries for Lua, <http://ctan.org/pkg/luatex>)
+ (dynamic libraries for Lua, <https://ctan.org/pkg/luatex>)
'CLUAINPUTS' suffixes '.dll' and '.so'.
'cmap'
@@ -1735,7 +1791,7 @@ Auxiliary tasks::).
'ris'
(RIS bibliography files, primarily for Biber,
- <http://ctan.org/pkg/biber>) 'RISINPUTS' suffix '.ris'.
+ <https://ctan.org/pkg/biber>) 'RISINPUTS' suffix '.ris'.
'subfont definition files'
(subfont definition files) 'SFDFONTS' suffix '.sfd'.
@@ -2468,7 +2524,7 @@ library.)
different systems. You will almost certainly want to use Autoconf and
probably Automake for configuring and building your software if you use
Kpathsea; I strongly recommend using Autoconf and Automake regardless.
-They are available from <http://www.gnu.org/software>.
+They are available from <https://gnu.org/software>.

File: kpathsea.info, Node: Program-specific files, Next: Programming with config files, Prev: Calling sequence, Up: Programming
@@ -2608,7 +2664,7 @@ investigation, your report should include the following:
* If the bug involved is an actual crash (i.e., core dump), it is
easy and useful to include a stack trace from a debugger (I
- recommend the GNU debugger GDB (<http://www.gnu.org/software/gdb>).
+ recommend the GNU debugger GDB (<https://gnu.org/software/gdb>).
If the cause is apparent (a 'NULL' value being dereferenced, for
example), please send the details along. If the program involved
is TeX or Metafont, and the crash is happening at apparently-sound
@@ -2627,7 +2683,7 @@ File: kpathsea.info, Node: Mailing lists, Next: Debugging, Prev: Bug checklis
Web2c and Kpathsea in general are discussed on the mailing list
<tex-k@tug.org>. You can subscribe and peruse the archives on the web
-<http://lists.tug.org/tex-k>.
+<https://lists.tug.org/tex-k>.
You do not need to join to submit a report, nor will it affect
whether you get a response. Be aware that large data files are
@@ -2636,7 +2692,7 @@ join the list.
If you are looking for general TeX help, such as how to install a
full TeX system or how to use LaTeX, please see
-<http://tug.org/begin.html>.
+<https://tug.org/begin.html>.

File: kpathsea.info, Node: Debugging, Next: Logging, Prev: Mailing lists, Up: Reporting bugs
@@ -2923,7 +2979,7 @@ configuration file:
the wrong device, most likely 'mktexpk''s built-in guess for the mode is
wrong, and you should override it as above.
- See <http://ctan.org/pkg/modes> for a list of resolutions and mode
+ See <https://ctan.org/pkg/modes> for a list of resolutions and mode
names for most devices (additional submissions are welcome).
If Metafont runs but generates fonts at a resolution of 2602dpi (and
@@ -2988,40 +3044,43 @@ Index
(line 12)
* --casefold-search: Path searching options.
(line 19)
+* --cnf-line: Path searching options.
+ (line 28)
+* --cnf-line, source for path: Path sources. (line 9)
* --color=tty: ls-R. (line 25)
* --debug=NUM: Auxiliary tasks. (line 9)
* --dpi=NUM: Path searching options.
- (line 28)
+ (line 49)
* --engine=NAME: Path searching options.
- (line 32)
+ (line 53)
* --expand-braces=STRING: Auxiliary tasks. (line 12)
* --expand-path=STRING: Auxiliary tasks. (line 16)
* --expand-var=STRING: Auxiliary tasks. (line 34)
* --format=NAME: Path searching options.
- (line 48)
+ (line 69)
* --help: Standard options. (line 8)
* --help-formats: Auxiliary tasks. (line 42)
* --interactive: Path searching options.
- (line 130)
+ (line 151)
* --mktex=FILETYPE: Path searching options.
- (line 135)
+ (line 156)
* --mode=STRING: Path searching options.
- (line 141)
+ (line 162)
* --must-exist: Path searching options.
- (line 146)
+ (line 167)
* --no-casefold-search: Path searching options.
(line 19)
* --no-mktex=FILETYPE: Path searching options.
- (line 135)
+ (line 156)
* --path=STRING: Path searching options.
- (line 151)
+ (line 172)
* --progname=NAME: Path searching options.
- (line 159)
+ (line 180)
* --safe-in-name=NAME: Auxiliary tasks. (line 48)
* --safe-out-name=NAME: Auxiliary tasks. (line 48)
* --show-path=NAME: Auxiliary tasks. (line 54)
* --subdir=STRING: Path searching options.
- (line 164)
+ (line 185)
* --var-brace-value=VARIABLE: Auxiliary tasks. (line 60)
* --var-value=VARIABLE: Auxiliary tasks. (line 74)
* --version: Standard options. (line 11)
@@ -3035,7 +3094,7 @@ Index
* -1 debugging value: Debugging. (line 23)
* -A option to ls: ls-R. (line 39)
* -D NUM: Path searching options.
- (line 28)
+ (line 49)
* -iname, find predicate: Casefolding examples.
(line 78)
* -L option to ls: ls-R. (line 44)
@@ -3115,6 +3174,7 @@ Index
(line 195)
* .pro: Supported file formats.
(line 169)
+* .PROGNAME qualifier in texmf.cnf: Config files. (line 50)
* .rhosts, writable by TeX: Security. (line 10)
* .ris: Supported file formats.
(line 173)
@@ -3152,6 +3212,8 @@ Index
* 8.3 filenames, using: mktex configuration. (line 68)
* : may not be :: Searching overview. (line 13)
* :: expansion: Default expansion. (line 6)
+* ; translated to : in texmf.cnf: Config files. (line 66)
+* = omitted in texmf.cnf and misparsing: Config files. (line 93)
* \, line continuation in texmf.cnf: Config files. (line 37)
* \openin: Searching overview. (line 31)
* \special, suppressing warnings about: Suppressing warnings.
@@ -3228,7 +3290,7 @@ Index
(line 46)
* cmr10, as fallback font: Fallback font. (line 15)
* cmr10.vf: Searching overview. (line 31)
-* cnf.c: Config files. (line 86)
+* cnf.c: Config files. (line 112)
* cnf.h: Programming with config files.
(line 27)
* comments, in fontmap files: Fontmap. (line 27)
@@ -3236,7 +3298,7 @@ Index
* comments, making: Introduction. (line 29)
* common features in glyph lookup: Basic glyph lookup. (line 6)
* common problems: Common problems. (line 6)
-* compilation value, source for path: Path sources. (line 20)
+* compilation value, source for path: Path sources. (line 23)
* compiler bugs: TeX or Metafont failing.
(line 6)
* compiler bugs, finding: TeX or Metafont failing.
@@ -3256,8 +3318,8 @@ Index
(line 57)
* config.status: Bug checklist. (line 27)
* configuration bugs: Bug checklist. (line 27)
-* configuration file, source for path: Path sources. (line 17)
-* configuration files as shell scripts.: Config files. (line 79)
+* configuration file, source for path: Path sources. (line 20)
+* configuration files as shell scripts.: Config files. (line 86)
* configuration of mktex scripts: mktex configuration. (line 6)
* configure options for mktex scripts: mktex configuration. (line 12)
* context diff: Bug checklist. (line 52)
@@ -3314,8 +3376,8 @@ Index
* ENCFONTS: Supported file formats.
(line 61)
* engine name: Path searching options.
- (line 32)
-* environment variable, source for path: Path sources. (line 9)
+ (line 53)
+* environment variable, source for path: Path sources. (line 12)
* environment variables for TeX: Supported file formats.
(line 6)
* environment variables in paths: Variable expansion. (line 6)
@@ -3387,7 +3449,7 @@ Index
(line 239)
* fopen, redefined: Debugging. (line 54)
* format of external database: Database format. (line 6)
-* ftp.cs.stanford.edu: unixtex.ftp. (line 19)
+* ftp.cs.stanford.edu: unixtex.ftp. (line 20)
* ftp.tug.org: unixtex.ftp. (line 6)
* fundamental purpose of Kpathsea: Introduction. (line 6)
* gdb, recommended: Bug checklist. (line 58)
@@ -3422,14 +3484,14 @@ Index
(line 84)
* input lines, reading: Calling sequence. (line 110)
* interactive query: Path searching options.
- (line 130)
+ (line 151)
* interface, not frozen: Introduction. (line 29)
* introduction: Introduction. (line 6)
* kdebug:: Debugging. (line 105)
* kdefault.c: Default expansion. (line 48)
* Knuth, Donald E.: History. (line 6)
-* Knuth, Donald E., archive of programs by: unixtex.ftp. (line 19)
-* Kpathsea config file, source for path: Path sources. (line 17)
+* Knuth, Donald E., archive of programs by: unixtex.ftp. (line 20)
+* Kpathsea config file, source for path: Path sources. (line 20)
* kpathsea.h: Programming overview.
(line 26)
* kpathsea_cnf_get: Programming with config files.
@@ -3645,10 +3707,10 @@ Index
* reporting bugs: Reporting bugs. (line 6)
* resident.c: Calling sequence. (line 47)
* resolution, setting: Path searching options.
- (line 28)
+ (line 49)
* resolutions, last-resort: Fallback font. (line 6)
* retrieving TeX: unixtex.ftp. (line 6)
-* right-hand side of variable assignments: Config files. (line 56)
+* right-hand side of variable assignments: Config files. (line 57)
* RISINPUTS: Supported file formats.
(line 173)
* Rokicki, Tom: History. (line 12)
@@ -3672,7 +3734,7 @@ Index
* setgid scripts: Security. (line 40)
* SFDFONTS: Supported file formats.
(line 177)
-* shell scripts as configuration files: Config files. (line 79)
+* shell scripts as configuration files: Config files. (line 86)
* shell variables: Variable expansion. (line 17)
* shell_escape, example for code: Programming with config files.
(line 10)
@@ -3745,7 +3807,7 @@ Index
(line 26)
* tex-k@tug.org: Mailing lists. (line 6)
* tex-k@tug.org (bug address): Reporting bugs. (line 6)
-* tex.web: unixtex.ftp. (line 19)
+* tex.web: unixtex.ftp. (line 20)
* TEXBIB: Supported file formats.
(line 30)
* TEXBIB <1>: Supported file formats.
@@ -3780,7 +3842,7 @@ Index
* texmf.cnf missing, warning about: Config files. (line 18)
* texmf.cnf, and variable expansion: Variable expansion. (line 6)
* texmf.cnf, definition for: Config files. (line 6)
-* texmf.cnf, source for path: Path sources. (line 17)
+* texmf.cnf, source for path: Path sources. (line 20)
* TEXMFCNF: Config files. (line 6)
* TEXMFCNF <1>: Supported file formats.
(line 49)
@@ -3824,6 +3886,8 @@ Index
* tolerance for glyph lookup: Basic glyph lookup. (line 15)
* trailing / in home directory: Tilde expansion. (line 19)
* trailing colons: Default expansion. (line 6)
+* translations, of path searching description: Path searching.
+ (line 10)
* TRFONTS: Supported file formats.
(line 203)
* trick for detecting leaf directories: Subdirectory expansion.
@@ -3893,60 +3957,65 @@ Index
Tag Table:
Node: Top1480
Node: Introduction2260
-Node: History4330
-Node: unixtex.ftp8926
-Node: Security10351
-Node: TeX directory structure12855
-Node: Path searching16903
-Node: Searching overview17630
-Node: Path sources21449
-Node: Config files22540
-Node: Path expansion26467
-Node: Default expansion27420
-Node: Variable expansion29490
-Node: Tilde expansion30891
-Node: Brace expansion31871
-Node: KPSE_DOT expansion32810
-Node: Subdirectory expansion33323
-Node: Casefolding search35677
-Node: Casefolding rationale36446
-Node: Casefolding examples37785
-Node: Filename database42835
-Node: ls-R43893
-Node: Filename aliases47569
-Node: Database format48747
-Node: Invoking kpsewhich49760
-Node: Path searching options50715
-Node: Specially-recognized files59234
-Node: Auxiliary tasks60589
-Node: Standard options64295
-Node: TeX support64651
-Node: Supported file formats66005
-Node: File lookup73670
-Node: Glyph lookup75419
-Node: Basic glyph lookup76543
-Node: Fontmap77423
-Node: Fallback font79952
-Node: Suppressing warnings80864
-Node: mktex scripts81991
-Node: mktex configuration83206
-Node: mktex script names89009
-Node: mktex script arguments90395
-Node: Programming91274
-Node: Programming overview91847
-Node: Calling sequence94708
-Node: Program-specific files101240
-Node: Programming with config files102263
-Node: Reporting bugs103850
-Node: Bug checklist104528
-Node: Mailing lists108000
-Node: Debugging108675
-Node: Logging113752
-Node: Common problems115619
-Node: Unable to find files116096
-Node: Slow path searching118506
-Node: Unable to generate fonts119881
-Node: TeX or Metafont failing122352
-Node: Index123554
+Node: History4327
+Node: unixtex.ftp8923
+Node: Security10393
+Node: TeX directory structure12897
+Node: Path searching16938
+Node: Searching overview17896
+Node: Path sources21715
+Node: Config files22941
+Node: Path expansion28204
+Node: Default expansion29157
+Node: Variable expansion31227
+Node: Tilde expansion32628
+Node: Brace expansion33608
+Node: KPSE_DOT expansion34547
+Node: Subdirectory expansion35060
+Node: Casefolding search37408
+Node: Casefolding rationale38177
+Node: Casefolding examples39523
+Node: Filename database44569
+Node: ls-R45551
+Node: Filename aliases49227
+Node: Database format50405
+Node: Invoking kpsewhich51418
+Node: Path searching options52373
+Node: Specially-recognized files61971
+Node: Auxiliary tasks63326
+Node: Standard options67051
+Node: TeX support67407
+Node: Supported file formats68761
+Node: File lookup76429
+Node: Glyph lookup78178
+Node: Basic glyph lookup79302
+Node: Fontmap80182
+Node: Fallback font82711
+Node: Suppressing warnings83623
+Node: mktex scripts84750
+Node: mktex configuration85965
+Node: mktex script names91768
+Node: mktex script arguments93154
+Node: Programming94033
+Node: Programming overview94606
+Node: Calling sequence97467
+Node: Program-specific files103996
+Node: Programming with config files105019
+Node: Reporting bugs106606
+Node: Bug checklist107284
+Node: Mailing lists110753
+Node: Debugging111430
+Node: Logging116507
+Node: Common problems118374
+Node: Unable to find files118851
+Node: Slow path searching121261
+Node: Unable to generate fonts122636
+Node: TeX or Metafont failing125108
+Node: Index126310

End Tag Table
+
+
+Local Variables:
+coding: utf-8
+End: