1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
<head>
<title>UK TeX FAQ -- question label wherefiles</title>
</head><body>
<h3>Where to put new files</h3>
<p>Where precisely you put files that you have downloaded does
depend on what TeX distribution you have. However,
assuming that you have one of the modern TDS-compliant
distributions (such as teTeX, fpTeX or mikTeX) there are
some general rules that you can follow:
<p>
(1) Always install new files in a local <i>texmf</i>
tree. The root directory will be named something like:
<pre>
teTeX: /usr/share/texmf-local/ or
/usr/local/share/texmf/
fpTeX: c:\Programs\TeXLive\texmf-local\
mikTeX: c:\localtexmf\
</pre>
(In fact, a teTeX system can be asked to tell you what its local
root is; on a Unix system, the command to use is:
<blockquote>
<pre>
kpsewhich -expand-var "\$TEXMFLOCAL"
</pre>
</blockquote>
the output being the actual path.)
<p>Let's write <code>$TEXMF</code> for this root, whatever it is for your system.
<p>
(2) In your local texmf tree, imitate the directory structure in your
main tree. Here are some examples of where files of given extensions
should go:
<pre>
.sty, .cls or .fd: $TEXMF/tex/latex/<package>/
.dvi, .ps or .pdf: $TEXMF/doc/latex/<package>/
.mf: $TEXMF/fonts/source/<supplier>/<font>/
.tfm: $TEXMF/fonts/tfm/<supplier>/<font>/
.vf: $TEXMF/fonts/vf/<supplier>/<font>/
.afm: $TEXMF/fonts/afm/<supplier>/<font>/
.pfb: $TEXMF/fonts/type1/<supplier>/<font>/
.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/
</pre>
and for modern systems (teTeX 3.0, and the like, using TDS
v1.1 format):
<pre>
.map: $TEXMF/fonts/map/<syntax>/<bundle>/
.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/
</pre>
Where of course <<i>package</i>>, <<i>font</i>> and <<i>supplier</i>> depend
upon what's appropriate for the individual file. The <<i>syntax</i>>
(for <code>.map</code> and <code>.enc</code> files) is a categorisation based
on the way the files are written; typically, it's the name of a
program such as <i>dvips</i> or <i>pdftex</i>.
<p>"Straight" (La)TeX input can take other forms than the <code>.sty</code>,
<code>.cls</code> or <code>.fd</code> listed above, too. Examples are
<code>.sto</code> and <code>.clo</code> for package and class options,
<code>.cfg</code> for configuration information, and so on.
<p>Note that <<i>font</i>> may stand for a single font or an entire family:
for example, files for all of Knuth's Computer Modern fonts are to be
found in <code>.../public/cm</code>, with various prefixes as appropriate.
<p>The font "supplier" <em>public</em> is a sort of hold-all for
"free fonts produced for use with (La)TeX": as well as Knuth's
fonts, <em>public</em>'s directory holds fonts designed by others
(originally, but no longer exclusively, in Metafont).
<p>Some packages have configuration files (commonly with file suffix
<code>.cfg</code>), and occasionally other run-time files. The package
documentation <em>should</em> mention these things, but sometimes
doesn't. A common exception is the <code>.drv</code> file, used by some
packages as part of the documentation building process; this is a
hang-over from the pre-LaTeX2e predecessor of the package
documentation process.
<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wherefiles">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wherefiles</a>
</body>
|
