diff options
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 | 62 |
1 files changed, 33 insertions, 29 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 index 0764f0a5450..42ec4dd1199 100644 --- 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 @@ -2,23 +2,17 @@ <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/>We assume here that you have decided what tree to put your files in, +after reading +“<a href="FAQ-what-TDS.html">choosing a TDS tree</a>”. We will therefore +write <code>$TEXMF</code> for it, and you need to substitute the tree +you decided on. <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>/ +.sty, .cls or .fd: $TEXMF/tex/<format>/<package>/ .mf: $TEXMF/fonts/source/<supplier>/<font>/ .tfm: $TEXMF/fonts/tfm/<supplier>/<font>/ .vf: $TEXMF/fonts/vf/<supplier>/<font>/ @@ -39,16 +33,28 @@ v1.1 layouts): </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/>In the lists above <<i>format</i>> identifies the format the macros +are designed for — it can be things such as <code>plain</code>, +<code>generic</code> (i.e., any format), <code>latex</code> or +<code>context</code> (or several less common formats). +<p/>For fonts, <<i>font</i>> refers to the font family (such as <code>cm</code> +for Knuth’s Computer Modern, <code>times</code> for Adobe’s Times Roman). +The supplier is usually obvious — the supplier +“public” is commonly used for free fonts. +<p/>The <<i>syntax</i>> (for <code>.map</code> and <code>.enc</code> files) is a +categorisation based on the way the files are written; candidates are +names of programs 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 +(apart from the ‘obvious’ <code>.tex</code>). Examples are (the +obvious) <code>.tex</code>, <code>.lfd</code> for <i>babel</i> language +definitions, <code>.sto</code> and <code>.clo</code> for package and class +options, <code>.cfg</code> for configuration information, +<code>.def</code> for variants (such as the types of devices +<i>graphics</i> drives). The <i>README</i> of the package should +tell you of any others, though sometimes that information is printed +when the package’s <a href="FAQ-install-unpack.html">comments are stripped</a>. +All of these files should live together with the main package files. <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. @@ -56,12 +62,10 @@ found in <code>.../public/cm</code>, with various prefixes as appropriate. “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/>Documentation for each package should all go, undifferentiated, into a +directory on the <i>doc/</i> subtree of the TDS. The layout of +the subtree is slightly different: <i>doc/latex</i> hosts all +LaTeX documentation directories, but more fundamental things are +covered, e.g., by <i>doc/etex</i> or <i>doc/xetex</i>. <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> |