diff options
author | Karl Berry <karl@freefriends.org> | 2007-12-28 19:57:02 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2007-12-28 19:57:02 +0000 |
commit | c7cfef6687f65c2538898ddd7c6bc9c9ba50e58d (patch) | |
tree | 8f4de70d1a11463779871162ba84c1dbc874155b /Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html | |
parent | 8948a31a6e2ac27883f7adac1b339003961ba43f (diff) |
uk-tex-faq 3.17 (7nov07)
git-svn-id: svn://tug.org/texlive/trunk@5977 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html')
-rw-r--r-- | Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html | 67 |
1 files changed, 67 insertions, 0 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html new file mode 100644 index 00000000000..0764f0a5450 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html @@ -0,0 +1,67 @@ +<head> +<title>UK TeX FAQ -- question label install-where</title> +</head><body> +<h3>Where to install packages</h3> +<p/>Where precisely you put files that you have downloaded depends on +what TeX distribution you have. We will assume that you have one +of the modern TDS-compliant distributions, and discuss the +general rules that you should follow. +<p/>First, you must decide which tree to put your files into; this isn’t +entirely trivial, and is discussed in +“<a href="FAQ-what-TDS.html">choosing a TDS tree</a>”. +<p/>We’ll assume from here on, that you’ve decided on a directory tree, +and we will write <code>$TEXMF</code> for it, whatever it is for your +system. +<p/>The basic idea is to imitate the directory structure in your +existing tree(s). Here are some examples of where various sorts of +files should go: +<blockquote> +<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>/ +.otf: $TEXMF/fonts/opentype/<supplier>/<font>/ +.pool, .fmt, .base or .mem: $TEXMF/web2c +</pre> +</blockquote><p> +and for modern systems (those distributed in 2005 or later, using TDS +v1.1 layouts): +<blockquote> +<pre> +.map: $TEXMF/fonts/map/<syntax>/<bundle>/ +.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ +</pre> +</blockquote><p> +(Map and encoding files went to directories under +<i>$TEXMF/dvips/</i>, in earlier distributions.) +<p/>In the lists above, <<i>package</i>>, <<i>font</i>> and <<i>supplier</i>> depend +upon what’s appropriate for the individual file — the supplier +“public” is commonly used for free fonts. 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. An exception is the <code>.drv</code> file, used by some +packages as part of the documentation building process; this is +usually part of the package documentation process, and should not be +installed. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-where">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-where</a> +</body> |