diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html')
| -rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html | 44 |
1 files changed, 22 insertions, 22 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html index 42ec4dd1199..797749a8fc3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html @@ -4,7 +4,7 @@ <h3>Where to install packages</h3> <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 +“<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 @@ -12,14 +12,14 @@ existing tree(s). Here are some examples of where various sorts of files should go: <blockquote> <pre> -.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>/ -.afm: $TEXMF/fonts/afm/<supplier>/<font>/ -.pfb: $TEXMF/fonts/type1/<supplier>/<font>/ -.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ -.otf: $TEXMF/fonts/opentype/<supplier>/<font>/ +.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>/ +.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> @@ -27,40 +27,40 @@ 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>/ +.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>format</i>> identifies the format the macros -are designed for — it can be things such as <code>plain</code>, +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. +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 +<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 +(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>. +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 +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 +<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/>Documentation for each package should all go, undifferentiated, into a directory on the <i>doc/</i> subtree of the TDS. The layout of |