summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex38
1 files changed, 22 insertions, 16 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
index e16460a7cb3..b65ecb06130 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
@@ -1,4 +1,4 @@
-% $Id: faq-install.tex,v 1.14 2011/04/13 09:45:46 rf10 Exp $
+% $Id: faq-install.tex,v 1.16 2012/02/08 21:59:32 rf10 Exp rf10 $
\section{Installing \AllTeX{} files}
@@ -27,17 +27,20 @@ decided what it is that you want to install:
How did you learn about the package?
If the information came from these \acro{FAQ}s, you should already
-have a link to the file (there are lists at the end of each answer):
+have a link to the file (there are lists of packages at the end of
+each answer).
\begin{narrowversion}
- make a browser link from \URL{http://mirror.ctan.org/} and the text
- in the list; if the link returns a directory listing, you can
+ Make a browser link from \URL{http://mirror.ctan.org/} and the text
+ in the package list; if the link returns a directory listing, you can
generally retrieve the whole directory by appending the link with
- \extension{zip}
+ \extension{zip}~--- so, for example
+ \URL{http://mirror.ctan.org/macros/latex/doc.zip} for the \latex{}
+ documentation directory.
\end{narrowversion}
\begin{wideversion}
- click on one of the links associated with the package, and you can
+ Click on one of the links associated with the package, and you can
get the package (which may be one file or several).
-% need searate wording for pdfversion and htmlversion, here
+% need separate wording for pdfversion and htmlversion, here
\end{wideversion}
If you heard about the file somewhere else, it's possible that the
@@ -52,10 +55,10 @@ very simplest will actually offer just \File{package.sty}~--- in this
case, just download the file and % ! line break
\Qref*{get on with installation}{Q-inst-wlcf}.
-Normally, though, you will want \File{foo.sty} but that file is distributed
-in a \LaTeX{} documented source file \File{foo.dtx}; thus you should
-search just for \emph{foo}~--- \File{foo.sty} won't be visible
-anywhere on the archive or in the catalogue.
+You will regularly find that the file you want (e.g., \File{foo.sty})
+is distributed in a \LaTeX{} documented source file \File{foo.dtx};
+thus you should search just for \emph{foo}~--- \File{foo.sty} won't be
+visible anywhere on the archive or in the catalogue.
Since most packages are distributed in this
\extension{dtx}/\extension{ins} way, they usually occupy their own
@@ -197,7 +200,8 @@ On a Unix(-alike) system, using te\TeX{} or \texlive{}, the root
directory will be named something like \path{/usr/share/texmf-local/}
or \path{/usr/local/share/texmf/}
You can ask such a system where it believes a local tree should be:
-\begin{quote}
+\begin{quote}
+
\begin{verbatim}
kpsewhich -var-value TEXMFLOCAL
\end{verbatim}
@@ -500,7 +504,7 @@ last being easy (unless it is forgotten!).
Ready-built \acro{ZIP} files~--- also known as % ! line break
\Qref*{\acro{TDS}-\acro{ZIP} files}{Q-tds-zip}~--- are designed to lighten
the load of performing the first two steps of installation: they
-contain all the files that are that's to be installed for a given
+contain all the files that are to be installed for a given
package, in their ``correct'' locations in a % ! line break
\Qref*{\acro{TDS} tree}{Q-tds}.
@@ -525,6 +529,7 @@ remaining chore is to update the file indexes~--- as in % ! line break
the package provides a font, you also need to enable the font's map,
which is discussed in % ! line break
``\Qref*{Installing a Type~1 font}{Q-instt1font}''
+\LastEdit{2012-02-08}
\Question[Q-tempinst]{``Temporary'' installation of \AllTeX{} files}
@@ -770,7 +775,7 @@ Other answers discuss specific font families~--- for example,
\Question[Q-instmffont]{Installing a font provided as \MF{} source}
-Metafont fonts are (by comparison with other sorts of font) rather
+Installing Metafont fonts is (by comparison with other sorts of font) rather
pleasingly simple. Nowadays, they are mostly distributed just as the
\MF{} source, since modern \TeX{} distributions are able to produce
everything the user needs ``on the fly''; however, if the distribution
@@ -787,9 +792,10 @@ specifies where the files should go.
Further confusion is introduced by font families whose authors devise rules
for automatic generation of \MF{} sources for generating fonts at
particular sizes; the installation has to know about the rules, as
-otherwise it cannot generate font files.
+otherwise it cannot generate font files. No general advice is
+available, but most such font families are now obsolescent.
-\Question[Q-instprinterfont]{Installing a \PS{} printer built-in font}
+\Question[Q-instprinterfont]{`Installing' a \PS{} printer built-in font}
There is a ``standard'' set of fonts that has appeared in every \PS{}
printer since the second generation of the type. These fonts