Go to the first, previous, next, last section, table of contents.
The directories under the `texmf' root identify the major components of
a TeX system (see Section section Summary for a summary). A site
may omit any unneeded directories.
Although the TDS by its nature can specify precise locations only
for implementation-independent files, we recognize that installers may
well wish to place other files under `texmf' to simplify administration
of the TeX tree, especially if it is maintained by someone other than
the system administrator. Therefore, additional top-level directories
may be present.
The top-level directories specified by the TDS are:
- `tex'
for TeX files (Section section Macros).
- `fonts'
for font-related files (Section section Fonts).
- `metafont'
for METAFONT files which are not fonts (Section section Non-font METAFONT files).
- `metapost'
for MetaPost files (Section section MetaPost).
- `bibtex'
for BibTeX files (Section section BibTeX).
- `doc'
for user documentation (Section section Documentation).
- `source'
for sources. This includes both traditional
program sources (for example, Web2c sources go in
`texmf/source/web2c') and, e.g., LaTeX `dtx' sources (which
go in `texmf/source/latex'). The TDS leaves unspecified any
structure under `source'.
`source' is intended for files which are not needed at runtime by
any TeX program; it should not be included in any search path. For
example, `plain.tex' does not belong under `texmf/source',
even though it is a "source file" in the sense of not being derived
from another file. (It goes in `texmf/tex/plain/base', as explained
in Section section Macros).
- `implementation'
for implementations (examples:
`emtex', `web2c'), to be used for whatever purpose deemed
suitable by the implementor or TeX administrator. Files that cannot
be shared between implementations, such as pool files (`tex.pool')
and memory dump files (`plain.fmt') go here, in addition to
implementation-wide configuration files. See Section section Example implementation-specific trees for examples of real
`implementation' trees.
- `extension'
for program-specific input files for new
programs (examples: `etex', `pdftex', `omega') that are
extensions of TeX, METAFONT, or any standard program. See
Section section Extensions.
- `program'
for program-specific input and
configuration files for any TeX-related programs (examples:
`mft', `dvips'). In fact, the `tex', `metafont',
`metapost', `bibtex', and `extension' items above
may all be seen as instances of this case.
Go to the first, previous, next, last section, table of contents.