octave-nkf: kpathsea/kpathsea.info comparison

comparison kpathsea/kpathsea.info @ 2999:faa5d0421460

[project @ 1997-05-23 03:02:09 by jwe]

author	jwe
date	Fri, 23 May 1997 03:02:36 +0000
parents
children	1f0b06020e36

comparison

equal deleted inserted replaced

-:692ba9d441ec
+:faa5d0421460
+This is Info file kpathsea.info, produced by Makeinfo version 1.67 from
+the input file kpathsea.texi.
+INFO-DIR-SECTION TeX
+START-INFO-DIR-ENTRY
+* Kpathsea: (kpathsea).              File lookup along search paths.
+* kpsewhich: (kpathsea)Invoking kpsewhich.      TeX file searching.
+* MakeTeXMF: (kpathsea)MakeTeX scripts.         MF source generation.
+* MakeTeXPK: (kpathsea)MakeTeX scripts.         PK bitmap generation.
+* MakeTeXTeX: (kpathsea)MakeTeX scripts.        TeX source generation.
+* MakeTeXTFM: (kpathsea)MakeTeX scripts.        TeX font metric generation.
+* MakeTeXls-R: (kpathsea)Filename database.     Update ls-R.
+END-INFO-DIR-ENTRY
+This file documents the Kpathsea library for path searching.
+Copyright (C) 1993, 94, 95, 96, 97 K. Berry.
+Permission is granted to make and distribute verbatim copies of this
+manual provided the copyright notice and this permission notice are
+preserved on all copies.
+Permission is granted to copy and distribute modified versions of this
+manual under the conditions for verbatim copying, provided that the
+entire resulting derived work is distributed under the terms of a
+permission notice identical to this one.
+Permission is granted to copy and distribute translations of this
+manual into another language, under the above conditions for modified
+versions, except that this permission notice may be stated in a
+translation approved by the Free Software Foundation.
+File: kpathsea.info,  Node: Top,  Next: Introduction,  Up: (dir)
+Kpathsea library
+****************
+This manual documents how to install and use the Kpathsea library for
+filename lookup.  It corresponds to version 3.0, released in February
+1997.
+* Menu:
+* Introduction::                Overview.
+* Installation::                Compilation, installation, and bug reporting.
+* Path searching::              How filename lookups work.
+* TeX support::                 Special support for TeX-related file lookups.
+* Programming::                 How to use Kpathsea features in your program.
+* Index::                       General index.
+File: kpathsea.info,  Node: Introduction,  Next: Installation,  Prev: Top,  Up: Top
+Introduction
+************
+This manual corresponds to version 3.0 of the Kpathsea library,
+released in February 1997.
+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
+looking up program names to execute.
+The following software, all of which I maintain, uses this library:
+* Dviljk (see the `dvilj' man page)
+* Dvipsk (*note Introduction: (dvips)Top.)
+* GNU font utilities (*note Introduction: (fontu)Top.)
+* Web2c (*note Introduction: (web2c)Top.)
+* Xdvik (see the `xdvi' man page)
+Other software that I do not maintain also uses it.
+I am still actively maintaining the library (and probably always will
+be, despite my hopes).  If you have comments or suggestions, please send
+them to me (*note Reporting bugs::.).
+I distribute the library under the GNU Library General Public License
+(LGPL), with one exception (see below).  In short, this means if you
+write a program using the library, you must (offer to) distribute the
+source to the library, along with any 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,
+although I hope you will.
+The exception is the part of the file `expand.c' which implements
+brace expansion.  I took this from Bash, which is covered by the GNU
+General Public License (GPL).  Therefore, if you wish to redistribute
+the library under the LGPL, you must remove this code.  (If you write a
+replacement I can distribute, I hope you'll share it with me.)  See the
+files `COPYING' and `COPYING.LIB' for the text of the GNU 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 already a member, great!).  TUG produces the periodical
+`TUGboat', sponsors an annual meeting and publishes the proceedings,
+and arranges courses on TeX for all levels of users throughout the
+world.  Anyway, here is the address:
+TeX Users Group
+870 Market St. #801
+San Francisco, CA 94102  USA
+phone: +1 (415) 982-8449
+fax:   +1 (415) 982-8559
+email: <tug@tug.org>
+* Menu:
+* History::
+File: kpathsea.info,  Node: History,  Up: Introduction
+History
+=======
+(This section is for those people who are curious about how the
+library came about.)  (If you like to read historical accounts of
+software, I urge you to seek out the GNU Autoconf manual and the
+"Errors of TeX" paper by Don Knuth, published in `Software--Practice and
+Experience' 19(7), July 1989.)
+My first ChangeLog entry for Web2c seems to be February 1990, but I
+may have done some work before then.  In any case, Tim Morgan and I were
+jointly maintaining it for a time.  (I should mention here that Tim had
+made Web2c into a real distribution long before I had ever used it or
+even heard of it, and Tom Rokicki did the original implementation.  I
+was using `pxp' and `pc' on VAX 11/750's and the hot new Sun 2
+machines.)
+It must have been later in 1990 and 1991 that I started working on
+`TeX for the Impatient'. Dvips, Xdvi, Web2c, and the GNU fontutils
+(which I was also writing at the time) all used different environment
+variables, and, more importantly, had different bugs in their path
+searching. This became extremely painful, as I was stressing everything
+to the limit working on the book.  I also desperately wanted to
+implement subdirectory searching, since I couldn't stand putting
+everything in one big directory, and also couldn't stand having to
+explicitly specify `cm', `pandora', ... in a path.
+In the first incarnation, I just hacked separately on each
+program--that was the original subdirectory searching code in both Xdvi
+and Dvips, though I think Paul Vojta has completely rewritten Xdvi's
+support by now.  That is, I tried to go with the flow in each program,
+rather than changing the program's calling sequences to conform to
+common routines.
+Then, as bugs inevitably appeared, I found I was fixing the same thing
+three times (Web2c and fontutils were always sharing code, since I
+maintained those--there was no Dvipsk or Xdvik or Dviljk at this
+point).  After a while, I finally started sharing source files.  They
+weren't yet a library, though.  I just kept things up to date with shell
+scripts.  (I was developing on a 386 running ISC 2.2 at the time, and so
+didn't have symbolic links.  An awful experience.)
+The ChangeLogs for Xdvik and Dvipsk record initial releases of those
+distributions in May and June 1992.  I think it was because I was tired
+of the different configuration strategies of each program, not so much
+because of the path searching.  (Autoconf was being developed by David
+MacKenzie and others, and I was adapting it to TeX and friends.)
+I started to make a separate library that other programs could link
+with on my birthday in April 1993, according to the ChangeLog.  I don't
+remember exactly why I finally took the time to make it a separate
+library; a conversation with david zuhn that initiated it.  Just seemed
+like it was time.
+Dviljk got started in March 1994 after I bought a Laserjet 4.
+(Kpathsea work got suspended while Norm Walsh and I, with Gustaf
+Neumann's help, implemented a way for TeX to get at all those neat
+builtin LJ4 fonts ... such a treat to have something to typeset in
+besides Palatino!)
+By spring of 1995, I had implemented just about all the path-searching
+features in Kpathsea that I plan to, driven beyond my initial goals by
+Thomas Esser and others.  I then started to integrate Web2c with
+Kpathsea. After the release of a stable Web2c, I hope to be able to stop
+development, and turn most of my attention back to making fonts for GNU.
+(Always assuming Micros**t hasn't completely obliterated Unix by then,
+or that software patents haven't stopped software development by anybody
+smaller than a company with a million-dollar-a-year legal budget.  Which
+is actually what I think is likely to happen, but that's another
+story...)
+File: kpathsea.info,  Node: Installation,  Next: Path searching,  Prev: Introduction,  Up: Top
+Installation
+************
+(A copy of this chapter is in the distribution file
+`kpathsea/INSTALL'.)
+The procedure for Kpathsea (and Web2c, etc.) configuration and
+installation follows.  If trouble, *note Common problems::., a copy of
+which is in the file `kpathsea/BUGS'.
+* Menu:
+* Simple installation::      If you just want to do it.
+* Custom installation::      If you want to change things around.
+* Security::                 Who can write what files, etc.
+* TeX directory structure::  Managing the horde of TeX input files.
+* unixtex.ftp::              Getting software via FTP, on CD-ROM, or on tape.
+* Reporting bugs::           Where and how to report bugs.
+File: kpathsea.info,  Node: Simple installation,  Next: Custom installation,  Up: Installation
+Simple installation
+===================
+Installing TeX and friends for the first time can be a daunting
+experience.  Thus, you may prefer to skip this whole thing and just get
+precompiled executables: *note unixtex.ftp::..
+This section explains what to do if you wish to take the defaults for
+everything (installing under `/usr/local'), and generally to install in
+the simplest possible way.  Most steps here refer to corresponding
+subsection in the next section which explains how to override defaults
+and generally gives more details.
+1. Be sure you have enough disk space: approximately 8 megabytes for
+the compressed archives, 15MB for sources, 45MB for compilation,
+40MB for the (initial) installed system (including library files).
+*Note Disk space::.
+2. Retrieve these two distribution archives:
+`ftp://ftp.tug.org/tex/texk.tar.gz'
+These are the sources, which you will be compiling.
+`ftp://ftp.tug.org/tex/texmflib.tar.gz'
+This is a basic set of input files.  You should unpack it in
+the directory `/usr/local/share'; doing so will create a
+`texmf' subdirectory there.
+*Note Kpathsea application distributions::.
+3. When using the default search paths, there is no need to edit any
+distribution files. *Note Changing search paths::.
+4. At the top level of the distribution, run `sh configure'.  (If you
+have the GNU Bash shell installed, run `bash configure'.) *Note
+Running configure::.
+5. `make'. *Note Running make::.
+6. `make install'. *Note Installing files::.
+7. `make distclean'. *Note Cleaning up::.
+8. Set up a cron job to rebuild the filename database that makes
+searching faster.  This line will rebuild it every midnight:
+0 0 * * * cd /usr/local/share/texmf && /BINDIR/MakeTeXls-R
+*Note Filename database generation::, and *Note Filename
+database::.
+9. If you're installing Dvips, you also need to set up configuration
+files for your printers and make any additional PostScript fonts
+available.  *Note Installation: (dvips)Installation.  If you have
+any color printers, *note Color device configuration: (dvips)Color
+device configuration..
+10. The first time you run a DVI driver, a bunch of PK fonts will be
+built by Metafont via `MakeTeXPK' (and added to the filename
+database).  This will take some time.  Don't be alarmed; they will
+created only this first time (unless something is wrong with your
+path definitions).
+By default, `MakeTeXPK' assumes `/usr/local/share/texmf/fonts' is
+globally writable.  If you need a different arrangement, *note
+MakeTeX configuration::..
+*Note MakeTeX scripts::.
+11. For some simple tests, try `tex story \\bye' and `latex simple'.
+Then run `xdvi story' or `dvips simple' on the resulting DVI files
+to preview/print the documents.  *Note Installation testing::.
+File: kpathsea.info,  Node: Custom installation,  Next: Security,  Prev: Simple installation,  Up: Installation
+Custom installation
+===================
+Most sites need to modify the default installation procedure in some
+way, perhaps merely changing the prefix from `/usr/local', perhaps
+adding extra compiler or loader options to work around `configure'
+bugs.  This section explains how to override default choices.  For
+additional distribution-specific information:
+* `dviljk/INSTALL'.
+* *Note Installation: (dvips)Installation.
+* *Note Installation: (web2c)Installation.
+* `xdvik/INSTALL'.
+These instructions are for Unix systems.  Other operating-system
+specific distributions have their own instructions.  The code base
+itself supports Amiga, DOS, OS/2, and VMS.
+Following are the same steps as in the previous section (which
+describes the simplest installation), but with much more detail.
+* Menu:
+* Disk space::
+* Kpathsea application distributions::
+* Changing search paths::
+* Running configure::
+* Running make::
+* Installing files::
+* Cleaning up::
+* Filename database generation::
+* MakeTeX scripts::
+* Installation testing::
+File: kpathsea.info,  Node: Disk space,  Next: Kpathsea application distributions,  Up: Custom installation
+Disk space
+----------
+Here is a table showing the disk space needed for each distribution
+(described in the next section).  The `(totals)' line reflects the
+`texk' source distribution and `texmflib'; the individual distributions
+don't enter into it.  Sizes are in megabytes.  All numbers are
+approximate.
+dviljk        .9       3.8
+dvipsk        .9       3.2
+xdvik         .7       2.5
+web2c         1.3      5.0
+web           1.9      6.5       -         -
+texk          3.8      14.1      43.1      23.5
+texmflib      3.8      15.0      -         15.0
+(totals)      7.6      29.1      43.1      38.5
+File: kpathsea.info,  Node: Kpathsea application distributions,  Next: Changing search paths,  Prev: Disk space,  Up: Custom installation
+Kpathsea application distributions
+----------------------------------
+The archive `ftp://ftp.tug.org/tex/texk.tar.gz' contains all of the
+Kpathsea applications I maintain, and the library itself.  For example,
+since NeXT does not generally support X11, you'd probably want to skip
+`xdvik' (or simply remove it after unpacking `texk.tar.gz'.  If you are
+not interested in all of them, you can also retrieve them separately:
+`dviljk.tar.gz'
+DVI to PCL, for LaserJet printers.
+`dvipsk.tar.gz'
+DVI to PostScript, for previewers, printers, or PDF generation.
+`web2c.tar.gz'
+The software needed to compile TeX and friends.
+`web.tar.gz'
+The original WEB source files, also used in compilation.
+`xdvik.tar.gz'
+DVI previewing under the X window system.
+If you want to use the Babel LaTeX package for support of non-English
+typesetting, you may need to retrieve additional files.  See the file
+`install.txt' in the Babel distribution.
+File: kpathsea.info,  Node: Changing search paths,  Next: Running configure,  Prev: Kpathsea application distributions,  Up: Custom installation
+Changing search paths
+---------------------
+If the search paths for your installation differ from the standard
+TeX directory structure (*note Introduction: (tds)Top.), edit the file
+`kpathsea/texmf.cnf.in' as desired, before running `configure'.  For
+example, if you have all your fonts or macros in one big directory.
+You may also wish to edit the file `MakeTeXnames.cnf', either before
+or after installation, to control various aspects of `MakeTeXPK' and
+friends.  *Note MakeTeX configuration::.
+You do not need to edit `texmf.cnf.in' to change the default
+top-level or other installation *directories* (only the paths).  You
+can and should do that when you run `configure' (next step).
+You also do not need to edit `texmf.cnf.in' if you are willing to
+rely on `texmf.cnf' at runtime to define the paths, and let the
+compile-time default paths be incorrect.  Usually there is no harm in
+doing this.
+The section below explains default generation in more detail.
+* Menu:
+* Default path features::
+* Default path generation::
+File: kpathsea.info,  Node: Default path features,  Next: Default path generation,  Up: Changing search paths
+Default path features
+.....................
+The purpose of having all the different files described in the section
+above is to avoid having the same information in more than one place. If
+you change the installation directories or top-level prefix at
+`configure'-time, those changes will propagate through the whole
+sequence.  And if you change the default paths in `texmf.cnf.in', those
+changes are propagated to the compile-time defaults.
+The Make definitions are all repeated in several Makefile's; but
+changing the top-level `Makefile' should suffice, as it passes down all
+the variable definitions, thus overriding the submakes.  (The
+definitions are repeated so you can run Make in the subdirectories, if
+you should have occasion to.)
+By default, the bitmap font paths end with `/$MAKETEX_MODE', thus
+including the device name (usually a Metafont mode name such as
+`ljfour').  This distinguishes two different devices with the same
+resolution--a write/white from a write/black 300dpi printer, for
+example.
+However, since most sites don't have this complication, Kpathsea
+(specifically, the `kpse_init_prog' function in `kpathsea/proginit.c')
+has a special case: if the mode has not been explicitly set by the user
+(or in a configuration file), it sets `MAKETEX_MODE' to `/'.  This
+makes the default PK path, for example, expand into `.../pk//', so
+fonts will be found even if there is no subdirectory for the mode (if
+you arranged things that way because your site has only one printer,
+for example) or if the program is mode-independent (e.g., `pktype').
+To make the paths independent of the mode, simply edit `texmf.cnf.in'
+before installation, or the installed `texmf.cnf', and remove the
+`$MAKETEX_MODE'.
+*Note MakeTeX script arguments::, for how this interacts with
+`MakeTeXPK'.
+*Note TeX directory structure: TeX directory structure, for a
+description of the default arrangement of the input files that comprise
+the TeX system.  The file `kpathsea/HIER' is a copy of that section.
+File: kpathsea.info,  Node: Default path generation,  Prev: Default path features,  Up: Changing search paths
+Default path generation
+.......................
+This section describes how the default paths are constructed.
+You may wish to ignore the whole mess and simply edit `texmf.cnf'
+after it is installed, perhaps even copying it into place beforehand so
+you can complete the installation, if it seems necessary.
+To summarize the chain of events that go into defining the default
+paths:
+1. `configure' creates a `Makefile' from each `Makefile.in'.
+2. When Make runs in the `kpathsea' directory, it creates a file
+`texmf.sed' that substitutes the Make value of `$(var)' for a
+string `@var@'.  The variables in question are the one that define
+the installation directories.
+3. `texmf.sed' (together with a little extra magic--see
+`kpathsea/Makefile') is applied to `texmf.cnf.in' to generate
+`texmf.cnf'.  This is the file that will eventually be installed
+and used.
+4. The definitions in `texmf.cnf' are recast as C `#define''s in
+`paths.h'.  These values will be the compile-time defaults; they
+are not used at runtime unless no `texmf.cnf' file can be found.
+(That's a lie: the compile-time defaults are what any extra :'s in
+`texmf.cnf' expand into; but the paths as distributed have no extra
+:'s, and there's no particular reason for them to.)
+File: kpathsea.info,  Node: Running configure,  Next: Running make,  Prev: Changing search paths,  Up: Custom installation
+Running `configure'
+-------------------
+Run `sh configure OPTIONS' (in the top-level directory, the one
+containing `kpathsea/'), possibly using a shell other than `sh' (*note
+configure shells::.).
+`configure' adapts the source distribution to the present system via
+`#define''s in `*/c-auto.h', which are created from the corresponding
+`c-auto.h.in'.  It also creates a `Makefile' from the corresponding
+`Makefile.in', doing `@VAR@' and `ac_include' substitutions).
+`configure' is the best place to control the configuration,
+compilation, and installed location of the software, either via
+command-line options, or by setting environment variables before
+invoking it.  For example, you can disable `MakeTeXPK' by default with
+the option `--disable-maketexpk'.  *Note configure options::.
+* Menu:
+* configure shells::
+* configure options::
+* configure environment::
+* configure scenarios::
+* Shared library::
+File: kpathsea.info,  Node: configure shells,  Next: configure options,  Up: Running configure
+`configure' shells
+..................
+If you have Bash, the GNU shell, use it if `sh' runs into trouble
+(*note Top: (features)Top.).
+Most Bourne shell variants other than Bash cannot handle `configure'
+scripts as generated by GNU Autoconf (*note Introduction:
+(autoconf)Top.).  Specifically:
+`ksh'
+The Korn shell may be installed as `/bin/sh' on AIX.  `/bin/bsh'
+may serve instead.
+`ash'
+Ash is sometimes installed as `/bin/sh' on NetBSD, FreeBSD, and
+Linux systems.  `/bin/bash' should be available.
+`Ultrix /bin/sh'
+`/bin/sh' under Ultrix is a DEC-grown shell that is notably
+deficient in many ways.  `/bin/sh5' may be necessary.
+File: kpathsea.info,  Node: configure options,  Next: configure environment,  Prev: configure shells,  Up: Running configure
+`configure' options
+...................
+For a complete list of all `configure' options, run `configure
+--help' or *note Running `configure' scripts: (autoconf)Invoking
+configure. (a copy is in the file `kpathsea/CONFIGURE').  The generic
+options are listed first in the `--help' output, and the
+package-specific options come last.  The environment variables
+`configure' pays attention to are listed below.
+Options particularly likely to be useful are `--prefix', `--datadir',
+and the like; *note configure scenarios::..
+This section gives pointers to descriptions of the `--with' and
+`--enable' options to `configure' that Kpathsea-using programs accept.
+`--without-maketexmf-default'
+`--without-maketexpk-default'
+`--without-maketextfm-default'
+`--with-maketextex-default'
+Enable or disable the dynamic generation programs.  *Note MakeTeX
+configuration::.
+`--enable-shared'
+Build Kpathsea as a shared library, and link against it.  Also
+build the usual static library.  *Note Shared library::.
+`--disable-static'
+Build only the shared library.
+File: kpathsea.info,  Node: configure environment,  Next: configure scenarios,  Prev: configure options,  Up: Running configure
+`configure' environment
+.......................
+`configure' uses the value of the following environment variables in
+determining your system's characteristics, and substitutes for them in
+Makefile's:
+`CC'
+The compiler to use: default is `gcc' if it's installed, otherwise
+`cc'.
+`CFLAGS'
+Options to give the compiler: default is `-g -O2' for `gcc', `-g'
+otherwise.  `CFLAGS' comes after any other options.  You may need
+to include `-w' here if your compilations commonly have useless
+warnings (e.g., `NULL redefined'), or `configure' may fail to
+detect the presence of header files (it takes the messages on
+standard error to mean the header file doesn't exist).
+`CPPFLAGS'
+Options to pass to the compiler preprocessor; this matters most for
+configuration, not the actual source compilation.  The `configure'
+script often does only preprocessing (e.g., to check for the
+existence of #include files), and `CFLAGS' is not used for this.
+You may need to set this to something like
+`-I/usr/local/include/wwwhatever' if you have the libwww library
+installed for hyper-xdvik (see `xdvik/INSTALL').
+`DEFS'
+Additional preprocessor options, but not used by `configure'.
+Provided for enabling or disabling program features, as documented
+in the various program-specific installation instructions.  `DEFS'
+comes before any compiler options included by the distribution
+`Makefile's or by `configure'.
+`LDFLAGS'
+Additional options to give to the loader.  `LDFLAGS' comes before
+any other linker options.
+`LIBS'
+Additional libraries to link with.
+File: kpathsea.info,  Node: configure scenarios,  Next: Shared library,  Prev: configure environment,  Up: Running configure
+`configure' scenarios
+.....................
+Here are some common installation scenarios:
+* Including X support in Metafont.  This is disabled by default,
+since many sites have no use for it, and it's a leading cause of
+configuration problems.
+configure --with-x-toolkit
+* Putting the binaries, TeX files, GNU info files, etc. into a single
+TeX hierarchy, say TEXMF, requires overriding defaults in both
+`configure' and `make':
+configure --prefix=TEXMF --datadir=TEXMF
+make texmf=TEXMF
+* You can compile on multiple architectures simultaneously either by
+building symbolic link trees with the `lndir' script from the X11
+distribution, or with the `--srcdir' option:
+configure --srcdir=SRCDIR
+* If you are installing binaries for multiple architectures into a
+single hierarchy, you will probably want to override the default
+`bin' and `lib' directories, something like this:
+configure --prefix=TEXMF --datadir=TEXMF \
+--bindir=TEXMF/ARCH/bin --libdir=TEXMF/ARCH/lib
+make texmf=TEXMF
+(Unless you make provisions for architecture-specific files in
+other ways, e.g., with Depot or an automounter.)
+* To compile with optimization (to compile without debugging, remove
+the `-g'):
+env CFLAGS="-g -O" sh configure ...
+For a potential problem if you optimize, see *Note TeX or
+Metafont failing: TeX or Metafont failing.
+File: kpathsea.info,  Node: Shared library,  Prev: configure scenarios,  Up: Running configure
+Shared library
+..............
+You can compile Kpathsea as a shared library on a few systems, by
+specifying the option `--enable-shared' when you run `configure'.
+The main advantage in doing this is that the executables can then
+share the code, thus decreasing memory and disk space requirements.
+On some systems, you can record the location of shared libraries in a
+binary, usually by giving certain options to the linker.  Then
+individual users do not need to set their system's environment variable
+(e.g., `LD_LIBRARY_PATH') to find shared libraries.  If you want to do
+this, you will need to add the necessary options to `LDFLAGS' yourself;
+for example, on Solaris, include something like `-R${prefix}/lib'.
+(Unfortunately, making this happen by default is very difficult,
+because of interactions with an existing installed shared library.)
+Currently, shared library support is implemented only on SunOS 4
+(Solaris 1) and SunOS 5 (Solaris 2).  If you're interested and willing
+in adding support for other systems, please see the `configure' mode in
+the `klibtool' script, especially the host-specific case statement
+around line 250.
+File: kpathsea.info,  Node: Running make,  Next: Installing files,  Prev: Running configure,  Up: Custom installation
+Running `make'
+--------------
+`make' (still in the top-level directory).  This also creates the
+`texmf.cnf' and `paths.h' files that define the default search paths,
+and (by default) the `plain' and `latex' TeX formats.
+You can override directory names and other values at `make'-time.
+`make/paths.make' lists the variables most commonly reset.  For
+example, `make default_texsizes=600' changes the list of fallback
+resolutions.
+You can also override each of `configure''s environment variables
+(*note configure environment::.).  The Make variables have the same
+names.
+Finally, you can supply additional options via the following
+variables.  (`configure' does not use these.)
+`XCPPFLAGS'
+`XDEFS'
+Preprocessor options.
+`XCFLAGS'
+Compiler options.
+`XLDFLAGS'
+Loader options (included at beginning of link commands).
+`XLOADLIBES'
+More loader options (included at end of link commands).
+`XMAKEARGS'
+Additional Make arguments passed to all sub-`make''s. You may need
+to include assignments to the other variables here via `XMAKEARGS';
+for example: `make XMAKEARGS="CFLAGS=-O XDEFS=-DA4"'.
+It's generally a bad idea to use a different compiler (`CC') or
+libraries (`LIBS') for compilation than you did for configuration,
+since the values `configure' determined may then be incorrect.
+Adding compiler options to change the "universe" you are using
+(typically BSD vs. system V) is generally a cause of trouble.  It's
+best to use the native environment, whatever that is; `configure' and
+the software usually adapt best to that.  In particular, under Solaris
+2.x, you should not use the BSD-compatibility library (`libucb') or
+include files (`ucbinclude').
+If you want to use the Babel LaTeX package for support of non-English
+typesetting, you need to modify some files before making the LaTeX
+format.  See the file `install.txt' in the Babel distribution.
+File: kpathsea.info,  Node: Installing files,  Next: Cleaning up,  Prev: Running make,  Up: Custom installation
+Installing files
+----------------
+The basic command is the usual `make install'.  For security issues,
+*note Security::..
+The first time you install any manual in the GNU Info system, you
+should add a line (you choose where) to the file `dir' in your
+`$(infodir)' directory.  Sample text for this is given near the top of
+the Texinfo source files (`kpathsea/kpathsea.texi',
+`dvipsk/dvips.texi', and `web2c/doc/web2c.texi').  If you have a recent
+version of the GNU Texinfo distribution installed
+(`ftp://prep.ai.mit.edu/pub/gnu/texinfo-3.9.tar.gz' or later), this
+should happen automatically.
+On the offchance that this is your first Info installation, the `dir'
+file I use is included in the distribution as `etc/dir-example'.
+You may wish to use one of the following targets, especially if you
+are installing on multiple architectures:
+* `make install-exec' to install in architecture-dependent
+directories, i.e., ones that depend on the `$(exec_prefix)' Make
+variable.  This includes links to binaries, libraries, etc., not
+just "executables".
+* `make install-data' to install in architecture-independent
+directories, such as documentation, configuration files, pool
+files, etc.
+If you use the Andrew File System, the normal path (e.g., PREFIX/bin)
+only gets you to a read-only copy of the files, and you must specify a
+different path for installation.  The best way to do this is by setting
+the `prefix' variable on the `make' command line.  The sequence becomes
+something like this:
+configure --prefix=/whatever
+make
+make install prefix=/afs/.SYSTEM.NAME/system/1.3/@sys/whatever
+With AFS, you will definitely want to use relative filenames in
+`ls-R' (*note Filename database::.), not absolute filenames.  This is
+done by default, but check anyway.
+File: kpathsea.info,  Node: Cleaning up,  Next: Filename database generation,  Prev: Installing files,  Up: Custom installation
+Cleaning up
+-----------
+The basic command is `make distclean'.  This removes all files created
+by the build.
+Alternatively,
+* `make mostlyclean' if you intend to compile on another
+architecture.  For Web2c, since the generated C files are portable,
+they are not removed.  If the `lex' vs. `flex' situation is going
+to be different on the next machine, `rm web2c/lex.yy.c'.
+* `make clean' to remove files created by compiling, but leave
+configuration files and Makefiles.
+* `make maintainer-clean' to remove everything that the Makefiles can
+rebuild.  This is more than `distclean' removes, and you should
+only use it if you are thoroughly conversant with (and have the
+necessary versions of) Autoconf.
+* `make extraclean' to remove other junk, e.g., core files, log
+files, patch rejects.  This is independent of the other `clean'
+targets.
+File: kpathsea.info,  Node: Filename database generation,  Next: MakeTeX scripts,  Prev: Cleaning up,  Up: Custom installation
+Filename database generation
+----------------------------
+You will probably want to set up a `cron' entry on the appropriate
+machine(s) to rebuild the filename database nightly or so, as in:
+0 0 * * * cd TEXMF && /BINDIR/MakeTeXls-R
+*Note Filename database::.
+Although the `MakeTeX...' scripts make every effort to add
+newly-created files on the fly, it can't hurt to make sure you get a
+fresh version every so often.
+File: kpathsea.info,  Node: MakeTeX scripts,  Next: Installation testing,  Prev: Filename database generation,  Up: Custom installation
+`MakeTeX' scripts
+-----------------
+If Kpathsea cannot otherwise find a file, for some file types it is
+configured by default to invoke an external program to create it
+dynamically (*note MakeTeX configuration::.).  This is most useful for
+fonts (bitmaps, TFM's, and arbitrarily-sizable Metafont sources such as
+the Sauter and DC fonts), since any given document can use fonts never
+before referenced.  Trying to build all fonts in advance is therefore
+impractical, if not impossible.
+The script is passed the name of the file to create and possibly other
+arguments, as explained below.  It must echo the full pathname of the
+file it created (and nothing else) to standard output; it can write
+diagnostics to standard error.
+* Menu:
+* MakeTeX configuration::
+* MakeTeX script names::
+* MakeTeX script arguments::
+File: kpathsea.info,  Node: MakeTeX configuration,  Next: MakeTeX script names,  Up: MakeTeX scripts
+`MakeTeX' configuration
+.......................
+The following file types can run an external program to create missing
+files: `pk', `tfm', `mf', `tex'; the scripts are named `MakeTeXPK',
+`MakeTeXTFM', `MakeTeXMF', and `MakeTeXTeX'.
+In the absence of `configure' options specifying otherwise,
+everything but `MakeTeXTeX' will be enabled by default. The `configure'
+options to change the defaults are:
+--without-maketexmf-default
+--without-maketexpk-default
+--without-maketextfm-default
+--with-maketextex-default
+The `configure' setting is overridden if the environment variable or
+configuration file value named for the script is set; e.g., `MAKETEXPK'
+(*note MakeTeX script arguments::.).
+As distributed, all the scripts source a file
+`texmf/web2c/MakeTeX.site' if it exists, so you can override various
+defaults.  See `MakeTeXcommon', for instance, which defines the default
+mode, resolution, directory permissions, some special directory names,
+etc.  If you prefer not to change the distributed scripts, you can
+simply create `MakeTeX.site' with the appropriate definitions (you do
+not need to create it if you have nothing to put in it).
+`MakeTeX.site' has no special syntax; it's an arbitrary Bourne shell
+script.  The distribution contains a sample `MakeTeX.site' for you to
+copy and modify as you please (it is not installed anywhere).
+In addition, you can configure a number of features with the
+`MT_FEATURES' variable, which you can define:
+* in `MakeTeX.site', as just mentioned;
+* by editing the file `MakeTeXnames.cnf', either before `make
+install' (in the source hierarchy) or after (in the installed
+hierarchy);
+* or in the environment.
+By default, `MakeTeXPK' installs fonts into the standard TeX
+directory structure (*note TeX directory structure: TeX directory
+structure.).  It uses aliases and directory names from the Fontname
+distribution (*note Introduction: (fontname)Top.). Most of the options
+here change that.
+`appendonlydir'
+Tell `MakeTeXmkdir' to create directories append-only, i.e., set
+their sticky bit (*note Mode Structure: (fileutils)Mode
+Structure.).
+`dosnames'
+Use 8.3 names; e.g., `dpi600/cmr10.pk' instead of `cmr10.600pk'.
+`nomode'
+Omit the directory level for the mode name; this is fine as long as
+you generate fonts for only one mode.
+`strip'
+Omit the font supplier and typeface name directory levels.
+`varfonts'
+Put `MakeTeXPK'-generated fonts under the directory named by
+`VARTEXFONTS'; the default value in `kpathsea/texmf.cnf.in' is
+`/var/tex/fonts', as recommended by the `Linux File System
+Standard' (but unless `varfonts' is enabled, nothing cares about
+that value).
+The `varfonts' setting in `MT_FEATURES' is overridden by the
+`USE_VARTEXFONTS' environment variable: if set to `1', the feature
+is enabled, and if set to `0', the feature is disabled.
+File: kpathsea.info,  Node: MakeTeX script names,  Next: MakeTeX script arguments,  Prev: MakeTeX configuration,  Up: MakeTeX scripts
+`MakeTeX' script names
+......................
+The following table shows the default name of the script for each
+possible file types.  (The source is the variable `kpse_make_specs' in
+`kpathsea/tex-make.c'.)
+`MakeTeXPK'
+Glyph fonts.
+`MakeTeXTeX'
+TeX input files.
+`MakeTeXMF'
+Metafont input files.
+`MakeTeXTFM'
+TFM files.
+These names are overridden by an environment variable specific to the
+program--for example, `DVIPSMAKEPK' for Dvipsk.
+If a `MakeTeX...' script fails, the invocation is appended to a file
+`missfont.log' (by default) in the current directory.  You can then
+execute the log file to create the missing files after fixing the
+problem.
+If the current directory is not writable and the environment variable
+or configuration file value `TEXMFOUTPUT' is set, its value is used.
+Otherwise, nothing is written.  The name `missfont.log' is overridden
+by the `MISSFONT_LOG' environment variable or configuration file value.
+File: kpathsea.info,  Node: MakeTeX script arguments,  Prev: MakeTeX script names,  Up: MakeTeX scripts
+`MakeTeX' script arguments
+..........................
+The first argument to a `MakeTeX' script is always the name of the
+file to be created.
+In the default `MakeTeXPK' implementation, from three to five
+additional arguments may also passed, via environment variables:
+1. The resolution to make the font at (`KPATHSEA_DPI').
+2. The "base dpi" the program is operating at (`MAKETEX_BASE_DPI'),
+i.e., the assumed resolution of the output device.
+3. A "magstep" string suitable for the Metafont `mag' variable
+(`MAKETEX_MAG').
+4. Optionally, a Metafont mode name to assign to the Metafont `mode'
+variable (`MAKETEX_MODE').  Otherwise, (the default) `MakeTeXPK'
+guesses the mode from the resolution.  *Note TeX directory
+structure: TeX directory structure.
+5. Optionally, a directory name. If the directory is absolute, it is
+used as-is. Otherwise, it is appended to the root destination
+directory set in the script (from environment variables `DESTDIR'
+or `MTP_DESTDIR' or a compile-time default). If this argument is
+not supplied, the mode name is appended to the root destination
+directory.
+Kpathsea sets `KPATHSEA_DPI' appropriately for each attempt at building
+a font.  It's up to the program using Kpathsea to set the others.
+(*Note Calling sequence::.)
+You can change the specification for the arguments passed to the
+external script by setting the environment variable named as the script
+name, but all capitals--`MAKETEXPK', for example.  If you've changed
+the script name by setting (say) `DVIPSMAKEPK' to `foo', then the spec
+is taken from the environment variable `FOO'.
+The spec can contain any variable references, to the above variables
+or any others.  As an example, the default spec for `MakeTeXPK' is:
+$KPATHSEA_DPI $MAKETEX_BASE_DPI $MAKETEX_MAG $MAKETEX_MODE
+The convention of passing the name of the file to be created as the
+first argument cannot be changed.
+File: kpathsea.info,  Node: Installation testing,  Prev: MakeTeX scripts,  Up: Custom installation
+Installation testing
+--------------------
+Besides the tests listed in *Note Simple installation::, you can try
+running `make check'.  This includes the torture tests (trip, trap, and
+mptrap) that come with Web2c (*note Torture tests: (web2c)Torture
+tests.).
+File: kpathsea.info,  Node: Security,  Next: TeX directory structure,  Prev: Custom installation,  Up: Installation
+Security
+========
+None of the programs in the TeX system require any special system
+privileges, so there's no first-level security concern of people gaining
+illegitimate root access.
+A TeX document, however, can write to arbitrary files, e.g.,
+`~/.rhosts', and thus an unwitting user who runs TeX on a random
+document is vulnerable to a trojan horse attack.  This loophole is
+closed by default, but you can be permissive if you so desire in
+`texmf.cnf'.  *Note tex invocation: (web2c)tex invocation.  MetaPost has
+the same issue.
+Dvips, Xdvi, and TeX can also execute shell commands under some
+circumstances.  To disable this, see the `-R' option in *Note Option
+details: (dvips)Option details, the xdvi man page, and *Note tex
+invocation: (web2c)tex invocation, respectively.
+Another security issue arises because it's very useful--almost
+necessary--to make arbitrary fonts on user demand with `MakeTeXPK' and
+friends.  Where do these files get installed?  By default, the
+`MakeTeXPK' distributed with Kpathsea assumes a globally writable
+`texmf' tree; this is the simplest and most convenient approach, but it
+may not suit your situation.
+The first restriction you can apply is to make newly-created
+directories under `texmf' be append-only with an option in
+`MakeTeXnames.cnf'.  *Note MakeTeX configuration::.
+Another approach is to establish a group (or user) for TeX files,
+make the `texmf' tree writable only to that group (or user), and make
+`MakeTeXPK' et al. setgid to that group (or setuid to that user).  Then
+users must invoke the scripts to install things.  (If you're worried
+about the inevitable security holes in scripts, then you could write a
+C wrapper to exec the script.)
+Finally, using a central writable `texmf' tree may be completely
+impossible, because it's on an NFS filesystem that you cannot export
+read/write, or AFS is in use, or simply because "it's policy".  Then
+you must resort to each user's machine having its own local directory of
+dynamically-created fonts; again, `MakeTeXnames.cnf' has an option to
+do this, and again, *note MakeTeX configuration::..
+File: kpathsea.info,  Node: TeX directory structure,  Next: unixtex.ftp,  Prev: Security,  Up: Installation
+TeX directory structure
+=======================
+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 standard is available
+as `ftp://prep.ai.mit.edu/pub/gnu/standards/standards.texi' and
+mirrors.  The TDS document is available from `CTAN:/tex-archive/tds'
+(*note unixtex.ftp::.).
+You can change the default paths in many ways (*note Changing search
+paths::.).  One common desire is to put everything (binaries and all)
+under a single top-level directory such as `/usr/local/texmf' or
+`/opt/texmf'--in the terms used below, make PREFIX and TEXMF the same.
+For specific instructions on doing that, *note configure scenarios::..
+Here is a skeleton of the default directory structure, extracted from
+the TDS document:
+PREFIX/      installation root (`/usr/local' by default)
+bin/         executables
+man/         man pages
+include/     C header files
+info/        GNU info files
+lib/         libraries (`libkpathsea.*')
+share/       architecture-independent files
+texmf/      TDS root
+bibtex/     BibTeX input files
+bib/        BibTeX databases
+base/       base distribution (e.g., `xampl.bib')
+misc/       single-file databases
+PKG/       name of a package
+bst/        BibTeX style files
+base/       base distribution (e.g., `plain.bst', `acm.bst')
+misc/       single-file styles
+PKG/       name of a package
+doc/         additional documentation
+dvips/       `.pro', `.ps', `psfonts.map'
+fonts/       font-related files
+TYPE/         file type (e.g., `tfm', `pk')
+MODE/          type of output device (types `pk' and `gf' only)
+SUPPLIER/       name of a font supplier (e.g., `public')
+TYPEFACE/        name of a typeface (e.g., `cm')
+dpiNNN/           font resolution (types `pk' and `gf' only)
+metafont/    Metafont (non-font) input files
+base/        base distribution (e.g., `plain.mf')
+misc/        single-file packages (e.g., `modes.mf')
+PKG/           name of a package (e.g., `mfpic')
+metapost/    MetaPost input files
+base/        base distribution (e.g., `plain.mp')
+misc/        single-file packages
+PKG/           name of a package
+support/     support files for MetaPost-related utilities (e.g., `trfonts.map')
+mft/         `MFT' inputs (e.g., `plain.mft')
+tex/         TeX input files
+FORMAT/         name of a format (e.g., `plain')
+base/        base distribution for FORMAT (e.g., `plain.tex')
+misc/        single-file packages (e.g., `webmac.tex')
+local/       local additions to or local configuration files for FORMAT
+PKG/           name of a package (e.g., `graphics', `mfnfss')
+generic/     format-independent packages
+hyphen/      hyphenation patterns (e.g., `hyphen.tex')
+images/      image input files (e.g., Encapsulated PostScript)
+misc/        single-file format-independent packages (e.g., `null.tex').
+PKG/           name of a package (e.g., `babel')
+web2c/        implementation-dependent files (`.pool', `.fmt', `texmf.cnf', etc.)
+Some concrete examples for most file types:
+/usr/local/bin/tex
+/usr/local/man/man1/xdvi.1
+/usr/local/info/kpathsea.info
+/usr/local/lib/libkpathsea.a
+/usr/local/share/texmf/bibtex/bst/base/plain.bst
+/usr/local/share/texmf/fonts/pk/ljfour/public/cm/cmr10.600pk
+/usr/local/share/texmf/fonts/source/public/pandora/pnr10.mf
+/usr/local/share/texmf/fonts/tfm/public/cm/cmr10.tfm
+/usr/local/share/texmf/fonts/type1/adobe/utopia/putr.pfa
+/usr/local/share/texmf/metafont/base/plain.mf
+/usr/local/share/texmf/metapost/base/plain.mp
+/usr/local/share/texmf/tex/plain/base/plain.tex
+/usr/local/share/texmf/tex/generic/hyphen/hyphen.tex
+/usr/local/share/texmf/web2c/tex.pool
+/usr/local/share/texmf/web2c/tex.fmt
+/usr/local/share/texmf/web2c/texmf.cnf
+File: kpathsea.info,  Node: unixtex.ftp,  Next: Reporting bugs,  Prev: TeX directory structure,  Up: Installation
+`unixtex.ftp': Obtaining TeX
+============================
+This is `ftp://ftp.tug.org/tex/unixtex.ftp', last updated 7 February
+1997.  Also available as `http://www.tug.org/unixtex.ftp'.  The IP
+address is currently [158.121.106.10], and the canonical host name is
+currently `tug.cs.umb.edu'.  It is also in Kpathsea source
+distributions as `etc/unixtex.ftp' (although the network version is
+usually newer).  Mail <kb@mail.tug.org> with comments or questions.
+Following are general instructions for Unix or other sites who wish to
+acquire the Web2c distribution, (plain) TeX, LaTeX (2e), BibTeX,
+Metafont, MetaPost, DVI processors for the X window system, PostScript,
+the PCL language in the HP LaserJet, and related programs.  They are
+oriented towards building from the original sources, though some
+information on alternative packages is included in the last section.
+See also `http://www.tug.org/web2c', the Web2c and Kpathsea home page.
+Please consider joining the TeX Users Group (TUG) to help support the
+maintenance and development of the programs you retrieve.  Email
+<tug@tug.org> or see `http://www.tug.org' for information and a
+membership form.
+For actual installation instructions after obtaining the necessary
+sources, *note Installation::..  A copy is in the distribution file
+`kpathsea/INSTALL'.
+* Menu:
+* Electronic distribution::  CTAN and so forth.
+* CD-ROM distribution::
+* Tape distribution::
+* Other TeX packages::
+File: kpathsea.info,  Node: Electronic distribution,  Next: CD-ROM distribution,  Up: unixtex.ftp
+Electronic distribution
+-----------------------
+In many places we refer to CTAN:.  This is *both* a host name and a
+directory name.  Here are some primary locations:
+`ftp://ftp.cdrom.com/pub/tex/ctan'  (California, USA)
+`ftp://ftp.dante.de/tex-archive'    (Germany)
+`ftp://ftp.tex.ac.uk/tex-archive'   (England)
+CTAN has many mirrors worldwide; see the top-level file
+`README.mirrors' from one of the sites above, or finger
+<ctan@ftp.tug.org>, or see `http://www.tug.org/CTAN.sites'.  A list
+current as of the time of distribution is in the top-level file
+`./MIRROR'.
+You can also access CTAN via the World Wide Web, Gopher, electronic
+mail, or NFS.  The same `README.mirrors' file explains how.
+You will need to retrieve some or all of the following archives,
+depending on your needs (don't forget to set binary mode for file
+transfers):
+`CTAN:/systems/web2c/texmflib.tar.gz'
+A basic collection of fonts (TFM files only) and macro packages
+(including Texinfo and LaTeX 2e).  It unpacks into `texmf/'; if
+you change the structure of this hierarchy, you will also have to
+change the default search paths (*note Changing search paths::.).
+It is required unless you already have these files, in which case
+you should change the default paths as necessary to find them.
+`CTAN:/systems/web2c/web.tar.gz'
+The original WEB source files, written mostly by Don Knuth.
+Required unless you already have this `web' version.  (The WEB
+sources change irregularly with respect to Web2c itself.)  Unpacks
+into `web2c-VERSION'.
+`CTAN:/systems/web2c/web2c.tar.gz'
+The Web2c system.  Required.  Also unpacks into `web2c-VERSION'.
+`CTAN:/dviware/dvipsk.tar.gz'
+DVI-to-PostScript translator.  Unpacks into `dvipsk-VERSION'.
+Optional.
+`CTAN:/dviware/xdvik.tar.gz'
+X window system DVI previewer.  Unpacks into `xdvik-VERSION'.
+Optional.
+`CTAN:/dviware/dviljk.tar.gz'
+DVI-to-PCL (HP LaserJet) translator.  Unpacks into
+`dviljk-VERSION'.  Optional.
+All that said, the originating host for the software above is
+`ftp.tug.org'.  You can retrieve these distributions (but not much
+else) from the `tex/' directory on that host.
+File: kpathsea.info,  Node: CD-ROM distribution,  Next: Tape distribution,  Prev: Electronic distribution,  Up: unixtex.ftp
+CD-ROM distribution
+-------------------
+Numerous organizations distribute various TeX CD-ROM's:
+* TUG, UK TUG, and GUTenberg (French-speaking TeX user group)
+collaborated to produce the `TeX Live' CD-ROM, based on teTeX,
+which in turn is based on Web2c; email <tex-live@mail.tug.org> or
+see `http://www.tug.org/tex-live.html'.
+* NTG (Dutch-speaking TeX user group) produced the 4allTeX CD-ROM;
+email <ntg@nic.surfnet.nl>, or see
+`http://ei0.ei.ele.tue.nl/ntg/'.  This is a runnable system.
+* The Free Software Foundation's `Source Code CD-ROM' contains the
+minimal TeX source distribution described in the previous section
+(i.e., enough to print GNU documentation); email
+<gnu@prep.ai.mit.edu> or finger <fsf@prep.ai.mit.edu>.
+* The Gateway! CD-ROM set contains a runnable NetBSD/Amiga
+distribution and sources; see
+`http://www.netbsd.org/Sites/cdroms.html'.
+* The Prime Time TeXcetera CD-ROM is a copy of CTAN (see the previous
+section); email <ptf@ctcl.com> or see `http://www.ptf.com/ptf/'.
+* Walnut Creek's TeX CD-ROM is also a copy of CTAN; email
+<info@cdrom.com> or see `http://www.cdrom.com:/titles/tex.html'.
+* Most Linux distributions include some TeX package based on Web2c;
+see the Linux documentation file `Distribution-HOWTO' for a
+comparison of Linux distributions, available (for example) via
+`http://www.linux.org'.
+If you know of additional TeX CD-ROM distributions to add to this
+list, please inform <kb@mail.tug.org>.
+File: kpathsea.info,  Node: Tape distribution,  Next: Other TeX packages,  Prev: CD-ROM distribution,  Up: unixtex.ftp
+Tape distribution
+-----------------
+You can obtain a complete TeX distribution, including Web2c, on tape.
+Contact:
+Pierre MacKay / Denny Hall, Mail Stop DH-10 / Department of Classics
+University of Washington / Seattle, WA 98195 / USA
+phone: 206-543-2268; email: <unixtex@u.washington.edu>
+At this writing, the distribution is available in `tar' format on 1/4
+inch 4-track QIC-24 cartridges and 4mm DAT cartridges, and the cost is
+US$210.  Make checks payable to the University of Washington, drawn on
+a U.S. bank.  Purchase orders are acceptable, but they carry an extra
+charge of $10 to pay for invoice processing.  Overseas sites, please
+add $20 for shipment via air parcel post, or $30 for shipment via
+courier.
+File: kpathsea.info,  Node: Other TeX packages,  Prev: Tape distribution,  Up: unixtex.ftp
+Other TeX packages
+------------------
+Many other TeX implementations are available in `CTAN:/systems',
+including ready-to-run distributions for Unix, Amiga, Acorn, VMS,
+Macintosh, DOS, and Windows (in various forms).  Although Web2c has
+support in the source code for many operating systems, and in fact some
+of the other distributions are based on it, it's unlikely to work as
+distributed on anything but Unix.  (Please contribute improvements!)
+The Unix distribution alluded to above is the teTeX distribution.
+This includes both complete sources and precompiled binaries for many
+popular Unix variants, including Linux. It is based on Web2c, and
+contains many other TeX-related programs as well.
+The host labrea.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 build your TeX library tree ab initio,
+it is more reliable and less work to retrieve these files as part of
+the above packages. In any case, labrea is not the canonical source for
+anything except what was created by Stanford TeX project, so do not
+rely on all the files available at that ftp site being up-to-date.
+File: kpathsea.info,  Node: Reporting bugs,  Prev: unixtex.ftp,  Up: Installation
+Reporting bugs
+==============
+(A copy of this chapter is in the file `kpathsea/BUGS'.)
+If you have problems or suggestions, please report them to
+<tex-k@mail.tug.org> using the bug checklist below.
+Please report bugs in the documentation; not only factual errors or
+inconsistent behavior, but unclear or incomplete explanations, typos,
+wrong fonts, ...
+* Menu:
+* Bug checklist::       What to include in a good bug report.
+* Mailing lists::       Joining the bugs or announcements mailing lists.
+* Debugging::           Analyzing runtime problems.
+* Logging::             Recording searches.
+* Common problems::     When things go wrong.
+File: kpathsea.info,  Node: Bug checklist,  Next: Mailing lists,  Up: Reporting bugs
+Bug checklist
+-------------
+Before reporting a bug, please check below to be sure it isn't already
+known (*note Common problems::.).
+Bug reports should be sent via electronic mail to
+<tex-k@mail.tug.org>, or by postal mail to 135 Center Hill Road /
+Plymouth, MA 02360 / USA.
+The general principle is that a good bug report includes all the
+information necessary for reproduction.  Therefore, to enable
+investigation, your report should include the following:
+* The version number(s) of the program(s) involved, and of Kpathsea
+itself.  You can get the former by giving a sole option `--version'
+to the program, and the latter by running `kpsewhich --version'.
+The `NEWS' and `ChangeLog' files also contain the version number.
+* The hardware, operating system (including version number),
+compiler, and `make' program you are using (the output of `uname
+-a' is a start on the first two, though often incomplete).  If the
+bug involves the X window system, include X version and supplier
+information as well (examples: X11R6 from MIT; X11R4 from HP;
+OpenWindows 3.3 bundled with SunOS 4.1.4).
+* Any options you gave to `configure'.  This is recorded in the
+`config.status' files.
+If you are reporting a bug in `configure' itself, it's probably
+system-dependent, and it will be unlikely the maintainers can do
+anything useful if you merely report that thus-and-such is broken.
+Therefore, you need to do some additional work: for some bugs, you
+can look in the file `config.log' where the test that failed should
+appear, along with the compiler invocation and source program in
+question.  You can then compile it yourself by hand, and discover
+why the test failed.  Other `configure' bugs do not involve the
+compiler; in that case, the only recourse is to inspect the
+`configure' shell script itself, or the Autoconf macros that
+generated `configure'.
+* The log of all debugging output, if the bug is in path searching.
+You can get this by setting the environment variable
+`KPATHSEA_DEBUG' to `-1' before running the program.  Please look
+at the log yourself to make sure the behavior is really a bug
+before reporting it; perhaps "old" environment variable settings
+are causing files not to be found, for example.
+* The contents of any input files necessary to reproduce the bug.
+For bugs in DVI-reading programs, for example, this generally
+means a DVI file (and any EPS or other files it uses)--TeX source
+files are helpful, but the DVI file is necessary, because that's
+the actual program input.
+GNU `shar', available from `ftp://prep.ai.mit.edu/pub/gnu' is a
+convenient way of packaging multiple (possibly binary) files for
+electronic mail.  If you feel your input files are too big to send
+by email, you can ftp them to `ftp://ftp.tug.org/incoming' (that
+directory is writable, but not readable).
+* If you are sending a patch (do so if you can!), please do so in
+the form of a context diff (`diff -c') against the original
+distribution source.  Any other form of diff is either not as
+complete or harder for me to understand.  Please also include a
+`ChangeLog' entry.
+* 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, available from
+`ftp://prep.ai.mit.edu/pub/gnu').  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 code, however, the bug
+may well be in the compiler, rather than in the program or the
+library (*note TeX or Metafont failing: TeX or Metafont failing.).
+* Any additional information that will be helpful in reproducing,
+diagnosing, or fixing the bug.
+File: kpathsea.info,  Node: Mailing lists,  Next: Debugging,  Prev: Bug checklist,  Up: Reporting bugs
+Mailing lists
+-------------
+Web2c and Kpathsea in general are discussed on the mailing list
+<tex-k@mail.tug.org>.  To join, email <tex-k-request@mail.tug.org> with
+a line consisting of
+subscribe YOU@YOUR.PREFERRED.EMAIL.ADDRESS
+in the body of the message.
+You do not need to join to submit a report, nor will it affect whether
+you get a response.  There is no Usenet newsgroup equivalent (if you can
+be the one to set this up, email `tex-k-request').  Traffic on the list
+is fairly light, and is mainly bug reports and enhancement requests to
+the software.  The best way to decide if you want to join or not is
+read some of the archives from `ftp://ftp.tug.org/mail/archives/tex-k/'.
+Be aware that large data files are sometimes included in bug reports.
+If this is a problem for you, do not join the list.
+If you only want announcements of new releases, not bug reports and
+discussion, join <tex-archive@math.utah.edu> (via mail to
+<tex-archive-request@math.utah.edu>).
+If you are looking for general TeX help, such as how to use LaTeX,
+please use the mailing list <info-tex@shsu.edu> mailing list, which is
+gatewayed to the `comp.text.tex' Usenet newsgroup (or post to the
+newsgroup; the gateway is bidirectional).
+File: kpathsea.info,  Node: Debugging,  Next: Logging,  Prev: Mailing lists,  Up: Reporting bugs
+Debugging
+---------
+Kpathsea provides a number of runtime debugging options, detailed
+below by their names and corresponding numeric values.  When the files
+you expect aren't being found, the thing to do is enable these options
+and examine the output.
+You can set these with some runtime argument (e.g., `-d') to the
+program; in that case, you should use the numeric values described in
+the program's documentation (which, for Dvipsk and Xdvik, are different
+than those below).  It's best to give the `-d' (or whatever) option
+first, for maximal output.  Dvipsk and Xdvik have additional
+program-specific debugging options as well.
+You can also set the environment variable `KPATHSEA_DEBUG'; in this
+case, you should use the numbers below.  Also, if you run the program
+under a debugger and set the variable `kpathsea_debug', Also use the
+numbers below
+In any case, by far the simplest value to use is `-1', which will
+turn on all debugging output.  This is usually better than guessing
+which particular values will yield the output you need.
+Debugging output always goes to standard error, so you can redirect it
+easily.  For example, in Bourne-compatible shells:
+dvips -d -1 ... 2>/tmp/debug
+It is sometimes helpful to run the standalone Kpsewhich utility
+(*note Invoking kpsewhich::.), instead of the original program.
+In any case, you can *not* use the *names* below; you must always use
+somebody's numbers.  (Sorry.)  To set more than one option, just sum
+the corresponding numbers.
+`KPSE_DEBUG_STAT (1)'
+Report `stat'(2) calls. This is useful for verifying that your
+directory structure is not forcing Kpathsea to do many additional
+file tests (*note Slow path searching::., and *note Subdirectory
+expansion::.). If you are using an up-to-date `ls-R' database
+(*note Filename database::.), this should produce no output unless
+a nonexistent file that must exist is searched for.
+`KPSE_DEBUG_HASH (2)'
+Report lookups in all hash tables: `ls-R' and `aliases' (*note
+Filename database::.); font aliases (*note Fontmap::.); and config
+file values (*note Config files::.).  Useful when expected values
+are not being found, e.g.., file searches are looking at the disk
+instead of using `ls-R'.
+`KPSE_DEBUG_FOPEN (4)'
+Report file openings and closings. Especially useful when your
+system's file table is full, for seeing which files have been
+opened but never closed. In case you want to set breakpoints in a
+debugger: this works by redefining `fopen' (`fclose') to be
+`kpse_fopen_trace' (`kpse_fclose_trace').
+`KPSE_DEBUG_PATHS (8)'
+Report general path information for each file type Kpathsea is
+asked to search. This is useful when you are trying to track down
+how a particular path got defined--from `texmf.cnf', `config.ps',
+an environment variable, the compile-time default, etc.  This is
+the contents of the `kpse_format_info_type' structure defined in
+`tex-file.h'.
+`KPSE_DEBUG_EXPAND (16)'
+Report the directory list corresponding to each path element
+Kpathsea searches. This is only relevant when Kpathsea searches
+the disk, since `ls-R' searches don't look through directory lists
+in this way.
+`KPSE_DEBUG_SEARCH (32)'
+Report on each file search: the name of the file searched for, the
+path searched in, whether or not the file must exist (when drivers
+search for `cmr10.vf', it need not exist), and whether or not we
+are collecting all occurrences of the file in the path (as with,
+e.g., `texmf.cnf' and `texfonts.map'), or just the first (as with
+most lookups).  This can help you correlate what Kpathsea is doing
+with what is in your input file.
+Debugging output from Kpathsea is always written to standard error,
+and begins with the string `kdebug:'. (Except for hash table buckets,
+which just start with the number, but you can only get that output
+running under a debugger. See comments at the `hash_summary_only'
+variable in `kpathsea/db.c'.)
+File: kpathsea.info,  Node: Logging,  Next: Common problems,  Prev: Debugging,  Up: Reporting bugs
+Logging
+-------
+Kpathsea can record the time and filename found for each successful
+search.  This may be useful in finding good candidates for deletion when
+your filesystem is full, or in discovering usage patterns at your site.
+To do this, define the environment or config file variable
+`TEXMFLOG'.  The value is the name of the file to append the
+information to.  The file is created if it doesn't exist, and appended
+to if it does.
+Each successful search turns into one line in the log file: two words
+separated by a space. The first word is the time of the search, as the
+integer number of seconds since "the epoch", i.e., UTC midnight 1
+January 1970 (more precisely, the result of the `time' system call).
+The second word is the filename.
+For example, after `setenv TEXMFLOG /tmp/log', running Dvips on
+`story.dvi' appends the following lines:
+774455887 /usr/local/share/texmf/dvips/config.ps
+774455887 /usr/local/share/texmf/dvips/psfonts.map
+774455888 /usr/local/share/texmf/dvips/texc.pro
+774455888 /usr/local/share/texmf/fonts/pk/ljfour/public/cm/cmbx10.600pk
+774455889 /usr/local/share/texmf/fonts/pk/ljfour/public/cm/cmsl10.600pk
+774455889 /usr/local/share/texmf/fonts/pk/ljfour/public/cm/cmr10.600pk
+774455889 /usr/local/share/texmf/dvips/texc.pro
+Only filenames that are absolute are recorded, to preserve some
+semblance of privacy.
+File: kpathsea.info,  Node: Common problems,  Prev: Logging,  Up: Reporting bugs
+Common problems
+---------------
+Here are some common problems with configuration, compilation,
+linking, execution, ...
+* Menu:
+* Unable to find files::        If your program can't find fonts (or whatever).
+* Slow path searching::         If it takes forever to find anything.
+* Unable to generate fonts::    If MakeTeXPK fails.
+* TeX or Metafont failing::     Likely compiler bugs.
+* XtStrings::                   When _XtStrings is undefined.
+* dlopen::                      When dlopen is undefined.
+* ShellWidgetClass::            For dynamic linking troubles under OpenWindows.
+* Pointer combination warnings::  For old compilers that don't grok char *.
+File: kpathsea.info,  Node: Unable to find files,  Next: Slow path searching,  Up: Common problems
+Unable to find files
+....................
+If a program complains it cannot find fonts (or other input files),
+any of several things might be wrong.  In any case, you may find the
+debugging options helpful.  *Note Debugging::.
+* Perhaps you simply haven't installed all the necessary files; the
+basic fonts and input files are distributed separately from the
+programs.  *Note unixtex.ftp::.
+* You have (perhaps unknowingly) told Kpathsea to use search paths
+that don't reflect where the files actually are.  One common cause
+is having environment variables set from a previous installation,
+thus overriding what you carefully set in `texmf.cnf' (*note
+Supported file formats::.).  System `/etc/profile' or other files
+such may be the culprit.
+* Your files reside in a directory that is only pointed to via a
+symbolic link, in a leaf directory and is not listed in `ls-R'.
+Unfortunately, Kpathsea's subdirectory searching has an
+irremediable deficiency: If a directory D being searched for
+subdirectories contains plain files and symbolic links to other
+directories, but no true subdirectories, D will be considered a
+leaf directory, i.e., the symbolic links will not be followed.
+*Note Subdirectory expansion::.
+You can work around this problem by creating an empty dummy
+subdirectory in D. Then D will no longer be a leaf, and the
+symlinks will be followed.
+The directory immediately followed by the `//' in the path
+specification, however, is always searched for subdirectories,
+even if it is a leaf.  Presumably you would not have asked for the
+directory to be searched for subdirectories if you didn't want it
+to be.
+* If the fonts (or whatever) don't already exist, `MakeTeXPK' (or
+`MakeTeXMF' or `MakeTeXTFM') will try to create them.  If these
+rather complicated shell scripts fail, you'll eventually get an
+error message saying something like `Can't find font FONTNAME'.
+The best solution is to fix (or at least report) the bug in
+`MakeTeXPK'; the workaround is to generate the necessary fonts by
+hand with Metafont, or to grab them from a CTAN site (*note
+unixtex.ftp::.).
+* There is a bug in the library. *Note Reporting bugs::.
+File: kpathsea.info,  Node: Slow path searching,  Next: Unable to generate fonts,  Prev: Unable to find files,  Up: Common problems
+Slow path searching
+...................
+If your program takes an excessively long time to find fonts or other
+input files, but does eventually succeed, here are some possible
+culprits:
+* Most likely, you just have a lot of directories to search, and that
+takes a noticeable time. The solution is to create and maintain a
+separate `ls-R' file that lists all the files in your main TeX
+hierarchy.  *Note Filename database::.  Kpathsea always uses `ls-R'
+if it's present; there's no need to recompile or reconfigure any
+of the programs.
+* Your recursively-searched directories (e.g.,
+`/usr/local/share/texmf/fonts//'), contain a mixture of files and
+directories. This prevents Kpathsea from using a useful
+optimization (*note Subdirectory expansion::.).
+It is best to have only directories (and perhaps a `README') in the
+upper levels of the directory structure, and it's very important
+to have *only* files, and no subdirectories, in the leaf
+directories where the dozens of TFM, PK, or whatever files reside.
+In any case, you may find the debugging options helpful in determining
+precisely when the disk or network is being pounded.  *Note Debugging::.
+File: kpathsea.info,  Node: Unable to generate fonts,  Next: TeX or Metafont failing,  Prev: Slow path searching,  Up: Common problems
+Unable to generate fonts
+........................
+This can happen if either `MakeTeXPK' hasn't been installed properly,
+or if the local installation of Metafont isn't correct.
+If `mf' is a command not found by `MakeTeXPK', then you need to
+install Metafont (*note unixtex.ftp::.).
+If Metafont runs, but generates fonts at the wrong resolution, you
+need to be sure the `M' and `D' lines in your Dvips configuration file
+match (*note Config files: (dvips)Config files.).  For example, if
+`MakeTeXPK' is generating 300dpi fonts, but you need 600dpi fonts, you
+should have:
+M ljfour
+D 600
+If Metafont runs but generates fonts at a resolution of 2602dpi (and
+prints out the name of each character as well as just a character
+number, and maybe tries to display the characters), then your Metafont
+base file probably hasn't been made properly.  (It's using the default
+`proof' mode, instead of an actual device mode.)  To make a proper
+`plain.base', assuming the local mode definitions are contained in a
+file `modes.mf', run the following command (assuming Unix):
+inimf "plain; input modes; dump"
+Then copy the `plain.base' file from the current directory to where the
+base files are stored on your system (`/usr/local/share/texmf/web2c' by
+default), and make a link (either hard or soft) from `plain.base' to
+`mf.base' in that directory.  *Note inimf invocation: (web2c)inimf
+invocation.
+File: kpathsea.info,  Node: TeX or Metafont failing,  Next: XtStrings,  Prev: Unable to generate fonts,  Up: Common problems
+TeX or Metafont failing
+.......................
+If TeX or Metafont get a segmentation fault or otherwise fail while
+running a normal input file, the problem is usually a compiler bug
+(unlikely as that may sound).  Even if the trip and trap tests are
+passed, problems may lurk.  Optimization occasionally causes trouble in
+programs other than TeX and Metafont themselves, too.
+Insufficient swap space may also cause core dumps or other erratic
+behavior.
+For a workaround, if you enabled any optimization flags, it's best to
+omit optimization entirely.  In any case, the way to find the facts is
+to run the program under the debugger and see where it's failing.
+Also, if you have trouble with a system C compiler, I advise trying
+the GNU C compiler. And vice versa, unfortunately; but in that case I
+also recommend reporting a bug to the GCC mailing list; *note Bugs:
+(gcc)Bugs..
+To report compiler bugs effectively requires perseverance and
+perspicacity: you must find the miscompiled line, and that usually
+involves delving backwards in time from the point of error, checking
+through TeX's (or whatever program's) data structures.  Things are not
+helped by all-too-common bugs in the debugger itself.  Good luck.
+File: kpathsea.info,  Node: XtStrings,  Next: dlopen,  Prev: TeX or Metafont failing,  Up: Common problems
+`XtStrings'
+...........
+You may find that linking X programs results in an error from the
+linker that `XtStrings' is undefined, something like this:
+gcc -o virmf ...
+.../x11.c:130: undefined reference to `XtStrings'
+This generally happens because of a mismatch between the X include
+files with which you compiled and the X libraries with which you linked;
+often, the include files are from MIT and the libraries from Sun.
+The solution is to use the same X distribution for compilation and
+linking.  Probably `configure' was unable to guess the proper
+directories from your installation.  You can use the `configure'
+options `--x-includes=PATH' and `--x-libraries=PATH' to explicitly
+specify them.
+File: kpathsea.info,  Node: dlopen,  Next: ShellWidgetClass,  Prev: XtStrings,  Up: Common problems
+`dlopen'
+........
+(This section adapted from the file `dlsym.c' in the X distribution.)
+The `Xlib' library uses the standard C function `wcstombs'.  Under
+SunOS 4.1, `wcstombs' uses the `dlsym' interface defined in `libdl.so'.
+Unfortunately, the SunOS 4.1 distribution does not include a static
+`libdl.a' library.
+As a result, if you try to link an X program statically under SunOS,
+you may get undefined references to `dlopen', `dlsym', and `dlclose'.
+One workaround is to include these definitions when you link:
+void *dlopen() { return 0; }
+void *dlsym()  { return 0; }
+int dlclose()  { return -1; }
+These are contained in the `dlsym.c' file in the MIT X distribution.
+File: kpathsea.info,  Node: ShellWidgetClass,  Next: Pointer combination warnings,  Prev: dlopen,  Up: Common problems
+`ShellWidgetClass'
+..................
+(This section adapted from the comp.sys.sun.admin FAQ.)
+If you are linking with Sun's OpenWindows libraries in SunOS 4.1.x,
+you may get undefined symbols `_get_wmShellWidgetClass' and
+`_get_applicationShellWidgetClass' when linking. This problem does not
+arise using the standard MIT X libraries under SunOS.
+The cause is bugs in the `Xmu' shared library as shipped from Sun.
+There are several fixes:
+* Install the free MIT distribution from `ftp.x.org' and mirrors.
+* Get the OpenWindows patches listed below.
+* Statically link the `Xmu' library into the executable.
+* Avoid using `Xmu' at all. If you are compiling Metafont, *note
+Online Metafont graphics: (web2c)Online Metafont graphics.. If you
+are compiling Xdvi, see the `-DNOTOOL' option in `xdvik/INSTALL'.
+* Ignore the errors. The binary runs fine regardless.
+Here is the information for getting the two patches:
+Patch ID: 100512-02
+Bug ID's: 1086793, 1086912, 1074766
+Description: 4.1.x OpenWindows 3.0 `libXt' jumbo patch
+Patch ID: 100573-03
+Bug ID: 1087332
+Description: 4.1.x OpenWindows 3.0 undefined symbols when using shared `libXmu'.
+The way to statically link with `libXmu' depends on whether you are
+using a Sun compiler (e.g., `cc') or `gcc'. If the latter, alter the
+`x_libs' Make variable to include
+-static -lXmu -dynamic
+If you are using the Sun compiler, use `-Bstatic' and `-Bdynamic'.
+File: kpathsea.info,  Node: Pointer combination warnings,  Prev: ShellWidgetClass,  Up: Common problems
+Pointer combination warnings
+............................
+When compiling with old C compilers, you may get some warnings about
+"illegal pointer combinations".  These are spurious; just ignore them.
+I decline to clutter up the source with casts to get rid of them.
+File: kpathsea.info,  Node: Path searching,  Next: TeX support,  Prev: Installation,  Up: Top
+Path searching
+**************
+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.
+* Menu:
+* Searching overview::          Basic scheme for searching.
+* Path sources::                Where search paths can be defined.
+* Path expansion::              Special constructs in search paths.
+* Filename database::           Using an externally-built list to search.
+* Invoking kpsewhich::          Standalone path lookup.
+File: kpathsea.info,  Node: Searching overview,  Next: Path sources,  Up: Path searching
+Searching overview
+==================
+A "search path" is a colon-separated list of "path elements", which
+are directory names with a few extra frills.  A search path can come
+from (a combination of) many sources; see below.  To look up a file
+`foo' along a path `.:/dir', Kpathsea checks each element of the path
+in turn: first `./foo', then `/dir/foo', returning the first match (or
+possibly all matches).
+The "colon" and "slash" mentioned here aren't necessarily `:' and `/'
+on non-Unix systems.  Kpathsea tries to adapt to other operating
+systems' conventions.
+To check a particular path element E, Kpathsea first sees if a
+prebuilt database (*note Filename database::.) applies to E, i.e., if
+the database is in a directory that is a prefix of E.  If so, the path
+specification is matched against the contents of the database.
+If the database does not exist, or does not apply to this path
+element, or contains no matches, the filesystem is searched (if this
+was not forbidden by the specification with `!!' and if the file being
+searched for must exist).  Kpathsea constructs the list of directories
+that correspond to this path element, and then checks in each for the
+file being searched for.  (To help speed future lookups of files in the
+same directory, the directory in which a file is found is floated to the
+top of the directory list.)
+The "file must exist" condition comes into play with VF files and
+input files read by the TeX `\openin' command.  These files may not
+exist (consider `cmr10.vf'), and so it would be wrong to search the
+disk for them.  Therefore, if you fail to update `ls-R' when you
+install a new VF file, it will never be found.
+Each path element is checked in turn: first the database, then the
+disk.  If a match is found, the search stops and the result is
+returned.  This avoids possibly-expensive processing of path
+specifications that are never needed on a particular run.  (Unless the
+search explicitly requested all matches.)
+Although the simplest and most common path element is a directory
+name, Kpathsea supports additional features in search paths: layered
+default values, environment variable names, config file values, users'
+home directories, and recursive subdirectory searching.  Thus, we say
+that Kpathsea "expands" a path element, meaning transforming all thel
+magic specifications into the basic directory name or names.  This
+process is described in the sections below.  It happens in the same
+order as the sections.
+Exception to all of the above: If the filename being searched for is
+absolute or explicitly relative, i.e., starts with `/' or `./' or
+`../', Kpathsea simply checks if that file exists.
+Ordinarily, if Kpathsea tries to access a file or directory that
+cannot be read, it gives a warning.  This is so you will be alerted to
+directories or files that accidentally lack read permission (for
+example, a `lost+found').  If you prefer not to see these warnings,
+include the value `readable' in the `TEX_HUSH' environment variable or
+config file value.
+This generic path searching algorithm is implemented in
+`kpathsea/pathsearch.c'.  It is employed by a higher-level algorithm
+when searching for a file of a particular type (*note File lookup::.,
+and *Note Glyph lookup::).
+File: kpathsea.info,  Node: Path sources,  Next: Path expansion,  Prev: Searching overview,  Up: Path searching
+Path sources
+============
+A search path can come from many sources.  In the order in which
+Kpathsea uses them:
+1. 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'.
+2. A program-specific configuration file, e.g., an `S /a:/b' line in
+Dvips' `config.ps' (*note Config files: (dvips)Config files.).
+3. A line in a Kpathsea configuration file `texmf.cnf', e.g.,
+`TEXINPUTS=/c:/d' (see below).
+4. The compile-time default (specified in `kpathsea/paths.h').
+You can see each of these values for a given search path by using the
+debugging options (*note Debugging::.).
+These sources may be combined via default expansion (*note Default
+expansion::.).
+* Menu:
+* Config files::        Kpathsea's runtime config files (texmf.cnf).
+File: kpathsea.info,  Node: Config files,  Up: Path sources
+Config files
+------------
+As mentioned above, Kpathsea reads "runtime configuration files"
+named `texmf.cnf' for search path and other definitions.  The search
+path used to look for these configuration files is named `TEXMFCNF',
+and is constructed in the usual way, as described above, except that
+configuration files cannot be used to define the path, naturally; also,
+an `ls-R' database is not used to search for them.
+Kpathsea reads *all* `texmf.cnf' files in the search path, not just
+the first one found; definitions in earlier files override those in
+later files.  Thus, with the search path of `.:$TEXMF', values from
+`./texmf.cnf' override those from `$TEXMF/texmf.cnf'.
+While (or instead of) reading this description, you may find it
+helpful to look at the distributed `texmf.cnf', which uses or at least
+mentions most features.  The format of `texmf.cnf' files follows:
+* Comments start with `%' and continue to the end of the line.
+* Blank lines are ignored.
+* A `\' at the end of a line acts as a continuation character, i.e.,
+the next line is appended.  Whitespace at the beginning of
+continuation lines is not ignored.
+* Each remaining line must look like
+VARIABLE [. PROGNAME] [=] VALUE
+where the `=' and surrounding whitespace is optional.
+* 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'.  This allows different
+flavors of TeX to have different search paths, for example.
+* 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 NT.  (If
+you really want `;''s in your filenames, add
+`-DALLOW_SEMICOLON_IN_FILENAMES' to `CFLAGS'.)
+* All definitions are read before anything is expanded, so you can
+use variables before they are defined (like Make, unlike most other
+programs).
+Here is a configuration file fragment illustrating most of these points:
+% TeX input files -- i.e., anything to be found by \input or \openin ...
+latex209_inputs = .:$TEXMF/tex/latex209//:$TEXMF/tex//
+latex2e_inputs = .:$TEXMF/tex/latex//:$TEXMF/tex//
+TEXINPUTS = .:$TEXMF/tex//
+TEXINPUTS.latex209 = $latex209_inputs
+TEXINPUTS.latex2e = $latex2e_inputs
+TEXINPUTS.latex = $latex2e_inputs
+Although 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.  But there seemed little advantage to doing 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 implementation of all this is in `kpathsea/cnf.c'.
+File: kpathsea.info,  Node: Path expansion,  Next: Filename database,  Prev: Path sources,  Up: Path searching
+Path expansion
+==============
+Kpathsea recognizes certain special characters and constructions in
+search paths, similar to that in shells.  As a general example:
+`~$USER/{foo,bar}//baz' expands to all subdirectories under directories
+`foo' and `bar' in $USER's home directory that contain a directory or
+file `baz'.  These expansions are explained in the sections below.
+* Menu:
+* Default expansion::           a: or :a or a::b expands to a default.
+* Variable expansion::          $foo and ${foo} expand to environment values.
+* Tilde expansion::             ~ and ~user expand to home directories.
+* Brace expansion::             a{foo,bar}b expands to afoob abarb.
+* Subdirectory expansion::      a// and a//b recursively expand to subdirs.
+File: kpathsea.info,  Node: Default expansion,  Next: Variable expansion,  Up: Path expansion
+Default expansion
+-----------------
+If the highest-priority search path (*note Path sources::.) contains
+an "extra colon" (i.e., leading, trailing, or doubled), Kpathsea
+inserts at that point the next-highest-priority search path that is
+defined.  If that inserted path has an extra colon, the same happens
+with the next-highest.  (An extra colon in the compile-time default
+value has unpredictable results, so installers beware.)
+For example, given an environment variable setting
+setenv TEXINPUTS /home/karl:
+and a `TEXINPUTS' value from `texmf.cnf' of
+.:$TEXMF//tex
+then the final value used for searching will be:
+/home/karl:.:$TEXMF//tex
+Since Kpathsea looks for multiple configuration files, it would be
+natural to expect that (for example) an extra colon in `./texmf.cnf'
+would expand to the path in `$TEXMF/texmf.cnf'.  Or, with Dvips'
+configuration files, that an extra colon in `config.$PRINTER' would
+expand to the path in `config.ps'.  This doesn't happen.  It's not
+clear this would be desirable in all cases, and trying to devise a way
+to specify the path to which the extra colon should expand seemed truly
+baroque.
+Technicality: Since it would be useless to insert the default value in
+more than one place, Kpathsea changes only one extra `:' and leaves any
+others in place (where they will eventually be equivalent to `.', i.e.,
+the current directory).  Kpathsea checks first for a leading `:', then
+a trailing `:', then a doubled `:'.
+You can trace this by debugging "paths" (*note Debugging::.).
+Default expansion is implemented in the source file
+`kpathsea/kdefault.c'.
+File: kpathsea.info,  Node: Variable expansion,  Next: Tilde expansion,  Prev: Default expansion,  Up: Path expansion
+Variable expansion
+------------------
+`$foo' or `${foo}' in a path element is replaced by (1) the value of
+an environment variable `foo' (if defined); (2) the value of `foo' from
+`texmf.cnf' (if defined); (3) the empty string.
+If the character after the `$' is alphanumeric or `_', the variable
+name consists of all consecutive such characters. If the character
+after the `$' is a `{', the variable name consists of everything up to
+the next `}' (braces may not be nested).  Otherwise, Kpathsea gives a
+warning and ignores the `$' and its following character.
+You must quote the $'s and braces as necessary for your shell.
+*Shell* variable values cannot be seen by Kpathsea, i.e., ones defined
+by `set' in C shells and without `export' in Bourne shells.
+For example, given
+setenv tex /home/texmf
+setenv TEXINPUTS .:$tex:${tex}prev
+the final `TEXINPUTS' path is the three directories:
+.:/home/texmf:/home/texmfprev
+The `.PROGNAME' suffix on variables and `_PROGNAME' on environment
+variable names are not implemented for general variable expansions.
+These are only recognized when search paths are initialized (*note Path
+sources::.).
+Variable expansion is implemented in the source file
+`kpathsea/variable.c'.
+File: kpathsea.info,  Node: Tilde expansion,  Next: Brace expansion,  Prev: Variable expansion,  Up: Path expansion
+Tilde expansion
+---------------
+A leading `~' in a path element is replaced by the value of the
+environment variable `HOME', or `.' if `HOME' is not set.
+A leading `~USER' in a path element is replaced by USER's home
+directory from the system `passwd' database.
+For example,
+setenv TEXINPUTS ~/mymacros:
+will prepend a directory `mymacros' in your home directory to the
+default path.
+As a special case, if a home directory ends in `/', the trailing
+slash is dropped, to avoid inadvertently creating a `//' construct in
+the path.  For example, if the home directory of the user `root' is
+`/', the path element `~root/mymacros' expands to just `/mymacros', not
+`//mymacros'.
+Tilde expansion is implemented in the source file `kpathsea/tilde.c'.
+File: kpathsea.info,  Node: Brace expansion,  Next: Subdirectory expansion,  Prev: Tilde expansion,  Up: Path expansion
+Brace expansion
+---------------
+`x{A,B}y' expands to `xAy:xBy'.  For example:
+foo/{1,2}/baz
+expands to `foo1baz:foo2baz'.  `:' is the path separator on the current
+system; e.g., on a DOS system, it's `;'.
+Braces can be nested; for example, `x{a,b{1,2}}y' expands to
+`xay:xb1y:xb2y'.
+This feature can be used to implement multiple TeX hierarchies, by
+assigning a brace list to `$TEXMF', as mentioned in `texmf.cnf.in'.
+Brace expansion is implemented in the source file
+`kpathsea/expand.c'.  It is taken from Bash, and is thus covered by the
+GNU General Public License, rather than the Library General Public
+License that covers the rest of Kpathsea.
+File: kpathsea.info,  Node: Subdirectory expansion,  Prev: Brace expansion,  Up: Path expansion
+Subdirectory expansion
+----------------------
+Two or more consecutive slashes in a path element following a
+directory D is replaced by all subdirectories of D: first those
+subdirectories directly under D, then the subsubdirectories under
+those, and so on.  At each level, the order in which the directories are
+searched is unspecified.  (It's "directory order", and definitely not
+alphabetical.)
+If you specify any filename components after the `//', only
+subdirectories which match those components are included.  For example,
+`/a//b' would expand into directories `/a/1/b', `/a/2/b', `/a/1/1/b',
+and so on, but not `/a/b/c' or `/a/1'.
+You can include multiple `//' constructs in the path.
+`//' at the beginning of a path is ignored; you didn't really want to
+search every directory on the system, did you?
+I should mention one related implementation trick, which I took from
+GNU find.  Matthew Farwell suggested it, and David MacKenzie
+implemented it.
+The trick is that in every real Unix implementation (as opposed to the
+POSIX specification), a directory which contains no subdirectories will
+have exactly two links (namely, one for `.' and one for `..').  That is
+to say, the `st_nlink' field in the `stat' structure will be two.
+Thus, we don't have to stat everything in the bottom-level (leaf)
+directories--we can just check `st_nlink', notice it's two, and do no
+more work.
+But if you have a directory that contains a single subdirectory and
+500 regular files, `st_nlink' will be 3, and Kpathsea has to stat every
+one of those 501 entries.  Therein lies slowness.
+You can disable the trick by undefining `UNIX_ST_LINK' in
+`kpathsea/config.h'. (It is undefined by default except under Unix.)
+Unfortunately, in some cases files in leaf directories are `stat''d:
+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.
+Subdirectory expansion is implemented in the source file
+`kpathsea/elt-dirs.c'.
+File: kpathsea.info,  Node: Filename database,  Next: Invoking kpsewhich,  Prev: Path expansion,  Up: Path searching
+Filename database (`ls-R')
+==========================
+Kpathsea goes to some lengths to minimize disk accesses for searches
+(*note Subdirectory expansion::.).  Nevertheless, at installations with
+enough directories, searching each possible directory for a given file
+can take an excessively long time (depending on the speed of the disk,
+whether it's NFS-mounted, how patient you are, etc.).
+In practice, a font tree containing the standard PostScript and PCL
+fonts is large enough for searching to be noticeably slow on typical
+systems these days.  Therefore, Kpathsea can use an externally-built
+"database" 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.
+The `ls-R' and `aliases' features are implemented in the source file
+`kpathsea/db.c'.
+* Menu:
+* ls-R::                        The main filename database.
+* Filename aliases::            Aliases for those names.
+* Database format::             Syntax details of the database file.
+File: kpathsea.info,  Node: ls-R,  Next: Filename aliases,  Up: Filename database
+`ls-R'
+------
+As mentioned above, you must name the main filename database `ls-R'.
+You can put one at the root of each TeX installation hierarchy you wish
+to search (`$TEXMF' by default); most sites have only one hierarchy.
+Kpathsea looks for `ls-R' files along the `TEXMFDBS' path, so that
+should presumably match the list of hierarchies.
+The recommended way to create and maintain `ls-R' is to run the
+`MakeTeXls-R' script, which is installed in `$(bindir)'
+(`/usr/local/bin' by default).  That script goes to some trouble to
+follow symbolic links as necessary, etc.  It's also invoked by the
+distributed `MakeTeX...' scripts.
+At its simplest, though, you can build `ls-R' with the command
+cd /YOUR/TEXMF/ROOT && ls -LAR ./ >ls-R
+presuming your `ls' produces the right output format (see the section
+below).  GNU `ls', for example, outputs in this format.  Also presuming
+your `ls' hasn't been aliased in a system file (e.g., `/etc/profile')
+to something problematic, e.g., `ls --color=tty'.  In that case, you
+will have to disable the alias before generating `ls-R'.  For the
+precise definition of the file format, *note Database format::..
+Regardless of whether you use the supplied script or your own, you
+will almost certainly want to invoke it via `cron', so when you make
+changes in the installed files (say if you install a new LaTeX
+package), `ls-R' will be automatically updated.
+The `-A' option to `ls' includes files beginning with `.' (except for
+`.' and `..'), such as the file `.tex' included with the LaTeX tools
+package.  (On the other hand, *directories* whose names begin with `.'
+are always ignored.)
+If your system does not support symbolic links, omit the `-L'.
+`ls -LAR /YOUR/TEXMF/ROOT' will also work.  But using `./' avoids
+embedding absolute pathnames, so the hierarchy can be easily
+transported.  It also avoids possible trouble with automounters or
+other network filesystem conventions.
+Kpathsea warns you if it finds an `ls-R' file, but the file does not
+contain any usable entries.  The usual culprit is running plain `ls -R'
+instead of `ls -LR ./' or `ls -R /YOUR/TEXMF/ROOT'.  Another
+possibility is some system directory name starting with a `.' (perhaps
+if you are using AFS); Kpathsea ignores everything under such
+directories.
+Because the database may be out-of-date for a particular run, if a
+file is not found in the database, by default Kpathsea goes ahead and
+searches the disk. If a particular path element begins with `!!',
+however, *only* the database will be searched for that element, never
+the disk.  If the database does not exist, nothing will be searched.
+Because this can surprise users ("I see the font `foo.tfm' when I do an
+`ls'; why can't Dvips find it?"), it is not in any of the default
+search paths.
+File: kpathsea.info,  Node: Filename aliases,  Next: Database format,  Prev: ls-R,  Up: Filename database
+Filename aliases
+----------------
+In some circumstances, you may wish to find a file under several
+names.  For example, suppose a TeX document was created using a DOS
+system and tries to read `longtabl.sty'.  But now it's being run on a
+Unix system, and the file has its original name, `longtable.sty'.  The
+file won't be found.  You need to give the actual file `longtable.sty'
+an alias `longtabl.sty'.
+You can handle this by creating a file `aliases' as a companion to
+the `ls-R' for the hierarchy containing the file in question.  (You
+must have an `ls-R' for the alias feature to work.)
+The format of `aliases' is simple: two whitespace-separated words per
+line; the first is the real name `longtable.sty', and second is the
+alias (`longtabl.sty').  These must be base filenames, with no
+directory components.  `longtable.sty' must be in the sibling `ls-R'.
+Also, blank lines and lines starting with `%' or `#' are ignored in
+`aliases', to allow for comments.
+If a real file `longtabl.sty' exists, it is used regardless of any
+aliases.
+File: kpathsea.info,  Node: Database format,  Prev: Filename aliases,  Up: Filename database
+Database format
+---------------
+The "database" read by Kpathsea is a line-oriented file of plain
+text. The format is that generated by GNU (and most other) `ls'
+programs given the `-R' option, as follows.
+* Blank lines are ignored.
+* If a line begins with `/' or `./' or `../' and ends with a colon,
+it's the name of a directory.  (`../' lines aren't useful,
+however, and should not be generated.)
+* All other lines define entries in the most recently seen directory.
+/'s in such lines will produce possibly-strange results.
+* Files with no preceding directory line are ignored.
+For example, here's the first few lines of `ls-R' (which totals about
+30K bytes) on my system:
+bibtex
+dvips
+fonts
+ls-R
+metafont
+metapost
+tex
+web2c
+./bibtex:
+bib
+bst
+doc
+./bibtex/bib:
+asi.bib
+btxdoc.bib
+...
+File: kpathsea.info,  Node: Invoking kpsewhich,  Prev: Filename database,  Up: Path searching
+`kpsewhich': Standalone path searching
+======================================
+The Kpsewhich program exercises the path searching functionality
+independent of any particular application.  This can also be useful as a
+sort of `find' program to locate files in your TeX hierarchies, perhaps
+in administrative scripts.  It is used heavily in the distributed
+`MakeTeX...' scripts.
+Synopsis:
+kpsewhich OPTION... FILENAME...
+The options and filename(s) to look up can be intermixed.  Options
+can start with either `-' or `--', and any unambiguous abbreviation is
+accepted.
+* Menu:
+* Path searching options::      Changing the mode, resolution, etc.
+* Auxiliary tasks::             Path and variable expansion.
+* Standard options::            -help and -version.
+File: kpathsea.info,  Node: Path searching options,  Next: Auxiliary tasks,  Up: Invoking kpsewhich
+Path searching options
+----------------------
+Kpsewhich looks up each non-option argument on the command line as a
+filename, and returns the first file found.  There is no option to
+return all the files with a particular name (you can run the Unix
+`find' utility for that, *note Invoking find: (findutils)Invoking
+find.).
+Various options alter the path searching behavior:
+`--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.
+`--format=NAME'
+Set the format for lookup to NAME.  By default, the format is
+guessed from the filename.  In fact, the recognized filename
+extensions and the allowable NAMEs (including any leading `.') are
+the same.
+You can also specify an integer for NAME; this is the only way to
+specify formats that don't have an associated suffix, such as
+MetaPost support files and Dvips configuration files.  It's also
+somewhat faster, since no unused formats need to be initialized.
+The integers appear in the output of `--help', and are of course
+subject to change.
+Here's the current list of recognized names and numbers.  *Note
+Supported file formats::, for more information on each of these.
+gf(0)
+pk(1)
+bitmap font (2)
+.afm(3)
+.base(4)
+.bib(5)
+.bst(6)
+.cnf(7)
+ls-R(8)
+.fmt(9)
+.map(10)
+.mem(11)
+.mf(12)
+.pool(13)
+.mft(14)
+.mp(15)
+.pool(16)
+MetaPost support (17)
+.ocp(18)
+.ofm(19)
+.opl(20)
+.otp(21)
+.ovf(22)
+.ovp(23)
+graphic/figure (24) .eps .epsi
+.tex(25) .ltx .dtx .texi .texinfo .txi .eps .epsi
+TeX documentation (26)
+.pool(27)
+TeX sources (28)
+PostScript header/font (29) .pro
+Troff fonts (30)
+.tfm(31)
+.pfa(32) .pfb
+.vf(33)
+dvips config (34)
+.ist(35)
+This option and `--path' are mutually exclusive.
+`--interactive'
+After processing the command line, read additional filenames to
+look up from standard input.
+`-maketex=FILETYPE'
+`-no-maketex=FILETYPE'
+Turn on or off the `MakeTeX' script associated with FILETYPE.  The
+only values that make sense for FILETYPE are `pk', `mf', `tex',
+and `tfm'. By default, all are off in Kpsewhich.  *Note MakeTeX
+scripts::.
+`--mode=STRING'
+Set the mode name to STRING; this also only affects `gf' and `pk'
+lookups.  No default: any mode will be found.  *Note MakeTeX
+script arguments::.
+`--must-exist'
+Do everything possible to find the files, notably including
+searching the disk.  By default, only the `ls-R' database is
+checked, in the interest of efficiency.
+`--path=STRING'
+Search along the path STRING (colon-separated as usual), instead
+of guessing the search path from the filename.  `//' and all the
+usual expansions are supported (*note Path expansion::.).  This
+option and `--format' are mutually exclusive.  To output the
+complete directory expansion of a path, instead of doing a
+one-shot lookup, see `--path-expand' in the following section.
+`--progname=NAME'
+Set the program name to NAME; default is `kpsewhich'.  This can
+affect the search paths via the `.PROGNAM' feature in
+configuration files (*note Config files::.).
+File: kpathsea.info,  Node: Auxiliary tasks,  Next: Standard options,  Prev: Path searching options,  Up: Invoking kpsewhich
+Auxiliary tasks
+---------------
+Kpsewhich provides some additional features not strictly related to
+path lookup:
+* `--debug=NUM' sets the debugging options to NUM.  *Note
+Debugging::.
+* `--expand-var=STRING' outputs the variable expansion of STRING.
+For example, the `MakeTeX...' scripts run `kpsewhich
+--expand-var='$TEXMF'' to find the root of the TeX system
+hierarchy.  *Note Path expansion::.
+* `--expand-path=STRING' outputs the complete expansion of STRING as
+a colon-separated path.  This is useful to construct a search path
+for a program that doesn't accept recursive subdirectory
+specifications.  The option `--separator=STRING' changes the
+separator in the output from `:' to STRING.
+For one-shot uses of an arbitrary (not built in to Kpathsea) path,
+see `--path' in the previous section.
+* `--show-path=NAME' shows the path that would be used for file
+lookups of file type NAME.  Either a filename extension (`pk',
+`.vf', etc.) or an integer can be used, just as with `--format',
+described in the previous section.
+File: kpathsea.info,  Node: Standard options,  Prev: Auxiliary tasks,  Up: Invoking kpsewhich
+Standard options
+----------------
+Kpsewhich accepts the standard GNU options:
+* `--help' prints a help message on standard output and exits.
+* `--version' prints the Kpathsea version number and exits.
+File: kpathsea.info,  Node: TeX support,  Next: Programming,  Prev: Path searching,  Up: Top
+TeX support
+***********
+Although the basic features in Kpathsea can be used for any type of
+path searching, it came about (like all libraries) with a specific
+application in mind: I wrote Kpathsea specifically for TeX system
+programs.  I had been struggling with the programs I was using (Dvips,
+Xdvi, and TeX itself) having slightly different notions of how to
+specify paths; and debugging was painful, since no code was shared.
+Therefore, Kpathsea provides some TeX-specific formats and features.
+Indeed, many of the supposedly generic path searching features were
+provided because they seemed useful in that conTeXt (font lookup,
+particularly).
+Kpathsea provides a standard way to search for files of any of the
+supported file types; glyph fonts are a bit different than all the rest.
+Searches are based solely on filenames, not file contents--if a GF file
+is named `cmr10.600pk', it will be found as a PK file.
+* Menu:
+* Supported file formats::      File types Kpathsea knows about.
+* File lookup::                 Searching for most kinds of files.
+* Glyph lookup::                Searching for bitmap fonts.
+* Suppressing warnings::        Avoiding warnings via TEX_HUSH.
+File: kpathsea.info,  Node: Supported file formats,  Next: File lookup,  Up: TeX support
+Supported file formats
+======================
+Kpathsea has support for a number of file types.  Each file type has a
+list of environment and config file variables that are checked to define
+the search path, and most have a default suffix that plays a role in
+finding files (see the next section).  Some also define additional
+suffixes, and/or a program to be run to create missing files on the fly.
+Since environment variables containing periods, such as
+`TEXINPUTS.latex', are not allowed on some systems, Kpathsea looks for
+environment variables with an underscore, e.g., `TEXINPUTS_latex'
+(*note Config files::.).
+The following table lists the above information.
+`.afm'
+(Adobe font metrics, *note Metric files: (dvips)Metric files.)
+`AFMFONTS'.
+`.base'
+(Metafont memory dump, *note Memory dumps: (web2c)Memory dumps.)
+`MFBASES', `TEXMFINI'.
+`.bib'
+(BibTeX bibliography source, *note bibtex invocation:
+(web2c)bibtex invocation.) `BIBINPUTS', `TEXBIB'.
+`.bst'
+(BibTeX style file, *note Basic BibTeX style files: (web2c)Basic
+BibTeX style files.) `BSTINPUTS'.
+`.cnf'
+(Runtime configuration files, *note Config files::.) `TEXMFCNF'.
+`ls-R'
+(Filename databases, *note Filename database::.) `TEXMFDBS'.
+`.fmt'
+(TeX memory dump, *note Memory dumps: (web2c)Memory dumps.)
+`TEXFORMATS', `TEXMFINI'.
+`gf'
+(generic font bitmap, *note Glyph files: (dvips)Glyph files.)
+`PROGRAMFONTS', `GFFONTS', `GLYPHFONTS', `TEXFONTS'.
+`.map'
+(Fontmaps, *note Fontmap::.) `TEXFONTMAPS'.
+`.ist'
+(makeindex style files) `TEXINDEXSTYLE', `INDEXSTYLE'.
+`.mem'
+(MetaPost memory dump, *note Memory dumps: (web2c)Memory dumps.)
+`MPMEMS', `TEXMFINI'.
+`.mf'
+(Metafont source, *note mf invocation: (web2c)mf invocation.)
+`MFINPUTS'; dynamic creation program: `MakeTeXMF'.
+`.mft'
+(`MFT' style file, *note mft invocation: (web2c)mft invocation.)
+`MFTINPUTS'.
+`mf.pool'
+(Metafont program strings, *note pooltype invocation:
+(web2c)pooltype invocation.) `MFPOOL', `TEXMFINI'.
+`.mp'
+(MetaPost source, *note mpost invocation: (web2c)mpost invocation.)
+`MPINPUTS'.
+`mp.pool'
+(MetaPost program strings, *note pooltype invocation:
+(web2c)pooltype invocation.) `MPPOOL', `TEXMFINI'.
+`(none)'
+(MetaPost support files, used by DMP; *note dmp invocation:
+(web2c)dmp invocation.) `MPSUPPORT'.
+`.ocp'
+(Omega compiled process files) `OCPINPUTS';
+dynamic creation program: `MakeOmegaOCP'.
+`.ofm'
+(Omega font metrics) `OFMFONTS', `TEXFONTS';
+dynamic creation program: `MakeOmegaOFM'.
+`.opl'
+(Omega property lists) `OPLFONTS', `TEXFONTS'.
+`.otp'
+(Omega translation process files) `OTPINPUTS'.
+`.ovf'
+(Omega virtual fonts) `OVFFONTS', `TEXFONTS'.
+`.ovp'
+(Omega virtual property lists) `OVPFONTS', `TEXFONTS'.
+`.eps'
+(Encapsulated PostScript figures, *note PostScript figures:
+(dvips)PostScript figures.) `TEXPICTS', `TEXINPUTS'; additional
+suffixes: `.epsi'.
+`pk'
+(packed bitmap fonts, *note Glyph files: (dvips)Glyph files.)
+`PROGRAMFONTS' (PROGRAM being `XDVI', etc.), `PKFONTS', `TEXPKS',
+`GLYPHFONTS', `TEXFONTS'; dynamic creation program: `MakeTeXPK'.
+`.pro'
+(downloadable PostScript, *note Header files: (dvips)Header files.)
+`TEXPSHEADERS', `PSHEADERS'.
+`.tex'
+(TeX source, *note tex invocation: (web2c)tex invocation.)
+`TEXINPUTS'; additional suffixes: `.ltx' `.dtx' `.texi' `.texinfo'
+`.txi' `.eps' `.epsi'; dynamic creation program: `MakeTeXTeX'.
+`(none)'
+(Documentation files for the TeX system) `TEXDOCS'.
+`tex.pool'
+(TeX program strings, *note pooltype invocation: (web2c)pooltype
+invocation.) `TEXPOOL', `TEXMFINI'.
+`(none)'
+(Source files for the TeX system) `TEXSOURCES'.
+`.tfm'
+(TeX font metrics, *note Metric files: (dvips)Metric files.)
+`TFMFONTS', `TEXFONTS'; dynamic creation program: `MakeTeXTFM'.
+`(none)'
+(Troff fonts, used by DMP; *note DMP invocation: (web2c)DMP
+invocation.) `TRFONTS'.
+`.pfa'
+(Type 1 PostScript outline fonts, *note Glyph files: (dvips)Glyph
+files.) `T1FONTS', `T1INPUTS', `TEXPSHEADERS', `DVIPSHEADERS';
+additional suffix: `.pfb'.
+`.vf'
+(virtual fonts, *note Virtual fonts: (dvips)Virtual fonts.)
+`VFFONTS', `TEXFONTS'.
+`(none)'
+(Dvips `config.*' files, such as `config.ps', *note Config files:
+(dvips)Config files.) `TEXCONFIG'.
+If an environment variable by these names are set, the corresponding
+`texmf.cnf' definition won't be looked at (unless, as usual, the
+environment variable value has an extra `:').  *Note Default
+expansion::.
+For the font variables, the intent is that:
+* `TEXFONTS' is the default for everything.
+* `GLYPHFONTS' is the default for bitmap (or, more precisely,
+non-metric) files.
+* Each font format has a variable of its own.
+* Each program has its own font override path as well; e.g.,
+`DVIPSFONTS' for Dvipsk.  Again, this is for bitmaps, not metrics.
+File: kpathsea.info,  Node: File lookup,  Next: Glyph lookup,  Prev: Supported file formats,  Up: TeX support
+File lookup
+===========
+This section describes how Kpathsea searches for most files (bitmap
+font searches are the exception, as described in the next section).
+Here is the search strategy for a file NAME:
+1. If NAME has a suffix, search for exactly NAME along the
+appropriate path.  Example: given `foo.sty', look for `foo.sty'
+before `foo.sty.tex', even though it's a TeX input file.
+2. If the file format defines a default suffix, and the suffix of
+NAME is not already that default, try appending the default.
+Example: given `foo.bar', search for `foo.bar.tex'.  But if given
+`foo.tex', don't bother to search for `foo.tex.tex'.
+3. If we're searching for a TFM, PK, or GF file, look for aliases of
+NAME in `texfonts.map' files (*note Fontmap::.).  Example: given
+`Times-Roman', find `ptmr'.
+4. If the file format defines a program to invoke to create missing
+files, run it (*note MakeTeX scripts::.).
+5. Search for NAME itself, if we haven't done so already.  Example:
+given `foo', search for `foo'.
+This is implemented in the routine `kpse_find_file' in
+`kpathsea/tex-file.c'.  You can watch it in action with the debugging
+options (*note Debugging::.).
+File: kpathsea.info,  Node: Glyph lookup,  Next: Suppressing warnings,  Prev: File lookup,  Up: TeX support
+Glyph lookup
+============
+This section describes how Kpathsea searches for a bitmap font in GF
+or PK format (or either) given a font name (e.g., `cmr10') and a
+resolution (e.g., 600).
+Here is an outline of the search strategy (details in the sections
+below) for a file NAME at resolution DPI.  The search stops at the
+first successful lookup.
+1. Look for an existing file NAME.DPIFORMAT in the specified
+format(s).
+2. If NAME is an alias for a file F in the fontmap file
+`texfonts.map', look for F.DPI.
+3. Run an external program (typically named `MakeTeXPK') to generate
+the font (*note MakeTeX scripts::.)
+4. Look for FALLBACK.DPI, where FALLBACK is some last-resort font
+(typically `cmr10').
+This is implemented in `kpse_find_glyph_format' in
+`kpathsea/tex-glyph.c'.
+* Menu:
+* Basic glyph lookup::          Features common to all glyph lookups.
+* Fontmap::                     Aliases for fonts.
+* Fallback font::               Resolutions and fonts of last resort.
+File: kpathsea.info,  Node: Basic glyph lookup,  Next: Fontmap,  Up: Glyph lookup
+Basic glyph lookup
+------------------
+When Kpathsea looks for a bitmap font NAME at resolution DPI in a
+format FORMAT, it first checks each directory in the search path for a
+file `NAME.DPIFORMAT'; for example, `cmr10.600pk'.  Kpathsea looks for
+a PK file first, then a GF file.
+If that fails, Kpathsea looks for `dpiDPI/NAME.FORMAT'; for example,
+`dpi600/cmr10.pk'. This is how fonts are typically stored on
+filesystems (such as DOS) that permit only three-character extensions.
+If that fails, Kpathsea looks for a font with a close-enough DPI.
+"Close enough" is defined by the macro `KPSE_BITMAP_TOLERANCE' in
+`kpathsea/tex-glyph.h' to be `DPI / 500 + 1'.  This is slightly more
+than the 0.2% minimum allowed by the DVI standard
+(`CTAN:/dviware/driv-standard/level-0').
+File: kpathsea.info,  Node: Fontmap,  Next: Fallback font,  Prev: Basic glyph lookup,  Up: Glyph lookup
+Fontmap
+-------
+If a bitmap font or metric file is not found with the original name
+(see the previous section), Kpathsea looks through any "fontmap" files
+for an "alias" for the original font name.  These files are named
+`texfonts.map' and searched for along the `TEXFONTMAPS'
+environment/config file variable.  All `texfonts.map' files that are
+found are read; earlier definitions override later ones.
+This feature is intended to help in two respects:
+1. An alias name is limited in length only by available memory, not
+by your filesystem.  Therefore, if you want to ask for
+`Times-Roman' instead of `ptmr', you can (you get `ptmr8r').
+2. A few fonts have historically had multiple names: specifically,
+LaTeX's "circle font" has variously been known as `circle10',
+`lcircle10', and `lcirc10'.  Aliases can make all the names
+equivalent, so that it no longer matters what the name of the
+installed file is; TeX documents will find their favorite name.
+The format of fontmap files is straightforward:
+* Comments start with `%' and continue to the end of the line.
+* Blank lines are ignored.
+* Each nonblank line is broken up into a series of "words":   a
+sequence of non-whitespace characters.
+* If the first word is `include', the second word is used as   a
+filename, and it is searched for and read.
+* Otherwise, the first word on each line is the true filename;
+* the second word is the alias;
+* subsequent words are ignored.
+If an alias has an extension, it matches only those files with that
+extension; otherwise, it matches anything with the same root, regardless
+of extension.  For example, an alias `foo.tfm' matches only when
+`foo.tfm' is being searched for; but an alias `foo' matches `foo.vf',
+`foo.600pk', etc.
+As an example, here is an excerpt from the `texfonts.map' in the
+Web2c distribution.  It makes the circle fonts equivalent and includes
+automatically generated maps for most PostScript fonts available from
+various font suppliers.
+circle10        lcircle10
+circle10        lcirc10
+lcircle10       circle10
+lcircle10       lcirc10
+lcirc10         circle10
+lcirc10         lcircle10
+...
+include adobe.map
+include apple.map
+include bitstrea.map
+...
+Fontmaps are implemented in the file `kpathsea/fontmap.c'.  The
+Fontname distribution has much more information on font naming (*note
+Introduction: (fontname)Introduction.).
+File: kpathsea.info,  Node: Fallback font,  Prev: Fontmap,  Up: Glyph lookup
+Fallback font
+-------------
+If a bitmap font cannot be found or created at the requested size,
+Kpathsea looks for the font at a set of "fallback resolutions".  You
+specify these resolutions as a colon-separated list (like search paths).
+Kpathsea looks first for a program-specific environment variable (e.g.,
+`DVIPSSIZES' for Dvipsk), then the environment variable `TEXSIZES',
+then a default specified at compilation time (the Make variable
+`default_texsizes').  You can set this list to be empty if you prefer
+to find fonts at their stated size or not at all.
+Finally, if the font cannot be found even at the fallback resolutions,
+Kpathsea looks for a fallback font, typically `cmr10'.  Programs must
+enable this feature by assigning to the global variable
+`kpse_fallback_font' or calling `kpse_init_prog' (*note Calling
+sequence::.); the default is no fallback font.
+File: kpathsea.info,  Node: Suppressing warnings,  Prev: Glyph lookup,  Up: TeX support
+Suppressing warnings
+====================
+Kpathsea provides a way to suppress selected usually-harmless
+warnings; this is useful at large sites where most users are not
+administrators, and thus the warnings are merely a source of confusion,
+not a help.  To do this, you set the environment variable or
+configuration file value `TEX_HUSH' to a colon-separated list of
+values.  Here are the possibilities:
+`all'
+Suppress everything possible.
+`checksum'
+Suppress mismatched font checksum warnings.
+`lostchar'
+Suppress warnings when a character is missing from a font that a
+DVI or VF file tries to typeset.
+`readable'
+Suppress warnings about attempts to access a file whose permissions
+render it unreadable.
+`special'
+Suppresses warnings about an unimplemented or unparsable
+`\special' command.
+`tex-hush.c' defines the function that checks the variable value.  Each
+driver implements its own checks where appropriate.
+File: kpathsea.info,  Node: Programming,  Next: Index,  Prev: TeX support,  Up: Top
+Programming
+***********
+This chapter is for programmers who wish to use Kpathsea.  *Note
+Introduction::, for the conditions under which you may do so.
+* Menu:
+* Overview: Programming overview.         Introduction.
+* Calling sequence::                      Specifics of what to call.
+* Config: Programming with config files.  Getting info from texmf.cnf.
+File: kpathsea.info,  Node: Programming overview,  Next: Calling sequence,  Up: Programming
+Programming overview
+====================
+Aside from this manual, your best source of information is the source
+to the programs I've modified to use Kpathsea (*note Introduction::.).
+Of those, Dviljk is probably the simplest, and hence a good place to
+start.  Xdvik adds VF support and the complication of X resources.
+Dvipsk adds the complication of its own config files.  Web2c is source
+code I also maintain, so it uses Kpathsea rather straightforwardly, but
+is of course complicated by the Web to C translation.  Finally,
+Kpsewhich is a small utility program whose sole purpose is to exercise
+the main path-searching functionality.
+Beyond these examples, the `.h' files in the Kpathsea source describe
+the interfaces and functionality (and of course the `.c' files define
+the actual routines, which are the ultimate documentation).
+`pathsearch.h' declares the basic searching routine.  `tex-file.h' and
+`tex-glyph.h' define the interfaces for looking up particular kinds of
+files.  You may wish to use `#include <kpathsea/kpathsea.h>', which
+includes every Kpathsea header.
+The library provides no way for an external program to register new
+file types: `tex-file.[ch]' must be modified to do this. For example,
+Kpathsea has support for looking up Dvips config files, even though no
+program other than Dvips will likely ever want to do so.  I felt this
+was acceptable, since along with new file types should also come new
+defaults in `texmf.cnf' (and its descendant `paths.h'), since it's
+simplest for users if they can modify one configuration file for all
+kinds of paths.
+Kpathsea does not parse any formats itself; it barely opens any files.
+Its primary purpose is to return filenames.  The GNU font utilities does
+contain libraries to read TFM, GF, and PK files, as do the programs
+above, of course.
+File: kpathsea.info,  Node: Calling sequence,  Next: Programming with config files,  Prev: Programming overview,  Up: Programming
+Calling sequence
+================
+The typical way to use Kpathsea in your program goes something like
+this:
+1. Call `kpse_set_progname' with `argv[0]'; This is the only
+initialization that is mandatory to take full advantage of
+Kpathsea--specifically, for the `.PROGRAM' feature of config files
+(*note Config files::.).
+If necessary, `kpse_set_progname' sets the global variables
+`program_invocation_name' and `program_invocation_short_name'.
+These variables are used in the error message macros defined in
+`kpathsea/lib.h'.  It also initializes debugging options based on
+the environment variable `KPATHSEA_DEBUG' (if that is set).
+Finally, it sets the variables `SELFAUTOLOC', `SELFAUTODIR' and
+`SELFAUTOPARENT' to the location, parent and grandparent directory
+of the executable, removing `.' and `..' path elements and
+resolving symbolic links.  These are used in the default
+configuration file to allow people to invoke TeX from anywhere,
+specifically from a mounted CD-ROM.  (You can use
+`--expand-var=\$SELFAUTOLOC', etc., to see the values finds.)
+2. Set debugging options. *Note Debugging::.  If your program doesn't
+have a debugging option already, you can define one and set
+`kpathsea_debug' to the number that the user supplies (as in Dviljk
+and Web2c), or you can just omit this altogether (people can
+always set `KPATHSEA_DEBUG').  If you do have runtime debugging
+already, you need to merge Kpathsea's options with yours (as in
+Dvipsk and Xdvik).
+3. If your program has its own configuration files that can define
+search paths, you should assign those paths to the `client_path'
+member in the appropriate element of the `kpse_format_info' array.
+(This array is indexed by file type; see `tex-file.h'.)  See
+`resident.c' in Dvipsk for an example.
+4. Call `kpse_init_prog' (see `proginit.c'). It's useful for the DVI
+drivers, at least, but for other programs it may be simpler to
+extract the parts of it that actually apply.  This does not
+initialize any paths, it just looks for (and sets) certain
+environment variables and other random information.  (A search
+path is always initialized at the first call to find a file of
+that type; this eliminates much useless work, e.g., initializing
+the BibTeX search paths in a DVI driver.)
+5. The routine to actually find a file of type FORMAT is
+`kpse_find_FORMAT', defined in `tex-file.h'. These are macros that
+expand to a call to `kpse_find_file'.  You can call, say,
+`kpse_find_tfm' after doing only the first of the initialization
+steps above--Kpathsea automatically reads the `texmf.cnf' generic
+config files, looks for environment variables, and does expansions
+at the first lookup.
+6. To find PK and/or GF bitmap fonts, the routines are `kpse_find_pk',
+`kpse_find_gf' and `kpse_find_glyph', defined in `tex-glyph.h'.
+These return a structure in addition to the resultant filename,
+because fonts can be found in so many ways. See the documentation
+in the source.
+7. To actually open a file, not just return a filename, call
+`kpse_open_file'.  This function takes the name to look up and a
+Kpathsea file format as arguments, and returns the usual `FILE *'.
+It always assumes the file must exist, and thus will search the
+disk if necessary (unless the search path specified `!!', etc.).
+In other words, if you are looking up a VF or some other file that
+need not exist, don't use this.
+Kpathsea also provides many utility routines. Some are generic: hash
+tables, memory allocation, string concatenation and copying, string
+lists, reading input lines of arbitrary length, etc. Others are
+filename-related: default path, tilde, and variable expansion, `stat'
+calls, etc. (Perhaps someday I'll move the former to a separate
+library.)
+The `c-*.h' header files can also help your program adapt to many
+different systems.  You will almost certainly want to use Autoconf for
+configuring your software if you use Kpathsea; I strongly recommend
+using Autoconf regardless.  It is available from
+`ftp://prep.ai.mit.edu/pub/gnu/'.
+File: kpathsea.info,  Node: Programming with config files,  Prev: Calling sequence,  Up: Programming
+Programming with config files
+=============================
+You can (and probably should) use the same `texmf.cnf' configuration
+file that Kpathsea uses for your program.  This helps installers by
+keeping all configuration in one place.
+To retrieve a value VAR from config files, the best way is to call
+`kpse_var_value' on the string `VAR'.  This will look first for an
+environment variable VAR, then a config file value.  The result will be
+the value found or `NULL'.  This function is declared in
+`kpathsea/variable.h'.  For an example, see the `shell_escape' code in
+`web2c/lib/texmfmp.c'.
+The routine to do variable expansion in the context of a search path
+(as opposed to simply retrieving a value) is `kpse_var_expand', also
+declared in `kpathsea/variable.h'.  It's generally only necessary to
+set the search path structure components as explained in the previous
+section, rather than using this yourself.
+If for some reason you want to retrieve a value *only* from a config
+file, not automatically looking for a corresponding environment
+variable, call `kpse_cnf_get' (declared in `kpathsea/cnf.h') with the
+string VAR.
+No initialization calls are needed.
+File: kpathsea.info,  Node: Index,  Prev: Programming,  Up: Top
+Index
+*****
+* Menu:
+* !! in path specifications:             ls-R.
+* $ expansion:                           Variable expansion.
+* -1 debugging value:                    Debugging.
+* -A option to ls:                       ls-R.
+* -Bdynamic:                             ShellWidgetClass.
+* -Bstatic:                              ShellWidgetClass.
+* -color=tty:                            ls-R.
+* -D NUM:                                Path searching options.
+* -debug=NUM:                            Auxiliary tasks.
+* -dpi=NUM:                              Path searching options.
+* -dynamic:                              ShellWidgetClass.
+* -enable options:                       configure options.
+* -enable-shared:                        Shared library.
+* -expand-path=STRING:                   Auxiliary tasks.
+* -expand-var=STRING:                    Auxiliary tasks.
+* -format=NAME:                          Path searching options.
+* -g, compiling without:                 configure scenarios.
+* -help:                                 Standard options.
+* -interactive:                          Path searching options.
+* -L option to ls:                       ls-R.
+* -maketex=FILETYPE:                     Path searching options.
+* -mode=STRING:                          Path searching options.
+* -must-exist:                           Path searching options.
+* -no-maketex=FILETYPE:                  Path searching options.
+* -O, compiling with:                    configure scenarios.
+* -path=STRING:                          Path searching options.
+* -progname=NAME:                        Path searching options.
+* -separator=STRING:                     Auxiliary tasks.
+* -show-path=NAME:                       Auxiliary tasks.
+* -srcdir, for building multiple architectures: configure scenarios.
+* -static:                               ShellWidgetClass.
+* -version:                              Standard options.
+* -with options:                         configure options.
+* -with-maketextex-default:              MakeTeX configuration.
+* -without-maketexmf-default:            MakeTeX configuration.
+* -without-maketexpk-default:            MakeTeX configuration.
+* -without-maketextfm-default:           MakeTeX configuration.
+* . directories, ignored:                ls-R.
+* . files:                               ls-R.
+* .2602gf:                               Unable to generate fonts.
+* .afm:                                  Supported file formats.
+* .base:                                 Supported file formats.
+* .bib:                                  Supported file formats.
+* .bst:                                  Supported file formats.
+* .cnf:                                  Supported file formats.
+* .dtx:                                  Supported file formats.
+* .eps:                                  Supported file formats.
+* .epsi:                                 Supported file formats.
+* .fmt:                                  Supported file formats.
+* .gf:                                   Supported file formats.
+* .ist:                                  Supported file formats.
+* .ltx:                                  Supported file formats.
+* .map:                                  Supported file formats.
+* .mem:                                  Supported file formats.
+* .mf:                                   Supported file formats.
+* .mft:                                  Supported file formats.
+* .mp:                                   Supported file formats.
+* .ocp:                                  Supported file formats.
+* .ofm:                                  Supported file formats.
+* .opl:                                  Supported file formats.
+* .otp:                                  Supported file formats.
+* .ovf:                                  Supported file formats.
+* .ovp:                                  Supported file formats.
+* .pfa:                                  Supported file formats.
+* .pfb:                                  Supported file formats.
+* .pk:                                   Supported file formats.
+* .pool:                                 Supported file formats.
+* .pro:                                  Supported file formats.
+* .rhosts, writable by TeX:              Security.
+* .tex:                                  Supported file formats.
+* .tex file, included in ls-R:           ls-R.
+* .texi:                                 Supported file formats.
+* .texinfo:                              Supported file formats.
+* .tfm:                                  Supported file formats.
+* .txi:                                  Supported file formats.
+* .vf:                                   Supported file formats.
+* / may not be /:                        Searching overview.
+* /, trailing in home directory:         Tilde expansion.
+* //:                                    Subdirectory expansion.
+* /afs/... , installing into:            Installing files.
+* /etc/profile:                          Unable to find files.
+* /etc/profile and aliases:              ls-R.
+* /var/tex/fonts:                        MakeTeX configuration.
+* 2602gf:                                Unable to generate fonts.
+* 4allTeX Live CD-ROM:                   CD-ROM distribution.
+* 8.3 filenames, using:                  MakeTeX configuration.
+* : may not be ::                        Searching overview.
+* :: expansion:                          Default expansion.
+* @VAR@ substitutions:                   Running configure.
+* \, line continuation in texmf.cnf:     Config files.
+* \openin:                               Searching overview.
+* \special, suppressing warnings about:  Suppressing warnings.
+* absolute filenames:                    Searching overview.
+* ac_include, Autoconf extension:        Running configure.
+* access warnings:                       Searching overview.
+* Acorn TeX implementations:             Other TeX packages.
+* AFMFONTS:                              Supported file formats.
+* AFS:                                   Installing files.
+* AIX shells and configure:              configure shells.
+* aliases for fonts:                     Fontmap.
+* aliases, for filenames:                Filename aliases.
+* all:                                   Suppressing warnings.
+* alphabetical order, not:               Subdirectory expansion.
+* Amiga support:                         Custom installation.
+* Amiga TeX implementations:             Other TeX packages.
+* Andrew File System, installing with:   Installing files.
+* announcement mailing list:             Mailing lists.
+* append-only directories and MakeTeXPK: Security.
+* appendonlydir:                         MakeTeX configuration.
+* architecture-(in)dependent files, installing only: Installing files.
+* architectures, compiling multiple:     configure scenarios.
+* arguments to MakeTeX:                  MakeTeX script arguments.
+* argv[0]:                               Calling sequence.
+* ash, losing with configure:            configure shells.
+* autoconf, recommended:                 Calling sequence.
+* automounter, and configuration:        configure scenarios.
+* automounter, and ls-R:                 ls-R.
+* auxiliary tasks:                       Auxiliary tasks.
+* Babel <1>:                             Running make.
+* Babel:                                 Kpathsea application distributions.
+* Bach, Johann Sebastian:                Default expansion.
+* backbone of CTAN:                      Electronic distribution.
+* backslash-newline:                     Config files.
+* base dpi:                              MakeTeX script arguments.
+* bash, recommended for running configure: configure shells.
+* basic glyph lookup:                    Basic glyph lookup.
+* BIBINPUTS:                             Supported file formats.
+* binary mode, for file transfers:       Electronic distribution.
+* blank lines, in texmf.cnf:             Config files.
+* brace expansion:                       Brace expansion.
+* BSD universe:                          Running make.
+* bsh, ok with configure:                configure shells.
+* BSTINPUTS:                             Supported file formats.
+* bug address:                           Reporting bugs.
+* bug checklist:                         Bug checklist.
+* bug mailing list:                      Mailing lists.
+* bugs, reporting:                       Reporting bugs.
+* c-*.h:                                 Calling sequence.
+* c-auto.h.in:                           Running configure.
+* cache of fonts, loca:                  Security.
+* calling sequence:                      Calling sequence.
+* CC:                                    configure environment.
+* cc warnings:                           Pointer combination warnings.
+* cc, compiling with:                    configure environment.
+* CD-ROM distributions:                  CD-ROM distribution.
+* CFLAGS:                                configure environment.
+* ChangeLog entry:                       Bug checklist.
+* checklist for bug reports:             Bug checklist.
+* checksum:                              Suppressing warnings.
+* circle fonts:                          Fontmap.
+* clean Make target:                     Cleaning up.
+* client_path in kpse_format_info:       Calling sequence.
+* cmr10, as fallback font:               Fallback font.
+* cmr10.vf:                              Searching overview.
+* cnf.c:                                 Config files.
+* cnf.h:                                 Programming with config files.
+* code sharing:                          Shared library.
+* color printers, configuring:           Simple installation.
+* comments, in fontmap files:            Fontmap.
+* comments, in texmf.cnf:                Config files.
+* comments, making:                      Introduction.
+* common features in glyph lookup:       Basic glyph lookup.
+* common problems:                       Common problems.
+* comp.sys.sun.admin FAQ:                ShellWidgetClass.
+* comp.text.tex:                         Mailing lists.
+* compilation:                           Installation.
+* compilation value, source for path:    Path sources.
+* compiler bugs:                         TeX or Metafont failing.
+* compiler bugs, finding:                TeX or Metafont failing.
+* compiler options, additional:          Running make.
+* compiler options, specifying:          configure environment.
+* compiler, changing:                    Running make.
+* conditions for use:                    Introduction.
+* config files:                          Config files.
+* config files, for Kpathsea-using programs: Calling sequence.
+* config files, programming with:        Programming with config files.
+* config.log:                            Bug checklist.
+* config.ps, search path for:            Supported file formats.
+* config.status:                         Bug checklist.
+* configuration:                         Installation.
+* configuration bugs:                    Bug checklist.
+* configuration compiler options:        configure environment.
+* configuration file, source for path:   Path sources.
+* configuration files as shell scripts.: Config files.
+* configuration of MakeTeX scripts:      MakeTeX configuration.
+* configuration of optional features:    configure options.
+* CONFIGURE:                             Running configure.
+* configure options:                     configure options.
+* configure options for MakeTeX scripts: MakeTeX configuration.
+* configure, running:                    Running configure.
+* context diff:                          Bug checklist.
+* continuation character:                Config files.
+* core dumps, reporting:                 Bug checklist.
+* CPPFLAGS:                              configure environment.
+* crashes, reporting:                    Bug checklist.
+* CTAN, defined:                         Electronic distribution.
+* CTAN.sites:                            Electronic distribution.
+* custom installation:                   Custom installation.
+* database search:                       Searching overview.
+* database, for filenames:               Filename database.
+* database, format of:                   Database format.
+* DC fonts, and dynamic source creation: MakeTeX scripts.
+* debug.h:                               Debugging.
+* debugger:                              Bug checklist.
+* debugging:                             Debugging.
+* debugging options, in Kpathsea-using program: Calling sequence.
+* debugging output:                      Debugging.
+* debugging with -g, disabling:          configure scenarios.
+* DEC shells and configure:              configure shells.
+* default expansion:                     Default expansion.
+* default path features:                 Default path features.
+* default paths, changing:               Default path generation.
+* default paths, how they're made:       Default path generation.
+* default_texsizes:                      Fallback font.
+* DEFS:                                  configure environment.
+* depot:                                 configure scenarios.
+* destination directory for MakeTeXPK:   MakeTeX script arguments.
+* directories, changing default installation: Default path generation.
+* directories, making append-only:       MakeTeX configuration.
+* directory structure, for TeX files:    TeX directory structure.
+* disabling MakeTeX scripts:             MakeTeX configuration.
+* disk search:                           Searching overview.
+* disk searching, avoiding:              ls-R.
+* disk space, needed:                    Disk space.
+* disk usage, reducing:                  Logging.
+* distclean Make target:                 Cleaning up.
+* distributions, compiling simultaneously: Kpathsea application distributions.
+* distributions, not compiling:          Kpathsea application distributions.
+* distributions, on CD-ROM:              CD-ROM distribution.
+* distributions, on tape:                Tape distribution.
+* distributions, via ftp:                Electronic distribution.
+* dlclose:                               dlopen.
+* dlopen:                                dlopen.
+* dlsym:                                 dlopen.
+* dlsym.c:                               dlopen.
+* doc files:                             Supported file formats.
+* DOS compatible names:                  MakeTeX configuration.
+* DOS support:                           Custom installation.
+* DOS TeX implementations:               Other TeX packages.
+* dosnames:                              MakeTeX configuration.
+* dot files:                             ls-R.
+* doubled colons:                        Default expansion.
+* dpiNNN directories:                    MakeTeX configuration.
+* DVI drivers:                           Kpathsea application distributions.
+* DVILJMAKEPK:                           MakeTeX script names.
+* DVILJSIZES:                            Fallback font.
+* DVIPSFONTS:                            Supported file formats.
+* DVIPSHEADERS:                          Supported file formats.
+* DVIPSMAKEPK:                           MakeTeX script names.
+* DVIPSSIZES:                            Fallback font.
+* dynamic creation of files:             MakeTeX scripts.
+* dynamic linking problems with OpenWin libraries: ShellWidgetClass.
+* elt-dirs.c:                            Subdirectory expansion.
+* email CTAN access:                     Electronic distribution.
+* enabling MakeTeX scripts:              MakeTeX configuration.
+* environment variable, source for path: Path sources.
+* environment variables for TeX:         Supported file formats.
+* environment variables in paths:        Variable expansion.
+* environment variables, old:            Unable to find files.
+* epoch, seconds since:                  Logging.
+* error message macros:                  Calling sequence.
+* excessive startup time:                Slow path searching.
+* expand.c:                              Brace expansion.
+* expanding symlinks:                    Calling sequence.
+* expansion, default:                    Default expansion.
+* expansion, path element:               Searching overview.
+* expansion, search path:                Path expansion.
+* expansion, subdirectory:               Subdirectory expansion.
+* expansion, tilde:                      Tilde expansion.
+* expansion, variable:                   Variable expansion.
+* explicitly relative filenames:         Searching overview.
+* externally-built filename database:    Filename database.
+* extra colons:                          Default expansion.
+* extraclean Make target:                Cleaning up.
+* failed MakeTeX... script invocation:   MakeTeX script names.
+* fallback font:                         Fallback font.
+* fallback resolutions:                  Fallback font.
+* fallback resolutions, overriding:      Running make.
+* FAQ, comp.sys.sun.admin:               ShellWidgetClass.
+* FAQ, Kpathsea:                         Common problems.
+* Farwell, Matthew:                      Subdirectory expansion.
+* features, of default paths:            Default path features.
+* file formats, supported:               Supported file formats.
+* file lookup:                           File lookup.
+* file types, registering new:           Programming overview.
+* filename aliases:                      Filename aliases.
+* filename database:                     Filename database.
+* filename database generation:          Filename database generation.
+* filenames, absolute or explicitly relative: Searching overview.
+* files, unable to find:                 Unable to find files.
+* filesystem search:                     Searching overview.
+* floating directories:                  Searching overview.
+* font alias files:                      Fontmap.
+* font generation failures:              Unable to generate fonts.
+* font of last resort:                   Fallback font.
+* font set, infinite:                    MakeTeX scripts.
+* fontmap files:                         Fontmap.
+* fontnames, arbitrary length:           Fontmap.
+* fonts, being created:                  Simple installation.
+* fopen, redefined:                      Debugging.
+* format of external database:           Database format.
+* Free Software Foundation:              CD-ROM distribution.
+* FreeBSD shells and configure:          configure shells.
+* FSF Source Code CD-ROM:                CD-ROM distribution.
+* ftp retrieval:                         Electronic distribution.
+* ftp.tug.org:                           unixtex.ftp.
+* fundamental purpose of Kpathsea:       Introduction.
+* gcc, compiling with:                   configure environment.
+* gdb, recommended:                      Bug checklist.
+* generation of filename database:       Filename database generation.
+* get_applicationShellWidgetClass:       ShellWidgetClass.
+* get_wmShellWidgetClass:                ShellWidgetClass.
+* GFFONTS:                               Supported file formats.
+* globally writable directories:         Security.
+* glyph lookup:                          Glyph lookup.
+* glyph lookup bitmap tolerance:         Basic glyph lookup.
+* GLYPHFONTS:                            Supported file formats.
+* GNU C compiler bugs:                   TeX or Metafont failing.
+* GNU General Public License:            Introduction.
+* Gopher CTAN access:                    Electronic distribution.
+* group-writable directories:            Security.
+* GUTenberg:                             CD-ROM distribution.
+* hash table buckets, printing:          Debugging.
+* hash table routines:                   Calling sequence.
+* hash_summary_only variable for debugging: Debugging.
+* help, mailing list for general TeX:    Mailing lists.
+* HIER:                                  Default path features.
+* history of Kpathsea:                   History.
+* home directories in paths:             Tilde expansion.
+* HOME, as ~ expansion:                  Tilde expansion.
+* identifiers, characters valid in:      Config files.
+* illegal pointer combination warnings:  Pointer combination warnings.
+* include fontmap directive:             Fontmap.
+* INDEXSTYLE:                            Supported file formats.
+* info-tex@shsu.edu:                     Mailing lists.
+* input lines, reading:                  Calling sequence.
+* install-data Make target:              Installing files.
+* install-exec Make target:              Installing files.
+* installation:                          Installation.
+* installation testing:                  Installation testing.
+* installation, architecture-(in)dependent files only: Installing files.
+* installation, changing default directories: Default path generation.
+* installation, customized:              Custom installation.
+* installation, getting executables instead of: Simple installation.
+* installation, simple:                  Simple installation.
+* installing files:                      Installing files.
+* interactive query:                     Path searching options.
+* interface, not frozen:                 Introduction.
+* introduction:                          Introduction.
+* kdebug::                               Debugging.
+* kdefault.c:                            Default expansion.
+* Knuth, Donald E.:                      History.
+* Knuth, Donald E., archive of programs by: Other TeX packages.
+* Knuth, Donald E., original author:     Electronic distribution.
+* Korn shell, losing with configure:     configure shells.
+* Kpathsea config file, source for path: Path sources.
+* Kpathsea version number:               Kpathsea application distributions.
+* kpathsea.h:                            Programming overview.
+* kpathsea/CONFIGURE:                    Running configure.
+* kpathsea/HIER:                         Default path features.
+* KPATHSEA_DEBUG:                        Debugging.
+* kpathsea_debug:                        Debugging.
+* KPATHSEA_DEBUG:                        Calling sequence.
+* kpathsea_debug variable:               Calling sequence.
+* KPATHSEA_DPI:                          MakeTeX script arguments.
+* KPSE_BITMAP_TOLERANCE:                 Basic glyph lookup.
+* kpse_cnf_get:                          Programming with config files.
+* KPSE_DEBUG_EXPAND (16):                Debugging.
+* KPSE_DEBUG_FOPEN (4):                  Debugging.
+* KPSE_DEBUG_HASH (2):                   Debugging.
+* KPSE_DEBUG_PATHS (8):                  Debugging.
+* KPSE_DEBUG_SEARCH (32):                Debugging.
+* KPSE_DEBUG_STAT (1):                   Debugging.
+* kpse_fallback_font:                    Fallback font.
+* kpse_find_*:                           Calling sequence.
+* kpse_find_file:                        File lookup.
+* kpse_find_glyph_format:                Glyph lookup.
+* kpse_format_info:                      Calling sequence.
+* kpse_format_info_type:                 Debugging.
+* kpse_init_prog:                        Calling sequence.
+* kpse_init_prog, and MAKETEX_MODE:      Default path features.
+* kpse_make_specs:                       MakeTeX script names.
+* kpse_open_file:                        Calling sequence.
+* kpse_set_progname:                     Calling sequence.
+* kpse_var_expand:                       Programming with config files.
+* kpsewhich:                             Invoking kpsewhich.
+* Kpsewhich, and debugging:              Debugging.
+* ksh, losing with configure:            configure shells.
+* labrea.stanford.edu:                   Other TeX packages.
+* LaserJet drive:                        Kpathsea application distributions.
+* last-resort font:                      Fallback font.
+* LaTeX help mailing list:               Mailing lists.
+* lcircle10:                             Fontmap.
+* LDFLAGS:                               configure environment.
+* leading colons:                        Default expansion.
+* leaf directories wrongly guessed:      Unable to find files.
+* leaf directory trick:                  Subdirectory expansion.
+* libdl.a:                               dlopen.
+* libraries, changing:                   Running make.
+* libraries, specifying additional:      configure environment.
+* LIBS:                                  configure environment.
+* libucb, avoiding:                      Running make.
+* license for using the library:         Introduction.
+* lines, reading arbitrary-length:       Calling sequence.
+* Linux File System Standard:            MakeTeX configuration.
+* Linux shells and configure:            configure shells.
+* Linux, using Web2c:                    CD-ROM distribution.
+* lndir for building symlink trees:      configure scenarios.
+* loader options:                        configure environment.
+* loader options, final:                 Running make.
+* loader options, initial:               Running make.
+* local cache of fonts:                  Security.
+* log file:                              Logging.
+* logging successful searches:           Logging.
+* lost+found directory:                  Searching overview.
+* lostchar:                              Suppressing warnings.
+* ls-R:                                  Supported file formats.
+* ls-R and AFS:                          Installing files.
+* ls-R database file:                    ls-R.
+* ls-R, simplest build:                  ls-R.
+* Macintosh TeX implementations:         Other TeX packages.
+* MacKenzie, David <1>:                  Subdirectory expansion.
+* MacKenzie, David:                      History.
+* mag Metafont variable:                 MakeTeX script arguments.
+* magic characters:                      Searching overview.
+* magstep for MakeTeXPK:                 MakeTeX script arguments.
+* mailing lists:                         Mailing lists.
+* maintainer-clean Make target:          Cleaning up.
+* Make arguments, additional:            Running make.
+* make, running:                         Running make.
+* Makefile.in:                           Running configure.
+* MakeTeX script configuration:          MakeTeX configuration.
+* MakeTeX script names:                  MakeTeX script names.
+* MakeTeX scripts:                       MakeTeX scripts.
+* MakeTeX.site:                          MakeTeX configuration.
+* MAKETEX_BASE_DPI:                      MakeTeX script arguments.
+* MAKETEX_MAG:                           MakeTeX script arguments.
+* MAKETEX_MODE <1>:                      Default path features.
+* MAKETEX_MODE:                          MakeTeX script arguments.
+* MakeTeXMF:                             MakeTeX script names.
+* MakeTeXmkdir:                          MakeTeX configuration.
+* MakeTeXnames.cnf:                      MakeTeX configuration.
+* MakeTeXPK:                             MakeTeX script names.
+* MakeTeXPK , initial runs:              Simple installation.
+* MAKETEXPK environment variable:        MakeTeX script arguments.
+* MakeTeXTeX:                            MakeTeX script names.
+* MakeTeXTFM:                            MakeTeX script names.
+* memory allocation routines:            Calling sequence.
+* Metafont failures:                     TeX or Metafont failing.
+* Metafont installation:                 Unable to generate fonts.
+* Metafont making too-large fonts:       Unable to generate fonts.
+* Metafont mode name for MakeTeXPK:      MakeTeX script arguments.
+* Metafont using the wrong resolution:   Unable to generate fonts.
+* MFBASES:                               Supported file formats.
+* MFINPUTS:                              Supported file formats.
+* MFPOOL:                                Supported file formats.
+* MFTINPUTS:                             Supported file formats.
+* mirrors, FTP:                          Electronic distribution.
+* mismatched checksum warnings:          Suppressing warnings.
+* missfont.log:                          MakeTeX script names.
+* MISSFONT_LOG:                          MakeTeX script names.
+* missing character warnings:            Suppressing warnings.
+* mode directory, omitting:              MakeTeX configuration.
+* mode Metafont variable:                MakeTeX script arguments.
+* Morgan, Tim:                           History.
+* mostlyclean Make target:               Cleaning up.
+* MPINPUTS:                              Supported file formats.
+* MPMEMS:                                Supported file formats.
+* MPPOOL:                                Supported file formats.
+* MPSUPPORT:                             Supported file formats.
+* MT_FEATURES:                           MakeTeX configuration.
+* mtp_destdir:                           MakeTeX script arguments.
+* multiple architectures, compiling on:  configure scenarios.
+* multiple architectures, directories for: configure scenarios.
+* multiple architectures, installing on: Installing files.
+* multiple TeX hierarchies:              Brace expansion.
+* must exist:                            Searching overview.
+* names for MakeTeX scripts:             MakeTeX script names.
+* NetBSD shells and configure:           configure shells.
+* Neumann, Gustaf:                       History.
+* newsgroup for TeX:                     Mailing lists.
+* NeXT, lacking X11:                     Kpathsea application distributions.
+* NFS and ls-R:                          ls-R.
+* NFS CTAN access:                       Electronic distribution.
+* nomode:                                MakeTeX configuration.
+* non-English typesetting:               Kpathsea application distributions.
+* non-Unix operating systems:            Custom installation.
+* Northwest Computing Support Center:    Tape distribution.
+* NTG:                                   CD-ROM distribution.
+* null pointers, dereferencing:          Bug checklist.
+* numeric debugging values:              Debugging.
+* obtaining TeX:                         unixtex.ftp.
+* obtaining TeX on tape:                 Tape distribution.
+* obtaining Web2c by ftp:                Electronic distribution.
+* obtaining Web2c on CD-ROM:             CD-ROM distribution.
+* OCPINPUTS:                             Supported file formats.
+* OFMFONTS:                              Supported file formats.
+* online Metafont display, spurious:     Unable to generate fonts.
+* OpenWin libraries, dynamic linking problems: ShellWidgetClass.
+* optimization caveat:                   TeX or Metafont failing.
+* optimization, enabling:                configure scenarios.
+* options for debugging:                 Debugging.
+* options to configure:                  configure options.
+* OS/2 support:                          Custom installation.
+* other TeX distributions:               Other TeX packages.
+* OTPINPUTS:                             Supported file formats.
+* overview of path searching:            Searching overview.
+* overview of programming with Kpathsea: Programming overview.
+* OVFFONTS:                              Supported file formats.
+* OVPFONTS:                              Supported file formats.
+* patches, Sun OpenWin:                  ShellWidgetClass.
+* path expansion:                        Path expansion.
+* path searching:                        Path searching.
+* path searching options:                Path searching options.
+* path searching, overview:              Searching overview.
+* path searching, standalone:            Invoking kpsewhich.
+* path sources:                          Path sources.
+* paths, changing default <1>:           Default path generation.
+* paths, changing default:               Changing search paths.
+* paths, device name included in:        Default path features.
+* paths.h:                               Default path generation.
+* paths.h, creating:                     Running make.
+* pathsearch.h:                          Programming overview.
+* pc Pascal compiler:                    History.
+* PCL driver:                            Kpathsea application distributions.
+* PDF generation:                        Kpathsea application distributions.
+* permission denied:                     Searching overview.
+* PKFONTS:                               Supported file formats.
+* plain.base:                            Unable to generate fonts.
+* pointer combination warnings:          Pointer combination warnings.
+* PostScript driver:                     Kpathsea application distributions.
+* PostScript fonts, additional:          Simple installation.
+* precompiled executables, instead of installation: Simple installation.
+* precompiled Unix binaries:             Other TeX packages.
+* preprocessor options:                  configure environment.
+* preprocessor options, additional:      Running make.
+* Prime Time TeXcetera CD-ROM:           CD-ROM distribution.
+* printer configuration files:           Simple installation.
+* privacy, semblance of:                 Logging.
+* problems, common:                      Common problems.
+* proginit.c:                            Default path features.
+* proginit.h:                            Calling sequence.
+* program-varying paths:                 Supported file formats.
+* program_invocation_name:               Calling sequence.
+* program_invocation_short_name:         Calling sequence.
+* programming overview:                  Programming overview.
+* programming with config files:         Programming with config files.
+* programming with Kpathsea:             Calling sequence.
+* programs using the library:            Introduction.
+* proof mode:                            Unable to generate fonts.
+* PSHEADERS:                             Supported file formats.
+* pxp Pascal preprocessor:               History.
+* quoting variable values:               Variable expansion.
+* readable:                              Suppressing warnings.
+* reading arbitrary-length lines:        Calling sequence.
+* README.mirrors:                        Electronic distribution.
+* recording successful searches:         Logging.
+* relative filenames:                    Searching overview.
+* relative filenames in ls-R:            Installing files.
+* reporting bugs:                        Reporting bugs.
+* resident.c:                            Calling sequence.
+* resolution, setting:                   Path searching options.
+* resolution, wrong:                     Unable to generate fonts.
+* resolutions, last-resort:              Fallback font.
+* retrieving TeX:                        unixtex.ftp.
+* right-hand side of variable assignments: Config files.
+* Rokicki, Tom:                          History.
+* root user:                             Tilde expansion.
+* runtime configuration files:           Config files.
+* runtime debugging:                     Debugging.
+* Sauter fonts, and dynamic source creation: MakeTeX scripts.
+* scripts for file creation:             MakeTeX scripts.
+* search path, defined:                  Searching overview.
+* search paths, changing default:        Changing search paths.
+* searching for files:                   File lookup.
+* searching for glyphs:                  Glyph lookup.
+* searching overview:                    Searching overview.
+* searching the database:                Searching overview.
+* searching the disk:                    Searching overview.
+* security considerations:               Security.
+* SELFAUTODIR:                           Calling sequence.
+* SELFAUTOLOC:                           Calling sequence.
+* SELFAUTOPARENT:                        Calling sequence.
+* sending patches:                       Bug checklist.
+* setgid scripts:                        Security.
+* sh5, ok with configure:                configure shells.
+* shar, recommended:                     Bug checklist.
+* shared library, making:                Shared library.
+* shell scripts as configuration files:  Config files.
+* shell variables:                       Variable expansion.
+* shell_escape, example for code:        Programming with config files.
+* shells and configure:                  configure shells.
+* simple installation:                   Simple installation.
+* site overrides for MakeTeX...:         MakeTeX configuration.
+* size of distribution archives:         Disk space.
+* skeleton TeX directory:                TeX directory structure.
+* slow startup time:                     Slow path searching.
+* Solaris BSD compatibility, not:        Running make.
+* source files:                          Supported file formats.
+* sources for search paths:              Path sources.
+* special:                               Suppressing warnings.
+* specification for MakeTeXPK:           MakeTeX script arguments.
+* st_nlink:                              Subdirectory expansion.
+* stack trace:                           Bug checklist.
+* standalone path searching:             Invoking kpsewhich.
+* standard error and debugging output:   Debugging.
+* standard options:                      Standard options.
+* startup time, excessive:               Slow path searching.
+* static linking:                        ShellWidgetClass.
+* static linking and dlsym:              dlopen.
+* string routines:                       Calling sequence.
+* strip:                                 MakeTeX configuration.
+* subdirectory searching:                Subdirectory expansion.
+* suggestions, making:                   Introduction.
+* Sun 2:                                 History.
+* Sun OpenWin patches:                   ShellWidgetClass.
+* supplier directory, omitting:          MakeTeX configuration.
+* support organization:                  Tape distribution.
+* supported file formats:                Supported file formats.
+* suppressing warnings:                  Suppressing warnings.
+* symbolic link trees, for multiple architectures: configure scenarios.
+* symbolic links not found:              Unable to find files.
+* symbolic links, and ls-R:              ls-R.
+* symlinks, resolving:                   Calling sequence.
+* system C compiler bugs:                TeX or Metafont failing.
+* system dependencies:                   Running configure.
+* system V universe:                     Running make.
+* T1FONTS:                               Supported file formats.
+* T1INPUTS:                              Supported file formats.
+* tape distribution:                     Tape distribution.
+* TDS:                                   TeX directory structure.
+* testing, post-installation:            Installation testing.
+* tests, simple:                         Simple installation.
+* teTeX:                                 Other TeX packages.
+* TeX directory structure:               TeX directory structure.
+* TeX distributions besides Web2c:       Other TeX packages.
+* TeX environment variables:             Supported file formats.
+* TeX failures:                          TeX or Metafont failing.
+* TeX file lookup:                       File lookup.
+* TeX glyph lookup:                      Glyph lookup.
+* TeX help mailing list:                 Mailing lists.
+* TeX hierarchy, one:                    configure scenarios.
+* TeX Live CD-ROM:                       CD-ROM distribution.
+* TeX support:                           TeX support.
+* TeX Users Group:                       Introduction.
+* tex-archive@math.utah.edu:             Mailing lists.
+* tex-file.c:                            File lookup.
+* tex-file.h:                            Programming overview.
+* tex-glyph.c:                           Glyph lookup.
+* tex-glyph.h:                           Programming overview.
+* tex-k-request@mail.tug.org:            Mailing lists.
+* tex-k@mail.tug.org (bug address):      Reporting bugs.
+* tex-make.c:                            MakeTeX script names.
+* TEX_HUSH <1>:                          Suppressing warnings.
+* TEX_HUSH:                              Searching overview.
+* TEXBIB:                                Supported file formats.
+* TEXCONFIG:                             Supported file formats.
+* TEXDOCS:                               Supported file formats.
+* TEXFONTMAPS:                           Supported file formats.
+* TEXFONTS:                              Supported file formats.
+* texfonts.map:                          Fontmap.
+* TEXFORMATS:                            Supported file formats.
+* TEXINDEXSTYLE:                         Supported file formats.
+* TEXINPUTS:                             Supported file formats.
+* TEXMF:                                 TeX directory structure.
+* texmf.cnf, and variable expansion:     Variable expansion.
+* texmf.cnf, creating:                   Running make.
+* texmf.cnf, definition for:             Config files.
+* texmf.cnf, generated:                  Default path generation.
+* texmf.cnf, source for path:            Path sources.
+* texmf.cnf.in:                          Default path generation.
+* texmf.cnf.in, editing:                 Changing search paths.
+* texmf.sed:                             Default path generation.
+* TEXMFCNF <1>:                          Supported file formats.
+* TEXMFCNF:                              Config files.
+* TEXMFDBS <1>:                          ls-R.
+* TEXMFDBS:                              Supported file formats.
+* TEXMFINI:                              Supported file formats.
+* TEXMFLOG:                              Logging.
+* TEXMFOUTPUT:                           MakeTeX script names.
+* TEXPICTS:                              Supported file formats.
+* TEXPKS:                                Supported file formats.
+* TEXPOOL:                               Supported file formats.
+* TEXPSHEADERS:                          Supported file formats.
+* TEXSIZES:                              Fallback font.
+* TEXSOURCES:                            Supported file formats.
+* TFMFONTS:                              Supported file formats.
+* tilde expansion:                       Tilde expansion.
+* tilde.c:                               Tilde expansion.
+* time system call:                      Logging.
+* tolerance for glyph lookup:            Basic glyph lookup.
+* total disk space:                      Disk space.
+* trailing / in home directory:          Tilde expansion.
+* trailing colons:                       Default expansion.
+* TRFONTS:                               Supported file formats.
+* trick for detecting leaf directories:  Subdirectory expansion.
+* trojan horse attack:                   Security.
+* TUG:                                   CD-ROM distribution.
+* tug.cs.umb.edu:                        unixtex.ftp.
+* tug@tug.org:                           Introduction.
+* typeface directory, omitting:          MakeTeX configuration.
+* ucbinclude, avoiding:                  Running make.
+* UKTUG:                                 CD-ROM distribution.
+* Ultrix shells and configure:           configure shells.
+* unable to find files:                  Unable to find files.
+* unable to generate fonts:              Unable to generate fonts.
+* uname:                                 Bug checklist.
+* universe, BSD vs. system V:            Running make.
+* UNIX_ST_LINK:                          Subdirectory expansion.
+* unixtex.ftp:                           unixtex.ftp.
+* unixtex@u.washington.edu:              Tape distribution.
+* unknown special warnings:              Suppressing warnings.
+* unreadable file warnings:              Suppressing warnings.
+* unreadable files:                      Searching overview.
+* unusable ls-R warning:                 ls-R.
+* usage patterns, finding:               Logging.
+* USE_VARTEXFONTS:                       MakeTeX configuration.
+* Usenet TeX newsgroup:                  Mailing lists.
+* varfonts:                              MakeTeX configuration.
+* variable expansion:                    Variable expansion.
+* variable.c:                            Variable expansion.
+* variable.h:                            Programming with config files.
+* VARTEXFONTS:                           MakeTeX configuration.
+* VAX 11/750:                            History.
+* version number, of Kpathsea:           Kpathsea application distributions.
+* version numbers, determining:          Bug checklist.
+* VF files, not found:                   Searching overview.
+* VFFONTS:                               Supported file formats.
+* VMS support:                           Custom installation.
+* VMS TeX implementations:               Other TeX packages.
+* Vojta, Paul:                           History.
+* Walnut Creek TeX CD-ROM:               CD-ROM distribution.
+* Walsh, Norman:                         History.
+* warning about unusable ls-R:           ls-R.
+* warnings, file access:                 Searching overview.
+* warnings, pointer combinations:        Pointer combination warnings.
+* warnings, suppressing:                 Suppressing warnings.
+* wcstombs:                              dlopen.
+* whitespace, in fontmap files:          Fontmap.
+* whitespace, not ignored on continuation lines: Config files.
+* Windows TeX implementations:           Other TeX packages.
+* World Wide Web CTAN access:            Electronic distribution.
+* www.tug.org:                           unixtex.ftp.
+* X11 previewer:                         Kpathsea application distributions.
+* X11, lacking on NeXT:                  Kpathsea application distributions.
+* XCFLAGS:                               Running make.
+* XCPPFLAGS:                             Running make.
+* XDEFS:                                 Running make.
+* XDVIFONTS:                             Supported file formats.
+* XDVIMAKEPK:                            MakeTeX script names.
+* XDVISIZES:                             Fallback font.
+* XLDFLAGS:                              Running make.
+* XLOADLIBES:                            Running make.
+* XMAKEARGS:                             Running make.
+* Xmu library problems:                  ShellWidgetClass.
+* XtStrings:                             XtStrings.
+* zuhn, david:                           History.
+* { expansion:                           Brace expansion.
+* ~ expansion:                           Tilde expansion.
+Tag Table:
+Node: Top1433
+Node: Introduction2080
+Node: History4437
+Node: Installation8250
+Node: Simple installation9023
+Node: Custom installation12062
+Node: Disk space13230
+Node: Kpathsea application distributions14090
+Node: Changing search paths15194
+Node: Default path features16385
+Node: Default path generation18513
+Node: Running configure19944
+Node: configure shells20990
+Node: configure options21759
+Node: configure environment22970
+Node: configure scenarios24758
+Node: Shared library26369
+Node: Running make27616
+Node: Installing files29648
+Node: Cleaning up31583
+Node: Filename database generation32618
+Node: MakeTeX scripts33179
+Node: MakeTeX configuration34140
+Node: MakeTeX script names37184
+Node: MakeTeX script arguments38287
+Node: Installation testing40355
+Node: Security40719
+Node: TeX directory structure42950
+Node: unixtex.ftp47362
+Node: Electronic distribution48931
+Node: CD-ROM distribution51252
+Node: Tape distribution52926
+Node: Other TeX packages53786
+Node: Reporting bugs55075
+Node: Bug checklist55810
+Node: Mailing lists59900
+Node: Debugging61245
+Node: Logging65404
+Node: Common problems66902
+Node: Unable to find files67652
+Node: Slow path searching70064
+Node: Unable to generate fonts71427
+Node: TeX or Metafont failing72978
+Node: XtStrings74335
+Node: dlopen75163
+Node: ShellWidgetClass75965
+Node: Pointer combination warnings77579
+Node: Path searching77954
+Node: Searching overview78599
+Node: Path sources81959
+Node: Config files83024
+Node: Path expansion86519
+Node: Default expansion87383
+Node: Variable expansion89106
+Node: Tilde expansion90474
+Node: Brace expansion91358
+Node: Subdirectory expansion92150
+Node: Filename database94478
+Node: ls-R95784
+Node: Filename aliases98662
+Node: Database format99827
+Node: Invoking kpsewhich100839
+Node: Path searching options101708
+Node: Auxiliary tasks105363
+Node: Standard options106604
+Node: TeX support106914
+Node: Supported file formats108201
+Node: File lookup113362
+Node: Glyph lookup114701
+Node: Basic glyph lookup115825
+Node: Fontmap116692
+Node: Fallback font119290
+Node: Suppressing warnings120246
+Node: Programming121303
+Node: Programming overview121751
+Node: Calling sequence123667
+Node: Programming with config files128053
+Node: Index129337
+End Tag Table

Mercurial > octave-nkf

comparison kpathsea/kpathsea.info @ 2999:faa5d0421460