diff options
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html')
| -rw-r--r-- | Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html | 29 |
1 files changed, 15 insertions, 14 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html index 95e890fa1ad..a3c090f3880 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html @@ -5,7 +5,7 @@ <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 +distributions (such as teTeX or MiKTeX) there are some general rules that you can follow: <p> @@ -17,7 +17,7 @@ tree. The root directory will be named something like: teTeX: /usr/share/texmf-local/ or /usr/local/share/texmf/ fpTeX: c:\Programs\TeXLive\texmf-local\ - mikTeX: c:\localtexmf\ + 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: @@ -25,9 +25,9 @@ root is; on a Unix system, the command to use is: <pre> kpsewhich -expand-var "\$TEXMFLOCAL" </pre> -</blockquote> +</blockquote><p> the output being the actual path.) -<p>Let's write <code>$TEXMF</code> for this root, whatever it is for your system. +<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 @@ -41,33 +41,34 @@ should go: .afm: $TEXMF/fonts/afm/<supplier>/<font>/ .pfb: $TEXMF/fonts/type1/<supplier>/<font>/ .ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ +.pool, .fmt, .base or .mem: $TEXMF/web2c </pre> -and for modern systems (teTeX 3.0, and the like, using TDS -v1.1 format): +and for modern systems (distributed in 2005 or later, such as +teTeX 3.0, using TDS v1.1 layouts): <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>> +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 +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>, +<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 +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>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 +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. |