diff options
| author | Karl Berry <karl@freefriends.org> | 2006-12-03 01:48:15 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2006-12-03 01:48:15 +0000 |
| commit | 0aa04ee7d3e4699f6db1ccd0abf67d3212977cc1 (patch) | |
| tree | 2e9c9c1a8d8c13bc2c219e2f21bdb67d5b33a1cc /Master/texmf-doc | |
| parent | f4d1dc22afa389a923af4319aa47ceaee7d17da0 (diff) | |
minimal 2006 doc updates
git-svn-id: svn://tug.org/texlive/trunk@2577 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-doc')
| -rw-r--r-- | Master/texmf-doc/doc/english/texlive-en/live.html | 1000 | ||||
| -rw-r--r-- | Master/texmf-doc/doc/english/texlive-en/live.pdf | bin | 771118 -> 791781 bytes | |||
| -rw-r--r-- | Master/texmf-doc/source/english/texlive-en/archive/live-2005.tex | 3174 | ||||
| -rw-r--r-- | Master/texmf-doc/source/english/texlive-en/archive/tex-live.sty-2005 | 429 | ||||
| -rw-r--r-- | Master/texmf-doc/source/english/texlive-en/live.tex | 138 |
5 files changed, 4212 insertions, 529 deletions
diff --git a/Master/texmf-doc/doc/english/texlive-en/live.html b/Master/texmf-doc/doc/english/texlive-en/live.html index d345b001196..f17e204d30c 100644 --- a/Master/texmf-doc/doc/english/texlive-en/live.html +++ b/Master/texmf-doc/doc/english/texlive-en/live.html @@ -2,13 +2,13 @@ "http://www.w3.org/TR/html4/loose.dtd"> <html > <head> - <title>The TEX Live Guide TeX Collection 2005 </title> + <title>The TEX Live Guide TeX Collection 2006 </title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="generator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/mn.html)"> <meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/mn.html)"> <!-- charset=utf-8,html,info,fn-in --> <meta name="src" content="live.tex"> -<meta name="date" content="2005-10-31 06:36:00"> +<meta name="date" content="2006-12-03 02:28:00"> <link rel="stylesheet" type="text/css" href="live.css"> <link rel="stylesheet" type="text/css" href="live.css" /> <link rel="stylesheet" type="text/css" href="tex-live.css" /> @@ -23,15 +23,15 @@ <h2 class="titleHead">The <span class="TEX">T<span class="E">E</span>X</span> Live Guide<br> <span class="TEX">T<span -class="E">E</span>X</span> Collection 2005 </h2> - <div class="author"><span -class="ec-lmr-12">Sebastian Rahtz & Karl Berry, editors</span> -<br> <span class="obeylines-h"><a +class="E">E</span>X</span> Collection 2006 </h2> + <div class="author"><span +class="ec-lmr-12">Karl Berry, editor</span> +<br> <span class="obeylines-h"><a href="http://tug.org/texlive/" class="url" ><span class="ec-lmtt-12">http://tug.org/texlive/</span></a></span> </div> <br> <div class="date" ><span -class="ec-lmr-12">October 2005</span></div> +class="ec-lmr-12">December 2006</span></div> </div> <h3 class="likesectionHead"><a id="x1-1000"></a>Contents</h3> @@ -132,9 +132,9 @@ href="#x1-6400010" id="QQ2-1-69">Release history</a></span> <br>  <span class="subsectionToc">10.1 <a href="#x1-6500010.1" id="QQ2-1-70">Past</a></span> <br>  <span class="subsectionToc">10.2 <a -href="#x1-6800010.2" id="QQ2-1-73">Present</a></span> +href="#x1-6900010.2" id="QQ2-1-74">Present</a></span> <br>  <span class="subsectionToc">10.3 <a -href="#x1-6900010.3" id="QQ2-1-74">Future</a></span> +href="#x1-7000010.3" id="QQ2-1-75">Future</a></span> </div> <h3 class="likesectionHead"><a id="x1-2000"></a>List of Tables</h3> @@ -411,7 +411,7 @@ href="http://tug.org/protext" class="url" ><span class="ec-lmtt-10">http://tug.org/protext</span></a></span>. <!--l. 199--><p class="noindent">Pro<span class="TEX">T<span class="E">E</span>X</span>t is provided as both the top level of the <span -class="ec-lmss-10">live </span>DVD  and on its own CD (for those +class="ec-lmss-10">live </span>DVD and on its own CD (for those who cannot use the DVD). </dd></dl> <!--l. 204--><p class="noindent">You can tell which type of distribution you’re in by looking for a <span @@ -431,7 +431,7 @@ class="E">E</span>X</span> Live distribution. On the <span class="ec-lmss-10">live</span> DVD, the entire <span class="TEX">T<span class="E">E</span>X</span> Live hierarchy is in a subdirectory <span -class="ec-lmtt-10">texlive2005</span>, not at the top level of the +class="ec-lmtt-10">texliveYYYY</span>, not at the top level of the disc. <div class="tabular"><table class="tabular" cellspacing="0" cellpadding="0" @@ -616,28 +616,26 @@ class="ec-lmbx-10">T</span><span class="E"><span class="ec-lmbx-10">E</span></span><span class="ec-lmbx-10">X</span></span> </dt><dd -class="description">writes Acrobat PDF format as well as DVI. The <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span -class="E">E</span>X</span></span> <span -class="ec-lmss-10">hyperref </span>package has an option - ‘<span -class="ec-lmtt-10">pdftex</span>’ which turns on all the program features. See <a -href="../../../../texmf/doc/pdftex/manual/" >texmf/doc/pdftex/manual/</a> for the - manual, and <a -href="../../../../texmf/doc/pdftex/manual/samplepdf/samplepdf.tex" >texmf/doc/pdftex/manual/samplepdf/samplepdf.tex</a>. +class="description">builds on the e-<span class="TEX">T<span +class="E">E</span>X</span> extensions, + adding support for writing PDF output as well as DVI. See <a +href="../../../../texmf/doc/pdftex/manual/" >texmf/doc/pdftex/manual/</a> for + the manual, and <a +href="../../../../texmf/doc/pdftex/manual/samplepdf/samplepdf.tex" >texmf/doc/pdftex/manual/samplepdf/samplepdf.tex</a>. This is the default + program for all formats except plain <span class="TEX">T<span +class="E">E</span>X</span>. </dd><dt class="description"> <span -class="ec-lmbx-10">pdfe</span><span class="TEX"><span +class="ec-lmbx-10">Xe</span><span class="TEX"><span class="ec-lmbx-10">T</span><span class="E"><span class="ec-lmbx-10">E</span></span><span class="ec-lmbx-10">X</span></span> </dt><dd -class="description">combines the pdf<span class="TEX">T<span -class="E">E</span>X</span> and e-<span class="TEX">T<span -class="E">E</span>X</span> extensions. This is the default program for all - formats except plain <span class="TEX">T<span -class="E">E</span>X</span>. See above for documentation. +class="description">adds support for Unicode input and OpenType fonts, using third-party libraries. See <span class="obeylines-h"><a +href="http://scripts.sil.org/xetex" class="url" ><span +class="ec-lmtt-10">http://scripts.sil.org/xetex</span></a></span>. </dd><dt class="description"> <span class="ec-lmbx-10">Omega</span><span @@ -655,13 +653,13 @@ class="E">E</span>X</span> extensions. See <a href="../../../../texmf-dist/doc/aleph/base" >texmf-dist/doc/aleph/base</a> for some minimal documentation. </dd></dl> -<!--l. 338--><p class="noindent"> +<!--l. 337--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">2.5 </span> <a id="x1-110002.5"></a>Other notable programs in <span class="TEX">T<span class="E">E</span>X</span> Live</h4> -<!--l. 340--><p class="noindent">Here are a few other commonly-used programs included in <span class="TEX">T<span +<!--l. 339--><p class="noindent">Here are a few other commonly-used programs included in <span class="TEX">T<span class="E">E</span>X</span> Live: -<!--l. 342--><p class="indent"> +<!--l. 341--><p class="indent"> <dl class="list1"><dt class="list"> <span class="ec-lmss-10">bibtex</span> </dt><dd @@ -720,14 +718,14 @@ class="E">E</span>X</span> to HTML converter. </dd></dl> -<!--l. 375--><p class="noindent"> +<!--l. 374--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">3 </span> <a id="x1-120003"></a>Unix installation</h3> -<!--l. 378--><p class="noindent">As introduced in section <a +<!--l. 377--><p class="noindent">As introduced in section <a href="#x1-40001.1">1.1<!--tex4ht:ref: sec:basic --></a> (p. <a href="#x1-40001.1">4<!--tex4ht:ref: sec:basic --></a>), <span class="TEX">T<span class="E">E</span>X</span> Live has three principal uses: -<!--l. 381--><p class="indent"> +<!--l. 380--><p class="indent"> <ol class="enumerate1" > <li class="enumerate" value="1" ><a @@ -741,15 +739,15 @@ class="E">E</span>X</span> Live has three principal uses: ><a id="x1-12006x3"></a>Integrate a particular package or collection into your existing <span class="TEX">T<span class="E">E</span>X</span> installation.</li></ol> -<!--l. 388--><p class="noindent">The following sections describes the Unix-specific procedures for each of these. -<!--l. 391--><p class="indent"> <hr class="figure"><div class="figure" +<!--l. 387--><p class="noindent">The following sections describes the Unix-specific procedures for each of these. +<!--l. 390--><p class="indent"> <hr class="figure"><div class="figure" ><table class="figure"><tr class="figure"><td class="figure" > -<!--l. 391--><p class="noindent"> <span +<!--l. 390--><p class="noindent"> <span class="ec-lmbx-10">Warning: </span>The <span class="TEX"><span class="ec-lmss-10">T</span><span class="E"><span @@ -768,15 +766,15 @@ documentation for your <span class="ec-lmss-10">mount </span>command to see how to do this. If you have several different machines on a local network, you may be able to mount the discs on one which does support Rock Ridge, and use this with the others. -<!--l. 402--><p class="indent"> Modern systems should be able to use the discs without problems. If troubles, let us know. The +<!--l. 401--><p class="indent"> Modern systems should be able to use the discs without problems. If troubles, let us know. The discussion below assumes you have been able to mount the CDs with full Rock Ridge compatibility. -<!--l. 406--><p class="indent"> </td></tr></table></div><hr class="endfigure"> +<!--l. 405--><p class="indent"> </td></tr></table></div><hr class="endfigure"> <h4 class="subsectionHead"><span class="titlemark">3.1 </span> <a id="x1-130003.1"></a>Running <span class="TEX">T<span class="E">E</span>X</span> Live directly from media (Unix)</h4> -<!--l. 454--><p class="noindent">It is possible to use the <span class="TEX">T<span +<!--l. 453--><p class="noindent">It is possible to use the <span class="TEX">T<span class="E">E</span>X</span> system directly from the <span class="ec-lmss-10">live </span>DVD, without installing the distribution to disk. (Thus the name <span class="TEX">T<span @@ -792,7 +790,7 @@ class="ec-lmtt-10">/dev/cdrom</span>, here) may vary. (All our examples will use class="ec-lmtt-10">> </span>as the shell prompt; user input is <span class="underline"><span class="ec-lmtt-10">underlined</span></span>.) <div class="alltt"> -<!--l. 455--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 454--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">mount</span> <span class="ec-lmtt-10">-t</span> <span @@ -801,18 +799,18 @@ class="ec-lmtt-10">/dev/cdrom</span> <span class="ec-lmtt-10">/mnt/cdrom</span></span> </div> </div> -<!--l. 455--><p class="noindent">Change the current directory to the mount point: <div class="alltt"> -<!--l. 455--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 454--><p class="noindent">Change the current directory to the mount point: <div class="alltt"> +<!--l. 454--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">cd</span> <span class="ec-lmtt-10">/mnt/cdrom</span></span> </div> </div> -<!--l. 455--><p class="noindent">Under Mac OS X, the directory is typically under <span +<!--l. 454--><p class="noindent">Under Mac OS X, the directory is typically under <span class="ec-lmtt-10">/Volumes</span>, and the media will be mounted automatically. Run the installation script <span class="ec-lmtt-10">install-tl.sh</span>: <div class="alltt"> -<!--l. 456--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 455--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">sh</span> <span class="ec-lmtt-10">install-tl.sh</span></span> @@ -820,24 +818,24 @@ class="ec-lmtt-10">install-tl.sh</span></span> class="ec-lmtt-10">Welcome to TeX Live...</span> </div> </div> -<!--l. 456--><p class="noindent">After various greeting messages and a list of the main menu options, the installation will ask you to +<!--l. 455--><p class="noindent">After various greeting messages and a list of the main menu options, the installation will ask you to enter a command. Do this by typing the desired character and hitting return; don’t type the angle brackets shown. Either uppercase or lowercase is ok; we’ll use lowercase in our examples. -<!--l. 458--><p class="indent"> For running live, our first command will be <span class="underline"><span +<!--l. 457--><p class="indent"> For running live, our first command will be <span class="underline"><span class="ec-lmtt-10">d</span></span> and then the subcommand <span class="underline"><span class="ec-lmtt-10">1</span></span> to set directories. Even in this case, we must choose a directory on the local disk to place files that the <span class="TEX">T<span class="E">E</span>X</span> system itself generates, such as fonts and formats, and also to provide a place for updated configuration files, if need be. -<!--l. 464--><p class="indent"> We’ll use <span -class="ec-lmtt-10">/opt/texlive2005 </span>in this example. It’s good to include the year in the name, -as these generated files are not compatible from release to release. (If the default value of +<!--l. 463--><p class="indent"> We’ll use <span +class="ec-lmtt-10">/opt/texlive2006 </span>in this example. It’s good to include the year in the name, as these +generated files are not in general compatible from release to release. (If the default value of <span -class="ec-lmtt-10">/usr/local/texlive/2005 </span>works for you, then you can skip this step.) +class="ec-lmtt-10">/usr/local/texlive/2006 </span>works for you, then you can skip this step.) <div class="alltt"> -<!--l. 470--><p class="noindent"><div class="obeylines-v"> +<!--l. 469--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">Enter</span><span class="ec-lmtt-10"> command:</span><span @@ -855,7 +853,7 @@ class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> </span><span -class="ec-lmtt-10"> /usr/local/texlive/2005</span> +class="ec-lmtt-10"> /usr/local/texlive/2006</span> <br><span class="ec-lmtt-10">...</span> <br><span @@ -870,7 +868,7 @@ class="ec-lmtt-10"> for</span><span class="ec-lmtt-10"> TEXDIR</span><span class="ec-lmtt-10"> [/usr/local/texlive/TeX]:</span><span class="ec-lmtt-10"> </span><span class="underline"><span -class="ec-lmtt-10">/opt/texlive2005</span></span> +class="ec-lmtt-10">/opt/texlive2006</span></span> <br><span class="ec-lmtt-10">...</span> <br><span @@ -881,10 +879,10 @@ class="ec-lmtt-10">r</span></span> </div> </div> -<!--l. 481--><p class="noindent">Back at the main menu, our second and last command is <span class="underline"><span +<!--l. 480--><p class="noindent">Back at the main menu, our second and last command is <span class="underline"><span class="ec-lmtt-10">r</span></span>, to set up for running live off the media without installing to disk: <div class="alltt"> -<!--l. 484--><p class="noindent"><div class="obeylines-v"> +<!--l. 483--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">Enter</span><span class="ec-lmtt-10"> command:</span><span @@ -905,14 +903,14 @@ class="ec-lmtt-10"> Live!</span> class="ec-lmtt-10">></span> </div> </div> -<!--l. 492--><p class="noindent">And we are back at the system prompt, as shown. -<!--l. 494--><p class="indent"> Next, it is necessary to alter two environment variables: <span +<!--l. 491--><p class="noindent">And we are back at the system prompt, as shown. +<!--l. 493--><p class="indent"> Next, it is necessary to alter two environment variables: <span class="ec-lmtt-10">PATH</span>, to an architecture-dependent value (so that we can run the programs), and <span class="ec-lmtt-10">TEXMFSYSVAR</span>, to the value specified above. See table <a href="#x1-13001r1">1<!--tex4ht:ref: tab:archlist --></a> for a list of the architecture names for the different systems. -<!--l. 508--><p class="indent"> After the main installation has completed, and environment variables have been set, the last step is to +<!--l. 507--><p class="indent"> After the main installation has completed, and environment variables have been set, the last step is to run <span class="ec-lmss-10">texconfig </span>or <span class="ec-lmss-10">texconfig-sys </span>to customize your installation to your needs. This is explained in @@ -921,7 +919,7 @@ href="#x1-170004.1">4.1<!--tex4ht:ref: sec:texconfig --></a>, p. <a href="#x1-170004.1">26<!--tex4ht:ref: sec:texconfig --></a>. -<!--l. 510--><p class="indent"> <a +<!--l. 509--><p class="indent"> <a id="x1-13001r1"></a><hr class="float"><div class="float" ><table class="float"><tr class="float"><td class="float" > @@ -997,14 +995,14 @@ class="td11"> </td> </tr></table> </td></tr></table></div><hr class="endfloat" /> -<!--l. 535--><p class="indent"> The syntax for setting the environment variables, and the initialization file to put them in, depends +<!--l. 534--><p class="indent"> The syntax for setting the environment variables, and the initialization file to put them in, depends on the shell you use. If you use a Bourne-compatible shell (<span class="ec-lmss-10">sh</span>, <span class="ec-lmss-10">bash</span>, <span class="ec-lmss-10">ksh</span>, et al.), put the following into your <span class="ec-lmtt-10">$HOME/.profile </span>file: <div class="alltt"> -<!--l. 539--><p class="noindent"><div class="obeylines-v"> +<!--l. 538--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">PATH=/mnt/cdrom/bin/</span><span class="ec-lmro-10">archname</span><span @@ -1012,16 +1010,16 @@ class="ec-lmtt-10">:$PATH;</span><span class="ec-lmtt-10"> export</span><span class="ec-lmtt-10"> PATH</span> <br><span -class="ec-lmtt-10">TEXMFSYSVAR=/opt/texlive2005/texmf-var;</span><span +class="ec-lmtt-10">TEXMFSYSVAR=/opt/texlive2006/texmf-var;</span><span class="ec-lmtt-10"> export</span><span class="ec-lmtt-10"> TEXMFVAR</span> </div> </div> -<!--l. 544--><p class="noindent">For C shell-compatible shells (<span +<!--l. 543--><p class="noindent">For C shell-compatible shells (<span class="ec-lmss-10">csh</span>, <span class="ec-lmss-10">tcsh</span>), put the following into your <span class="ec-lmtt-10">$HOME/.cshrc </span>file: <div class="alltt"> -<!--l. 546--><p class="noindent"><div class="obeylines-v"> +<!--l. 545--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">setenv</span><span class="ec-lmtt-10"> PATH</span><span @@ -1031,20 +1029,20 @@ class="ec-lmtt-10">:$PATH</span> <br><span class="ec-lmtt-10">setenv</span><span class="ec-lmtt-10"> TEXMFSYSVAR</span><span -class="ec-lmtt-10"> /opt/texlive2005/texmf-var</span> +class="ec-lmtt-10"> /opt/texlive2006/texmf-var</span> </div> </div> -<!--l. 551--><p class="noindent">Then log out, log back in, and test your installation (see section <a +<!--l. 550--><p class="noindent">Then log out, log back in, and test your installation (see section <a href="#x1-180004.2">4.2<!--tex4ht:ref: sec:test-install --></a>, p. <a href="#x1-180004.2">27<!--tex4ht:ref: sec:test-install --></a>). -<!--l. 560--><p class="indent"> If in doubt, please ask any local system gurus to help you with problems; for example, the way to +<!--l. 559--><p class="indent"> If in doubt, please ask any local system gurus to help you with problems; for example, the way to mount the <span class="TEX">T<span class="E">E</span>X</span> Live media, which directory or directories to use, and precise details of the changes to your personal initialization files can and do vary from site to site. <h4 class="subsectionHead"><span class="titlemark">3.2 </span> <a id="x1-140003.2"></a>Installing <span class="TEX">T<span class="E">E</span>X</span> Live to disk</h4> -<!--l. 567--><p class="noindent">It is possible, indeed typical, to install the <span class="TEX">T<span +<!--l. 566--><p class="noindent">It is possible, indeed typical, to install the <span class="TEX">T<span class="E">E</span>X</span> Live distribution to hard disk. This can be done from either the <span class="ec-lmss-10">live </span>or <span @@ -1052,14 +1050,14 @@ class="ec-lmss-10">inst </span>distributions. (See section <a href="#x1-70002.1">2.1<!--tex4ht:ref: sec:multiple-dist --></a>, p. <a href="#x1-70002.1">6<!--tex4ht:ref: sec:multiple-dist --></a>, for an explanation of the different distributions.) -<!--l. 573--><p class="indent"> To start, you mount the CD or DVD, with Rock Ridge extensions enabled. The exact command to do +<!--l. 572--><p class="indent"> To start, you mount the CD or DVD, with Rock Ridge extensions enabled. The exact command to do this varies from system to system; the following works under Linux, except the name of the device (<span class="ec-lmtt-10">/dev/cdrom</span>, here) may vary. (All our examples will use <span class="ec-lmtt-10">> </span>as the shell prompt; user input is <span class="underline"><span class="ec-lmtt-10">underlined</span></span>.) <div class="alltt"> -<!--l. 573--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 572--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">mount</span> <span class="ec-lmtt-10">-t</span> <span @@ -1068,18 +1066,18 @@ class="ec-lmtt-10">/dev/cdrom</span> <span class="ec-lmtt-10">/mnt/cdrom</span></span> </div> </div> -<!--l. 573--><p class="noindent">Change the current directory to the mount point: <div class="alltt"> -<!--l. 573--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 572--><p class="noindent">Change the current directory to the mount point: <div class="alltt"> +<!--l. 572--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">cd</span> <span class="ec-lmtt-10">/mnt/cdrom</span></span> </div> </div> -<!--l. 573--><p class="noindent">Under Mac OS X, the directory is typically under <span +<!--l. 572--><p class="noindent">Under Mac OS X, the directory is typically under <span class="ec-lmtt-10">/Volumes</span>, and the media will be mounted automatically. Run the installation script <span class="ec-lmtt-10">install-tl.sh</span>: <div class="alltt"> -<!--l. 574--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 573--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">sh</span> <span class="ec-lmtt-10">install-tl.sh</span></span> @@ -1088,11 +1086,11 @@ class="ec-lmtt-10">Welcome to TeX Live...</span> </div> </div> -<!--l. 574--><p class="noindent">After various greeting messages and a list of the main menu options, the installation will ask you to +<!--l. 573--><p class="noindent">After various greeting messages and a list of the main menu options, the installation will ask you to enter a command. Do this by typing the desired character and hitting return; don’t type the angle brackets shown. Either uppercase or lowercase is ok; we’ll use lowercase in our examples. -<!--l. 576--><p class="indent"> Table <a +<!--l. 575--><p class="indent"> Table <a href="#x1-14001r2">2<!--tex4ht:ref: tab:main-menu-options --></a> briefly lists the options in the main menu. The order in which you select the options makes little difference, except that <span class="underline"><span class="ec-lmtt-10">i</span></span> must be last. It’s reasonable to go through them in the order presented @@ -1100,7 +1098,7 @@ here. <div class="table"> -<!--l. 582--><p class="indent"> <a +<!--l. 581--><p class="indent"> <a id="x1-14001r2"></a><hr class="float"><div class="float" ><table class="float"><tr class="float"><td class="float" > @@ -1161,13 +1159,13 @@ class="td11"> </td> </tr></table> </td></tr></table></div><hr class="endfloat" /> </div> -<!--l. 598--><p class="indent"> Here are further details on each option. -<!--l. 600--><p class="indent"> <span +<!--l. 597--><p class="indent"> Here are further details on each option. +<!--l. 599--><p class="indent"> <span class="ec-lmtk-10">p </span><span class="ec-lmbx-10">– Current platform. </span>Since the installation script automatically guesses which platform you’re running on, it is usually unnecessary to use this option. It’s there in case you need to override the automatic detection. -<!--l. 605--><p class="indent"> <span +<!--l. 604--><p class="indent"> <span class="ec-lmtk-10">b </span><span class="ec-lmbx-10">– Binary architectures. </span>By default, only the binaries for your current platform will be installed. From this menu, you can select installation of binaries for other architectures as well (or omit @@ -1177,7 +1175,7 @@ network of heterogenous machines. For a list of the supported architectures, see href="#x1-13001r1">1<!--tex4ht:ref: tab:archlist --></a>, p. <a href="#x1-13001r1">16<!--tex4ht:ref: tab:archlist --></a>. -<!--l. 613--><p class="indent"> <span +<!--l. 612--><p class="indent"> <span class="ec-lmtk-10">s </span><span class="ec-lmbx-10">– Base installation scheme. </span>From this menu, you can choose an overall set of package collections, called a “scheme”. The default <span @@ -1186,7 +1184,7 @@ choose the <span class="ec-lmtt-10">basic </span>scheme for a minimal system, or <span class="ec-lmtt-10">medium </span>to get something in between. There are also specific sets for Omega and XML. -<!--l. 620--><p class="indent"> <span +<!--l. 619--><p class="indent"> <span class="ec-lmtk-10">c </span><span class="ec-lmbx-10">– Individual collections. </span>From this menu, you can override the scheme’s set of collections to install. Collections are one level more detailed than schemes — collections consist of one or more @@ -1194,7 +1192,7 @@ packages, where packages (the lowest level grouping in <span class="TEX">T<span class="E">E</span>X</span> Live) contain the actual <span class="TEX">T<span class="E">E</span>X</span> macro files, font families, and so on. In this menu, selection letters are case-sensitive. -<!--l. 627--><p class="indent"> <span +<!--l. 626--><p class="indent"> <span class="ec-lmtk-10">l </span><span class="ec-lmbx-10">– Language collections</span>. This menu has the same basic purpose as <span class="underline"><span class="ec-lmtt-10">c</span></span>, to override the collection set @@ -1211,7 +1209,7 @@ class="tabbing">Arabic </td><td width="203" class="tabbing">Armenian </td><td class="tabbing">Chinese Japanese Korean </td></tr></table> -<!--l. 643--><p class="indent"> <table +<!--l. 642--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td width="203" @@ -1219,7 +1217,7 @@ class="tabbing">Croatian </td><td width="203" class="tabbing">Cyrillic </td><td width="203" class="tabbing">Czech/Slovak </td><td class="tabbing">Danish</td></tr></table> -<!--l. 647--><p class="indent"> <table +<!--l. 646--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td width="203" @@ -1227,7 +1225,7 @@ class="tabbing">Dutch </td><td width="203" class="tabbing">Finnish </td><td width="203" class="tabbing">French </td><td class="tabbing">German</td></tr></table> -<!--l. 651--><p class="indent"> <table +<!--l. 650--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td width="203" @@ -1235,7 +1233,7 @@ class="tabbing">Greek </td><td width="203" class="tabbing">Hebrew </td><td width="203" class="tabbing">Hungarian </td><td class="tabbing">Indic</td></tr></table> -<!--l. 655--><p class="indent"> <table +<!--l. 654--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td width="203" @@ -1243,7 +1241,7 @@ class="tabbing">Italian </td><td width="203" class="tabbing">Latin </td><td width="203" class="tabbing">Manju </td><td class="tabbing">Mongolian</td></tr></table> -<!--l. 659--><p class="indent"> <table +<!--l. 658--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td width="203" @@ -1251,7 +1249,7 @@ class="tabbing">Norwegian </td><td width="203" class="tabbing">Polish </td><td width="203" class="tabbing">Portuguese </td><td class="tabbing">Spanish</td></tr></table> -<!--l. 663--><p class="indent"> <table +<!--l. 662--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td width="203" @@ -1259,20 +1257,20 @@ class="tabbing">Swedish </td><td width="203" class="tabbing">Tibetan </td><td width="203" class="tabbing">UK English </td><td class="tabbing">Vietnamese</td></tr></table> -<!--l. 667--><p class="indent"> <table +<!--l. 666--><p class="indent"> <table cellpadding="0" border="0" cellspacing="0" class="tabbing"><tr valign="baseline" class="tabbing"><td class="tabbing"></td></tr></table> -<!--l. 668--><p class="indent"> -<!--l. 670--><p class="noindent">Language collections typically include fonts, macros, hyphenation patterns, and other support files. (For +<!--l. 667--><p class="indent"> +<!--l. 669--><p class="noindent">Language collections typically include fonts, macros, hyphenation patterns, and other support files. (For instance, <span class="ec-lmss-10">frenchle.sty </span>is installed if you select the <span class="ec-lmtt-10">French </span>collection.) In addition, installing a language collection will alter the <span class="ec-lmtt-10">language.dat </span>configuration file controlling which hyphenation patterns are loaded. -<!--l. 677--><p class="indent"> <span +<!--l. 676--><p class="indent"> <span class="ec-lmtk-10">d </span><span class="ec-lmbx-10">– Installation directories</span>. Three directories can be changed here: <dl class="list1"><dt class="list"> @@ -1280,13 +1278,13 @@ class="ec-lmbx-10">– Installation directories</span>. Three directories ca class="ec-lmtt-10">TEXDIR</span> </dt><dd class="list">The top-level directory under which everything else will be installed. The default value is <span -class="ec-lmtt-10">/usr/local/texlive/2005</span>, and is often changed. We recommend including the year +class="ec-lmtt-10">/usr/local/texlive/2006</span>, and is often changed. We recommend including the year in the name, to keep different releases of <span class="TEX">T<span class="E">E</span>X</span> Live separate. (You may wish to make a version-independent name such <span class="ec-lmtt-10">/usr/local/texlive </span>via a symbolic link, which you can then update after testing the new release.) - <!--l. 690--><p class="noindent">Under Mac OS X, the usual frontends look for <span class="TEX">T<span + <!--l. 689--><p class="noindent">Under Mac OS X, the usual frontends look for <span class="TEX">T<span class="E">E</span>X</span> in <span class="ec-lmtt-10">/usr/local/teTeX</span>, so you may wish to install <span class="TEX">T<span @@ -1318,7 +1316,7 @@ class="ec-lmss-10">texconfig </span>looks for modified configuration data. href="#x1-170004.1">4.1<!--tex4ht:ref: sec:texconfig --></a>, p. <a href="#x1-170004.1">26<!--tex4ht:ref: sec:texconfig --></a> for more information. </dd></dl> -<!--l. 710--><p class="indent"> <span +<!--l. 709--><p class="indent"> <span class="ec-lmtk-10">o </span><span class="ec-lmbx-10">– Other options. </span>From this menu, you can select the following general options: <dl class="list1"><dt class="list"> @@ -1337,7 +1335,7 @@ class="ec-lmtt-10">/usr/local/man </span>and the Info files available under <span class="ec-lmtt-10">/usr/local/info</span>. (Of course you need appropriate privileges to write in the specified directories.) - <!--l. 726--><p class="noindent">It is not advisable to overwrite a <span class="TEX">T<span + <!--l. 725--><p class="noindent">It is not advisable to overwrite a <span class="TEX">T<span class="E">E</span>X</span> system that came with your system with this option. It’s intended primarily for creating the links in standard directories that are known to users, such as <span @@ -1354,11 +1352,11 @@ class="ec-lmtt-10">s</span> </dt><dd class="list">Skip installation of the main font/macro source tree. This is useful if you are arranging to share that tree between machines and/or architectures in some other way, such as NFS. </dd></dl> -<!--l. 741--><p class="indent"> <span +<!--l. 740--><p class="indent"> <span class="ec-lmbx-10">i – Perform installation. </span>When you’re satisfied with your configuration options, enter <span class="underline"><span class="ec-lmtt-10">i</span></span> to actually do the installation from the media to your chosen locations. -<!--l. 746--><p class="indent"> After the installation completes, your next step is to include the architecture-specific subdirectory of +<!--l. 745--><p class="indent"> After the installation completes, your next step is to include the architecture-specific subdirectory of <span class="ec-lmtt-10">TEXDIR/bin </span>in your <span class="ec-lmtt-10">PATH</span>, so the newly-installed programs can be found. The architecture names are @@ -1366,7 +1364,7 @@ listed in table <a href="#x1-13001r1">1<!--tex4ht:ref: tab:archlist --></a>, p. <a href="#x1-13001r1">16<!--tex4ht:ref: tab:archlist --></a>, or you can simply list the directory <span class="ec-lmtt-10">TEXDIR/bin</span>. -<!--l. 753--><p class="indent"> The syntax for doing this, and the initialization file to use, depends on your shell. If you use a +<!--l. 752--><p class="indent"> The syntax for doing this, and the initialization file to use, depends on your shell. If you use a Bourne-compatible shell (<span class="ec-lmss-10">sh</span>, <span class="ec-lmss-10">bash</span>, <span @@ -1374,43 +1372,43 @@ class="ec-lmss-10">ksh</span>, et al.), put the following into your <span class="ec-lmtt-10">$HOME/.profile</span> file: <div class="alltt"> -<!--l. 758--><p class="noindent"><div class="obeylines-v"> +<!--l. 757--><p class="noindent"><div class="obeylines-v"> <span -class="ec-lmtt-10">PATH=/usr/local/texlive/2005/bin/</span><span +class="ec-lmtt-10">PATH=/usr/local/texlive/2006/bin/</span><span class="ec-lmro-10">archname</span><span class="ec-lmtt-10">:$PATH;</span><span class="ec-lmtt-10"> export</span><span class="ec-lmtt-10"> PATH</span> </div> </div> -<!--l. 762--><p class="noindent">For C shell-compatible shells (<span +<!--l. 761--><p class="noindent">For C shell-compatible shells (<span class="ec-lmss-10">csh</span>, <span class="ec-lmss-10">tcsh</span>), put the following into your <span class="ec-lmtt-10">$HOME/.cshrc </span>file: <div class="alltt"> -<!--l. 764--><p class="noindent"><div class="obeylines-v"> +<!--l. 763--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">setenv</span><span class="ec-lmtt-10"> PATH</span><span -class="ec-lmtt-10"> /usr/local/texlive/2005/bin/</span><span +class="ec-lmtt-10"> /usr/local/texlive/2006/bin/</span><span class="ec-lmro-10">archname</span><span class="ec-lmtt-10">:$PATH</span> </div> </div> -<!--l. 768--><p class="indent"> After the main installation has completed, and environment variables have been set, the last step is to +<!--l. 767--><p class="indent"> After the main installation has completed, and environment variables have been set, the last step is to run <span class="ec-lmss-10">texconfig </span>or <span class="ec-lmss-10">texconfig-sys </span>to customize your installation to your needs. This is explained in section <a href="#x1-170004.1">4.1<!--tex4ht:ref: sec:texconfig --></a>, p. <a href="#x1-170004.1">26<!--tex4ht:ref: sec:texconfig --></a>. -<!--l. 770--><p class="indent"> Here is a minimal annotated example which accepts the default directories and installs binaries for +<!--l. 769--><p class="indent"> Here is a minimal annotated example which accepts the default directories and installs binaries for the current system only. Thus, only one command is needed, <span class="underline"><span class="ec-lmtt-10">i</span></span> for install. The <span class="ec-lmtt-10">> </span>is the shell prompt as usual. <div class="alltt"> -<!--l. 775--><p class="noindent"><div class="obeylines-v"> +<!--l. 774--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1479,29 +1477,29 @@ class="ec-lmtt-10"> example:</span> <br><span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span -class="ec-lmtt-10">PATH=/usr/local/texlive/2005/bin/i386-linux:$PATH;</span> <span +class="ec-lmtt-10">PATH=/usr/local/texlive/2006/bin/i386-linux:$PATH;</span> <span class="ec-lmtt-10">export</span> <span class="ec-lmtt-10">PATH</span></span> </div> </div> -<!--l. 783--><p class="indent"> If in doubt, please ask any local system gurus to help you with problems; for example, the way to +<!--l. 782--><p class="indent"> If in doubt, please ask any local system gurus to help you with problems; for example, the way to mount the <span class="TEX">T<span class="E">E</span>X</span> Live media, which directory or directories to use, and precise details of the changes to your personal initialization files can and do vary from site to site. <h4 class="subsectionHead"><span class="titlemark">3.3 </span> <a id="x1-150003.3"></a>Installing individual packages to disk</h4> -<!--l. 789--><p class="noindent">You can add individual packages or collections from the current distribution to an existing non-<span class="TEX">T<span +<!--l. 788--><p class="noindent">You can add individual packages or collections from the current distribution to an existing non-<span class="TEX">T<span class="E">E</span>X</span> Live setup, or an earlier <span class="TEX">T<span class="E">E</span>X</span> Live installation. -<!--l. 793--><p class="indent"> To start, you mount the CD or DVD, with Rock Ridge extensions enabled. The exact command to do +<!--l. 792--><p class="indent"> To start, you mount the CD or DVD, with Rock Ridge extensions enabled. The exact command to do this varies from system to system; the following works under Linux, except the name of the device (<span class="ec-lmtt-10">/dev/cdrom</span>, here) may vary. (All our examples will use <span class="ec-lmtt-10">> </span>as the shell prompt; user input is <span class="underline"><span class="ec-lmtt-10">underlined</span></span>.) <div class="alltt"> -<!--l. 793--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 792--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">mount</span> <span class="ec-lmtt-10">-t</span> <span @@ -1510,23 +1508,23 @@ class="ec-lmtt-10">/dev/cdrom</span> <span class="ec-lmtt-10">/mnt/cdrom</span></span> </div> </div> -<!--l. 793--><p class="noindent">Change the current directory to the mount point: <div class="alltt"> -<!--l. 793--><p class="noindent"><div class="obeylines-v"> <span +<!--l. 792--><p class="noindent">Change the current directory to the mount point: <div class="alltt"> +<!--l. 792--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">> </span><span class="underline"><span class="ec-lmtt-10">cd</span> <span class="ec-lmtt-10">/mnt/cdrom</span></span> </div> </div> -<!--l. 793--><p class="noindent">Under Mac OS X, the directory is typically under <span +<!--l. 792--><p class="noindent">Under Mac OS X, the directory is typically under <span class="ec-lmtt-10">/Volumes</span>, and the media will be mounted automatically. -<!--l. 795--><p class="indent"> Run the installation script <span +<!--l. 794--><p class="indent"> Run the installation script <span class="ec-lmtt-10">install-pkg.sh </span>(not <span class="ec-lmtt-10">install-tl.sh</span>, which is intended for complete installations only): <div class="alltt"> -<!--l. 798--><p class="noindent"><div class="obeylines-v"> +<!--l. 797--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1535,8 +1533,8 @@ class="ec-lmtt-10">install-pkg.sh</span> <span class="ec-lmro-10">options</span></span> </div> </div> -<!--l. 802--><p class="indent"> The first set of options controls what gets read: -<!--l. 804--><p class="noindent"> +<!--l. 801--><p class="indent"> The first set of options controls what gets read: +<!--l. 803--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">--package=</span><span @@ -1571,7 +1569,7 @@ class="ec-lmro-10">cddir </span>from which to read the package class="E">E</span>X</span> Live yourself. </dd></dl> -<!--l. 824--><p class="indent"> What actually happens is controlled by the following options. If neither of these are specified, the +<!--l. 823--><p class="indent"> What actually happens is controlled by the following options. If neither of these are specified, the default action is to install the selected files. The main destination tree is found by expanding <span class="ec-lmtt-10">$TEXMFMAIN</span> with <span @@ -1579,7 +1577,7 @@ class="ec-lmss-10">kpsewhich</span>. You can override it by setting either the e class="ec-lmtt-10">TEXMFMAIN </span>or <span class="ec-lmtt-10">TEXMF</span>. -<!--l. 831--><p class="noindent"> +<!--l. 830--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">--listonly</span> </dt><dd @@ -1592,8 +1590,8 @@ class="list">Instead of installing the files into the <span class="TEX">T<span class="E">E</span>X</span> system, make a <span class="ec-lmss-10">tar </span>archive. </dd></dl> -<!--l. 840--><p class="indent"> Additional options: -<!--l. 842--><p class="noindent"> +<!--l. 839--><p class="indent"> Additional options: +<!--l. 841--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">--config</span> </dt><dd @@ -1609,8 +1607,8 @@ class="ec-lmss-10">mktexlsr </span>to rebuild the filename database. class="ec-lmtt-10">--verbose</span> </dt><dd class="list">Give more information as the script runs. </dd></dl> -<!--l. 853--><p class="indent"> Here are some usage examples: -<!--l. 855--><p class="indent"> +<!--l. 852--><p class="indent"> Here are some usage examples: +<!--l. 854--><p class="indent"> <ol class="enumerate1" > <li class="enumerate" value="1" @@ -1618,7 +1616,7 @@ class="list">Give more information as the script runs. id="x1-15002x1"></a>To see the files in the package <span class="ec-lmss-10">fancyhdr </span>without installing it: <div class="alltt"> - <!--l. 860--><p class="noindent"><div class="obeylines-v"> + <!--l. 859--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1641,7 +1639,7 @@ class="ec-lmtt-10">...</span> id="x1-15004x2"></a>Install the <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> package <span class="ec-lmss-10">natbib</span>: <div class="alltt"> - <!--l. 871--><p class="noindent"><div class="obeylines-v"> + <!--l. 870--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1656,7 +1654,7 @@ class="ec-lmtt-10">--package=natbib</span></span> id="x1-15006x3"></a>Install the <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> package <span class="ec-lmss-10">alg </span>without source files or documentation: <div class="alltt"> - <!--l. 877--><p class="noindent"><div class="obeylines-v"> + <!--l. 876--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1672,7 +1670,7 @@ class="ec-lmtt-10">--nodoc</span></span> ><a id="x1-15008x4"></a>Install all the packages in the collection of additional plain <span class="TEX">T<span class="E">E</span>X</span> macros: <div class="alltt"> - <!--l. 885--><p class="noindent"><div class="obeylines-v"> + <!--l. 884--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1688,7 +1686,7 @@ class="ec-lmtt-10">--collection=tex-plainextra</span></span> class="ec-lmss-10">pstricks </span>package to a <span class="ec-lmss-10">tar </span>file in <span class="path"><span class="ec-lmtt-10">/tmp</span></span>: <div class="alltt"> - <!--l. 891--><p class="noindent"><div class="obeylines-v"> + <!--l. 890--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1700,16 +1698,16 @@ class="ec-lmtt-10">--archive=/tmp/pstricks.tar</span></span> </div> </div> </li></ol> -<!--l. 900--><p class="indent"> If in doubt, please ask any local system gurus to help you with problems; for example, the way to +<!--l. 899--><p class="indent"> If in doubt, please ask any local system gurus to help you with problems; for example, the way to mount the <span class="TEX">T<span class="E">E</span>X</span> Live media, which directory or directories to use, and precise details of the changes to your personal initialization files can and do vary from site to site. -<!--l. 904--><p class="noindent"> +<!--l. 903--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">4 </span> <a id="x1-160004"></a>Post-installation</h3> -<!--l. 907--><p class="noindent">After the main installation is done, for any operating system, the remaining steps are to configure the +<!--l. 906--><p class="noindent">After the main installation is done, for any operating system, the remaining steps are to configure the system for your local needs, and perform some basic tests. -<!--l. 911--><p class="indent"> Another sort of post-installation is to acquire packages, fonts, or programs that were not included in +<!--l. 910--><p class="indent"> Another sort of post-installation is to acquire packages, fonts, or programs that were not included in <span class="TEX">T<span class="E">E</span>X</span> Live. The basic idea is to install such additions in the <span class="ec-lmtt-10">TEXMFLOCAL </span>tree (if you installed to @@ -1717,7 +1715,7 @@ disk), or <span class="ec-lmtt-10">TEXMFSYSVAR </span>(if you are running live). See the “Installation directories” option on p. <a href="#x1-140003.2">21<!--tex4ht:ref: text:instdir --></a>. -<!--l. 917--><p class="indent"> Unfortunately, the details can and do vary widely, and so we do not attempt to address them here. +<!--l. 916--><p class="indent"> Unfortunately, the details can and do vary widely, and so we do not attempt to address them here. Here are some external links to descriptions: <ul class="itemize1"> <li class="itemize"><span class="obeylines-h"><a @@ -1736,22 +1734,22 @@ class="ec-lmtt-10">http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5 href="http://www.ctan.org/tex-archive/info/Type1fonts" class="url" ><span class="ec-lmtt-10">http://www.ctan.org/tex-archive/info/Type1fonts</span></a></span> for installation information for fonts in particular.</li></ul> -<!--l. 932--><p class="noindent"> +<!--l. 931--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">4.1 </span> <a id="x1-170004.1"></a>The <span class="ec-lmss-10">texconfig </span>program</h4> -<!--l. 935--><p class="noindent">At any time after installation, you can and should use the program <span +<!--l. 934--><p class="noindent">At any time after installation, you can and should use the program <span class="ec-lmss-10">texconfig </span>to configure the system to fit your local needs. It is installed in the architecture-specific subdirectory <span class="ec-lmtt-10">TEXDIR/bin/</span><span class="ec-lmro-10">arch </span>along with everything else. -<!--l. 940--><p class="indent"> If you run it without arguments, it will enter full-screen mode and allow you to view and change +<!--l. 939--><p class="indent"> If you run it without arguments, it will enter full-screen mode and allow you to view and change options interactively. -<!--l. 943--><p class="indent"> You can also run it with various command-line options. Here are some of the most common (<span class="TEX">T<span +<!--l. 942--><p class="indent"> You can also run it with various command-line options. Here are some of the most common (<span class="TEX">T<span class="E">E</span>X</span> Live is configured for the A4 paper size by default): -<!--l. 946--><p class="noindent"> +<!--l. 945--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">texconfig paper letter</span> </dt><dd @@ -1783,7 +1781,7 @@ class="ec-lmtt-10">texconfig help</span> </dt><dd class="list">Output help information for <span class="ec-lmss-10">texconfig</span>. </dd></dl> -<!--l. 963--><p class="indent"> Of course, <span +<!--l. 962--><p class="indent"> Of course, <span class="ec-lmss-10">texconfig </span>can only support changing a few of the many options and configuration parameters in a <span class="TEX">T<span class="E">E</span>X</span> system. The main configuration file for the base Web2C programs is named @@ -1791,56 +1789,56 @@ class="E">E</span>X</span> system. The main configuration file for the base Web2 class="ec-lmtt-10">texmf.cnf</span>. You can find its location by running ‘<span class="ec-lmtt-10">kpsewhich texmf.cnf</span>’; it contains many comments explaining the default settings and useful alternatives. -<!--l. 970--><p class="indent"> As of 2005, <span -class="ec-lmss-10">texconfig </span>alters files in a user-specific directory, namely <span -class="ec-lmtt-10">$HOME/.texlive2005</span>. If you -install <span class="TEX">T<span +<!--l. 969--><p class="indent"> As of 2005, <span +class="ec-lmss-10">texconfig </span>alters files in a user-specific directory, as in <span +class="ec-lmtt-10">$HOME/.texlive2005</span>. If you install +<span class="TEX">T<span class="E">E</span>X</span> just for yourself, that is unlikely to make a difference. But if you install <span class="TEX">T<span -class="E">E</span>X</span> on a -multi-user system, you will want to change the configuration for the whole system. In this case, run -<span -class="ec-lmss-10">texconfig-sys </span>instead of <span +class="E">E</span>X</span> on a multi-user +system, you will want to change the configuration for the whole system. In this case, run <span +class="ec-lmss-10">texconfig-sys</span> +instead of <span class="ec-lmss-10">texconfig</span>. -<!--l. 977--><p class="indent"> Likewise, the <span +<!--l. 976--><p class="indent"> Likewise, the <span class="ec-lmss-10">updmap </span>and <span class="ec-lmss-10">fmtutil </span>scripts were changed, to work under <span -class="ec-lmtt-10">$HOME/.texlive2005</span>. To alter +class="ec-lmtt-10">$HOME/.texliveYYYY</span>. To alter system directories, use <span class="ec-lmss-10">updmap-sys </span>and <span class="ec-lmss-10">fmtutil-sys</span>. -<!--l. 981--><p class="indent"> In particular, for multi-user systems, you will probably want to pregenerate the standard formats +<!--l. 980--><p class="indent"> In particular, for multi-user systems, you will probably want to pregenerate the standard formats with <span class="ec-lmtt-10">fmtutil-sys –missing</span>. Otherwise, each user will end up with their own formats. -<!--l. 985--><p class="indent"> Also, if you have a personally-modified copy of <span +<!--l. 984--><p class="indent"> Also, if you have a personally-modified copy of <span class="ec-lmtt-10">fmtutil.cnf </span>or <span class="ec-lmtt-10">updmap.cfg</span>, instead of using the ones generated by installation, they must be installed in the tree referenced by the variable <span class="ec-lmtt-10">TEXMFSYSCONFIG</span>. -<!--l. 990--><p class="indent"> The variables specifying the directories altered by these commands are listed in section <a +<!--l. 989--><p class="indent"> The variables specifying the directories altered by these commands are listed in section <a href="#x1-90002.3">2.3<!--tex4ht:ref: sec:texmftrees --></a>, p. <a href="#x1-90002.3">7<!--tex4ht:ref: sec:texmftrees --></a>. You can see the actual directories by running <span class="ec-lmtt-10">texconfig conf</span>, and you can change them by editing <span class="ec-lmtt-10">texmf.cnf</span>. -<!--l. 996--><p class="noindent"> +<!--l. 995--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">4.2 </span> <a id="x1-180004.2"></a>Testing the installation</h4> -<!--l. 999--><p class="noindent">After installing <span class="TEX">T<span +<!--l. 998--><p class="noindent">After installing <span class="TEX">T<span class="E">E</span>X</span> Live as best you can, you naturally want to test it out, so you can start creating beautiful documents and/or fonts. -<!--l. 1002--><p class="indent"> This section gives some basic procedures for testing that the new system is functional. We give Unix +<!--l. 1001--><p class="indent"> This section gives some basic procedures for testing that the new system is functional. We give Unix commands; under Mac OS X and Windows, you’re more likely to run the tests through a graphical interface, but the principles are the same. -<!--l. 1007--><p class="indent"> +<!--l. 1006--><p class="indent"> <ol class="enumerate1" > <li class="enumerate" value="1" ><a id="x1-18002x1"></a>Make sure that you can run the <span class="ec-lmss-10">tex </span>program in the first place: <div class="alltt"> - <!--l. 1012--><p class="noindent"><div class="obeylines-v"> + <!--l. 1011--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1871,7 +1869,7 @@ href="#x1-130003.1">17<!--tex4ht:ref: text:path --></a>. class="E">E</span>X</span></span> file: <div class="alltt"> - <!--l. 1024--><p class="noindent"><div class="obeylines-v"> + <!--l. 1023--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1911,7 +1909,7 @@ href="#x1-610008.2.4">59<!--tex4ht:ref: Debugging --></a>. <li class="enumerate" value="3" ><a id="x1-18006x3"></a>Preview the result online: <div class="alltt"> - <!--l. 1038--><p class="noindent"><div class="obeylines-v"> + <!--l. 1037--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1933,7 +1931,7 @@ class="ec-lmtt-10">display</span>’. <li class="enumerate" value="4" ><a id="x1-18008x4"></a>Create a PostScript file for printing or display: <div class="alltt"> - <!--l. 1049--><p class="noindent"><div class="obeylines-v"> + <!--l. 1048--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1949,7 +1947,7 @@ class="ec-lmtt-10">sample2e.ps</span></span> id="x1-18010x5"></a>Create a PDF file instead of DVI; this processes the <span class="ec-lmtt-10">.tex </span>file and writes PDF directly: <div class="alltt"> - <!--l. 1055--><p class="noindent"><div class="obeylines-v"> + <!--l. 1054--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1963,7 +1961,7 @@ class="ec-lmtt-10">sample2e.tex</span></span> id="x1-18012x6"></a>Preview the PDF file: <div class="alltt"> - <!--l. 1060--><p class="noindent"><div class="obeylines-v"> + <!--l. 1059--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -1990,7 +1988,7 @@ class="ec-lmtt-10">http://www.foolabs.com/xpdf</span></a></span>, <li class="enumerate" value="7" ><a id="x1-18014x7"></a>Other standard test files you may find useful: - <!--l. 1072--><p class="noindent"> + <!--l. 1071--><p class="noindent"> <dl class="list2"><dt class="list"> <span class="ec-lmtt-10">small2e.tex</span> </dt><dd @@ -2019,20 +2017,20 @@ class="ec-lmtt-10">\bye</span>’ to the <span class="ec-lmtt-10">*</span> prompt after ‘<span class="ec-lmtt-10">tex story.tex</span>’.</dd></dl> - <!--l. 1082--><p class="noindent">You can process these in the same way as we did with <span + <!--l. 1081--><p class="noindent">You can process these in the same way as we did with <span class="ec-lmtt-10">sample2e.tex</span>. </li></ol> -<!--l. 1087--><p class="indent"> If you are new to <span class="TEX">T<span +<!--l. 1086--><p class="indent"> If you are new to <span class="TEX">T<span class="E">E</span>X</span>, or otherwise need help with actually constructing <span class="TEX">T<span class="E">E</span>X</span> or <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> documents, please visit <span class="obeylines-h"><a href="http://tug.org/begin.html" class="url" ><span class="ec-lmtt-10">http://tug.org/begin.html</span></a></span> for some introductory resources. -<!--l. 1092--><p class="noindent"> +<!--l. 1091--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">5 </span> <a id="x1-190005"></a>Mac OS X installation</h3> -<!--l. 1095--><p class="noindent">The recommended way to install <span class="TEX">T<span +<!--l. 1094--><p class="noindent">The recommended way to install <span class="TEX">T<span class="E">E</span>X</span> on Mac OS X is from the Mac<span class="TEX">T<span class="E">E</span>X</span> distribution, new in 2005. This is provided on the <span @@ -2045,12 +2043,12 @@ class="E">E</span>X</span> Live, along with many additional applications and documentation. The project web page is <span class="obeylines-h"><a href="http://tug.org/mactex" class="url" ><span class="ec-lmtt-10">http://tug.org/mactex</span></a></span>. -<!--l. 1102--><p class="indent"> If you prefer, installation of <span class="TEX">T<span +<!--l. 1101--><p class="indent"> If you prefer, installation of <span class="TEX">T<span class="E">E</span>X</span> under Mac OS X can also be done directly from <span class="TEX">T<span class="E">E</span>X</span> Live, using the <span class="ec-lmtt-10">install* </span>scripts, as follows. -<!--l. 1105--><p class="indent"> In order to run the installation scripts under Mac OS X, you need to have the <span +<!--l. 1104--><p class="indent"> In order to run the installation scripts under Mac OS X, you need to have the <span class="ec-lmss-10">bash </span>shell installed. If you are running Mac OS X 10.2 or later, you have <span class="ec-lmss-10">bash</span>, and can proceed. If you’re running an earlier @@ -2058,23 +2056,23 @@ Mac OS X version, however, the default shell is <span class="ec-lmss-10">zsh</span>, which won’t work; you’ll need to get <span class="ec-lmss-10">bash </span>from the Internet, or more likely upgrade your system. -<!--l. 1112--><p class="indent"> Once you have <span +<!--l. 1111--><p class="indent"> Once you have <span class="ec-lmss-10">bash</span>, the Unix installation documentation in the previous section can be followed. See section <a href="#x1-120003">3<!--tex4ht:ref: sec:unix-install --></a> on p. <a href="#x1-120003">10<!--tex4ht:ref: sec:unix-install --></a>; Mac OS X-specific notes are included there where needed. -<!--l. 1117--><p class="noindent"> +<!--l. 1116--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">6 </span> <a id="x1-200006"></a>Windows installation</h3> -<!--l. 1120--><p class="noindent">In this release of <span class="TEX">T<span +<!--l. 1119--><p class="noindent">In this release of <span class="TEX">T<span class="E">E</span>X</span> Live, happily, the distribution once again has a native Windows installer, named <span class="ec-lmss-10">tlpmgui.exe</span>. (See section <a href="#x1-70002.1">2.1<!--tex4ht:ref: sec:multiple-dist --></a>, p. <a href="#x1-70002.1">6<!--tex4ht:ref: sec:multiple-dist --></a>, for an explanation of the different distributions.) -<!--l. 1125--><p class="indent"> <span +<!--l. 1124--><p class="indent"> <span class="ec-lmss-10">tlpmgui </span>has essentially the same options as the Unix installer, only done through a GUI interface: selecting schemes, individual collections, installation directories, and so on. Section <a href="#x1-140003.2">3.2<!--tex4ht:ref: sec:unix-install-disk --></a> on p. <a @@ -2083,11 +2081,11 @@ the basic elements. It also allows some post-installation activities such as add updating the filename database and building formats. Moreover, <span class="ec-lmss-10">tlpmgui </span>can setup the system for running programs directly from the DVD. -<!--l. 1135--><p class="indent"> For those who like to look underneath the hood, <span +<!--l. 1134--><p class="indent"> For those who like to look underneath the hood, <span class="ec-lmss-10">tlpmgui </span>uses as its “engine” a command-line Windows program named <span class="ec-lmss-10">tlpm</span>. -<!--l. 1138--><p class="indent"> The Windows <span class="TEX">T<span +<!--l. 1137--><p class="indent"> The Windows <span class="TEX">T<span class="E">E</span>X</span> system included in <span class="TEX">T<span class="E">E</span>X</span> Live is based on new binaries borrowed from the XEm<span class="TEX">T<span class="E">E</span>X</span> @@ -2102,10 +2100,10 @@ is similar in usage to the established Unix <span class="ec-lmss-10">xdvi</span>. The documentation can be found in <a href="../../../../texmf/doc/html/windvi/windvi.html" >texmf/doc/html/windvi/windvi.html</a>. -<!--l. 1146--><p class="indent"> <span class="TEX">T<span +<!--l. 1145--><p class="indent"> <span class="TEX">T<span class="E">E</span>X</span> Live can be installed on systems running Windows 98, ME, NT, 2K or XP. Older versions of Windows (3.1x) and MS-DOS are not supported. -<!--l. 1150--><p class="indent"> <span +<!--l. 1149--><p class="indent"> <span class="ec-lmbx-10">Warning: </span>Win9.x users must ensure they have enough environment space before undertaking installation. The <span class="ec-lmss-10">tlpmgui.exe </span>program won’t change the environment size for them. A few @@ -2113,11 +2111,11 @@ environment variables will be created and it is possible you run out of environm <span class="ec-lmtt-10">SHELL=<path>COMMAND.COM /E:4096 /P </span>in the config.sys file in order to increase your environment size. -<!--l. 1157--><p class="noindent"> +<!--l. 1156--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">6.1 </span> <a id="x1-210006.1"></a>Installing <span class="TEX">T<span class="E">E</span>X</span> Live to disk</h4> -<!--l. 1159--><p class="noindent">After inserting the <span class="TEX">T<span +<!--l. 1158--><p class="noindent">After inserting the <span class="TEX">T<span class="E">E</span>X</span> Live CD into the CD drive, autostart should activate <span class="ec-lmss-10">tlpmgui</span>. If it does not, click <span @@ -2133,7 +2131,7 @@ DVD), where <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10"><drive</span><span class="ec-lmtt-10"> letter></span></span></span> is the drive letter with the TeX Live CD (or TeX Collection DVD), and then click OK. -<!--l. 1167--><p class="indent"> The installation window titled <span +<!--l. 1166--><p class="indent"> The installation window titled <span class="ec-lmss-10">TeX Live installation and maintenance utility </span>should open. It contains the following sections: <span class="ec-lmss-10">Main customization</span>, <span @@ -2143,7 +2141,7 @@ class="ec-lmss-10">Select systems</span>, <span class="ec-lmss-10">Directories </span>and <span class="ec-lmss-10">Options</span>. -<!--l. 1172--><p class="indent"> In the <span +<!--l. 1171--><p class="indent"> In the <span class="ec-lmss-10">Directories </span>section the installation drive (directory) next to the <span class="ec-lmss-10">CD/DVD </span>button should be displayed (e.g., <span @@ -2153,7 +2151,7 @@ class="ec-lmtt-10">F:/texlive/ </span>for the DVD), but if it is not, then click class="ec-lmss-10">CD/DVD </span>button and select the CD/DVD drive, with the <span class="TEX">T<span class="E">E</span>X</span> Live CD (or TeX Collection DVD). -<!--l. 1177--><p class="indent"> The directory in which you wish to install the software can be set by clicking the <span +<!--l. 1176--><p class="indent"> The directory in which you wish to install the software can be set by clicking the <span class="ec-lmss-10">TLroot </span>button. This directory will be set as <span class="path"><span class="ec-lmtt-10">TLroot</span></span> environment variable for later usage. The <span class="path"><span @@ -2164,7 +2162,7 @@ class="ec-lmss-10">TEXMFTEMP </span>and <span class="ec-lmss-10">TEXMFCNF </span>buttons will be adjusted automatically and set during installation, but they can also be adjusted manually now to suit special needs. -<!--l. 1185--><p class="indent"> In the <span +<!--l. 1184--><p class="indent"> In the <span class="ec-lmss-10">Select a scheme </span>section the desired <span class="TEX">T<span class="E">E</span>X</span> Live installation scheme should be chosen by clicking the radio button labelled with the installation scheme name (e.g., <span @@ -2172,7 +2170,7 @@ class="ec-lmss-10">scheme-gust</span>). Each scheme is accompanied by an <span class="ec-lmss-10">Info </span>button which, when clicked, displays a short description of the relevant scheme. -<!--l. 1191--><p class="indent"> A scheme is a large set of files targeted at some kind of usage. There are generic schemes for +<!--l. 1190--><p class="indent"> A scheme is a large set of files targeted at some kind of usage. There are generic schemes for basic, medium and full installations. The remaining ones are either targeted at certain LUGs (i.e., what GUST or GUTenberg propose for their members) or application targeted (e.g., @@ -2188,7 +2186,7 @@ class="ec-lmss-10">Select </span>button labelled <span class="ec-lmss-10">Standard collections</span>, additional collections like Metapost, Omega or documentation in different languages can be selected. -<!--l. 1202--><p class="indent"> <span +<!--l. 1201--><p class="indent"> <span class="ec-lmbx-10">Note: </span>The <span class="ec-lmss-10">Ghostscript</span>, <span class="ec-lmss-10">Perl </span>and <span @@ -2198,33 +2196,33 @@ required by many important tools. The <span class="obeylines-h"><span class="ver class="ec-lmtt-10">PERL5LIB</span></span></span> and <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10">GS_LIB</span></span></span> environment variables will be set too. -<!--l. 1208--><p class="indent"> Next, clicking the <span +<!--l. 1207--><p class="indent"> Next, clicking the <span class="ec-lmss-10">Select </span>button labelled <span class="ec-lmss-10">Language Collections </span>in the <span class="ec-lmss-10">Main customization </span>section opens the <span class="ec-lmss-10">Language collections </span>window in which the installation language can be chosen by ticking the box next to the language. -<!--l. 1213--><p class="indent"> Next, click the <span +<!--l. 1212--><p class="indent"> Next, click the <span class="ec-lmss-10">Install </span>button in the <span class="ec-lmss-10">Install </span>section to start the installation proper process. -<!--l. 1216--><p class="indent"> The <span class="TEX">T<span +<!--l. 1215--><p class="indent"> The <span class="TEX">T<span class="E">E</span>X</span> Live system needs some post-processing steps (format files generation, ls-R databases generation, environment variables, etc.). All these operations are done there, some of them can be lengthy. So please wait until you see a statement about the successfully finished installation. -<!--l. 1221--><p class="indent"> The shortcut for <span +<!--l. 1220--><p class="indent"> The shortcut for <span class="ec-lmss-10">tlpmgui </span>will be added to the <span class="ec-lmss-10">Start</span><span class="cmsy-10">→</span><span class="ec-lmss-10">Programs</span><span class="cmsy-10">→</span><span -class="ec-lmss-10">TeXLive2005 </span>menu. -<!--l. 1224--><p class="indent"> If it is needed (Win9x/WinME), you will be asked to reboot your computer. -<!--l. 1226--><p class="noindent"> +class="ec-lmss-10">TeXLive2006 </span>menu. +<!--l. 1223--><p class="indent"> If it is needed (Win9x/WinME), you will be asked to reboot your computer. +<!--l. 1225--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">6.2 </span> <a id="x1-220006.2"></a>Support packages for Windows</h4> -<!--l. 1229--><p class="noindent">To be complete, a <span class="TEX">T<span +<!--l. 1228--><p class="noindent">To be complete, a <span class="TEX">T<span class="E">E</span>X</span> Live installation needs support packages that are not commonly found on a Windows machine. Many scripts are written using the Perl language. Some important tools require the Ghostscript PostScript interpreter to render or to convert files. A graphic file toolbox is also needed in @@ -2232,7 +2230,7 @@ some cases. Last but not least, a <span class="TEX">T<span class="E">E</span>X</span>-oriented editor makes it easy to type in your <span class="TEX">T<span class="E">E</span>X</span> files. -<!--l. 1236--><p class="indent"> All these tools are quite easy to find for Windows, but in order to try to make your life even easier, +<!--l. 1235--><p class="indent"> All these tools are quite easy to find for Windows, but in order to try to make your life even easier, we have put such a set of tools on <span class="TEX">T<span class="E">E</span>X</span> Live: <ul class="itemize1"> @@ -2244,15 +2242,15 @@ class="ec-lmss-10">Perl </span>5.8, sufficient to run all the <span class="TEX"> class="E">E</span>X</span> Live Perl scripts. </li> <li class="itemize">win-tools is a set of small programs (bzip2, gzip, jpeg2ps and tiff2png)</li></ul> -<!--l. 1250--><p class="indent"> These packages are borrowed from the XEm<span class="TEX">T<span +<!--l. 1249--><p class="indent"> These packages are borrowed from the XEm<span class="TEX">T<span class="E">E</span>X</span> distribution (the successor of fp<span class="TEX">T<span class="E">E</span>X</span>). -<!--l. 1253--><p class="indent"> Perl and Ghostscript are installed by default; you may explicitly deselect them during installation if +<!--l. 1252--><p class="indent"> Perl and Ghostscript are installed by default; you may explicitly deselect them during installation if you already have them. -<!--l. 1256--><p class="indent"> If you don’t want to install this bundle, then you are on your own to install the required tools to +<!--l. 1255--><p class="indent"> If you don’t want to install this bundle, then you are on your own to install the required tools to complete your <span class="TEX">T<span class="E">E</span>X</span> Live system. Here is a list of places to get those tools: -<!--l. 1260--><p class="indent"> +<!--l. 1259--><p class="indent"> <dl class="description"><dt class="description"> <span class="ec-lmbx-10">Ghostscript</span> </dt><dd @@ -2336,7 +2334,7 @@ class="ec-lmss-10">SciTE </span>is available from <span class="obeylines-h"><a href="http://www.scintilla.org/SciTE.html" class="url" ><span class="ec-lmtt-10">http://www.scintilla.org/SciTE.html</span></a></span></li></ul> </dd></dl> -<!--l. 1288--><p class="indent"> You might want to install other tools that are not +<!--l. 1287--><p class="indent"> You might want to install other tools that are not free<span class="footnote-mark"><a href="#fn1x0" id="fn1x0-bk"><sup>1</sup></a></span><a id="x1-22001f1"></a> @@ -2349,22 +2347,22 @@ class="ec-lmss-10">GSView </span>is available from <span class="obeylines-h"><a href="http://www.cs.wisc.edu/~ghost/gsview/" class="url" ><span class="ec-lmtt-10">http://www.cs.wisc.edu/~ghost/gsview/</span></a></span> or any CTAN site. -<!--l. 1296--><p class="noindent"> +<!--l. 1295--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">7 </span> <a id="x1-230007"></a>Maintenance of the installation in Windows</h3> -<!--l. 1298--><p class="noindent">If you have TeX Live installed, you can use <span -class="ec-lmss-10">tlpmgui </span>again for modyfying and maintaining your +<!--l. 1297--><p class="noindent">If you have TeX Live installed, you can use <span +class="ec-lmss-10">tlpmgui </span>again for modifying and maintaining your installation. -<!--l. 1301--><p class="noindent"> +<!--l. 1300--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.1 </span> <a id="x1-240007.1"></a>Adding/removing packages</h4> -<!--l. 1303--><p class="noindent">As the <span +<!--l. 1302--><p class="noindent">As the <span class="ec-lmss-10">tlpmgui </span>shortcut is available in the <span class="ec-lmss-10">Start</span><span class="cmsy-10">→</span><span class="ec-lmss-10">Programs</span><span class="cmsy-10">→</span><span -class="ec-lmss-10">TeXLive2005 </span>menu, start it from here. The +class="ec-lmss-10">TeXLive2006 </span>menu, start it from here. The maintenance window titled <span class="ec-lmss-10">TeX Live installation and maintenance utility </span>shows. It contains several tabs: <span @@ -2372,7 +2370,7 @@ class="ec-lmss-10">Add Packages</span>, <span class="ec-lmss-10">Remove packages</span>, <span class="ec-lmss-10">Manage installation</span>, <span class="ec-lmss-10">Remove installation</span>. -<!--l. 1309--><p class="indent"> Click the tab labelled <span +<!--l. 1308--><p class="indent"> Click the tab labelled <span class="ec-lmss-10">Add packages </span>or <span class="ec-lmss-10">Remove packages </span>to enter the relevant functionality and then: @@ -2390,11 +2388,11 @@ class="ec-lmss-10">Buttons </span>section to display or refresh in the <span class="ec-lmss-10">Select packages</span> <span class="ec-lmss-10">to... </span>section the list of packages to install or remove. - <!--l. 1319--><p class="noindent">When adding packages, the list of installed packages is compared to the list of packages + <!--l. 1318--><p class="noindent">When adding packages, the list of installed packages is compared to the list of packages available from your CD/DVD. Only packages not already installed are displayed. It is up to you to select which packages you want to install. - <!--l. 1324--><p class="noindent">When removing individual packages, only a list of installed packages will be displayed. - <!--l. 1327--><p class="noindent">Please note that for both <span + <!--l. 1323--><p class="noindent">When removing individual packages, only a list of installed packages will be displayed. + <!--l. 1326--><p class="noindent">Please note that for both <span class="ec-lmss-10">Add packages </span>and <span class="ec-lmss-10">Remove packages </span>the collections are listed first. </li> @@ -2411,15 +2409,15 @@ class="ec-lmss-10">Info about the selected item </span>section. To select severa class="ec-lmss-10">Install </span>or <span class="ec-lmss-10">Remove </span>button in the <span class="ec-lmss-10">Buttons </span>section to perform the appropriate action.</li></ul> -<!--l. 1342--><p class="noindent"> +<!--l. 1341--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.2 </span> <a id="x1-250007.2"></a>Configuring and other management tasks</h4> -<!--l. 1344--><p class="noindent">The functions available in the tab labelled <span +<!--l. 1343--><p class="noindent">The functions available in the tab labelled <span class="ec-lmss-10">Manage the installation </span>are helpful in performing actions needed when you want to add support for a language which was not selected during the installation, or add/regenerate a format which was not selected during the installation or was modified after the installation. -<!--l. 1350--><p class="indent"> The following actions can be performed: +<!--l. 1349--><p class="indent"> The following actions can be performed: <ul class="itemize1"> <li class="itemize">Refresh the <span class="ec-lmtt-10">ls-R </span>database @@ -2434,36 +2432,36 @@ class="ec-lmtt-10">fmtutil.cnf</span> </li> <li class="itemize">Edit <span class="ec-lmtt-10">updmap.cfg</span></li></ul> -<!--l. 1360--><p class="indent"> Note: you can close the Edit... window with the <span +<!--l. 1359--><p class="indent"> Note: you can close the Edit... window with the <span class="ec-lmss-10">Cancel </span>or <span class="ec-lmss-10">Done </span>button; the latter will start rebuilding the format files (or the fontmap files if you have edited <span class="ec-lmtt-10">updmap.cfg</span>), followed by a <span class="ec-lmtt-10">ls-R</span> database files refresh. -<!--l. 1365--><p class="indent"> For more information about the configuration see section <a +<!--l. 1364--><p class="indent"> For more information about the configuration see section <a href="#x1-310007.8">7.8<!--tex4ht:ref: sec:persconf --></a>, p. <a href="#x1-310007.8">36<!--tex4ht:ref: sec:persconf --></a>. -<!--l. 1368--><p class="noindent"> +<!--l. 1367--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.3 </span> <a id="x1-260007.3"></a>Uninstalling <span class="TEX">T<span class="E">E</span>X</span> Live</h4> -<!--l. 1370--><p class="noindent">The tab labelled <span +<!--l. 1369--><p class="noindent">The tab labelled <span class="ec-lmss-10">Remove the TeX Live installation </span>opens a window which contains functionality not worth describing and we do not know who would need it and what it is for...:-) -<!--l. 1374--><p class="indent"> Anyway, if you have the <span class="path"><span +<!--l. 1373--><p class="indent"> Anyway, if you have the <span class="path"><span class="ec-lmtt-10">texmf-local</span></span> directory for your local additions, the removal procedure will not wipe it out or delete things in it. The <span class="path"><span class="ec-lmtt-10">setup-win32</span></span> directory containing <span class="ec-lmss-10">tlpmgui </span>and related files will not be deleted. You will have to do some manual cleanup to actually remove them. -<!--l. 1379--><p class="noindent"> +<!--l. 1378--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.4 </span> <a id="x1-270007.4"></a>Adding your own packages to the installation</h4> -<!--l. 1381--><p class="noindent">First, whatever changes you make, <span +<!--l. 1380--><p class="noindent">First, whatever changes you make, <span class="ec-lmbx-10">do not forget to rebuild the ls-R database files</span>. Otherwise, your new files will not be found. You can do this either via the <span class="ec-lmss-10">tlpmgui </span>run and selection of the @@ -2471,26 +2469,26 @@ appropriate action from the <span class="ec-lmss-10">Manage the installation </span>tab, or manually running the <span class="ec-lmtt-10">mktexlsr</span> command. -<!--l. 1387--><p class="indent"> If you want to add files that are not provided by the <span class="TEX">T<span +<!--l. 1386--><p class="indent"> If you want to add files that are not provided by the <span class="TEX">T<span class="E">E</span>X</span> Live distribution, it is recommended to put them in the <span class="path"><span class="ec-lmtt-10">$TEXMFLOCAL</span></span> directory. This way, you will be safe against upgrades of the <span class="TEX">T<span class="E">E</span>X</span> Live software. -<!--l. 1391--><p class="indent"> The directory pointed to by <span class="path"><span +<!--l. 1390--><p class="indent"> The directory pointed to by <span class="path"><span class="ec-lmtt-10">$TEXMFLOCAL</span></span> is initially empty. If, for example, you want to add the support file for the Maple symbolic computation program, you will have to put the style files in: <br class="newline"><span class="path"><span -class="ec-lmtt-10">c:\TeXLive2005\texmf-local\tex\latex\maple\</span></span> +class="ec-lmtt-10">c:\TeXLive2006\texmf-local\tex\latex\maple\</span></span> <br class="newline">and the documentation files in: <br class="newline"><span class="path"><span -class="ec-lmtt-10">c:\TeXLive2005\texmf-local\doc\latex\maple\</span></span> -<!--l. 1397--><p class="noindent"> +class="ec-lmtt-10">c:\TeXLive2006\texmf-local\doc\latex\maple\</span></span> +<!--l. 1396--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.5 </span> <a id="x1-280007.5"></a>Running <span class="ec-lmtt-10">tlmp.exe </span>from the command line</h4> -<!--l. 1398--><p class="noindent">The <span +<!--l. 1397--><p class="noindent">The <span class="ec-lmss-10">tlpm.exe </span>program which is used as engine by <span class="ec-lmss-10">tlpmgui </span>has a number of other useful options. You can get the list by running: @@ -2505,13 +2503,13 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> -<!--l. 1402--><p class="nopar"> -<!--l. 1404--><p class="indent"> More information and examples of use can be found in <span class="path"><span +<!--l. 1401--><p class="nopar"> +<!--l. 1403--><p class="indent"> More information and examples of use can be found in <span class="path"><span class="ec-lmtt-10">tlpm.readme</span></span>. -<!--l. 1406--><p class="noindent"> +<!--l. 1405--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.6 </span> <a id="x1-290007.6"></a>Network installation</h4> -<!--l. 1408--><p class="noindent">Kpathsea knows about UNC names, so you can use them to get your TEXMF tree from the network. +<!--l. 1407--><p class="noindent">Kpathsea knows about UNC names, so you can use them to get your TEXMF tree from the network. But there is better than this. All the support files and configuration files, everything except the files in the <span class="path"><span class="ec-lmtt-10">bin/win32</span></span> are shareable with a te<span class="TEX">T<span @@ -2534,11 +2532,11 @@ class="ec-lmtt-10">$TEXMFMAIN</span></span> to the class="ec-lmtt-10">texmf</span></span> tree that will be accessed remotely. Set <span class="path"><span class="ec-lmtt-10">$TEXMFVAR</span></span> to be a local directory which will hold local configuration files and on-the-fly generated files.</li></ul> -<!--l. 1427--><p class="noindent"> +<!--l. 1426--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.7 </span> <a id="x1-300007.7"></a>What’s different in Windows?</h4> -<!--l. 1429--><p class="noindent">The Windows version of Web2C has some specific features that should be pointed out. -<!--l. 1432--><p class="indent"> +<!--l. 1428--><p class="noindent">The Windows version of Web2C has some specific features that should be pointed out. +<!--l. 1431--><p class="indent"> <dl class="description"><dt class="description"> <span class="ec-lmbx-10">Kpathsea</span> </dt><dd @@ -2568,14 +2566,14 @@ class="ec-lmtt-10">README</span></span> files). class="ec-lmtt-10">-multiple-occurrences</span></span> with 2 other options for including or excluding any filename that match some pattern (you can request for several patterns). - <!--l. 1456--><p class="noindent">The <span + <!--l. 1455--><p class="noindent">The <span class="ec-lmss-10">kpsecheck </span>command will also report the status of shared memory: in use or not used. That might be useful to know because if the status reported is ‘<span class="ec-lmtt-10">in use</span>’, that means one or several processes are working, and the effect of any <span class="ec-lmss-10">mktexlsr </span>command will be delayed until the next time where no Kpathsea linked process will be running. - <!--l. 1463--><p class="noindent">Last, this same command will report about the location it thinks Ghostscript can be found. + <!--l. 1462--><p class="noindent">Last, this same command will report about the location it thinks Ghostscript can be found. Under Win32, for many programs, it is easier to use the Ghostscript dll, and find it by using the Ghostscript registry key than to change the <span class="path"><span class="ec-lmtt-10">PATH</span></span>, which has a limited length anyway. @@ -2605,17 +2603,17 @@ class="ec-lmtt-10">-time-statistics</span></span> print statistics about the job the <span class="path"><span class="ec-lmtt-10">time</span></span> command is not usually available to Windows users.</li></ul> </dd></dl> -<!--l. 1488--><p class="noindent"> +<!--l. 1487--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.8 </span> <a id="x1-310007.8"></a>Personal configurations</h4> -<!--l. 1491--><p class="noindent"> +<!--l. 1490--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.8.1 </span> <a id="x1-320007.8.1"></a>Dvips</h5> -<!--l. 1493--><p class="noindent">The configuration file for dvips can be found in +<!--l. 1492--><p class="noindent">The configuration file for dvips can be found in <br class="newline"><span class="obeylines-h"><span class="verb"><span -class="ec-lmtt-10">C:\TeXLive2005\texmf-var\dvips\config\config.ps</span></span></span> +class="ec-lmtt-10">C:\TeXLive2006\texmf-var\dvips\config\config.ps</span></span></span> <br class="newline">You may open it with any editor and change some parameters: -<!--l. 1499--><p class="indent"> +<!--l. 1498--><p class="indent"> <dl class="description"><dt class="description"> <span class="ec-lmbx-10">fonts</span> </dt><dd @@ -2647,7 +2645,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> - <!--l. 1512--><p class="nopar"> + <!--l. 1511--><p class="nopar"> </dd><dt class="description"> <span class="ec-lmbx-10">paper</span> </dt><dd @@ -2661,23 +2659,23 @@ class="ec-lmtt-10">@</span>. Move the appropriate lines so that this section beg <br class="newline">  @+ %%BeginPaperSize: Letter <br class="newline">  @+ letter <br class="newline">  @+ %%EndPaperSize</dd></dl> -<!--l. 1525--><p class="indent"> The current <span class="TEX">T<span +<!--l. 1524--><p class="indent"> The current <span class="TEX">T<span class="E">E</span>X</span> Live distribution implements the procedure of making always up-to-date fontmaps files for Dvips and Pdftex. This is done by the <span class="ec-lmss-10">updmap </span>program during installation, as well as during any font package addition. If you add new packages by hand, edit the file <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10">updmap.cfg</span></span></span> in <span class="path"><span class="ec-lmtt-10">$TEXMFVAR/web2c</span></span>. -<!--l. 1531--><p class="noindent"> +<!--l. 1530--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.8.2 </span> <a id="x1-330007.8.2"></a>PdfTeX</h5> -<!--l. 1533--><p class="noindent">If you use the program pdflatex to write PDF format directly, and you are using US letter-size paper, +<!--l. 1532--><p class="noindent">If you use the program pdflatex to write PDF format directly, and you are using US letter-size paper, edit the file <span class="obeylines-h"><span class="verb"><span -class="ec-lmtt-10">C:\TeXLive2005\texmf-var\tex\generic\config\pdftexconfig.tex</span></span></span> and change +class="ec-lmtt-10">C:\TeXLive2006\texmf-var\tex\generic\config\pdftexconfig.tex</span></span></span> and change ‘<span class="ec-lmtt-10">\pdfpagewidth</span>’ and ‘<span class="ec-lmtt-10">\pdfpageheight</span>’. These entries should read: <div class="alltt"> -<!--l. 1538--><p class="noindent"><div class="obeylines-v"> +<!--l. 1537--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">\pdfpagewidth=8.5</span><span class="ec-lmtt-10"> true</span><span @@ -2688,44 +2686,44 @@ class="ec-lmtt-10"> true</span><span class="ec-lmtt-10"> in</span> </div> </div> Save the file and exit the editor. -<!--l. 1544--><p class="noindent"> +<!--l. 1543--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.8.3 </span> <a id="x1-340007.8.3"></a>GSView</h5> -<!--l. 1545--><p class="noindent">GSView is now distributed under the Aladdin License, and therefore is no longer included in <span class="TEX">T<span +<!--l. 1544--><p class="noindent">GSView is now distributed under the Aladdin License, and therefore is no longer included in <span class="TEX">T<span class="E">E</span>X</span> Live. -<!--l. 1548--><p class="indent"> If you may want to change the page size to US letter size. If so, open GSView from the <span +<!--l. 1547--><p class="indent"> If you may want to change the page size to US letter size. If so, open GSView from the <span class="ec-lmss-10">Start </span>menu, and select <span class="ec-lmss-10">Media</span><span class="cmsy-10">→</span><span class="ec-lmss-10">Letter</span>. -<!--l. 1551--><p class="indent"> Also, there are menu settings that are supposed to give you the most readable screen image. On +<!--l. 1550--><p class="indent"> Also, there are menu settings that are supposed to give you the most readable screen image. On <span class="ec-lmss-10">Media</span><span class="cmsy-10">→</span><span class="ec-lmss-10">Display Settings</span>, set both <span class="ec-lmtt-10">Text Alpha </span>and <span class="ec-lmtt-10">Graphics Alpha </span>to 4 bits. -<!--l. 1555--><p class="indent"> Note that the installation process has set all <span +<!--l. 1554--><p class="indent"> Note that the installation process has set all <span class="ec-lmtt-10">.ps </span>and <span class="ec-lmtt-10">.eps </span>files to automatically open with <span class="ec-lmss-10">GSView</span>. -<!--l. 1558--><p class="indent"> For printing instructions, see section <a +<!--l. 1557--><p class="indent"> For printing instructions, see section <a href="#x1-370007.10">7.10<!--tex4ht:ref: printing --></a> below. -<!--l. 1560--><p class="noindent"> +<!--l. 1559--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.8.4 </span> <a id="x1-350007.8.4"></a>WinDvi</h5> -<!--l. 1563--><p class="noindent">The <span +<!--l. 1562--><p class="noindent">The <span class="ec-lmtt-10">tlpmgui.exe </span>program takes care of associating the files with the <span class="ec-lmtt-10">.dvi </span>extension with <span class="ec-lmtt-10">Windvi</span>, but it doesn’t make an icon on the desktop, so please do it yourself. -<!--l. 1567--><p class="indent"> Open <span +<!--l. 1566--><p class="indent"> Open <span class="ec-lmss-10">windvi </span>by clicking an icon or from the command line. -<!--l. 1569--><p class="indent"> You can set it for US letter-size paper by going to <span +<!--l. 1568--><p class="indent"> You can set it for US letter-size paper by going to <span class="ec-lmss-10">View</span><span class="cmsy-10">→</span><span class="ec-lmss-10">Options</span><span @@ -2736,11 +2734,11 @@ class="ec-lmtt-10">"</span></span></span> x class="ec-lmtt-10">"</span></span></span>) (and then <span class="ec-lmtt-10">OK</span>. Exit <span class="ec-lmss-10">windvi</span>. -<!--l. 1573--><p class="indent"> You can change other parameters from there as well, such as the ability to execute system commands +<!--l. 1572--><p class="indent"> You can change other parameters from there as well, such as the ability to execute system commands specified by the document (disabled by default for security reasons). Also, the first time you view any .dvi file, you may find the magnification too large. Zoom out until you get an appropriate size. -<!--l. 1579--><p class="indent"> All configuration settings for <span +<!--l. 1578--><p class="indent"> All configuration settings for <span class="ec-lmss-10">windvi </span>are stored in a file named <span class="path"><span class="ec-lmtt-10">windvi.cnf</span></span> file. You can find it by running this command at the prompt: @@ -2755,20 +2753,20 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> -<!--l. 1584--><p class="nopar"> -<!--l. 1586--><p class="indent"> Should you have problems with <span +<!--l. 1583--><p class="nopar"> +<!--l. 1585--><p class="indent"> Should you have problems with <span class="ec-lmss-10">windvi</span>, please remove the configuration file and test your problem against a vanilla configuration. -<!--l. 1589--><p class="noindent"> +<!--l. 1588--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.9 </span> <a id="x1-360007.9"></a>Testing</h4> -<!--l. 1591--><p class="noindent">For generic verification procedures, see section <a +<!--l. 1590--><p class="noindent">For generic verification procedures, see section <a href="#x1-180004.2">4.2<!--tex4ht:ref: sec:test-install --></a> (p. <a href="#x1-180004.2">27<!--tex4ht:ref: sec:test-install --></a>). This section describes Windows-specific tests. -<!--l. 1595--><p class="indent"> Open the file <span class="obeylines-h"><span class="verb"><span +<!--l. 1594--><p class="indent"> Open the file <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10">sample2e.tex</span></span></span> in your editor (Xemacs, WinShell), found in <span class="path"><span -class="ec-lmtt-10">C:\TeXLive2005\texmf-dist\tex\latex\base</span></span>. The <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span +class="ec-lmtt-10">C:\TeXLive2006\texmf-dist\tex\latex\base</span></span>. The <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> source should appear on the screen. Process it by clicking on the <span class="ec-lmss-10">Command</span><span @@ -2780,18 +2778,18 @@ class="ec-lmss-10">Command</span><span class="cmsy-10">→</span><span class="ec-lmss-10">View DVI </span>menu (XEmacs) or Preview (Windvi) icon (WinShell). -<!--l. 1602--><p class="indent"> At first, when you preview files with Windvi, it will create fonts because screen fonts were not +<!--l. 1601--><p class="indent"> At first, when you preview files with Windvi, it will create fonts because screen fonts were not installed. After a while, you will have created most of the fonts you use, and you will rarely see the font-creation window. -<!--l. 1606--><p class="indent"> <span +<!--l. 1605--><p class="indent"> <span class="ec-lmbx-10">Hint for the future: </span>If a <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> run stops because <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> cannot find a file, you can press Ctrl-z to quit. -<!--l. 1610--><p class="noindent"> +<!--l. 1609--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.10 </span> <a id="x1-370007.10"></a>Printing</h4> -<!--l. 1613--><p class="noindent">It is possible to print from Windvi. In this case, printing will be done using the Windows unified printer +<!--l. 1612--><p class="noindent">It is possible to print from Windvi. In this case, printing will be done using the Windows unified printer driver. By definition, it is compatible with all printers. However, there is some drawback: it can generate some huge spool files, and some (older) versions of Windows just don’t like them. The advantage is that you can use features like embedding BMP or WMF images. You also need to make @@ -2799,7 +2797,7 @@ sure that the printer parameters are correctly set (subsection <a href="#x1-350007.8.4">7.8.4<!--tex4ht:ref: sub:windvi --></a>), else you will get scaled printing (printing at 600dpi on a 300dpi printer will give you only one quadrant of your page). -<!--l. 1623--><p class="indent"> Printing is faster and more reliable if you run <span +<!--l. 1622--><p class="indent"> Printing is faster and more reliable if you run <span class="ec-lmss-10">dvips </span>to make a <span class="ec-lmtt-10">.ps </span>file and then print from <span class="ec-lmss-10">GSView</span>. In @@ -2809,7 +2807,7 @@ class="ec-lmss-10">File</span><span class="cmsy-10">→</span><span class="ec-lmss-10">Print...</span>. A <span class="ec-lmss-10">Print </span>window will appear. -<!--l. 1628--><p class="indent"> If you are using a PostScript printer, <span +<!--l. 1627--><p class="indent"> If you are using a PostScript printer, <span class="ec-lmri-10">be sure to select </span><span class="ec-lmsso-10">PostScript Printer</span>. This is done in the <span class="ec-lmss-10">Print</span> @@ -2819,7 +2817,7 @@ class="ec-lmss-10">Print </span>window. You can then select any of the printers previously installed. If you fail to check the box for <span class="ec-lmtt-10">PostScript Printer</span>, printing will not work. -<!--l. 1634--><p class="indent"> If you will be using your own non-PostScript printer, select <span +<!--l. 1633--><p class="indent"> If you will be using your own non-PostScript printer, select <span class="ec-lmss-10">Ghostscript device </span>in the <span class="ec-lmss-10">Print Method</span> box, then click on the button to the right labelled <span @@ -2830,18 +2828,18 @@ class="ec-lmtt-10">PostScript Printer </span>is <span class="ec-lmri-10">not </span>selected, then select your printer type from the <span class="ec-lmss-10">Device </span>list.) -<!--l. 1641--><p class="noindent"> +<!--l. 1640--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.11 </span> <a id="x1-380007.11"></a>Tips and tricks for Win32</h4> -<!--l. 1643--><p class="noindent"> +<!--l. 1642--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.11.1 </span> <a id="x1-390007.11.1"></a>Different flavors of Win32</h5> -<!--l. 1645--><p class="noindent">What we call Win32 is not an operating system by itself. It is a large set of functions (around 12,000 in +<!--l. 1644--><p class="noindent">What we call Win32 is not an operating system by itself. It is a large set of functions (around 12,000 in the header files of the Microsoft SDK) that you can use to write programs for different operating systems of the Windows family. -<!--l. 1650--><p class="indent"> Windows comes in different flavors: +<!--l. 1649--><p class="indent"> Windows comes in different flavors: <ul class="itemize1"> <li class="itemize">Win95, Win98 and WinME, which <span class="ec-lmri-10">are not true multitasking, multithreading </span>environments. @@ -2859,7 +2857,7 @@ class="ec-lmtt-10">MS-DOS 7.0</span>’ (at least for the old versions of Wi </li> <li class="itemize">Windows XP, which comes with Personal and Pro flavors. This is the last step in merging both lines of products (Win9x based and NT based). XP is based on NT.</li></ul> -<!--l. 1669--><p class="indent"> Win9x are able to run 32 bits programs and 16 bits programs concurrently. But the operating +<!--l. 1668--><p class="indent"> Win9x are able to run 32 bits programs and 16 bits programs concurrently. But the operating system by itself is not entirely written in 32 bits mode, and does not support memory protection: 16bits applications can overwrite parts of the operating system memory! Some parts of the system like the GDI (Graphical Device Interface) manage limited resources like bitmaps, fonts, pens and so on for the @@ -2867,24 +2865,24 @@ set of all programs that run concurrently. All the bitmaps headers available at time can’t amount for more than 64kB. This explains the performance tool and the fact that you can put your system on his knees by making intensive use of graphic objects for example. -<!--l. 1680--><p class="indent"> NT, 2K and XP do not suffer from these limitations, and neither from other Win9x limitations. They +<!--l. 1679--><p class="indent"> NT, 2K and XP do not suffer from these limitations, and neither from other Win9x limitations. They are true multitasking environments, with protected memory. They are much more responsive than Win9x because of better memory management, better file system and so on. -<!--l. 1685--><p class="noindent"> +<!--l. 1684--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.11.2 </span> <a id="x1-400007.11.2"></a>Command line prompt</h5> -<!--l. 1687--><p class="noindent">You may wonder, “Why would I need to use a command line prompt when I have Windows?” -<!--l. 1690--><p class="indent"> Good question. The problem is of very general nature. Not all operations can be done easily using +<!--l. 1686--><p class="noindent">You may wonder, “Why would I need to use a command line prompt when I have Windows?” +<!--l. 1689--><p class="indent"> Good question. The problem is of very general nature. Not all operations can be done easily using only a GUI. Command line gives you programming power — assuming a clever command interpreter. -<!--l. 1694--><p class="indent"> But the problem here is more fundamental: <span class="TEX">T<span +<!--l. 1693--><p class="indent"> But the problem here is more fundamental: <span class="TEX">T<span class="E">E</span>X</span> is <span class="ec-lmri-10">a batch </span>tool. Not an interactive one. <span class="TEX">T<span class="E">E</span>X</span> needs to compute the best layout for each page, resolve cross-references and so on. This can be done only by a global processing of the document. It is not (yet) a task that can be done interactively. -<!--l. 1700--><p class="indent"> This means that you should use <span class="TEX">T<span +<!--l. 1699--><p class="indent"> This means that you should use <span class="TEX">T<span class="E">E</span>X</span> from a command line. In fact the situation is not so bad. There is an advantage to write command line tools for complex processing: they are better debugged, because they are independent of any GUI problems, and GUI tools can be designed to interface to the command @@ -2893,9 +2891,9 @@ class="E">E</span>X</span>, where you will mostly interact with it through a GUI editor. -<!--l. 1708--><p class="indent"> However, you may need to use the command line prompt in a number of situations. One is when you +<!--l. 1707--><p class="indent"> However, you may need to use the command line prompt in a number of situations. One is when you are having difficulties and want to debug your setup. -<!--l. 1712--><p class="indent"> +<!--l. 1711--><p class="indent"> <dl class="description"><dt class="description"> <span class="ec-lmbx-10">Win9x</span> </dt><dd @@ -2925,11 +2923,11 @@ class="ec-lmtt-10">cmd.exe</span></span>, which is the name of the brand new command interpreter for NT (thus, it is untrue to call this a <span class="ec-lmri-10">DOS</span> box!).</dd></dl> -<!--l. 1725--><p class="indent"> These locations may change across different Windows versions. -<!--l. 1727--><p class="noindent"> +<!--l. 1724--><p class="indent"> These locations may change across different Windows versions. +<!--l. 1726--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.11.3 </span> <a id="x1-410007.11.3"></a>Path separators</h5> -<!--l. 1729--><p class="noindent">The Win32 API understands both <span class="path"><span +<!--l. 1728--><p class="noindent">The Win32 API understands both <span class="path"><span class="ec-lmtt-10">/</span></span> and <span class="path"><span class="ec-lmtt-10">\</span></span> characters as PATH separators. But the command interpreters do not! So whenever a path name is used programmatically, you can use both separators, @@ -2938,14 +2936,14 @@ class="ec-lmtt-10">\</span></span> as path separator. The reason is compatibility: the command processor used ‘<span class="ec-lmtt-10">/</span>’ to introduce arguments to commands. -<!--l. 1736--><p class="indent"> All this to say: do not be surprised to read path names written using the Unix convention; fp<span class="TEX">T<span +<!--l. 1735--><p class="indent"> All this to say: do not be surprised to read path names written using the Unix convention; fp<span class="TEX">T<span class="E">E</span>X</span> is a port of Web2C, and aims to be compatible across platforms. For this reason, all the configuration files that need to specify path names use the Unix convention. -<!--l. 1741--><p class="noindent"> +<!--l. 1740--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.11.4 </span> <a id="x1-420007.11.4"></a>File systems</h5> -<!--l. 1744--><p class="noindent">The worst feature of Win9x with regard to <span class="TEX">T<span +<!--l. 1743--><p class="noindent">The worst feature of Win9x with regard to <span class="TEX">T<span class="E">E</span>X</span> is probably the so-called FAT file system. <span class="TEX">T<span class="E">E</span>X</span> uses very many small files, with size around 1–3kB. The FAT file system is old, and predates by decades the @@ -2957,19 +2955,19 @@ class="ec-lmri-10">any</span> file on a huge partition. It means that <span class="TEX">T<span class="E">E</span>X</span> will use much more disk space than it actually needs. -<!--l. 1753--><p class="indent"> The other, more modern, file systems available, FAT32 and NTFS, do not have this drawback. They +<!--l. 1752--><p class="indent"> The other, more modern, file systems available, FAT32 and NTFS, do not have this drawback. They manage clusters of 4kB only. (You can lower the limit to 512 bytes on NTFS.) -<!--l. 1757--><p class="noindent"> +<!--l. 1756--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.11.5 </span> <a id="x1-430007.11.5"></a>How to add some directory to your PATH</h5> -<!--l. 1759--><p class="noindent">There are pairs of variables and values which behave much like global variables inside your programs. +<!--l. 1758--><p class="noindent">There are pairs of variables and values which behave much like global variables inside your programs. The set of those variables is called the environment. Each program is initialized with a copy of the environment when it is run. It can request and change the value of any variable. The changes happen in the copy of the environment, and is not at all propagated to the other running programs. -<!--l. 1767--><p class="indent"> Your PATH is a special environment variable used to search for programs you want to run. There is a +<!--l. 1766--><p class="indent"> Your PATH is a special environment variable used to search for programs you want to run. There is a different procedure to change it for Win9x, WinME and NT/2K/XP: -<!--l. 1771--><p class="indent"> +<!--l. 1770--><p class="indent"> <dl class="description"><dt class="description"> @@ -2988,11 +2986,11 @@ class="verbatim"><tr class="verbatim"><td class="verbatim"><div class="verbatim"> <div class="fancyvrb" id="fancyvrb4"> <a - id="x1-43002r1"></a>  PATH=c:\windows;c:\windows\system;c:\TeXLive2005\bin\win32 + id="x1-43002r1"></a>  PATH=c:\windows;c:\windows\system;c:\TeXLive2006\bin\win32 </div> </div> </td></tr></table> - <!--l. 1778--><p class="nopar"> + <!--l. 1777--><p class="nopar"> </dd><dt class="description"> <span class="ec-lmbx-10">Windows ME</span> </dt><dd @@ -3021,7 +3019,7 @@ class="ec-lmss-10">Environment Variables </span>among the dialog boxes. Now class="ec-lmtt-10">PATH </span>for all users, you will have to contact your system administrator or be the system administrator yourself — in the latter case you should know what you are doing. - <!--l. 1797--><p class="noindent">If there is already a <span + <!--l. 1796--><p class="noindent">If there is already a <span class="ec-lmtt-10">PATH </span>setting for your user account, left click on <span class="ec-lmtt-10">PATH</span>. In the field <span @@ -3030,7 +3028,7 @@ class="ec-lmtt-10">PATH </span>while the field Value shows the current setting o class="ec-lmtt-10">PATH </span>as a list of directories separated by <span class="path"><span class="ec-lmtt-10">;</span></span>. Add the directory where the executables are located (e.g. <span class="path"><span -class="ec-lmtt-10">c:\TeXLive2005\bin\win32</span></span>). If there isn’t a <span +class="ec-lmtt-10">c:\TeXLive2006\bin\win32</span></span>). If there isn’t a <span class="ec-lmtt-10">PATH </span>variable for your user account, simply click in the field Variable and type in <span class="ec-lmtt-10">PATH</span>, click in the field <span @@ -3041,7 +3039,7 @@ class="ec-lmss-10">Ok</span>, otherwise the changes to <span class="ec-lmtt-10">PATH </span>won’t apply to your system. Be careful when changing the environment settings.</dd></dl> -<!--l. 1811--><p class="indent"> The best way to be sure that a variable has been properly set is to open a console and +<!--l. 1810--><p class="indent"> The best way to be sure that a variable has been properly set is to open a console and type: @@ -3054,27 +3052,27 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> -<!--l. 1815--><p class="nopar">which should return the corresponding value. -<!--l. 1818--><p class="noindent"> +<!--l. 1814--><p class="nopar">which should return the corresponding value. +<!--l. 1817--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.11.6 </span> <a id="x1-440007.11.6"></a><span class="TEX">T<span class="E">E</span>X</span> engines</h5> -<!--l. 1820--><p class="noindent">If you have a look at the Web2C documentation, you will read that all the various <span class="TEX">T<span +<!--l. 1819--><p class="noindent">If you have a look at the Web2C documentation, you will read that all the various <span class="TEX">T<span class="E">E</span>X</span> derived programs use the same base engine. For example, <span class="path"><span class="ec-lmtt-10">tex.exe</span></span> and <span class="path"><span class="ec-lmtt-10">latex.exe</span></span> are exact copies of the same program, but each one will use a different format file, based on its calling name. -<!--l. 1826--><p class="indent"> Under Unix, this feature is implemented through <span +<!--l. 1825--><p class="indent"> Under Unix, this feature is implemented through <span class="ec-lmri-10">symbolic links</span>. It saves up a bit of disk space, because some engines are used with many different format files. -<!--l. 1830--><p class="indent"> The Win32 API does not know about file links. So to save up almost the same amount of memory, all +<!--l. 1829--><p class="indent"> The Win32 API does not know about file links. So to save up almost the same amount of memory, all the <span class="TEX">T<span class="E">E</span>X</span> base engines have been put in DLLs (<span class="ec-lmri-10">Dynamic Linked Library</span>). This means that you will have the following layout: <div class="alltt"> -<!--l. 1834--><p class="noindent"><div class="obeylines-v"> +<!--l. 1833--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">18/09/2005</span><span class="ec-lmtt-10"> </span><span @@ -3147,13 +3145,13 @@ class="ec-lmtt-10">tl90pdfetex.dll</span></span>. The same trick has been used f class="ec-lmtt-10">mktex*.exe</span></span> family of programs which are linked to the <span class="path"><span class="ec-lmtt-10">mktex.dll</span></span> library. -<!--l. 1844--><p class="indent"> In fact, a generic tool called <span class="path"><span +<!--l. 1843--><p class="indent"> In fact, a generic tool called <span class="path"><span class="ec-lmtt-10">irun.exe</span></span> is provided to build the equivalent of Unix hard links for executable files only under Win32. -<!--l. 1847--><p class="noindent"> +<!--l. 1846--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">7.12 </span> <a id="x1-450007.12"></a>In case of problems</h4> -<!--l. 1850--><p class="noindent"> +<!--l. 1849--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.12.1 </span> <a id="x1-460007.12.1"></a>What to do if <span class="ec-lmtt-10">latex </span>does not find your files?</h5> @@ -3176,7 +3174,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> - <!--l. 1863--><p class="nopar">You can also set the debug level: + <!--l. 1862--><p class="nopar">You can also set the debug level: <table width="100%" @@ -3188,8 +3186,8 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> - <!--l. 1867--><p class="nopar"> - <!--l. 1869--><p class="noindent">If you want to redirect stderr to stdout, which is not possible Windows, then do: + <!--l. 1866--><p class="nopar"> + <!--l. 1868--><p class="noindent">If you want to redirect stderr to stdout, which is not possible Windows, then do: <table width="100%" @@ -3201,7 +3199,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> - <!--l. 1873--><p class="nopar">This way you can capture both stdout and stderr in the same file. + <!--l. 1872--><p class="nopar">This way you can capture both stdout and stderr in the same file. </li> <li class="itemize">Assuming the installation has been done in <span class="path"><span class="ec-lmtt-10">c:/TeX</span></span>, check the following values: @@ -3264,11 +3262,11 @@ class="E">E</span>X</span> and friends should work. If it is not the case, you w class="ec-lmtt-10">-debug=n</span></span> option from <span class="path"><span class="ec-lmtt-10">kpsewhich</span></span>, and check back all the values. Try to identify and report the problem.</li></ul> -<!--l. 1903--><p class="noindent"> +<!--l. 1902--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">7.12.2 </span> <a id="x1-470007.12.2"></a>What to do if your setup still does not work as expected?</h5> -<!--l. 1905--><p class="noindent">Here are several questions to investigate: -<!--l. 1907--><p class="indent"> +<!--l. 1904--><p class="noindent">Here are several questions to investigate: +<!--l. 1906--><p class="indent"> <ol class="enumerate1" > <li class="enumerate" value="1" ><a @@ -3280,7 +3278,7 @@ class="ec-lmtt-10">PATH</span></span>? ><a id="x1-47004x2"></a>Is the <span class="path"><span class="ec-lmtt-10">TEXMFCNF</span></span> variable correctly set to <span class="path"><span -class="ec-lmtt-10">c:/TeXLive2005/texmf-var/web2c</span></span> (default +class="ec-lmtt-10">c:/TeXLive2006/texmf-var/web2c</span></span> (default value)? </li> <li class="enumerate" value="3" @@ -3302,34 +3300,34 @@ class="ec-lmtt-10">http://tug.org/texlive/</span></a></span>? (Unlikely, but it hurt to check.) </li></ol> -<!--l. 1926--><p class="indent"> The <span class="TEX">T<span +<!--l. 1925--><p class="indent"> The <span class="TEX">T<span class="E">E</span>X</span> Live software consists of hundreds of programs and tens of thousands of files, all from varying sources. So it is quite difficult to predict all possible causes for problems. Nevertheless, we will do our best to help you. (See section <a href="#x1-50001.2">1.2<!--tex4ht:ref: sec:help --></a>, p. <a href="#x1-50001.2">5<!--tex4ht:ref: sec:help --></a>.) -<!--l. 1932--><p class="noindent"> +<!--l. 1931--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">8 </span> <a id="x1-480008"></a>A user’s guide to Web2C</h3> -<!--l. 1934--><p class="noindent">Web2C is an integrated collection of <span class="TEX">T<span +<!--l. 1933--><p class="noindent">Web2C is an integrated collection of <span class="TEX">T<span class="E">E</span>X</span>-related programs: <span class="TEX">T<span class="E">E</span>X</span> itself, Metafont, MetaPost, BibTeX, etc. It is the heart of <span class="TEX">T<span class="E">E</span>X</span> Live. -<!--l. 1937--><p class="indent"> A bit of history: The original implementation was by Tomas Rokicki who, in 1987, developed a first +<!--l. 1936--><p class="indent"> A bit of history: The original implementation was by Tomas Rokicki who, in 1987, developed a first <span class="TEX">T<span class="E">E</span>X</span>-to-C system based on change files under Unix, which were primarily the original work of Howard Trickey and Pavel Curtis. Tim Morgan became the maintainer of the system, and during this period the name changed to Web-to-C. In 1990, Karl Berry took over the work, assisted by dozens of additional contributors, and in 1997 he handed the baton to Olaf Weber. -<!--l. 1945--><p class="indent"> The Web2C system runs on Unix, 32-bit Windows systems, Mac OS X, and other operating systems. +<!--l. 1944--><p class="indent"> The Web2C system runs on Unix, 32-bit Windows systems, Mac OS X, and other operating systems. It uses Knuth’s original sources for <span class="TEX">T<span class="E">E</span>X</span> and other basic programs written in <span class="ec-lmtt-10">web </span>and translates them into C source code. The core <span class="TEX">T<span class="E">E</span>X</span> programs are: -<!--l. 1950--><p class="indent"> +<!--l. 1949--><p class="indent"> <dl class="list1"><dt class="list"> <span class="ec-lmss-10">bibtex</span> </dt><dd @@ -3436,10 +3434,10 @@ class="ec-lmss-10">weave</span> </dt><dd class="list"><span class="ec-lmtt-10">web </span>to <span class="TEX">T<span class="E">E</span>X</span>.</dd></dl> -<!--l. 1978--><p class="noindent">The precise functions and syntax of these programs are described in the documentation of the individual +<!--l. 1977--><p class="noindent">The precise functions and syntax of these programs are described in the documentation of the individual packages and of Web2C itself. However, knowing a few principles governing the whole family of programs will help you take advantage of your Web2C installation. -<!--l. 1983--><p class="indent"> All programs honor these standard GNU options: +<!--l. 1982--><p class="indent"> All programs honor these standard GNU options: <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">--help</span> </dt><dd @@ -3452,7 +3450,7 @@ class="list">print detailed progress report. <span class="ec-lmtt-10">--version</span> </dt><dd class="list">print version information, then exit.</dd></dl> -<!--l. 1990--><p class="indent"> For locating files the Web2C programs use the path searching library Kpathsea. This +<!--l. 1989--><p class="indent"> For locating files the Web2C programs use the path searching library Kpathsea. This library uses a combination of environment variables and a configuration files to optimize searching the (huge) collection of <span class="TEX">T<span class="E">E</span>X</span> files. Web2C can look at more than one directory @@ -3462,13 +3460,13 @@ extensions in two distinct trees. To speed up file searches the root of each tre <span class="ec-lmtt-10">ls-R</span>, containing an entry showing the name and relative pathname for all files under that root. -<!--l. 2000--><p class="noindent"> +<!--l. 1999--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">8.1 </span> <a id="x1-490008.1"></a>Kpathsea path searching</h4> -<!--l. 2002--><p class="noindent">Let us first describe the generic path searching mechanism of the Kpathsea library. +<!--l. 2001--><p class="noindent">Let us first describe the generic path searching mechanism of the Kpathsea library. -<!--l. 2005--><p class="indent"> We call a <span +<!--l. 2004--><p class="indent"> We call a <span class="ec-lmri-10">search path </span>a colon- or semicolon-separated list of <span class="ec-lmri-10">path elements</span>, which are basically directory names. A search path can come from (a combination of) many sources. To look up a file @@ -3478,23 +3476,23 @@ class="ec-lmtt-10">.:/dir</span>’, Kpathsea checks each element of the pat class="ec-lmtt-10">./my-file</span>, then <span class="ec-lmtt-10">/dir/my-file</span>, returning the first match (or possibly all matches). -<!--l. 2013--><p class="indent"> In order to adapt optimally to all operating systems’ conventions, on non-Unix systems Kpathsea can +<!--l. 2012--><p class="indent"> In order to adapt optimally to all operating systems’ conventions, on non-Unix systems Kpathsea can use filename separators different from colon (‘<span class="ec-lmtt-10">:</span>’) and slash (‘<span class="ec-lmtt-10">/</span>’). -<!--l. 2017--><p class="indent"> To check a particular path element <span +<!--l. 2016--><p class="indent"> To check a particular path element <span class="ec-lmro-10">p</span>, Kpathsea first checks if a prebuilt database (see “Filename database” on page <a href="#x1-570008.2">55<!--tex4ht:ref: Filename-database --></a>) applies to <span class="ec-lmro-10">p</span>, i.e., if the database is in a directory that is a prefix of <span class="ec-lmro-10">p</span>. If so, the path specification is matched against the contents of the database. -<!--l. 2023--><p class="indent"> If the database does not exist, or does not apply to this path element, or contains no matches, the +<!--l. 2022--><p class="indent"> If the database does not exist, or does not apply to this path element, or contains no matches, the filesystem is searched (if this was not forbidden by a specification starting with ‘<span class="ec-lmtt-10">!!</span>’ and if the file being searched for must exist). Kpathsea constructs the list of directories that correspond to this path element, and then checks in each for the file being sought. -<!--l. 2030--><p class="indent"> The “file must exist” condition comes into play with ‘<span +<!--l. 2029--><p class="indent"> The “file must exist” condition comes into play with ‘<span class="ec-lmtt-10">.vf</span>’ files and input files read by <span class="TEX">T<span class="E">E</span>X</span>’s <span class="ec-lmtt-10">\openin</span> @@ -3505,23 +3503,23 @@ class="ec-lmtt-10">ls-R </span>when you install a new ‘<span class="ec-lmtt-10">.vf</span>’ file, it will never be found. Each path element is checked in turn: first the database, then the disk. If a match is found, the search stops and the result is returned. -<!--l. 2039--><p class="indent"> Although the simplest and most common path element is a directory name, Kpathsea supports +<!--l. 2038--><p class="indent"> Although the simplest and most common path element is a directory name, Kpathsea supports additional features in search paths: layered default values, environment variable names, config file values, users’ home directories, and recursive subdirectory searching. Thus, we say that Kpathsea <span class="ec-lmri-10">expands </span>a path element, meaning it transforms all the specifications into basic directory name or names. This is described in the following sections in the same order as it takes place. -<!--l. 2048--><p class="indent"> Note that if the filename being searched for is absolute or explicitly relative, i.e., starts with ‘<span +<!--l. 2047--><p class="indent"> Note that if the filename being searched for is absolute or explicitly relative, i.e., starts with ‘<span class="ec-lmtt-10">/</span>’ or ‘<span class="ec-lmtt-10">./</span>’ or ‘<span class="ec-lmtt-10">../</span>’, Kpathsea simply checks if that file exists. -<!--l. 2062--><p class="noindent"> +<!--l. 2061--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.1.1 </span> <a id="x1-500008.1.1"></a>Path sources</h5> -<!--l. 2065--><p class="noindent">A search path can come from many sources. In the order in which Kpathsea uses them: -<!--l. 2068--><p class="indent"> +<!--l. 2064--><p class="noindent">A search path can come from many sources. In the order in which Kpathsea uses them: +<!--l. 2067--><p class="indent"> <ol class="enumerate1" > <li class="enumerate" value="1" ><a @@ -3550,15 +3548,15 @@ class="ec-lmtt-10">TEXINPUTS=/c:/d</span>’ (see <li class="enumerate" value="4" ><a id="x1-50008x4"></a>The compile-time default.</li></ol> -<!--l. 2081--><p class="noindent">You can see each of these values for a given search path by using the debugging options (see “Debugging +<!--l. 2080--><p class="noindent">You can see each of these values for a given search path by using the debugging options (see “Debugging actions” on page <a href="#x1-610008.2.4">59<!--tex4ht:ref: Debugging --></a>). -<!--l. 2085--><p class="noindent"> +<!--l. 2084--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.1.2 </span> <a id="x1-510008.1.2"></a>Config files</h5> -<!--l. 2088--><p class="noindent">Kpathsea reads <span +<!--l. 2087--><p class="noindent">Kpathsea reads <span class="ec-lmri-10">runtime configuration files </span>named <span class="ec-lmtt-10">texmf.cnf </span>for search path and other definitions. The search path used to look for these files is named <span @@ -3583,7 +3581,7 @@ class="ec-lmtt-10">\ </span>at the end of a line acts as a continuation characte Whitespace at the beginning of continuation lines is not ignored. </li> <li class="itemize">Each remaining line has the form: <div class="alltt"> - <!--l. 2109--><p class="noindent"><div class="obeylines-v"> + <!--l. 2108--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> </span><span @@ -3633,8 +3631,8 @@ class="ec-lmtt-10">texmf.cnf </span>for Unix, MS-DOS and </li> <li class="itemize">All definitions are read before anything is expanded, so variables can be referenced before they are defined.</li></ul> -<!--l. 2134--><p class="noindent">A configuration file fragment illustrating most of these points is shown below: -<!--l. 2138--><p class="indent"> +<!--l. 2133--><p class="noindent">A configuration file fragment illustrating most of these points is shown below: +<!--l. 2137--><p class="indent"> <div class="fancyvrb" id="fancyvrb9"> <a id="x1-51002r1"></a><span @@ -3698,10 +3696,10 @@ class="ec-lmtt-8x-x-87"> .;$TEXMF/{etex,tex}/{eplain,plain,generic;}//</s </div> -<!--l. 2143--><p class="noindent"> +<!--l. 2142--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.1.3 </span> <a id="x1-520008.1.3"></a>Path expansion</h5> -<!--l. 2147--><p class="noindent">Kpathsea recognizes certain special characters and constructions in search paths, similar to those +<!--l. 2146--><p class="noindent">Kpathsea recognizes certain special characters and constructions in search paths, similar to those available in Unix shells. As a general example, the complex path, <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10">~$USER/{foo,bar}//baz</span></span></span>, expands to all subdirectories under directories <span @@ -3712,14 +3710,14 @@ class="ec-lmtt-10">$USER</span>’s home directory that contain a directory class="ec-lmtt-10">baz</span>. These expansions are explained in the sections below. <h5 class="subsubsectionHead"><span class="titlemark">8.1.4 </span> <a id="x1-530008.1.4"></a>Default expansion</h5> -<!--l. 2159--><p class="noindent">If the highest-priority search path (see “Path sources” on page <a +<!--l. 2158--><p class="noindent">If the highest-priority search path (see “Path sources” on page <a href="#x1-500008.1.1">50<!--tex4ht:ref: Path-sources --></a>) contains an <span class="ec-lmri-10">extra colon </span>(i.e., leading, trailing, or doubled), Kpathsea inserts at that point the next-highest-priority search path that is defined. If that inserted path has an extra colon, the same happens with the next highest. For example, given an environment variable setting <div class="alltt"> -<!--l. 2168--><p class="noindent"><div class="obeylines-v"> +<!--l. 2167--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -3731,30 +3729,30 @@ class="ec-lmtt-10">/home/karl:</span></span> class="ec-lmtt-10">TEXINPUTS </span>value from <span class="ec-lmtt-10">texmf.cnf </span>of <div class="alltt"> -<!--l. 2173--><p class="noindent"><div class="obeylines-v"> +<!--l. 2172--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> .:$TEXMF//tex</span> </div> </div> then the final value used for searching will be: <div class="alltt"> -<!--l. 2178--><p class="noindent"><div class="obeylines-v"> +<!--l. 2177--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> /home/karl:.:$TEXMF//tex</span> </div> </div> -<!--l. 2182--><p class="indent"> Since it would be useless to insert the default value in more than one place, Kpathsea changes only +<!--l. 2181--><p class="indent"> Since it would be useless to insert the default value in more than one place, Kpathsea changes only one extra ‘<span class="ec-lmtt-10">:</span>’ and leaves any others in place. It checks first for a leading ‘<span class="ec-lmtt-10">:</span>’, then a trailing ‘<span class="ec-lmtt-10">:</span>’, then a doubled ‘<span class="ec-lmtt-10">:</span>’. -<!--l. 2187--><p class="noindent"> +<!--l. 2186--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.1.5 </span> <a id="x1-540008.1.5"></a>Brace expansion</h5> -<!--l. 2189--><p class="noindent">A useful feature is brace expansion, which means that, for instance, <span class="obeylines-h"><span class="verb"><span +<!--l. 2188--><p class="noindent">A useful feature is brace expansion, which means that, for instance, <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10">v{a,b}w</span></span></span> expands to <span class="obeylines-h"><span class="verb"><span class="ec-lmtt-10">vaw:vbw</span></span></span>. Nesting is allowed. This is used to implement multiple <span class="TEX">T<span @@ -3774,7 +3772,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> -<!--l. 2197--><p class="nopar">Using this you can then write something like +<!--l. 2196--><p class="nopar">Using this you can then write something like <table width="100%" @@ -3786,7 +3784,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> -<!--l. 2201--><p class="nopar">which means that, after looking in the current directory, the <span +<!--l. 2200--><p class="nopar">which means that, after looking in the current directory, the <span class="ec-lmtt-10">$TEXMFHOME/tex</span>, <span class="ec-lmtt-10">$TEXMFLOCAL/tex</span>, <span @@ -3800,17 +3798,17 @@ instance) and the other being continuously updated with new versions as they bec using the <span class="ec-lmtt-10">$TEXMF </span>variable in all definitions, one is sure to always search the up-to-date tree first. -<!--l. 2213--><p class="noindent"> +<!--l. 2212--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.1.6 </span> <a id="x1-550008.1.6"></a>Subdirectory expansion</h5> -<!--l. 2216--><p class="noindent">Two or more consecutive slashes in a path element following a directory <span +<!--l. 2215--><p class="noindent">Two or more consecutive slashes in a path element following a directory <span class="ec-lmro-10">d </span>is replaced by all subdirectories of <span class="ec-lmro-10">d</span>: first those subdirectories directly under <span class="ec-lmro-10">d</span>, then the subsubdirectories under those, and so on. At each level, the order in which the directories are searched is <span class="ec-lmri-10">unspecified</span>. -<!--l. 2222--><p class="indent"> If you specify any filename components after the ‘<span +<!--l. 2221--><p class="indent"> If you specify any filename components after the ‘<span class="ec-lmtt-10">//</span>’, only subdirectories with matching components are included. For example, ‘<span class="ec-lmtt-10">/a//b</span>’ expands into directories <span @@ -3820,15 +3818,15 @@ class="ec-lmtt-10">/a/1/1/b</span>, and so on, but not <span class="ec-lmtt-10">/a/b/c </span>or <span class="ec-lmtt-10">/a/1</span>. -<!--l. 2227--><p class="indent"> Multiple ‘<span +<!--l. 2226--><p class="indent"> Multiple ‘<span class="ec-lmtt-10">//</span>’ constructs in a path are possible, but ‘<span class="ec-lmtt-10">//</span>’ at the beginning of a path is ignored. -<!--l. 2230--><p class="noindent"> +<!--l. 2229--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.1.7 </span> <a id="x1-560008.1.7"></a>List of special characters and their meaning: a summary</h5> -<!--l. 2232--><p class="noindent">The following list summarizes the special characters in Kpathsea configuration files. -<!--l. 2237--><p class="noindent"> +<!--l. 2231--><p class="noindent">The following list summarizes the special characters in Kpathsea configuration files. +<!--l. 2236--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">:</span> </dt><dd @@ -3871,23 +3869,23 @@ class="ec-lmtt-10">!!</span> </dt><dd class="list">Search <span class="ec-lmri-10">only </span>database to locate file, <span class="ec-lmri-10">do not </span>search the disk.</dd></dl> -<!--l. 2253--><p class="noindent"> +<!--l. 2252--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">8.2 </span> <a id="x1-570008.2"></a>Filename databases</h4> -<!--l. 2256--><p class="noindent">Kpathsea goes to some lengths to minimize disk accesses for searches. Nevertheless, at installations with +<!--l. 2255--><p class="noindent">Kpathsea goes to some lengths to minimize disk accesses for searches. Nevertheless, at installations with enough directories, searching each possible directory for a given file can take an excessively long time (this is especially true if many hundreds of font directories have to be traversed.) Therefore, Kpathsea can use an externally-built plain text “database” file named <span class="ec-lmtt-10">ls-R </span>that maps files to directories, thus avoiding the need to exhaustively search the disk. -<!--l. 2264--><p class="indent"> A second database file <span +<!--l. 2263--><p class="indent"> A second database file <span class="ec-lmtt-10">aliases </span>allows you to give additional names to the files listed in <span class="ec-lmtt-10">ls-R</span>. This can be helpful to confirm to DOS 8.3 filename conventions in source files. -<!--l. 2268--><p class="noindent"> +<!--l. 2267--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.2.1 </span> <a id="x1-580008.2.1"></a>The filename database</h5> -<!--l. 2271--><p class="noindent">As explained above, the name of the main filename database must be <span +<!--l. 2270--><p class="noindent">As explained above, the name of the main filename database must be <span class="ec-lmtt-10">ls-R</span>. You can put one at the root of each <span class="TEX">T<span class="E">E</span>X</span> hierarchy in your installation that you wish to be searched (<span @@ -3896,13 +3894,13 @@ default); most sites have only one hierarchy. Kpathsea looks for <span class="ec-lmtt-10">ls-R </span>files along the <span class="ec-lmtt-10">TEXMFDBS</span> path. -<!--l. 2277--><p class="indent"> The recommended way to create and maintain ‘<span +<!--l. 2276--><p class="indent"> The recommended way to create and maintain ‘<span class="ec-lmtt-10">ls-R</span>’ is to run the <span class="ec-lmtt-10">mktexlsr </span>script included with the distribution. It is invoked by the various ‘<span class="ec-lmtt-10">mktex</span>’... scripts. In principle, this script just runs the command <div class="alltt"> -<!--l. 2281--><p class="noindent"><div class="obeylines-v"> +<!--l. 2280--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">cd</span><span class="ec-lmtt-10"> </span><span @@ -3923,15 +3921,15 @@ class="ec-lmtt-10">cron</span>, so that it is automatically updated when the installed files change, such as after installing or updating a <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> package. -<!--l. 2290--><p class="indent"> If a file is not found in the database, by default Kpathsea goes ahead and searches the disk. If a +<!--l. 2289--><p class="indent"> If a file is not found in the database, by default Kpathsea goes ahead and searches the disk. If a particular path element begins with ‘<span class="ec-lmtt-10">!!</span>’, however, <span class="ec-lmri-10">only </span>the database will be searched for that element, never the disk. -<!--l. 2296--><p class="noindent"> +<!--l. 2295--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.2.2 </span> <a id="x1-590008.2.2"></a>kpsewhich: Standalone path searching</h5> -<!--l. 2299--><p class="noindent">The <span +<!--l. 2298--><p class="noindent">The <span class="ec-lmtt-10">kpsewhich </span>program exercises path searching independent of any particular application. This can be useful as a sort of <span class="ec-lmtt-10">find </span>program to locate files in <span class="TEX">T<span @@ -3939,7 +3937,7 @@ class="E">E</span>X</span> hierarchies (this is used heavily in the distributed ‘<span class="ec-lmtt-10">mktex</span>’... scripts). <div class="alltt"> -<!--l. 2304--><p class="noindent"><div class="obeylines-v"> +<!--l. 2303--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -3956,12 +3954,12 @@ class="ec-lmro-10">option </span>start with either ‘<span class="ec-lmtt-10">-</span>’ or ‘<span class="ec-lmtt-10">--</span>’, and any unambiguous abbreviation is accepted. -<!--l. 2310--><p class="indent"> Kpathsea looks up each non-option argument on the command line as a filename, and returns the +<!--l. 2309--><p class="indent"> Kpathsea looks up each non-option argument on the command line as a filename, and returns the first file found. There is no option to return all the files with a particular name (you can run the Unix ‘<span class="ec-lmtt-10">find</span>’ utility for that). -<!--l. 2315--><p class="indent"> The more important options are described next. -<!--l. 2317--><p class="noindent"> +<!--l. 2314--><p class="indent"> The more important options are described next. +<!--l. 2316--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">--dpi=</span><span @@ -4045,14 +4043,14 @@ class="ec-lmro-10">num</span> </dt><dd class="list"> <br class="newline">sets the debugging options to <span class="ec-lmro-10">num</span>.</dd></dl> -<!--l. 2357--><p class="noindent"> +<!--l. 2356--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.2.3 </span> <a id="x1-600008.2.3"></a>Examples of use</h5> -<!--l. 2360--><p class="noindent">Let us now have a look at Kpathsea in action. Here’s a straightforward search: +<!--l. 2359--><p class="noindent">Let us now have a look at Kpathsea in action. Here’s a straightforward search: <div class="alltt"> -<!--l. 2362--><p class="noindent"><div class="obeylines-v"> +<!--l. 2361--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4072,10 +4070,10 @@ class="E">E</span>X</span> source file directories). We find it in the subdirectory <span class="ec-lmtt-10">tex/latex/base </span>below the ‘<span class="ec-lmtt-10">texmf-dist</span>’ <span class="TEX">T<span -class="E">E</span>X</span> Live  directory. +class="E">E</span>X</span> Live directory. Similarly, all of the following are found without problems thanks to their unambiguous suffix. <div class="alltt"> -<!--l. 2372--><p class="noindent"><div class="obeylines-v"> +<!--l. 2371--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4123,10 +4121,10 @@ class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib</span> </div> </div> -<!--l. 2385--><p class="indent"> That last is a BibTeX bibliography database for <span +<!--l. 2384--><p class="indent"> That last is a BibTeX bibliography database for <span class="ec-lmro-10">TUGBoat </span>articles. <div class="alltt"> -<!--l. 2387--><p class="noindent"><div class="obeylines-v"> +<!--l. 2386--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4141,7 +4139,7 @@ in this case since there are no pre-generated Computer Modern ‘<span class="ec-lmtt-10">.pk</span>’ files in <span class="TEX">T<span class="E">E</span>X</span> Live — the Type 1 variants are used by default. <div class="alltt"> -<!--l. 2394--><p class="noindent"><div class="obeylines-v"> +<!--l. 2393--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4153,12 +4151,12 @@ class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk</span> </div> </div> -<!--l. 2401--><p class="indent"> For these fonts (a phonetic alphabet from the University of Washington) we had to generate ‘<span +<!--l. 2400--><p class="indent"> For these fonts (a phonetic alphabet from the University of Washington) we had to generate ‘<span class="ec-lmtt-10">.pk</span>’ files, and since the default Metafont mode on our installation is <span class="ec-lmtt-10">ljfour </span>with a base resolution of 600dpi (dots per inch), this instantiation is returned. <div class="alltt"> -<!--l. 2405--><p class="noindent"><div class="obeylines-v"> +<!--l. 2404--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4175,7 +4173,7 @@ required <span class="ec-lmtt-10">.pk </span>files using the script <span class="ec-lmss-10">mktexpk</span>. -<!--l. 2414--><p class="indent"> Next we turn our attention to <span +<!--l. 2413--><p class="indent"> Next we turn our attention to <span class="ec-lmss-10">dvips</span>’s header and configuration files. We first look at one of the commonly used files, the general prolog <span class="ec-lmtt-10">tex.pro </span>for <span class="TEX">T<span @@ -4190,7 +4188,7 @@ ambiguous we have to specify explicitly which type we are considering (<span class="ec-lmtt-10">dvips config</span>) for the file <span class="ec-lmtt-10">config.ps</span>. <div class="alltt"> -<!--l. 2423--><p class="noindent"><div class="obeylines-v"> +<!--l. 2422--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4222,11 +4220,11 @@ class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map</span> </div> </div> -<!--l. 2432--><p class="indent"> We now take a closer look at the URW Times PostScript support files. The prefix for these in the +<!--l. 2431--><p class="indent"> We now take a closer look at the URW Times PostScript support files. The prefix for these in the standard font naming scheme is ‘<span class="ec-lmtt-10">utm</span>’. The first file we look at is the configuration file, which contains the name of the map file: <div class="alltt"> -<!--l. 2436--><p class="noindent"><div class="obeylines-v"> +<!--l. 2435--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4240,7 +4238,7 @@ class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> /usr/local/texmf-dist/dvips/psnfss/config.utm</span> </div> </div> The contents of that file is <div class="alltt"> -<!--l. 2441--><p class="noindent"><div class="obeylines-v"> +<!--l. 2440--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> p</span><span @@ -4248,7 +4246,7 @@ class="ec-lmtt-10"> +utm.map</span> </div> </div> which points to the file <span class="ec-lmtt-10">utm.map</span>, which we want to locate next. <div class="alltt"> -<!--l. 2446--><p class="noindent"><div class="obeylines-v"> +<!--l. 2445--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4261,7 +4259,7 @@ class="ec-lmtt-10"> /usr/local/texmf-dist/fonts/map/dvips/times/utm.map</ </div> </div> This map file defines the file names of the Type 1 PostScript fonts in the URW collection. Its contents look like (we only show part of the lines): <div class="alltt"> -<!--l. 2453--><p class="noindent"><div class="obeylines-v"> +<!--l. 2452--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">utmb8r</span><span class="ec-lmtt-10"> </span><span @@ -4310,7 +4308,7 @@ class="ec-lmtt-10"> <utmr8a.pfb</span> class="ec-lmtt-10">utmr8a.pfb </span>and find its position in the <span class="ec-lmtt-10">texmf</span> directory tree with a search for Type 1 font files: <div class="alltt"> -<!--l. 2464--><p class="noindent"><div class="obeylines-v"> +<!--l. 2463--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4322,16 +4320,16 @@ class="ec-lmtt-10"> </span><span class="ec-lmtt-10"> /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb</span> </div> </div> -<!--l. 2471--><p class="indent"> It should be evident from these examples how you can easily locate the whereabouts of a given file. +<!--l. 2470--><p class="indent"> It should be evident from these examples how you can easily locate the whereabouts of a given file. This is especially important if you suspect that the wrong version of a file is picked up somehow, since <span class="ec-lmss-10">kpsewhich </span>will show you the first file encountered. -<!--l. 2476--><p class="noindent"> +<!--l. 2475--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">8.2.4 </span> <a id="x1-610008.2.4"></a>Debugging actions</h5> -<!--l. 2479--><p class="noindent">Sometimes it is necessary to investigate how a program resolves file references. To make this practical, +<!--l. 2478--><p class="noindent">Sometimes it is necessary to investigate how a program resolves file references. To make this practical, Kpathsea offers various levels of debugging output: -<!--l. 2483--><p class="noindent"> +<!--l. 2482--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10"> 1</span> </dt><dd @@ -4361,21 +4359,21 @@ class="list">Directory list for each path element (only relevant for searches on <span class="ec-lmtt-10">32</span> </dt><dd class="list">File searches.</dd></dl> -<!--l. 2497--><p class="noindent">A value of <span +<!--l. 2496--><p class="noindent">A value of <span class="ec-lmtt-10">-1 </span>will set all the above options; in practice, this is usually the most convenient. -<!--l. 2500--><p class="indent"> Similarly, with the <span +<!--l. 2499--><p class="indent"> Similarly, with the <span class="ec-lmss-10">dvips </span>program, by setting a combination of debug switches, one can follow in detail where files are being picked up from. Alternatively, when a file is not found, the debug trace shows in which directories the program looks for the given file, so that one can get an indication what the problem is. -<!--l. 2506--><p class="indent"> Generally speaking, as most programs call the Kpathsea library internally, one can select a debug +<!--l. 2505--><p class="indent"> Generally speaking, as most programs call the Kpathsea library internally, one can select a debug option by using the <span class="ec-lmtt-10">KPATHSEA_DEBUG </span>environment variable, and setting it to (a combination of) values as described in the above list. -<!--l. 2511--><p class="indent"> (Note for Windows users: it is not easy to redirect all messages to a file in this system. For diagnostic +<!--l. 2510--><p class="indent"> (Note for Windows users: it is not easy to redirect all messages to a file in this system. For diagnostic purposes you can temporarily <span class="ec-lmtt-10">SET KPATHSEA_DEBUG_OUTPUT=err.log</span>). -<!--l. 2515--><p class="indent"> Let us consider, as an example, a small <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span +<!--l. 2514--><p class="indent"> Let us consider, as an example, a small <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span class="E">E</span>X</span></span> source file, <span class="ec-lmtt-10">hello-world.tex</span>, which contains the following input. @@ -4396,13 +4394,13 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> -<!--l. 2522--><p class="nopar">This little file only uses the font <span +<!--l. 2521--><p class="nopar">This little file only uses the font <span class="ec-lmtt-10">cmr10</span>, so let us look at how <span class="ec-lmss-10">dvips </span>prepares the PostScript file (we want to use the Type 1 version of the Computer Modern fonts, hence the option <span class="ec-lmtt-10">-Pcms</span>). <div class="alltt"> -<!--l. 2526--><p class="noindent"><div class="obeylines-v"> +<!--l. 2525--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4419,7 +4417,7 @@ class="ec-lmss-10">dvips </span>Reference Manual, <a href="../../../../texmf/doc/html/dvips/dvips_toc.html" >texmf/doc/html/dvips/dvips_toc.html</a>). The output (slightly rearranged) appears in Figure <a href="#x1-61031r1">1<!--tex4ht:ref: fig:dvipsdbga --></a>. -<!--l. 2534--><p class="indent"> <a +<!--l. 2533--><p class="indent"> <a id="x1-61031r1"></a><a id="x1-61036r2"></a><a id="x1-61049r3"></a><hr class="float"><div class="float" @@ -4607,7 +4605,7 @@ class="content">Finding the font file</td></tr></table><!--tex4ht:label?: x1-610 </td></tr></table></div><hr class="endfloat" /> -<!--l. 2550--><p class="indent"> <span +<!--l. 2549--><p class="indent"> <span class="ec-lmss-10">dvips </span>starts by locating its working files. First, <span class="ec-lmtt-10">texmf.cnf </span>is found, which gives the definitions of the search paths for the other files, then the file database <span @@ -4629,7 +4627,7 @@ class="ec-lmss-10">dvips </span>command). This file contains the list of the map which define the relation between the <span class="TEX">T<span class="E">E</span>X</span>, PostScript and file system names of the fonts. <div class="alltt"> -<!--l. 2564--><p class="noindent"><div class="obeylines-v"> +<!--l. 2563--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">></span><span class="ec-lmtt-10"> </span><span class="underline"><span @@ -4662,9 +4660,9 @@ class="ec-lmtt-10">psfonts.map</span>, which is always loaded (it contains declarations for commonly used PostScript fonts; see the last part of Section <a href="#x1-600008.2.3">8.2.3<!--tex4ht:ref: SExamplesofuse --></a> for more details about PostScript map file handling). -<!--l. 2577--><p class="indent"> At this point <span +<!--l. 2576--><p class="indent"> At this point <span class="ec-lmss-10">dvips </span>identifies itself to the user: <div class="alltt"> -<!--l. 2578--><p class="noindent"><div class="obeylines-v"> +<!--l. 2577--><p class="noindent"><div class="obeylines-v"> <span class="ec-lmtt-10">This</span><span class="ec-lmtt-10"> is</span><span @@ -4679,7 +4677,7 @@ class="ec-lmtt-10"> (www.radicaleye.com)</span> </div> </div> Then it goes on to look for the prolog file <span class="ec-lmtt-10">texc.pro</span>: <div class="alltt"> -<!--l. 2583--><p class="noindent"><div class="obeylines-v"> +<!--l. 2582--><p class="noindent"><div class="obeylines-v"> <br><span class="ec-lmtt-9">kdebug:start</span><span class="ec-lmtt-9"> search(file=texc.pro,</span><span @@ -4702,13 +4700,13 @@ class="ec-lmtt-9"> =></span><span class="ec-lmtt-9"> /usr/local/texmf/dvips/base/texc.pro</span> </div> </div> -<!--l. 2594--><p class="indent"> After having found the file in question, <span +<!--l. 2593--><p class="indent"> After having found the file in question, <span class="ec-lmss-10">dvips </span>outputs date and time, and informs us that it will generate the file <span class="ec-lmtt-10">hello-world.ps</span>, then that it needs the font file <span class="ec-lmtt-10">cmr10</span>, and that the latter is declared as “resident” (no bitmaps needed): <div class="alltt"> -<!--l. 2599--><p class="noindent"><div class="obeylines-v"> +<!--l. 2598--><p class="noindent"><div class="obeylines-v"> <br><span class="ec-lmtt-9">TeX</span><span class="ec-lmtt-9"> output</span><span @@ -4736,7 +4734,7 @@ class="ec-lmtt-10">cmr10.pfb </span>of the font is located and included in the o file (see last line). <div class="alltt"> -<!--l. 2608--><p class="noindent"><div class="obeylines-v"> +<!--l. 2607--><p class="noindent"><div class="obeylines-v"> <br><span class="ec-lmtt-9">kdebug:start</span><span class="ec-lmtt-9"> search(file=cmr10.tfm,</span><span @@ -4794,13 +4792,13 @@ class="ec-lmtt-9"><cmr10.pfb>[1]</span> </div> <h4 class="subsectionHead"><span class="titlemark">8.3 </span> <a id="x1-620008.3"></a>Runtime options</h4> -<!--l. 2625--><p class="noindent">Another useful feature of Web2C is its possibility to control a number of memory parameters +<!--l. 2624--><p class="noindent">Another useful feature of Web2C is its possibility to control a number of memory parameters (in particular, array sizes) via the runtime file <span class="ec-lmtt-10">texmf.cnf </span>read by Kpathsea. The memory settings can be found in Part 3 of that file in the <span class="TEX">T<span class="E">E</span>X</span> Live distribution. The more important are: -<!--l. 2631--><p class="noindent"> +<!--l. 2630--><p class="noindent"> <dl class="list1"><dt class="list"> <span class="ec-lmtt-10">main_memory</span> </dt><dd @@ -4836,36 +4834,31 @@ class="list">Additional space for the hash table of control sequence names. Appr class="ec-lmtt-10">hash_extra </span>is <span class="ec-lmtt-10">50000</span>.</dd></dl> -<!--l. 2656--><p class="noindent">Of course, this facility is no substitute for truly dynamic arrays and memory allocation, but since these +<!--l. 2655--><p class="noindent">Of course, this facility is no substitute for truly dynamic arrays and memory allocation, but since these are extremely difficult to implement in the present <span class="TEX">T<span class="E">E</span>X</span> source, these runtime parameters provide a practical compromise allowing some flexibility. -<!--l. 2764--><p class="noindent"> +<!--l. 2763--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">9 </span> <a id="x1-630009"></a>Acknowledgements</h3> -<!--l. 2766--><p class="noindent"><span class="TEX">T<span +<!--l. 2765--><p class="noindent"><span class="TEX">T<span class="E">E</span>X</span> Live is a joint effort by virtually all of the <span class="TEX">T<span class="E">E</span>X</span> user groups. This edition of <span class="TEX">T<span class="E">E</span>X</span> Live was overseen by Sebastian Rahtz and Karl Berry. The other principal contributors are listed below. <ul class="itemize1"> - <li class="itemize">The German-speaking <span class="TEX">T<span -class="E">E</span>X</span> Users (DANTE e.V.), who provide the hardware for the - <span class="TEX">T<span -class="E">E</span>X</span> Live source repository; and Rainer Schöpf and Reinhard Zierke who look after it. - DANTE officers Volker Schaa and Klaus Höppner coordinate production with the Lehmann’s - Bookstore (<span class="obeylines-h"><a -href="http://www.lob.de" class="url" ><span -class="ec-lmtt-10">http://www.lob.de</span></a></span>). + <li class="itemize">The English, German, Dutch, and Polish <span class="TEX">T<span +class="E">E</span>X</span> user groups (TUG, DANTE e.V., NTG, + and GUST, respectively), which together provide the necessary technical and administrative + infrastructure. Please join your local user group! </li> - <li class="itemize">The Perforce corporation (<span class="obeylines-h"><a -href="http://www.perforce.com" class="url" ><span -class="ec-lmtt-10">http://www.perforce.com</span></a></span>), for providing a free copy of their - excellent change management system, which we use to manage the <span class="TEX">T<span -class="E">E</span>X</span> Live sources. + <li class="itemize">The CTAN team, which distributes the <span class="TEX">T<span +class="E">E</span>X</span> Live images and provides the common + infrastructure for package updates, upon which <span class="TEX">T<span +class="E">E</span>X</span> Live depends. </li> <li class="itemize">Peter Breitenlohner and the e-<span class="TEX">T<span class="E">E</span>X</span> team for the stable foundation of future <span class="TEX">T<span @@ -4887,23 +4880,48 @@ class="E">E</span>X</span>t format conform to <span class="TEX">T<span class="E">E</span>X</span> Live’s needs. </li> - <li class="itemize">Paweł Jackowski, for the Windows installer <span -class="ec-lmss-10">tlpm</span>, and Tomasz Łuczak, for <span -class="ec-lmss-10">tlpmgui</span>. - </li> <li class="itemize">Hàn Thê´ Thành, Martin Schröder, and the pdf<span class="TEX">T<span class="E">E</span>X</span> team for continuing enhancements of <span class="TEX">T<span class="E">E</span>X</span>’s abilities. </li> + <li class="itemize">Taco Hoekwater, for renewed development efforts on MetaPost and <span class="TEX">T<span +class="E">E</span>X</span> itself. + </li> + <li class="itemize">Paweł Jackowski, for the Windows installer <span +class="ec-lmss-10">tlpm</span>, and Tomasz Łuczak, for <span +class="ec-lmss-10">tlpmgui</span>. + </li> + <li class="itemize">Akira Kakuto, for updated Windows binaries as part of his W32TEX distribution effort (<span class="obeylines-h"><a +href="http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/" class="url" ><span +class="ec-lmtt-10">http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/</span></a></span>). + </li> + <li class="itemize">Jonathan Kew and his employer SIL, for the major new development of Xe<span class="TEX">T<span +class="E">E</span>X</span> and taking + the time and trouble to integrate it in <span class="TEX">T<span +class="E">E</span>X</span> Live. + </li> + <li class="itemize">Reinhard Kotucha, for helping with the massive task of updating packages in <span class="TEX">T<span +class="E">E</span>X</span> Live, as + well as Windows research efforts, the <span +class="ec-lmtt-10">getnonfreefonts </span>script, and more. + </li> <li class="itemize">Petr Olsak, who coordinated and checked all the Czech and Slovak material very carefully. </li> - <li class="itemize">Fabrice Popineau, for the Windows binaries in <span class="TEX">T<span + <li class="itemize">Fabrice Popineau, for the original Windows support in <span class="TEX">T<span class="E">E</span>X</span> Live. </li> + <li class="itemize">Norbert Preining, for helping with the <span class="TEX">T<span +class="E">E</span>X</span> Live infrastructure and package updates, and + coordinating the Debian version of <span class="TEX">T<span +class="E">E</span>X</span> Live (together with Frank Küster), making many + suggestions for improvement along the way. + </li> <li class="itemize">Staszek Wawrykiewicz, the principal tester for all of <span class="TEX">T<span class="E">E</span>X</span> Live, and coordinator of the many major Polish contributions: fonts, Windows installation, and more. + + </li> <li class="itemize">Olaf Weber, for his patient assembly and maintenance of Web2C, upon which all else depends. @@ -4913,7 +4931,7 @@ class="E">E</span>X</span> Live, and coordinator of the many </li> <li class="itemize">Graham Williams, on whose work the catalogue of packages depends. </li></ul> -<!--l. 2823--><p class="indent"> Builders of the binaries: Tigran Aivazian (<span +<!--l. 2841--><p class="indent"> Builders of the binaries: Tigran Aivazian (<span class="ec-lmss-10">x86_64-linux</span>), Manfred Lotz (<span class="ec-lmss-10">i386-freebsd</span>), Fabrice Popineau (<span @@ -4928,20 +4946,19 @@ class="ec-lmss-10">mips-irix</span>), Gerben Wierda (<span class="ec-lmss-10">i386-darwin</span>, <span class="ec-lmss-10">powerpc-darwin</span>). -<!--l. 2834--><p class="indent"> Documentation and translation updates: Karl Berry (English), Daniel Flipo & Fabrice Popineau - +<!--l. 2852--><p class="indent"> Documentation and translation updates: Karl Berry (English), Daniel Flipo & Fabrice Popineau (French), Günter Partosch & Hartmut Henkel (German), Petr Sojka & Jan Busa (Czech/Slovak), Boris Veytsman (Russian), Staszek Wawrykiewicz (Polish). -<!--l. 2842--><p class="indent"> Of course the most important acknowledgement must go to Donald Knuth, first for inventing <span class="TEX">T<span +<!--l. 2860--><p class="indent"> Of course the most important acknowledgement must go to Donald Knuth, first for inventing <span class="TEX">T<span class="E">E</span>X</span>, and then for giving it to the world. -<!--l. 2846--><p class="noindent"> +<!--l. 2864--><p class="noindent"> <h3 class="sectionHead"><span class="titlemark">10 </span> <a id="x1-6400010"></a>Release history</h3> -<!--l. 2849--><p class="noindent"> +<!--l. 2867--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">10.1 </span> <a id="x1-6500010.1"></a>Past</h4> -<!--l. 2851--><p class="noindent">Discussion began in late 1993 when the Dutch <span class="TEX">T<span +<!--l. 2869--><p class="noindent">Discussion began in late 1993 when the Dutch <span class="TEX">T<span class="E">E</span>X</span> Users Group was starting work on its 4All<span class="TEX">T<span class="E">E</span>X</span> CD for MS-DOS users, and it was hoped at that time to issue a single, rational, CD for all systems. This was @@ -4965,7 +4982,7 @@ class="E">E</span>X</span> CD showed that Unix users would benefit from a similarly easy system, and this is the other main strand of <span class="TEX">T<span class="E">E</span>X</span> Live. -<!--l. 2867--><p class="indent"> We first undertook to make a new Unix-based TDS CD in the autumn of 1995, and quickly identified +<!--l. 2885--><p class="indent"> We first undertook to make a new Unix-based TDS CD in the autumn of 1995, and quickly identified Thomas Esser’s te<span class="TEX">T<span class="E">E</span>X</span> as the ideal setup, as it already had multi-platform support and was built with portability across file systems in mind. Thomas agreed to help, and work began seriously at the start of @@ -4983,9 +5000,11 @@ almost all of its features. The 4th edition followed the same pattern, using a n te<span class="TEX">T<span class="E">E</span>X</span>, and a new release of Web2C (7.3). The system now included a complete Windows setup. -<!--l. 2883--><p class="indent"> For the 5th edition (March 2000) many parts of the CD were revised and checked, updating hundreds +<!--l. 2901--><p class="indent"> For the 5th edition (March 2000) many parts of the CD were revised and checked, updating hundreds of packages. Package details were stored in XML files. But the major change for <span class="TEX">T<span class="E">E</span>X</span> Live 5 was that all + + non-free software was removed. Everything in <span class="TEX">T<span class="E">E</span>X</span> Live is now intended to be compatible with the Debian Free Software Guidelines (<span class="obeylines-h"><a @@ -4993,21 +5012,19 @@ href="http://www.debian.org/intro/free" class="url" ><span class="ec-lmtt-10">http://www.debian.org/intro/free</span></a></span>); we have done our best to check the license conditions of all packages, but we would very much appreciate hearing of any mistakes. -<!--l. 2892--><p class="indent"> The 6th edition (July 2001) had much more material updated. The major change was a new install +<!--l. 2910--><p class="indent"> The 6th edition (July 2001) had much more material updated. The major change was a new install concept: the user could select a more exact set of needed collections. Language-related collections were completely reorganized, so selecting any of them installs not only macros, fonts, etc., but also prepares an appropriate <span class="ec-lmtt-10">language.dat</span>. -<!--l. 2898--><p class="indent"> The 7th edition of 2002 had the notable addition of Mac OS X support, and the usual myriad of +<!--l. 2916--><p class="indent"> The 7th edition of 2002 had the notable addition of Mac OS X support, and the usual myriad of updates to all sorts of packages and programs. An important goal was integration of the source back with te<span class="TEX">T<span class="E">E</span>X</span>, to correct the drift apart in versions 5 and 6. -<!--l. 2903--><p class="noindent"> - - +<!--l. 2921--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">10.1.1 </span> <a id="x1-6600010.1.1"></a>2003</h5> -<!--l. 2905--><p class="noindent">In 2003, with the continuing flood of updates and additions, we found that <span class="TEX">T<span +<!--l. 2923--><p class="noindent">In 2003, with the continuing flood of updates and additions, we found that <span class="TEX">T<span class="E">E</span>X</span> Live had grown so large it could no longer be contained on a single CD, so we split it into three different distributions (see section <a @@ -5062,16 +5079,18 @@ class="ec-lmtt-10">texmf/web2c/cp8bit.tcx</span></span></span>. (Future releases <li class="itemize">Finally, since the edition numbers had grown unwieldy, the version is now simply identified by the year: <span class="TEX">T<span class="E">E</span>X</span> Live 2003.</li></ul> -<!--l. 2943--><p class="noindent"> + + +<!--l. 2961--><p class="noindent"> <h5 class="subsubsectionHead"><span class="titlemark">10.1.2 </span> <a id="x1-6700010.1.2"></a>2004</h5> -<!--l. 2945--><p class="noindent">2004 saw many changes: +<!--l. 2963--><p class="noindent">2004 saw many changes: <ul class="itemize1"> <li class="itemize">If you have locally-installed fonts which use their own <span class="ec-lmtt-10">.map </span>or (much less likely) <span class="ec-lmtt-10">.enc </span>support files, you may need to move those support files. - <!--l. 2953--><p class="noindent"><span + <!--l. 2971--><p class="noindent"><span class="ec-lmtt-10">.map </span>files are now searched for in subdirectories of <span class="ec-lmtt-10">fonts/map </span>only (in each <span class="ec-lmtt-10">texmf </span>tree), @@ -5083,10 +5102,9 @@ class="ec-lmtt-10">fonts/enc </span>only, along the <span class="ec-lmtt-10">ENCFONTS </span>path. <span class="ec-lmss-10">updmap </span>will attempt to warn about problematic files. - <!--l. 2960--><p class="noindent">For methods of handling this and other information, please see <span class="obeylines-h"><a + <!--l. 2978--><p class="noindent">For methods of handling this and other information, please see <span class="obeylines-h"><a href="http://tug.org/texlive/mapenc.html" class="url" ><span -class="ec-lmtt-10">http://tug.org/texlive/mapenc.html</span></a></span>. - +class="ec-lmtt-10">http://tug.org/texlive/mapenc.html</span></a></span>. </li> <li class="itemize">The <span class="TEX"><span class="ec-lmss-10">T</span><span @@ -5163,7 +5181,7 @@ class="E">E</span>X</span>t, etc., as well as the e-<span class="TEX">T<span class="E">E</span>X</span> features (<a href="../../../../texmf-dist/doc/etex/base/" >texmf-dist/doc/etex/base/</a>). - <!--l. 3007--><p class="noindent">It also means it’s <span + <!--l. 3025--><p class="noindent">It also means it’s <span class="ec-lmri-10">more important than ever </span>to use the <span class="ec-lmss-10">ifpdf </span>package (works with both plain and <span class="LATEX">L<span class="A">A</span><span class="TEX">T<span @@ -5172,7 +5190,8 @@ class="ec-lmtt-10">\pdfoutput </span>or some other primitive is defined is not a reliable way to determine if PDF output is being generated. We made this backward compatible as best we could this year, but next year, <span class="ec-lmtt-10">\pdfoutput </span>may - be defined even when DVI is being written. + be defined even when DVI is being written. + </li> <li class="itemize">pdf<span class="TEX">T<span class="E">E</span>X</span> (<span class="obeylines-h"><a @@ -5196,8 +5215,7 @@ class="ec-lmtt-10">pdftex.cfg </span>is no longer supported. Any extant <span class="ec-lmtt-10">.fmt </span>files must be redumped when <span class="ec-lmtt-10">pdftexconfig.tex</span> - is changed. - + is changed. </li> <li class="itemize">See the pdf<span class="TEX">T<span class="E">E</span>X</span> manual for more: <a @@ -5223,7 +5241,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> - <!--l. 3041--><p class="nopar">See the Web2C manual for more: <a + <!--l. 3059--><p class="nopar">See the Web2C manual for more: <a href="../../../../texmf/doc/web2c" >texmf/doc/web2c</a>. </li> <li class="itemize">enc<span class="TEX">T<span @@ -5300,10 +5318,10 @@ class="ec-lmss-10">mips-irix</span>, the MIPSpro 7.4 runtimes are </li></ul> -<!--l. 3092--><p class="noindent"> - <h4 class="subsectionHead"><span class="titlemark">10.2 </span> <a - id="x1-6800010.2"></a>Present</h4> -<!--l. 3095--><p class="noindent">2005 saw the usual huge number of updates to packages and programs. The infrastructure stayed +<!--l. 3110--><p class="noindent"> + <h5 class="subsubsectionHead"><span class="titlemark">10.1.3 </span> <a + id="x1-6800010.1.3"></a>2005</h5> +<!--l. 3112--><p class="noindent">2005 saw the usual huge number of updates to packages and programs. The infrastructure stayed relatively stable from 2004, but inevitably there were some changes there as well: <ul class="itemize1"> <li class="itemize">New scripts <span @@ -5365,7 +5383,7 @@ class="verbatim"><div class="verbatim"> </div> </div> </td></tr></table> - <!--l. 3133--><p class="nopar"> + <!--l. 3150--><p class="nopar"> </li> <li class="itemize">The new program <span class="ec-lmss-10">dvipdfmx </span>is included for translation of DVI to PDF; this is an actively @@ -5391,36 +5409,60 @@ class="ec-lmtt-10">TEXMFSYSVAR</span>, respectively. There is also <span class="ec-lmtt-10">TEXMFVAR</span>, which is by default user-specific. See the first point above. </li></ul> -<!--l. 3154--><p class="noindent"> +<!--l. 3172--><p class="noindent"> + <h4 class="subsectionHead"><span class="titlemark">10.2 </span> <a + id="x1-6900010.2"></a>Present</h4> +<!--l. 3175--><p class="noindent">In 2006, the major new addition to <span class="TEX">T<span +class="E">E</span>X</span> Live was the Xe<span class="TEX">T<span +class="E">E</span>X</span> program, available as the <span +class="ec-lmtt-10">xetex </span>and +<span +class="ec-lmtt-10">xelatex </span>programs; see <span class="obeylines-h"><a +href="http://scripts.sil.org/xetex" class="url" ><span +class="ec-lmtt-10">http://scripts.sil.org/xetex</span></a></span>. +<!--l. 3179--><p class="indent"> MetaPost also received a notable update, with more planned for the future (<span class="obeylines-h"><a +href="http://tug.org/metapost/articles" class="url" ><span +class="ec-lmtt-10">http://tug.org/metapost/articles</span></a></span>), likewise pdf<span class="TEX">T<span +class="E">E</span>X</span> (<span class="obeylines-h"><a +href="http://tug.org/applications/pdftex" class="url" ><span +class="ec-lmtt-10">http://tug.org/applications/pdftex</span></a></span>) +<!--l. 3183--><p class="indent"> Of course the year also saw (the usual) hundreds of other updates to packages and programs. As +usual, please check CTAN (<span class="obeylines-h"><a +href="http://www.ctan.org" class="url" ><span +class="ec-lmtt-10">http://www.ctan.org</span></a></span>) for updates. +<!--l. 3187--><p class="indent"> Internally, the source tree is now stored in Subversion, with a standard web interface for viewing the +tree, as linked from our home page. Although not visible in the final distribution, we expect this will +provide a stable development foundation for future years. +<!--l. 3193--><p class="noindent"> <h4 class="subsectionHead"><span class="titlemark">10.3 </span> <a - id="x1-6900010.3"></a>Future</h4> -<!--l. 3156--><p class="noindent"><span class="TEX"><span + id="x1-7000010.3"></a>Future</h4> +<!--l. 3195--><p class="noindent"><span class="TEX"><span class="ec-lmri-10">T</span><span class="E"><span class="ec-lmri-10">E</span></span><span class="ec-lmri-10">X</span></span> <span -class="ec-lmri-10">Live is not perfect! </span>(And never will be.) We intend to continue to release new versions yearly, and -would like to provide more help material, more utilities, more installation programs, and (of course) an +class="ec-lmri-10">Live is not perfect! </span>(And never will be.) We intend to continue to release new versions, and would +like to provide more help material, more utilities, more installation programs, and (of course) an ever-improved and checked tree of macros and fonts. This work is all done by hard-pressed volunteers in their limited spare time, and a great deal remains to be done. If you can help, don’t hesitate to put your name forward! -<!--l. 3164--><p class="indent"> Please send corrections, suggestions, and offers of help to: +<!--l. 3203--><p class="indent"> Please send corrections, suggestions, and offers of help to: <div class="quote"> - <!--l. 3166--><p class="noindent">Sebastian Rahtz  /  7 Stratfield Road  /  Oxford OX2 7BG  /  UK - <br class="newline"><a + <!--l. 3205--><p class="noindent"><a href="mailto:tex-live@tug.org" ><span class="path"><span class="ec-lmtt-10">tex-live@tug.org</span></span></a> <br class="newline"><span class="obeylines-h"><a href="http://tug.org/texlive" class="url" ><span -class="ec-lmtt-10">http://tug.org/texlive</span></a></span></div> -<!--l. 3172--><p class="noindent"><span +class="ec-lmtt-10">http://tug.org/texlive</span></a></span></div> + +<!--l. 3210--><p class="noindent"><span class="ec-lmro-10">Happy </span><span class="TEX"><span class="ec-lmro-10">T</span><span class="E"><span class="ec-lmro-10">E</span></span><span class="ec-lmro-10">X</span></span><span class="ec-lmro-10">ing!</span> - <div class="footnotes"><!--l. 1291--><p class="indent"> <span class="footnote-mark"><a + <div class="footnotes"><!--l. 1290--><p class="indent"> <span class="footnote-mark"><a href="#fn1x0-bk" id="fn1x0"><sup>1</sup></a></span><span class="ec-lmr-8">Not free, that is, in the sense of freedom to modify and redistribute, following free software guidelines. This does</span> <span diff --git a/Master/texmf-doc/doc/english/texlive-en/live.pdf b/Master/texmf-doc/doc/english/texlive-en/live.pdf Binary files differindex 61609909b9b..84208344552 100644 --- a/Master/texmf-doc/doc/english/texlive-en/live.pdf +++ b/Master/texmf-doc/doc/english/texlive-en/live.pdf diff --git a/Master/texmf-doc/source/english/texlive-en/archive/live-2005.tex b/Master/texmf-doc/source/english/texlive-en/archive/live-2005.tex new file mode 100644 index 00000000000..5b525535c63 --- /dev/null +++ b/Master/texmf-doc/source/english/texlive-en/archive/live-2005.tex @@ -0,0 +1,3174 @@ +% $Id: live.tex 1513 2006-02-13 00:22:35Z karl $ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg +\usepackage{tex-live} +\begin{document} + +\title{% + {\huge \textit{The \protect\TL{} Guide}\\\strut} + {\LARGE \textsf{\TK{} 2005}} +} + +\author{Sebastian Rahtz \& Karl Berry, editors \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{October 2005} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +This document describes the main features of the \TL{} software +distribution\Dash \TeX{} and friends for \acro{GNU}/Linux and other Unix +flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is not +especially useful for older Mac or \acro{MS-DOS} systems.) + +\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, +\BibTeX{} and many other programs; an extensive collection of macros, +fonts and documentation; and support for typesetting in many different +scripts from around the world. It is part of the even larger \TK{} +(briefly described below in section~\ref{sec:struct-tl}, +\p.\pageref{sec:struct-tl}). Both are cooperative efforts by the \TeX\ +user groups. + +For newer versions of the packages included here, please check +\acro{CTAN}: \url{http://www.ctan.org}. + +For a brief summary of the major changes in this edition of \TL{}, +see the end of the document, section~\ref{sec:history} +(\p.\pageref{sec:history}). + + +\subsection{Basic usage of \protect\TL{}} +\label{sec:basic} + +You can use \TL{} in three principal ways: + +\begin{enumerate} + +\item You can run \TL{} directly from the \pkgname{live} \DVD +(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). +This takes almost no disk space, and gives you immediate access to +everything in \TL{}. Of course performance will be worse than running +on local disk, but you may well find it useful. + +\item You can install all or part of \TL{} to a local disk, from either +the \DVD\ or the \pkgname{inst} \acro{CD}. This is the most common use +of \TL. You will need (approximately) 100 megabytes for the most +minimal system, and upwards of 1.3 gigabytes for a full system. + +\item You can integrate a particular package or collection into your +existing \TeX{} system, either a \TL{} system you installed +earlier, or a different system. + +\end{enumerate} + +\noindent All of these are described in detail in the \acro{OS}-specific +installation sections following, but here is a quick start: + +\begin{itemize*} + +\item The main installation script for Unix and \MacOSX{} is +\texttt{install-tl.sh}. + +\item The single package installation script is \texttt{install-pkg.sh}. + +\item The installation program for Windows is \texttt{tlpmgui.exe}. +It can be used also for adding or removing the packages. +See section~\ref{sec:win-install} below for more information. + +\end{itemize*} + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and virtually all +serious questions end up getting answered. However, the support is +informal, done by volunteers and casual readers, so it's especially +important that you do your homework before asking. (If you prefer +guaranteed commercial support, you can forego \TL{} completely and +purchase a vendor's system; \url{http://tug.org/interest.html#vendors} +has a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [Getting Started] If you are new to \TeX, the web page +\url{http://tug.org/begin.html} gives a brief introduction to the system. + +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of +answers to all sorts of questions, from the most basic to the most +arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is +available on the Internet through \url{http://www.tex.ac.uk/faq}. +Please check here first. + +\item [\TeX{} Catalogue] If you are looking for a specific package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge collection of all \TeX{}-related items. See +\OnCD{texmf-doc/doc/english/catalogue}, or +\url{http://www.ctan.org/tex-archive/help/Catalogue}. + +\item [\TeX{} Web Resources] The web page +\url{http://tug.org/interest.html} has many \TeX{}-related links, in +particular for numerous books, manuals, and articles on all aspects of +the system. + +\item [support archives] The two principal support forums are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. Their archives have years of past +questions and answers for your searching pleasure, via +\url{http://groups.google.com/groups?group=comp.text.tex} and +\url{http://tug.org/mail-archives/texhax}, respectively. And a general web +search, for example on \url{http://google.com}, never hurts. + +\item [asking questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or to +\email{texhax@tug.org} through email. But before you post, +\emph{please} read this \acro{FAQ} entry on asking questions in such a +way that you're most likely to get an answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TL{} support] If you want to report a bug or have +suggestions or comments on the \TL{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TL{}, you are better off writing to that program's maintainer or +mailing list. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. Welcome to +\TeX{}! + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Structure of \protect\TeX\protect\ Live} +\label{sec:struct-tl} + +This section describes the structure and contents of \TL{} and the +\TK{} of which it is a part. + +\subsection{Multiple distributions: \protect\pkgname{live}, + \protect\pkgname{inst}, + \protect\pkgname{protext}} +\label{sec:multiple-dist} + +Space limitations of \acro{CD-ROM} format have forced us to divide +\TK{} into several distributions, as follows. + +\begin{description} + +\item [live] A complete system on \acro{DVD}; it is too large +for \acro{CD}. It can be run live or installed to disk. It also +includes a snapshot of the \CTAN{} repository, the \pkgname{protext} +distribution for Windows and the Mac\TeX\ distribution for \MacOSX, entirely +independent of \TL{}, as well as assorted other packages in a +\texttt{texmf-extra} directory. + +\CTAN{}, \pkgname{protext}, Mac\TeX, and \texttt{texmf-extra} do not follow +the same copying conditions as \TL{}, so be careful when redistributing or +modifying. + +\item [inst(allable)] A complete system on \CD; in order to make this fit, +the packages and programs are compressed. Therefore, it is not possible +to run \TeX\ directly from the installable \CD, you have to install it +to disk (hence its name). Installation is described in subsequent sections. + +\item [protext] An enhancement of the \MIKTEX\ distribution for Windows, +\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies +installation. It is entirely independent of \TL{}, and has its own +installation instructions. It can be run live, or installed to disk. +The \ProTeXt\ home page is \url{http://tug.org/protext}. + +\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ +and on its own \CD\ (for those who cannot use the \DVD). + +\end{description} + +\noindent You can tell which type of distribution you're in by looking +for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. +This file also contains the \TL{} release date. + +Naturally, each user group chooses what to distribute, at its own +discretion. (\acro{TUG} is sending all three discs above to all of its +members.) + + +\subsection{Top level directories} +\label{sec:tld} + +Here is a brief listing and description of the top level directories in +the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} +hierarchy is in a subdirectory \dirname{texlive2005}, not at the top +level of the disc. + +\smallskip +\begingroup + \renewcommand{\arraystretch}{1.3} % open up interrow spacing +\begin{tabular}{>{\ttfamily}lp{.78\hsize}} +bin & The \TeX{} system programs, arranged by platform. \\ +source & The source of all programs, including the main \Webc{} + \TeX{} and \MF{} distributions. These are stored in a + \cmdname{bzip2}-compressed tar archive. \\ +support & Assorted auxiliary packages and programs. These are + \emph{not} installed automatically. This includes + assorted editors and \TeX\ shells. \\ +texmf & Tree for the programs, along with their support files and + documentation. Does not include \TeX\ formats and packages. + (\texttt{TEXMFMAIN} in the next section.) \\ +texmf-dist & The main tree of formats and packages. + (\texttt{TEXMFDIST} in the next section.) \\ +texmf-doc & Tree for self-contained pure documentation, arranged by + language. \\ +texmf-var & Tree for files automatically generated and stored. + (\texttt{TEXMFSYSVAR} in the next section.) \\ +xemtex & Tree for supporting programs used only in Windows. + These programs generally come pre-installed on Unix systems, or are + at least easy to compile. \\ +\end{tabular} +\endgroup + +\smallskip + +In addition to the directories above, the installation scripts and +\filename{README} files (in various languages) are at the top level of +the distribution. + +The \dirname{texmf-doc} directory contains only documentation, but +it does not contain all the documentation. The documentation for the +programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, +since the programs are in \dirname{texmf}. Similarly, the documentation +for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can +use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any +documentation wherever it's located. The comprehensive links in the +top-level file \OnCD{doc.html} may also be helpful. + + +\subsection{Overview of the predefined texmf trees} +\label{sec:texmftrees} + +This section lists all predefined variables specifying texmf trees used +by the system, and their intended purpose. The command \texttt{texconfig +conf} shows you the values of these variables, so that you can easily +find out how they map to directory names in your installation. + +\begin{ttdescription} +\item [TEXMFMAIN] The tree which holds vital parts of the system + such as helper scripts (e.g., \verb+web2c/mktexdir+), pool files and + other support files. +\item [TEXMFDIST] The tree which holds the main set of macro packages, + fonts, etc., as originally distributed. +\item [TEXMFLOCAL] The tree which administrators can use for system-wide + installation of additional or updated macros, fonts, etc. +\item [TEXMFHOME] The tree which users can use for their own individual + installations of additional or updated macros, fonts, etc. + The expansion of this variable depends on \verb+$HOME+ by default, % $ + which dynamically adjusts for each user to an individual + directory. +\item [TEXMFCONFIG] The tree used by te\TeX's utilities + \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified + configuration data. Under \verb+$HOME+ by default. %$ +\item [TEXMFSYSCONFIG] The tree used by te\TeX's utilities + \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to + store modified configuration data. +\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and + \verb+fmtutil+ to store (cached) runtime data such as format files and + generated map files. Under \verb+$HOME+ by default. %$ +\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, + \verb+updmap-sys+ and \verb+fmtutil-sys+ to store (cached) runtime + data such as format files and generated map files. +\end{ttdescription} + +For more discussion of \texttt{texconfig} and related utilities, please +see section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + + +\subsection{Extensions to \protect\TeX} +\label{sec:tex-extensions} + +\TL{} contains several extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a small but powerful set of new primitives +\label{text:etex} (related to macro expansion, character scanning, +classes of marks, additional debugging features, and more) and the +\TeXXeT{} extensions for bidirectional typesetting. In default mode, +\eTeX{} is 100\% compatible with ordinary \TeX. See +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] writes Acrobat \acro{PDF} format as well as \dvi{}. The +\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' +which turns on all the program features. See +\OnCD{texmf/doc/pdftex/manual/} for the manual, and +\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. + +\item [pdfe\TeX] combines the pdf\TeX\ and \eTeX\ extensions. This is +the default program for all formats except plain \TeX. +See above for documentation. + +\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. +See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. + +\end{description} + + +\subsection{Other notable programs in \protect\TL} + +Here are a few other commonly-used programs included in \TL{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] \dvi{} drive for the HP LaserJet family. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec] Con\TeX{}t and \acro{PDF} processor. + +\item [tex4ht] \TeX{} to \acro{HTML} converter. + +\end{cmddescription} + + +\section{Unix installation} +\label{sec:unix-install} + +As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), +\TL{} has three principal uses: + +\begin{enumerate} +\item Run directly from media. +\item Install to disk. +\item Integrate a particular package or collection into your existing +\TeX{} installation. +\end{enumerate} + +\noindent The following sections describes the Unix-specific procedures +for each of these. + +\ifSingleColumn \begin{figure}[ht]\noindent \fi +\begin{warningbox} +\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) +format, \emph{with} Rock Ridge (and Joliet, for Windows) +extensions. Therefore, in order to take full advantage of the \TK{} +under Unix, your system needs to be able to use the Rock Ridge +extensions. Please consult the documentation for your \cmdname{mount} +command to see how to do this. If you have several different machines +on a local network, you may be able to mount the discs on one which +does support Rock Ridge, and use this with the others. + +\leavevmode\quad Modern systems should be able to use the discs without +problems. If troubles, let us know. The discussion below assumes you +have been able to mount the \CD{}s with full Rock Ridge compatibility. +\end{warningbox} +\ifSingleColumn\end{figure}\fi + + +% +\subsection{Running \protect\TL{} directly from media (Unix)} + +\def\runlive{% text repeated in windows section +It is possible to use the \TeX{} system directly from the \pkgname{live} +\DVD{}, without installing the distribution to disk. (Thus the name +\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} +directly from the other \CD{}s (see section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}). +} + +\def\startinst{% repeated in other subsections +To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions +enabled. The exact command to do this varies from system to system; the +following works under Linux, except the name of the device +(\filename{/dev/cdrom}, here) may vary. (All our examples will use +\texttt{>} as the shell prompt; user input is +\Ucom{\texttt{underlined}}.) +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Change the current directory to the mount point: +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} + +\noindent Under \MacOSX, the directory is typically under +\dirname{/Volumes}, and the media will be mounted automatically. +} + +\def\installtlsh{ +Run the installation script \filename{install-tl.sh}: +\begin{alltt} +> \Ucom{sh install-tl.sh}\\ +Welcome to TeX Live... +\end{alltt} + +\noindent After various greeting messages and a list of the main menu +options, the installation will ask you to enter a command. Do this by +typing the desired character and hitting return; don't type the angle +brackets shown. Either uppercase or lowercase is ok; we'll use +lowercase in our examples. +} + +\runlive +\startinst +\installtlsh + +For running live, our first command will be \Ucom{d} and then the +subcommand \Ucom{1} to set directories. Even in this case, we must +choose a directory on the local disk to place files that the \TeX{} +system itself generates, such as fonts and formats, and also to provide +a place for updated configuration files, if need be. + +We'll use \dirname{/opt/texlive2005} in this example. It's good to +include the year in the name, as these generated files are not +compatible from release to release. (If the default value of +\dirname{/usr/local/texlive/2005} works for you, then you can skip this +step.) + +\begin{alltt} +Enter command: \Ucom{d} +Current directories setup: +<1> TEXDIR: /usr/local/texlive/2005 +... +Enter command: \Ucom{1} +New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2005} +... +Enter command: \Ucom{r} +\end{alltt} + +\noindent Back at the main menu, our second and last command is +\Ucom{r}, to set up for running live off the media without installing +to disk: +\begin{alltt} +Enter command: \Ucom{r} +Preparing destination directories... +... +Welcome to TeX Live! +> +\end{alltt} + +\noindent And we are back at the system prompt, as shown. + +Next, it is necessary to alter two environment variables: +\envname{PATH}, to an architecture-dependent value (so that we can run +the programs), and \envname{TEXMFSYSVAR}, to the value specified above. +See table~\ref{tab:archlist} for a list of the architecture names for +the different systems. + + +\def\textruntexconfig{% +After the main installation has completed, and environment variables +have been set, the last step is to run \cmdname{texconfig} or +\cmdname{texconfig-sys} to customize your installation to your needs. +This is explained in section~\ref{sec:texconfig}, +\p.\pageref{sec:texconfig}. +} +\textruntexconfig + +\begin{table*}[ht] +\caption[Supported system architectures.]{Supported system +architectures.} +\label{tab:archlist} +\begin{tabular}{>{\ttfamily}ll} +alpha-linux & HP Alpha GNU/Linux \\ +%alphaev5-osf4.0d & HP Alphaev5 OSF \\ +%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ +i386-darwin & Intel x86 \MacOSX \\ +i386-freebsd & Intel x86 FreeBSD \\ +i386-linux & Intel x86 GNU/Linux \\ +%i386-openbsd3.3 & Intel x86 OpenBSD \\ +%i386-solaris2.8 & Intel x86 Solaris \\ +mips-irix & SGI IRIX \\ +powerpc-aix & IBM RS/6000 AIX \\ +powerpc-darwin & PowerPC \MacOSX \\ +sparc-linux & Sun Sparc GNU/Linux \\ +sparc-solaris & Sun Sparc Solaris \\ +win32 & Windows (32-bit) \\ +x86\_64-linux & Intel x86 64-bit GNU/Linux \\ +\hline +\end{tabular} +\end{table*} + +\label{text:path} +The syntax for setting the environment variables, and the initialization +file to put them in, depends on the shell you use. If you use a +Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et +al.), put the following into your \filename{$HOME/.profile} file: +\begin{alltt} +PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH +TEXMFSYSVAR=/opt/texlive2005/texmf-var; export TEXMFVAR +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH +setenv TEXMFSYSVAR /opt/texlive2005/texmf-var +\end{alltt} + +\noindent Then log out, log back in, and test your installation +(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). + +\def\textifindoubt{% +If in doubt, please ask any local system gurus to help you with +problems; for example, the way to mount the \TL{} media, which +directory or directories to use, and precise details of the changes to +your personal initialization files can and do vary from site to site. +} +\textifindoubt + + +% +\subsection{Installing \protect\TeX\protect\ Live to disk} +\label{sec:unix-install-disk} + +It is possible, indeed typical, to install the \TL{} distribution to +hard disk. This can be done from either the \pkgname{live} or +\pkgname{inst} distributions. (See section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}, for an explanation of the different +distributions.) + +\startinst +\installtlsh + +Table~\ref{tab:main-menu-options} briefly lists the options in the main +menu. The order in which you select the options makes little +difference, except that \Ucom{i} must be last. It's reasonable to go +through them in the order presented here. + +% apparently here.sty [H] doesn't support table*. +\begin{table}[H] +\caption{Main menu options for the installation.} +\label{tab:main-menu-options} +\begin{tabular}{>{\ttfamily}ll} +p & The platform you are running on.\\ +b & The architectures for which to install binaries.\\ +s & The base installation scheme to use (minimal, recommended, + full, etc.)\\ +c & Override the base scheme for individual collections.\\ +l & Override for language collections.\\ +d & Directories in which to install.\\ +o & Other options.\\ +i & Perform the installation.\\ +\end{tabular} +\end{table} + +Here are further details on each option. + +\textbf{\optname{p} -- Current platform.} Since the installation script +automatically guesses which platform you're running on, it is usually +unnecessary to use this option. It's there in case you need to override +the automatic detection. + +\textbf{\optname{b} -- Binary architectures.} By default, only the +binaries for your current platform will be installed. From this menu, +you can select installation of binaries for other architectures as well +(or omit installing the current platform). This can be useful if you are +sharing a \TeX\ tree across a network of heterogenous machines. For a +list of the supported architectures, see table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}. + +\textbf{\optname{s} -- Base installation scheme.} From this menu, you +can choose an overall set of package collections, called a ``scheme''. +The default \optname{full} scheme installs everything available, but you +can also choose the \optname{basic} scheme for a minimal system, or +\optname{medium} to get something in between. There are also specific +sets for Omega and \acro{XML}. + +\textbf{\optname{c} -- Individual collections.} From this menu, you can +override the scheme's set of collections to install. Collections are +one level more detailed than schemes\Dash collections consist of one or +more packages, where packages (the lowest level grouping in \TL) contain +the actual \TeX\ macro files, font families, and so on. In this menu, +selection letters are case-sensitive. + +\textbf{\optname{l} -- Language collections}. This menu has the same +basic purpose as \Ucom{c}, to override the collection set in the chosen +scheme. In this case, the collections are specifically for different +languages. Selection letters are case-sensitive here too. Here is a +list of the language collections in \TL: + +% xx really should generate list from texmf/tpm/collection/tex-lang* +% a la install-tl.sh. +\begin{tabbing} +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \kill +(some) African scripts \> +Arabic \> +Armenian \> +Chinese\,Japanese\,Korean \\ +Croatian \> +Cyrillic \> +Czech/Slovak \> +Danish \\ +Dutch \> +Finnish \> +French \> +German \\ +Greek \> +Hebrew \> +Hungarian \> +Indic \\ +Italian \> +Latin \> +Manju \> +Mongolian \\ +Norwegian \> +Polish \> +Portuguese \> +Spanish \\ +Swedish \> +Tibetan \> +\acro{UK} English \> +Vietnamese \\ +\end{tabbing} + +\noindent Language collections typically include fonts, macros, +hyphenation patterns, and other support files. (For instance, +\pkgname{frenchle.sty} is installed if you select the \optname{French} +collection.) In addition, installing a language collection will alter +the \filename{language.dat} configuration file controlling which +hyphenation patterns are loaded. + +\textbf{\optname{d} -- Installation directories}. Three directories can +be changed here: +\label{text:instdir} + +\begin{ttdescription} +\item [TEXDIR] The top-level directory under which +everything else will be installed. The default value is +\dirname{/usr/local/texlive/2005}, and is often changed. We recommend +including the year in the name, to keep different releases of \TL{} +separate. (You may wish to make a version-independent name such +\dirname{/usr/local/texlive} via a symbolic link, which you can then +update after testing the new release.) + +Under \MacOSX, the usual frontends look for \TeX{} in +\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. + +\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of +the initial installation, but rather as time goes by) puts +non-version-specific files, primarily fonts. The default value is +\dirname{/usr/local/texlive/texmf-local}, independent of the current +\TL{} release, because it's also the recommended location to put any +local packages or configuration settings. + +\item [TEXMFSYSVAR] This tree is where \cmdname{texconfig-sys} puts +files that \emph{are} version-specific. The default value is +\dirname{TEXDIR/texmf-var}, and there's generally no reason to change +it. There is also \envname{TEXMFSYSCONFIG}, which is where +\cmdname{texconfig} looks for modified configuration data. See +section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig} for more +information. + +\end{ttdescription} + +\textbf{\optname{o} -- Other options.} From this menu, you can select +the following general options: + +\begin{ttdescription} +\item [a] Specify an alternate directory for generated fonts. +The default is to use the \envname{TEXMFVAR} tree, as explained above. +Setting this is useful if you plan to mount the main tree read-only, and +therefore you need another location (perhaps host-specific) for +dynamically created fonts. + +\item [l] Create symbolic links for the binaries, man pages, +and\slash or \acro{GNU} Info files in other locations. For example, you may +wish to make the man pages available under \dirname{/usr/local/man} and +the Info files available under \dirname{/usr/local/info}. (Of course +you need appropriate privileges to write in the specified directories.) + +It is not advisable to overwrite a \TeX\ system that came with your +system with this option. It's intended primarily for creating the links +in standard directories that are known to users, such as +\dirname{/usr/local/bin}, which don't already contain any \TeX\ files. + +\item [d] Skip installation of the font/macro documentation tree. +This is useful if you need to save space, or if you've previously +installed the documentation elsewhere. + +\item [s] Skip installation of the main font/macro source +tree. This is useful if you are arranging to share that tree between +machines and\slash or architectures in some other way, such as \acro{NFS}. + +\end{ttdescription} + +\textbf{i -- Perform installation.} When you're satisfied with your +configuration options, enter \Ucom{i} to actually do the installation +from the media to your chosen locations. + +% text is similar to above, but no TEXMFSYSVAR, so we have to write out. +After the installation completes, your next step is to include the +architecture-specific subdirectory of \dirname{TEXDIR/bin} in your +\envname{PATH}, so the newly-installed programs can be found. The +architecture names are listed in table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}, or you can simply list the directory +\dirname{TEXDIR/bin}. + +The syntax for doing this, and the initialization file to use, depends +on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, +\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your +\filename{$HOME/.profile} file: + +\begin{alltt} +PATH=/usr/local/texlive/2005/bin/\var{archname}:$PATH; export PATH +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /usr/local/texlive/2005/bin/\var{archname}:$PATH +\end{alltt} + +\textruntexconfig + +Here is a minimal annotated example which accepts the default +directories and installs binaries for the current system only. Thus, +only one command is needed, \Ucom{i} for install. The \texttt{>} is the +shell prompt as usual. + +\begin{alltt} +> \Ucom{sh install-tl.sh} +\Ucom{i} # perform installation +> \Ucom{texconfig} ... # see section \ref{sec:texconfig} +# New PATH element, with Linux as the example: +> \Ucom{PATH=/usr/local/texlive/2005/bin/i386-linux:$PATH; export PATH} +\end{alltt} + +\textifindoubt + + +% +\subsection{Installing individual packages to disk} + +You can add individual packages or collections from the current +distribution to an existing non-\TL{} setup, or an earlier +\TL{} installation. + +\startinst + +Run the installation script \filename{install-pkg.sh} (not +\filename{install-tl.sh}, which is intended for complete installations +only): +\begin{alltt} +> \Ucom{sh install-pkg.sh \var{options}} +\end{alltt} + +The first set of options controls what gets read: + +\begin{ttdescription} +\item [-{}-package=\var{pkgname}] The individual package to work on. + +\item [-{}-collection=\var{colname}] The individual collection to work on. + +\item [-{}-nodoc] Exclude documentation files from the operation. + +\item [-{}-nosrc] Exclude source files from the operation. + +\item [-{}-cddir=\var{dir}] Source directory to read from; defaults +to the current directory. If you followed the instructions above, that +will be the distribution directory, and won't need to be changed. + +\item [-{}-listdir=\var{dir}] The so-called `lists' directory within +\var{cddir} from which to read the package information. The only +reason to change the default is if you're making changes to \TL{} +yourself. + +\end{ttdescription} + +What actually happens is controlled by the following options. If +neither of these are specified, the default action is to install the +selected files. The main destination tree is found by expanding +\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by +setting either the environment variable \envname{TEXMFMAIN} or +\envname{TEXMF}. + +\begin{ttdescription} +\item [-{}-listonly] List the files that would be installed, but don't +actually install anything. + +\item [-{}-archive=\var{tarfile}] Instead of installing the files into +the \TeX{} system, make a \cmdname{tar} archive. + +\end{ttdescription} + +Additional options: + +\begin{ttdescription} + +\item [-{}-config] After installation, run \code{texconfig init}. + +\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to +rebuild the filename database. + +\item [-{}-verbose] Give more information as the script runs. + +\end{ttdescription} + +Here are some usage examples: + +\begin{enumerate} + +\item To see the files in the package \pkgname{fancyhdr} without +installing it: + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} +> \Ucom{--listonly} +\fi{} +texmf/doc/latex/fancyhdr/README +texmf/doc/latex/fancyhdr/fancyhdr.pdf +... +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{natbib}: +\begin{alltt} +> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{alg} without source files or +documentation: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} + +\item Install all the packages in the collection of additional +plain \TeX\ macros: +\begin{alltt} +> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} + +\item Write all files in the \pkgname{pstricks} package to a +\cmdname{tar} file in \path|/tmp|: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} + +\end{enumerate} + +\textifindoubt + + +% +\section{Post-installation} +\label{sec:postinstall} + +After the main installation is done, for any operating system, the +remaining steps are to configure the system for your local needs, and +perform some basic tests. + +Another sort of post-installation is to acquire packages, fonts, or +programs that were not included in \TL{}. The basic idea is to +install such additions in the \envname{TEXMFLOCAL} tree (if you +installed to disk), or \envname{TEXMFSYSVAR} (if you are running live). +See the ``Installation directories'' option on \p.\pageref{text:instdir}. + +Unfortunately, the details can and do vary widely, and so we do not attempt to +address them here. Here are some external links to descriptions: +\begin{itemize*} +\item +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} +\item +\url{http://www.ctan.org/installationadvice} +\item +\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} +\item +\url{http://www.ctan.org/tex-archive/info/Type1fonts} for +installation information for fonts in particular. +\end{itemize*} + + +\subsection{The \protect\cmdname{texconfig} program} +\label{sec:texconfig} + +At any time after installation, you can and should use the program +\cmdname{texconfig} to configure the system to fit your local needs. It +is installed in the architecture-specific subdirectory +\texttt{TEXDIR/bin/\var{arch}} along with everything else. + +If you run it without arguments, it will enter full-screen mode and +allow you to view and change options interactively. + +You can also run it with various command-line options. Here are some of +the most common (\TL{} is configured for the A4 paper size by default): + +\begin{ttdescription} + +\item [texconfig paper letter] Set default paper size for +various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, +\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other +allowable size is \optname{a4}, which is the default. + +\item [texconfig rehash] Update all the \TeX{} ``filename databases'', +after adding or removing files. + +\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. +(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) + +\item [texconfig help] Output help information for \cmdname{texconfig}. + +\end{ttdescription} + +Of course, \cmdname{texconfig} can only support changing a few of the +many options and configuration parameters in a \TeX{} system. The main +configuration file for the base \Webc{} programs is named +\filename{texmf.cnf}. You can find its location by running +\samp{kpsewhich texmf.cnf}; it contains many comments explaining the +default settings and useful alternatives. + +As of 2005, \cmdname{texconfig} alters files in a user-specific +directory, namely \dirname{$HOME/.texlive2005}. If you install \TeX\ +just for yourself, that is unlikely to make a difference. But if you +install \TeX\ on a multi-user system, you will want to change the +configuration for the whole system. In this case, run +\cmdname{texconfig-sys} instead of \cmdname{texconfig}. + +Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were +changed, to work under \dirname{$HOME/.texlive2005}. To alter system +directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}. + +In particular, for multi-user systems, you will probably want to +pregenerate the standard formats with \texttt{fmtutil-sys --missing}. +Otherwise, each user will end up with their own formats. + +Also, if you have a personally-modified copy of \filename{fmtutil.cnf} +or \filename{updmap.cfg}, instead of using the ones generated by +installation, they must be installed in the tree referenced by the +variable \envname{TEXMFSYSCONFIG}. + +The variables specifying the directories altered by these commands are +listed in section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. +You can see the actual directories by running \texttt{texconfig conf}, +and you can change them by editing \filename{texmf.cnf}. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TL{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and\slash or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We give Unix commands; under \MacOSX{} and Windows, +you're more likely to run the tests through a graphical interface, but +the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.141592 (Web2C 7.5.5) +kpathsea version 3.5.5 +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, most likely you don't have the correct +\dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on \p.\pageref{text:path}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.141592... +... +Output written on sample2e.dvi (3 pages, 7496 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, perhaps +you have interference from old environment variables or configuration +files. For a deep analysis, you can always ask \TeX{} to report on +exactly what it is searching for, and finding; see ``Debugging actions'' +on page~\pageref{Debugging}. + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Under Windows, the analogous command is \cmdname{windvi}.) You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, by the way if you're new to the system.) +You do have to be running under X for \cmdname{xdvi} to work; if you're +not, or your \envname{DISPLAY} environment variable is set incorrectly, +you'll get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TL{}, so you must install them separately. See +\url{http://www.gnu.org/software/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. + +\item Other standard test files you may find useful: + +\begin{ttdescription} +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} +You can process these in the same way as we did with +\filename{sample2e.tex}. + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually +constructing \TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html} for some introductory resources. + + +\section{\MacOSX{} installation} +\label{sec:mac-install} + +The recommended way to install \TeX\ on \MacOSX\ is from the Mac\TeX\ +distribution, new in 2005. This is provided on the \pkgname{live} +\DVD{} in the top-level \dirname{mactex/} directory. It contains its +own (native) installer for a full \TeX\ distribution, based on a +combination of te\TeX\ and \TL, along with many additional applications +and documentation. The project web page is \url{http://tug.org/mactex}. + +If you prefer, installation of \TeX{} under \MacOSX{} can also be done +directly from \TL, using the \filename{install*} scripts, as follows. + +In order to run the installation scripts under \MacOSX, you need to have +the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 +or later, you have \cmdname{bash}, and can proceed. If you're running +an earlier \MacOSX{} version, however, the default shell is +\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from +the Internet, or more likely upgrade your system. + +Once you have \cmdname{bash}, the Unix installation documentation in the +previous section can be followed. See section~\ref{sec:unix-install} on +\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there +where needed. + +\section{Windows installation} +\label{sec:win-install} + +In this release of \TL{}, happily, the distribution once +again has a native Windows installer, named \cmdname{tlpmgui.exe}. (See +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, for an +explanation of the different distributions.) + +\cmdname{tlpmgui} has essentially the same options as the Unix +installer, only done through a GUI interface: selecting schemes, +individual collections, installation directories, and so on. +Section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk} describes the basic elements. It +also allows some post-installation activities such as adding/removing +packages, updating the filename database and building formats. +Moreover, \cmdname{tlpmgui} can setup the system for running +programs directly from the \DVD. + +For those who like to look underneath the hood, \cmdname{tlpmgui} uses +as its ``engine'' a command-line Windows program named \cmdname{tlpm}. + +The Windows \TeX{} system included in \TL{} is based on new binaries +borrowed from the \XEmTeX{} project, formerly known as \fpTeX{} (see +\url{http://www.metz.supelec.fr/~popineau/xemtex-1.html}). +It also includes some older (but still working) tools, notably +a \texttt{dvi} previewer, \textsf{Windvi}, which is similar in usage to +the established Unix \textsf{xdvi}. The documentation can be found in +\OnCD{texmf/doc/html/windvi/windvi.html}. + +\TL{} can be installed on systems running Windows 98, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) +and \acro{MS-DOS} are not supported. + +\textbf{Warning:} Win9.x users must ensure they have enough environment + space before undertaking installation. The \cmdname{tlpmgui.exe} + program won't change the environment size for them. A few environment + variables will be created and it is possible you run out of + environment space. Add \texttt{SHELL=<path>COMMAND.COM /E:4096 /P} in the + config.sys file in order to increase your environment size. + +\subsection{Installing \protect\TeX\protect\ Live to disk} + +After inserting the \TL{} CD into the \acro{CD} drive, autostart should +activate \cmdname{tlpmgui}. If it does not, click \guiseq{Start\arw Run}, +then type \verb|<drive letter>:\setup-win32\tplmgui.exe| (or +\verb|<drive letter>:\texlive\setup-win32\tplmgui.exe| if you are +installing from the TeX Collection DVD), where \verb|<drive letter>| +is the drive letter with the TeX Live CD (or TeX Collection DVD), and +then click OK. + +The installation window titled \guiseq{TeX Live installation and maintenance +utility} should open. It contains the following sections: \guiseq{Main +customization}, \guiseq{Install}, \guiseq{Select a scheme}, \guiseq{Select +systems}, \guiseq{Directories} and \guiseq{Options}. + +In the \guiseq{Directories} section the installation drive (directory) next +to the \guiseq{CD/DVD} button should be displayed (e.g., \texttt{F:/} or \texttt{F:/texlive/} for the DVD), but +if it is not, then click the \guiseq{CD/DVD} button and select the \acro{CD/DVD} +drive, with the \TL{} CD (or TeX Collection DVD). + +The directory in which you wish to install the software can be set by +clicking the \guiseq{TLroot} button. This directory will be set as +\path|TLroot| environment variable for later usage. The \path|TEXMFTEMP| and +\path|TEXMFCNF| environment variables as displayed next to the +\guiseq{TEXMFTEMP} and \guiseq{TEXMFCNF} buttons will be adjusted +automatically and set during installation, but they can also be adjusted +manually now to suit special needs. + +In the \guiseq{Select a scheme} section the desired \TL{} installation scheme +should be chosen by clicking the radio button labelled with the installation +scheme name (e.g., \guiseq{scheme-gust}). Each scheme is accompanied by an +\guiseq{Info} button which, when clicked, displays a short description of the +relevant scheme. + +A scheme is a large set of files targeted at some kind of usage. There are +generic schemes for basic, medium and full installations. The remaining ones +are either targeted at certain LUGs (i.e., what GUST or GUTenberg propose +for their members) or application targeted (e.g., for XML and \TeX{} +cooperation). A preselected scheme can be refined. This is done in the +\guiseq{Main customization} section by choosing additional collections from +\guiseq{Standard collections} or \guiseq{Language collections}. For example, +by clicking the \guiseq{Select} button labelled \guiseq{Standard +collections}, additional collections like Metapost, Omega or documentation +in different languages can be selected. + +\textbf{Note:} The \guiseq{Ghostscript}, \guiseq{Perl} and \guiseq{Wintools} +collections are selected by default and should be installed unless they are +already installed and you really know what you are doing. This is because +they are required by many important tools. The \verb|PERL5LIB| and +\verb|GS_LIB| environment variables will be set too. + +Next, clicking the \guiseq{Select} button labelled \guiseq{Language +Collections} in the \guiseq{Main customization} section opens the +\guiseq{Language collections} window in which the installation language can +be chosen by ticking the box next to the language. + +Next, click the \guiseq{Install} button in the \guiseq{Install} section to +start the installation proper process. + +The \TL{} system needs some post-processing steps (format files +generation, ls-R databases generation, environment variables, etc.). All +these operations are done there, some of them can be lengthy. So please wait +until you see a statement about the successfully finished installation. + +The shortcut for \cmdname{tlpmgui} will be added to the +\guiseq{Start\arw Programs\arw TeXLive2005} menu. + +If it is needed (Win9x/WinME), you will be asked to reboot your computer. + +\subsection{Support packages for Windows} +\label{sec:win-xemtex} + +To be complete, a \TL installation needs support packages that are not +commonly found on a Windows machine. Many scripts are written using the Perl +language. Some important tools require the Ghostscript \PS{} interpreter to +render or to convert files. A graphic file toolbox is also needed in some +cases. Last but not least, a \TeX-oriented editor makes it easy to type in +your \TeX{} files. + +All these tools are quite easy to find for Windows, but in order to try to +make your life even easier, we have put such a set of tools on \TL: +\begin{itemize*} +\item GNU \cmdname{Ghostscript} 7.07 +\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} + Perl scripts. +\item win-tools is a set of small programs (bzip2, gzip, jpeg2ps + and tiff2png) +%\item a subset of \cmdname{ImageMagick} 5.5.6 +%\item the \cmdname{ISpell} checker +%\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support +%\TeX{} typesetting. +\end{itemize*} + +These packages are borrowed from the \XEmTeX{} distribution +(the successor of fp\TeX). + +Perl and Ghostscript are installed by default; you may explicitly +deselect them during installation if you already have them. + +If you don't want to install this bundle, then you are on your own to +install the required tools to complete your \TL{} system. Here is a +list of places to get those tools: + +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} (but you might need some + supplementary packages from CPAN: \url{http://www.cpan.org/}) +\item[ImageMagick] \url{http://www.imagemagick.com} +\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to + process or convert your graphic files. NetPBM home page is + \url{http://netpbm.sourceforge.net/} +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection: + \begin{itemize*} + \item \cmdname{GNU Emacs} is available natively under Windows, see + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} + \item \cmdname{XEmacs} is available natively under Windows, see + \url{http://www.xemacs.org/} + \item \cmdname{WinShell} is available on \TL in the \path|support| + directory, see \url{http://www.winshell.de} + \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} + \item \cmdname{Vim} is available on \TL{} in the + \path|support\vim| directory and the + reference site is \url{http://www.vim.org} + \item TeXnicCenter is free software, available from + \url{http://www.toolscenter.org} and in the proTeXt distribution. + \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd} + \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} + \end{itemize*} +\end{description} + +You might want to install other tools that are not free\footnote{Not +free, that is, in the sense of freedom to modify and redistribute, +following free software guidelines. This does not mean you can't acquire +them for no money.} and therefore not included on \TL{}, such as +\cmdname{GSView}, the \cmdname{Ghostscript} companion to more +conveniently view PS/PDF files. \cmdname{GSView} is available from +\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. + +\section{Maintenance of the installation in Windows} + +If you have TeX Live installed, you can use \cmdname{tlpmgui} again +for modyfying and maintaining your installation. + +\subsection{Adding/removing packages} + +As the \cmdname{tlpmgui} shortcut is available in the \guiseq{Start\arw +Programs\arw TeXLive2005} menu, start it from here. The maintenance window +titled \guiseq{TeX Live installation and maintenance utility} shows. It +contains several tabs: \guiseq{Add Packages}, \guiseq{Remove packages}, +\guiseq{Manage installation}, \guiseq{Remove installation}. + +Click the tab labelled \guiseq{Add packages} or \guiseq{Remove packages} +to enter the relevant functionality and then: + +\begin{itemize} +\item In the first tab select the proper \CD{} drive (or \DVD with + \texttt{texlive} directory) by pressing the \guiseq{CD/DVD} button. +\item Click the \guiseq{Search} button in the \guiseq{Buttons} section to +display or refresh in the \guiseq{Select packages to\dots} section the +list of packages to install or remove. + +When adding packages, the list of installed packages is compared to the list +of packages available from your \CD/\DVD. Only packages not already installed are +displayed. It is up to you to select which packages you want to +install. + +When removing individual packages, only a list of installed packages +will be displayed. + +Please note that for both \guiseq{Add packages} and \guiseq{Remove packages} +the collections are listed first. + +\item Select a package by clicking on the name of the package. Clicking the +\guiseq{Info} button in the \guiseq{Buttons} section displays a short +description of the selected package in the window located in the \guiseq{Info +about the selected item} section. To select several packages at once hold +down one of the Ctrl or Shift keys at your keyboard while holding down the +left mouse button or drag the mouse pointer while holding down the left mouse +button. + +\item Click the \guiseq{Install} or \guiseq{Remove} button in the +\guiseq{Buttons} section to perform the appropriate action. +\end{itemize} + +\subsection{Configuring and other management tasks} + +The functions available in the tab labelled \guiseq{Manage the installation} +are helpful in performing actions needed when you want to add support for a +language which was not selected during the installation, or add/regenerate a +format which was not selected during the installation or was modified after +the installation. + +The following actions can be performed: + +\begin{itemize} +\item Refresh the \filename{ls-R} database +\item Create formats (All or Missing) +\item Edit \filename{language.dat} +\item Edit \filename{fmtutil.cnf} +\item Edit \filename{updmap.cfg} +\end{itemize} + +Note: you can close the Edit\dots{} window with the \guiseq{Cancel} or +\guiseq{Done} button; the latter will start rebuilding the format files +(or the fontmap files if you have edited \filename{updmap.cfg}), followed by a +\filename{ls-R} database files refresh. + +For more information about the configuration see section~\ref{sec:persconf}, +\p.\pageref{sec:persconf}. + +\subsection{Uninstalling \protect\TL{}} + +The tab labelled \guiseq{Remove the TeX Live installation} opens a window +which contains functionality not worth describing and we do not know who would +need it and what it is for\dots :-) + +Anyway, if you have the \path|texmf-local| directory for your local additions, +the removal procedure will not wipe it out or delete things in it. The \path|setup-win32| +directory containing \cmdname{tlpmgui} and related files will not be deleted. You will have to do some manual cleanup to +actually remove them. + +\subsection{Adding your own packages to the installation} + +First, whatever changes you make, \textbf{do not forget to rebuild the ls-R +database files}. Otherwise, your new files will not be found. You can do this +either via the \cmdname{tlpmgui} run and selection of the appropriate action +from the \guiseq{Manage the installation} tab, or manually running the +\file{mktexlsr} command. + +If you want to add files that are not provided by the \TL{} distribution, +it is recommended to put them in the \path|$TEXMFLOCAL| directory. This +way, you will be safe against upgrades of the \TL{} software. + +The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, +for example, you want to add the support file for the Maple symbolic +computation program, you will have to put the style files in:\\ +\path|c:\TeXLive2005\texmf-local\tex\latex\maple\|\\ and the +documentation files in:\\ \path|c:\TeXLive2005\texmf-local\doc\latex\maple\| + +\subsection{Running \texttt{tlmp.exe} from the command line} +The \cmdname{tlpm.exe} program which is used as engine by \cmdname{tlpmgui} +has a number of other useful options. You can get the list by running: +\begin{verbatim} +tlpm --help +\end{verbatim} + +More information and examples of use can be found in \path|tlpm.readme|. + +\subsection{Network installation} + +\KPS{} knows about UNC names, so you can use them to get your TEXMF +tree from the network. But there is better than this. +All the support files and configuration files, everything except the files in the +\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means +you can use Samba either to mount from an NT server to a Unix +workstation or the converse. Several strategies are possible: +\begin{itemize} +\item Put everything on the server. Just add each set of files for the OS and +architecture you want to use in the \path|bin| directory. That means +for example \path|bin/win32| and \path|bin/i386-linux|. Next configure +your main variables. You can use UNC names to +point to the right directories under Win32. +\item Install a local copy for the binaries and format files. In this + case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that + will be accessed remotely. Set \path|$TEXMFVAR| to be a local + directory which will hold local configuration files and on-the-fly + generated files. +\end{itemize} + +\subsection{What's different in Windows?} + +The Windows version of \Webc{} has some specific features that should be +pointed out. + +\begin{description} +\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for + the \TL{}. In order to cut down the starting time of any + \KPS{}-enabled program, these hash-tables have been put in shared + memory. This way, when you chain the execution of several such + programs, like \path|tex| calling \path|mpost| calling \path|tex|, + the overhead when starting each of the subprograms is + reduced. This change is hidden to the user, except if you set the + debug flag of kpathsea to the \path|-1| value: you will then trace + access to the shared memory, which is not what you want (it is + accessed very often!). What is useful in a log trace of the shared + memory access is still to be defined, so the situation might evolve + in the future. +\item[\cmdname{kpsecheck}] This command provides some options that did + not fit well into \cmdname{kpsewhich}. It will allow you to list all + the files that occur multiple times across your texmf trees. This + could be handy, but most of the time you will also get unwanted + output (like dozens of \path|README| files). It is noticeable + that all these files result in clashes inside the \KPS{}-hashing + mechanism; fortunately, \KPS{} never looks for these files. For + this reason, you can combine the \path|-multiple-occurrences| with 2 + other options for including or excluding any filename that match + some pattern (you can request for several patterns). + + The \cmdname{kpsecheck} command will also report the status of shared + memory: in use or not used. That might be useful to know because if + the status reported is \samp{in use}, that means one or several + processes are working, and the effect of any \cmdname{mktexlsr} + command will be delayed until the next time where no \KPS{} linked + process will be running. + + Last, this same command will report about the location it thinks + Ghostscript can be found. Under Win32, for many programs, it is + easier to use the Ghostscript dll, and find it by using the + Ghostscript registry key than to change the \path|PATH|, which has a + limited length anyway. +\item[\Webc{}] The engines have a few more options than in Unix + \Webc{}, and one option with a different behavior: + \begin{itemize} + \item \path|-halt-on-error| stop the compilation at the first error. + \item \path|-job-time| set the job time to the same timestamp as the + file given in argument. +\item \path|-oem| use the DOS codepage for console output. + \item \path|-output-directory| allow to write all the output files in the + specified directory. + \item \path|-time-statistics| print statistics about the job run + time. It is to be noted that Win9x not being a true multitasking + operating system, it has no reliable timer for short periods, so + the value printed is an approximation. Under NT/2K/XP, the result + is quite accurate with user time and system time values allocated + for this run. For Unix + users: the \path|time| command is not usually available to Windows + users. + \end{itemize} +\end{description} + +\subsection{Personal configurations} +\label{sec:persconf} + +\subsubsection{Dvips} + +The configuration file for dvips can be found in\\ +\verb+C:\TeXLive2005\texmf-var\dvips\config\config.ps+\\ +You may open it with any editor + %(\cmdname{WinShell} will do fine) + and change some parameters: + +\begin{description} +\item [fonts] you can change the default printer \MF{} mode or printer + resolution in case \cmdname{dvips} needs to generate PK fonts. By default it + is configured to use Type~1 versions of the CM fonts, so it should + not call \cmdname{mktexpk} too often; +\item[printer] you can tell dvips where you want to print by default. If + the \optname{o} option is not followed by a printer name, then a + \file{.ps} \PS{} file is written. You can give dvips a printer + name such as: +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[paper] Next, you might want + to change the paper size from European (A4) to US letter + by making the US letter the first paper size mentioned in the file. + Scroll to the group of lines beginning with \code{@}. Move + the appropriate lines so that this section begins with the lines:\\ +\hspace*{1em} @ letterSize 8.5in 11in\\ +\hspace*{1em} @ letter 8.5in 11in\\ +\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ +\hspace*{1em} @+ letter\\ +\hspace*{1em} @+ \%\%EndPaperSize +\end{description} + +The current \TL{} distribution implements the procedure of making +always up-to-date fontmaps files for Dvips and Pdftex. This is done by +the \cmdname{updmap} program during installation, as well as during any +font package addition. If you add new packages by hand, edit the file +\verb+updmap.cfg+ in \path|$TEXMFVAR/web2c|. + +\subsubsection{PdfTeX} + +If you use the program pdf{}latex to write \acro{PDF} format directly, +and you are using \acro{US} letter-size paper, edit the file +\verb+C:\TeXLive2005\texmf-var\tex\generic\config\pdftexconfig.tex+ and +change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries +should read: +\begin{alltt} +\bs{}pdfpagewidth=8.5 true in +\bs{}pdfpageheight=11 true in +\end{alltt} +Save the file and exit the editor. + +\subsubsection{GSView} +GSView is now distributed under the Aladdin License, and therefore is no +longer included in \TL{}. + +If you may want to change the page size to US letter size. If so, open +GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. + +Also, there are menu settings that are supposed to give you the most +readable screen image. On \guiseq{Media \arw Display Settings}, set both +\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. + +Note that the installation process has set all \code{.ps} and +\code{.eps} files to automatically open with \cmdname{GSView}. + +For printing instructions, see section~\ref{printing} below. + +\subsubsection{WinDvi} +\label{sub:windvi} + +The \file{tlpmgui.exe} program takes care of associating the files +with the \file{.dvi} extension with \file{Windvi}, but it doesn't make an icon +on the desktop, so please do it yourself. + +Open \cmdname{windvi} by clicking an icon or from the command line. + +You can set it for US letter-size paper by going to \guiseq{View\arw +Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and +then \optname{OK}. Exit \cmdname{windvi}. + +You can change other parameters from there as well, such as the ability +to execute system commands specified by the document (disabled by +default for security reasons). Also, the first time you view any .dvi +file, you may find the magnification too large. Zoom out until you get +an appropriate size. + +All configuration settings for \cmdname{windvi} are stored in a file +named \path|windvi.cnf| file. You can find it by running this command at +the prompt: +\begin{verbatim} +c:\>kpsewhich --expand-var $HOME/windvi.cnf +\end{verbatim} + +Should you have problems with \cmdname{windvi}, please remove the +configuration file and test your problem against a vanilla configuration. + +\subsection{Testing} + +For generic verification procedures, see section~\ref{sec:test-install} +(\p.\pageref{sec:test-install}). This section describes +Windows-specific tests. + +Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), +found in \path|C:\TeXLive2005\texmf-dist\tex\latex\base|. The \LaTeX\ source +should appear on the screen. Process it by clicking on the +\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar +(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} +menu (XEmacs) or Preview (Windvi) icon (WinShell). + +At first, when you preview files with Windvi, it will create fonts because +screen fonts were not installed. After a while, you will have created most +of the fonts you use, and you will rarely see the font-creation window. + +\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ +cannot find a file, you can press Ctrl-z to quit. + + +\subsection{Printing} +\label{printing} + +It is possible to print from Windvi. In this case, printing will be done +using the Windows unified printer driver. By definition, it is +compatible with all printers. However, there is some drawback: it can +generate some huge spool files, and some (older) versions of Windows +just don't like them. The advantage is that you can use features like +embedding BMP or WMF images. You also need to make sure that the printer +parameters are correctly set (subsection~\ref{sub:windvi}), else you +will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer +will give you only one quadrant of your page). + +Printing is faster and more reliable if you run \cmdname{dvips} to make +a \filename{.ps} file and then print from \cmdname{GSView}. In +\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} +window will appear. + +If you are using a \PS{} printer, \textit{be sure to select +\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box +at the bottom left of the \guiseq{Print} window. You can then select any +of the printers that you have previously installed. If you fail to +check the box for \optname{\PS{} Printer}, printing will not work. + +If you will be using your own non-\PS{} printer, select +\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click +on the button to the right labelled \guiseq{djet500} and select your +printer type from the list that pops up. (In the older version of +\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} +selected, then select your printer type from the \guiseq{Device} list.) + +\subsection{Tips and tricks for Win32} + +\subsubsection{Different flavors of Win32} + +What we call Win32 is not an operating system by itself. It is a large +set of functions (around 12,000 in the header files of the Microsoft +\acro{SDK}) that you can use to write programs for different operating +systems of the Windows family. + +Windows comes in different flavors: +\begin{itemize} +\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, + multithreading} environments. They are the latest\Dash and hopefully + last\Dash metamorphosis of \acro{DOS}. This can be more or less proven + by the fact that when booting, the PC will load the \path|command.com| + interpreter, and if you stop the boot process at this point, you can + ask for the current (\acro{DOS}) version and it will answer something + like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). +\item Windows \acro{NT}, which is a new operating system written from + scratch, capable of true multitasking behavior, and including many + high level features. +\item Windows 2000, based on \acro{NT}, with all the bells and + whistles of Win98. +\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is + the last step in merging both lines of products (Win9x based and + \acro{NT} based). \acro{XP} is based on \acro{NT}. +\end{itemize} + +Win9x are able to run 32~bits programs and 16~bits programs +concurrently. But the operating system by itself is not entirely +written in 32~bits mode, and does not support memory protection: 16bits +applications can overwrite parts of the operating system memory! Some +parts of the system like the \acro{GDI} (Graphical Device Interface) +manage limited resources like bitmaps, fonts, pens and so on for the set +of all programs that run concurrently. All the bitmaps headers available +at the same time can't amount for more than 64kB. This explains the +performance tool and the fact that you can put your system on his knees +by making intensive use of graphic objects for example. + +NT, 2K and XP do not suffer from these limitations, and neither from +other Win9x limitations. They are true multitasking environments, with +protected memory. They are much more responsive than Win9x because +of better memory management, better file system and so on. + +\subsubsection{Command line prompt} + +You may wonder, ``Why would I need to use a command line prompt when +I have Windows?'' + +Good question. The problem is of very general nature. Not all operations +can be done easily using only a \acro{GUI}. Command line gives you +programming power\Dash assuming a clever command interpreter. + +But the problem here is more fundamental: \TeX{} is \emph{a batch} +tool. Not an interactive one. \TeX{} needs to compute the best +layout for each page, resolve cross-references and so on. This can be +done only by a global processing of the document. It is not (yet) a +task that can be done interactively. + +This means that you should use \TeX{} from a command line. In fact the +situation is not so bad. There is an advantage to write command line +tools for complex processing: they are better debugged, because they are +independent of any \acro{GUI} problems, and \acro{GUI} tools can be +designed to interface to the command line tools. This is the case for +\TeX{}, where you will mostly interact with it through a \acro{GUI} text +editor. + +However, you may need to use the command line prompt in a number of +situations. One is when you are having difficulties and want to debug +your setup. + +\begin{description} + \item[Win9x] You can open a command line prompt by looking either for + the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, + or by choosing \guiseq{Start\arw Run} menu typing in + \path|command.com| as the progrm name. + \item[NT, 2K, XP] You can open a command line prompt by looking for + \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. + You can also choose \guiseq{Start\arw Run} and type in + \path|cmd.exe|, which is the name of the brand new command + interpreter for \acro{NT} (thus, it is untrue to call this a + \emph{DOS} box!). +\end{description} + +These locations may change across different Windows versions. + +\subsubsection{Path separators} + +The Win32 API understands both \path|/| and \path|\| characters as PATH +separators. But the command interpreters do not! So whenever a path name +is used programmatically, you can use both separators, and even mix them +up in the same path name. But on the command line, you must type +\path|\| as path separator. The reason is compatibility: the command +processor used \samp{/} to introduce arguments to commands. + +All this to say: do not be surprised to read path names written using +the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible +across platforms. For this reason, all the configuration files that +need to specify path names use the Unix convention. + +\subsubsection{File systems} +\label{sec:clusters} + +The worst feature of Win9x with regard to \TeX{} is probably the +so-called FAT file system. \TeX{} uses very many small files, with size +around 1--3kB. The \acro{FAT} file system is old, and predates by +decades the multi-gigabytes hard disks we have today. As a result, it +cannot manage efficiently the tens of thousands of \TeX{} files found in +\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for +\emph{any} file on a huge partition. It means that \TeX{} will use much +more disk space than it actually needs. + +The other, more modern, file systems available, \acro{FAT32} and +\acro{NTFS}, do not have this drawback. They manage clusters of 4kB +only. (You can lower the limit to 512 bytes on \acro{NTFS}.) + +\subsubsection{How to add some directory to your PATH} + +There are pairs of variables and values which behave much like global +variables inside your programs. The set of those variables is called the +environment. Each program is initialized with a copy of the +environment when it is run. It can request and change the +value of any variable. The changes happen in the copy of the +environment, and is not at all propagated to the other running +programs. + +Your PATH is a special environment variable used to search for +programs you want to run. +There is a different procedure to change it for Win9x, WinME and NT/2K/XP: + +\begin{description} +\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line + starting with \texttt{PATH=} and followed by a list of directories separated + by \path|;|. Please add the directory with the executables in this line. + After this, this line could look as follows: +\begin{verbatim} +PATH=c:\windows;c:\windows\system;c:\TeXLive2005\bin\win32 +\end{verbatim} +\item[Windows ME] You need to run the special program + \path|c:\windows\system\msconfig.exe| to be able to change any + environment variable. From this program, select the `Environment' + tab, and then add or modify the variable you want. You will be asked to reboot the + machine upon any change. +\item[Windows NT/2K/XP] + Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the + window with the control panel icons opens. Double click on System. The + System Properties window opens. Click on the tab \textsf{Environment} + or look for a button named \guiseq{Environment Variables} among the + dialog boxes. Now you can change the environment variables for your + user account. Note: There are also displayed the environment settings + for the system. Normally, you can't change the system variables + unless you have administrator rights on your machine. If you want to + change the \texttt{PATH} for all users, you will have to contact your + system administrator or be the system administrator yourself\Dash in + the latter case you should know what you are doing. + + If there is already a \texttt{PATH} setting for your user account, + left click on \texttt{PATH}. In the field \textsf{Variable} appears + \texttt{PATH} while the field Value shows the current setting of + \texttt{PATH} as a list of directories separated by \path|;|. Add + the directory where the executables are located (e.g. + \path|c:\TeXLive2005\bin\win32|). If there isn't a \texttt{PATH} variable + for your user account, simply click in the field Variable and type + in \texttt{PATH}, click in the field \textsf{Value} + and type in the directory with the executables. Important: Click on + the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the + changes to \texttt{PATH} won't apply to your system. Be careful when + changing the environment settings. +\end{description} + +The best way to be sure that a variable has been properly set is to +open a console and type: +\begin{verbatim} +set VARIABLE +\end{verbatim} +which should return the corresponding value. + +\subsubsection{\TeX{} engines} + +If you have a look at the \Webc{} documentation, you will read that all +the various \TeX{} derived programs use the same base engine. For +example, \path|tex.exe| and \path|latex.exe| are exact copies of the +same program, but each one will use a different format file, based on +its calling name. + +Under Unix, this feature is implemented through \emph{symbolic +links}. It saves up a bit of disk space, because some engines are +used with many different format files. + +The Win32 API does not know about file links. So to save up almost +the same amount of memory, all the \TeX{} base engines have been put +in DLLs (\emph{Dynamic Linked Library}). This means that you will have +the following layout: +\begin{alltt} +18/09/2005 14:19 3 584 latex.exe +18/09/2005 14:19 3 584 pdfetex.exe +18/09/2005 14:19 524 288 tl90pdfetex.dll +\end{alltt} +and the \path|latex.exe| file is nothing but a rough copy of +\path|pdfetex.exe| using the same core \path|tl90pdfetex.dll|. +The same trick has been used for the \path|mktex*.exe| family of programs +which are linked to the \path|mktex.dll| library. + +In fact, a generic tool called \path|irun.exe| is provided to build the +equivalent of Unix hard links for executable files only under Win32. + +\subsection{In case of problems} +\label{sec:troubleshooting} + +\subsubsection{What to do if \texttt{latex} does not find your files?} + +\begin{itemize} + +\item \cmdname{kpsewhich} is the tool of choice to debug any +problem. Unfortunately, \cmdname{kpsewhich} outputs debug information +to stderr, and the older Windows consoles do not know how to redirect stderr +to a file. (NT and Windows 2000 consoles know how to do that. But +the trick will work for any console.) For diagnostic purposes you can +temporarily set an environment variable (in a \acro{DOS} box): + +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +You can also set the debug level: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +If you want to redirect stderr to stdout, which is not possible +Windows, then do: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +This way you can capture both stdout and stderr in the same file. + +\item Assuming the installation has been done in \path|c:/TeX|, check + the following values: \\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ + \path|kpsewhich -expand-path $TEXMFCNF| & + \path|.;c:/TeX/texmf-var/web2c;| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| + \end{tabular} +} +\item If you have other \TeX{}-related values already set in your + environment, please, remove them. They are overriding the ones in + texmf.cnf. +\item Check the values from:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf/web2c/latex.fmt| + \end{tabular} +} +\item At this point, if everything is correct, \TeX{} and friends + should work. If it is not the case, you will need to play with + the \path|-debug=n| option from \path|kpsewhich|, and check back all + the values. Try to identify and report the problem. +\end{itemize} + +\subsubsection{What to do if your setup still does not work as expected?} + +Here are several questions to investigate: + +\begin{enumerate} +\item Is \file{tex.exe} in my \path|PATH|? + +\item Is the \path|TEXMFCNF| variable correctly set to +\path|c:/TeXLive2005/texmf-var/web2c| (default value)? + +\item Are there any errors in the log file generated by the +\file{tlmpgui.exe} program? +\file{tlmpgui.log} can be found in your +\file{TEMP} directory. You can find this by searching for the +string \samp{Error}. Hint: the log file can show some errors after +building all format files. Please do not panic: perhaps some formats +weren't already installed. + +\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? +(Unlikely, but it doesn't hurt to check.) + +\end{enumerate} + +The \TL{} software consists of hundreds of programs and tens of +thousands of files, all from varying sources. So it is quite difficult to +predict all possible causes for problems. Nevertheless, we will do our +best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) + +% don't use \Webc so the \uppercase in the headline works. +\section{A user's guide to Web2C} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system based on change files +under Unix, which were primarily the original work of Howard Trickey and +Pavel Curtis. Tim Morgan became the maintainer of the system, and +during this period the name changed to Web-to-C\@. In 1990, Karl Berry +took over the work, assisted by dozens of additional contributors, and +in 1997 he handed the baton to Olaf Weber. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in \web{} and translates them into C source +code. The core \TeX{} programs are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \acro{GNU} options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{}. This library uses a combination of environment variables and a +configuration files to optimize searching the (huge) collection of +\TeX{} files. \Webc{} can look at more than one directory tree +simultaneously, which is useful in maintaining \TeX's standard +distribution and local extensions in two distinct trees. To speed up +file searches the root of each tree has a file \file{ls-R}, containing +an entry showing the name and relative pathname for all files under that +root. + +\subsection{Kpathsea path searching} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database +is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{Path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given +search path by using the debugging options (see ``Debugging actions'' +on page~\pageref{Debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{Path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{Default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place. It checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This is used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, the following definition +(appproximately; there are actually even more trees) is made: +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{Subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarizes the special characters in \KPS{} +configuration files. + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion.\par +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{Filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\acro{GNU} \code{ls} is all right). To ensure that the database is +always up-to-date, it is easiest to rebuild it regularly via +\code{cron}, so that it is automatically updated when the installed +files change, such as after installing or updating a \LaTeX{} package. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{Invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The more important options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run + \texttt{kpsewhich -{}-help} for a list. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{SExamplesofuse} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files in \TL{}\Dash the Type~1 variants are used by default. +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} + +For these fonts (a phonetic alphabet from the University of Washington) +we had to generate \samp{.pk} files, and since the default \MF{} mode on +our installation is \texttt{ljfour} with a base resolution of 600\dpi{} +(dots per inch), this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. A program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the required \texttt{.pk} files +using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prolog \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the \PS{} font +map \file{psfonts.map}\Dash as of 2004, map and encoding files have +their own search paths and new location in \dirname{texmf} trees. As +the \samp{.ps} suffix is ambiguous we have to specify explicitly which +type we are considering (\optname{dvips config}) for the file +\texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... <utmb8a.pfb +utmbi8r NimbusRomNo9L-MediItal... <utmbi8a.pfb +utmr8r NimbusRomNo9L-Regu ... <utmr8a.pfb +utmri8r NimbusRomNo9L-ReguItal... <utmri8a.pfb +utmbo8r NimbusRomNo9L-Medi ... <utmb8a.pfb +utmro8r NimbusRomNo9L-Regu ... <utmr8a.pfb +\end{alltt} +Let us, for instance, take the Times Roman instance +\file{utmr8a.pfb} and find its position in the \file{texmf} directory +tree with a search for Type~1 font files: +\begin{alltt} +> \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these examples how you can easily locate the +whereabouts of a given file. This is especially important if you suspect +that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{Debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} + databases, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look at +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{SExamplesofuse} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 <CMR10> is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... +<texps.pro> +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +<cmr10.pfb>[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TL{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf}. + etc.). +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all TFM files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Approximately 10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. The default value of + \texttt{hash\_extra} is \texttt{50000}. +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since these are extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\begin{comment} +\section{Building on a new Unix platform} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \acro{GNU} version of these programs +(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. +\end{comment} + +\section{Acknowledgements} + +\TL{} is a joint effort by virtually all of the \TeX{} user groups. +This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. +The other principal contributors are listed below. + +\begin{itemize*} + +\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide +the hardware for the \TL{} source repository; and Rainer Sch\"opf and +Reinhard Zierke who look after it. \acro{DANTE} officers Volker Schaa +and Klaus H\"oppner coordinate production with the Lehmann's Bookstore +(\url{http://www.lob.de}). + +\item The Perforce corporation (\url{http://www.perforce.com}), for providing +a free copy of their excellent change management system, which we use +to manage the \TL{} sources. + +\item Peter Breitenlohner and the \eTeX\ team for the stable foundation +of future \TeX's. + +\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} +would certainly not exist, and whose continual help makes it a better +product. + +\item Michel Goossens, who co-authored the original documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item Hans Hagen, for major testing and making the \ConTeXt\ format +conform to \TL's needs. + +\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, +and Tomasz {\L}uczak, for \cmdname{tlpmgui}. + +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing +enhancements of \TeX's abilities. + +\item Petr Olsak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Fabrice Popineau, for the Windows binaries in \TL{}. + +\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, +and coordinator of the many major Polish contributions: fonts, Windows +installation, and more. + +\item Olaf Weber, for his patient assembly and maintenance of Web2C, +upon which all else depends. + +\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, +and much integration and testing. + +\item Graham Williams, on whose work the catalogue of packages depends. + +\end{itemize*} + +Builders of the binaries: +Tigran Aivazian (\pkgname{x86\_64-linux}), +Manfred Lotz (\pkgname{i386-freebsd}), +Fabrice Popineau (\pkgname{win32}), +Norbert Preining (\pkgname{alpha-linux}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux}, + \pkgname{sparc-solaris}), +Staszek Wawrykiewicz (\pkgname{i386-linux}), +Olaf Weber (\pkgname{mips-irix}), +Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). + +Documentation and translation updates: +Karl Berry (English), +Daniel Flipo \& Fabrice Popineau (French), +G\"unter Partosch \& Hartmut Henkel (German), +Petr Sojka \& Jan Busa (Czech\slash Slovak), +Boris Veytsman (Russian), +Staszek Wawrykiewicz (Polish). + +Of course the most important acknowledgement must go to Donald Knuth, first +for inventing \TeX, and then for giving it to the world. + + +\section{Release history} +\label{sec:history} + +\subsection{Past} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TL. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TL{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TL{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +\subsubsection{2003} + +In 2003, with the continuing flood of updates and additions, we found +that \TL{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In +addition: + +\begin{itemize*} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + \p.\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TL{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output most input + characters (32 and above) as themselves in output (e.g., + \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TL{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TL{} 2003. +\end{itemize*} + + +\subsubsection{2004} + +2004 saw many changes: + +\begin{itemize} + +\item If you have locally-installed fonts which use their own +\filename{.map} or (much less likely) \filename{.enc} support files, you +may need to move those support files. + +\filename{.map} files are now searched for in subdirectories of +\dirname{fonts/map} only (in each \filename{texmf} tree), along the +\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now +searched for in subdirectories of \dirname{fonts/enc} only, along the +\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about +problematic files. + +For methods of handling this and other information, please see +\url{http://tug.org/texlive/mapenc.html}. + +\item The \TK\ has been expanded with the addition of a \MIKTEX-based +installable \CD, for those who prefer that implementation to Web2C. +See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). + +\item Within \TL, the single large \dirname{texmf} tree of previous +releases has been replaced by three: \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{texmf-doc}. See +section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} +files for each. + +\item All \TeX-related input files are now collected in +the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than +having separate sibling directories \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Helper scripts (not meant to be invoked by users) are now located +in a new \dirname{scripts} directory of \dirname{texmf*} trees, and +searched for via \verb|kpsewhich -format=texmfscripts|. So if you have +programs which call such scripts, they'll need to be adjusted. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Almost all formats leave most characters printable as +themselves via the ``translation file'' \filename{cp227.tcx}, instead of +translating them with the \verb|^^| notation. Specifically, characters +at positions 32--256, plus tab, vertical tab, and form feed are +considered printable and not translated. The exceptions are plain \TeX\ +(only 32--126 printable), \ConTeXt\ (0--255 printable), and the +\OMEGA-related formats. This default behavior is almost the same as in +\TL\,2003, but it's implemented more cleanly, with more possibilities +for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(By the way, with Unicode input, \TeX\ may output partial character +sequences when showing error contexts, since it is byte-oriented.) + +\item \textsf{pdfetex} is now the default engine for all formats +except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} +when run as \textsf{latex}, etc.) This means, among other things, that +the microtypographic features of \textsf{pdftex} are available in +\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features +(\OnCD{texmf-dist/doc/etex/base/}). + +It also means it's \emph{more important than ever} to use the +\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent +code, because simply testing whether \cs{pdfoutput} or some other +primitive is defined is not a reliable way to determine if \acro{PDF} +output is being generated. We made this backward compatible as best we +could this year, but next year, \cs{pdfoutput} may be defined even when +\acro{DVI} is being written. + +\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: + + \begin{itemize*} + + \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support + from within a document. + + \item Microtypographic font expansion can be used more easily.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item All parameters previously set through the special configuration + file \filename{pdftex.cfg} must now be set through primitives, + typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no + longer supported. Any extant \filename{.fmt} files must be redumped + when \filename{pdftexconfig.tex} is changed. + + \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize*} + +\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and +\cmdname{mpost}) now accepts double quotes containing spaces and other +special characters. Typical examples: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +See the Web2C manual for more: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ support is now included within Web2C and consequently all +\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when +formats are built}. enc\TeX\ supports general re-encoding of input and +output, enabling full support of Unicode (in \acro{UTF}-8). See +\OnCD{texmf-dist/doc/generic/enctex/} and +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. +A little information is available in \OnCD{texmf-dist/doc/aleph/base} +and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The +\LaTeX-based format for Aleph is named \textsf{lamed}. + +\item The latest \LaTeX\ release has a new version of the +\acro{LPPL}\Dash now officially a Debian-approved license. Assorted +other updates, see the \filename{ltnews} files in +\OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng}, a new program for converting \acro{DVI} to +\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set +of fonts, with the assent and advice of the author (Claudio Beccari). +The excised fonts are the invisible, outline, and transparency ones, +which are relatively rarely used, and we needed the space. The full set +is of course available from \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. + +\item The \cmdname{ini} and \cmdname{vir} commands (links) for +\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, +such as \cmdname{initex}. The \cmdname{ini} functionality has been +available through the command-line option \optname{-ini} for years now. + +\item \textsf{i386-openbsd} platform support was removed. Since the +\pkgname{tetex} package in the \acro{BSD} Ports system is available, and +\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed +volunteer time could be better spent elsewhere. + +\item On \textsf{sparc-solaris} (at least), you may have to set the +\envname{LD\_LIBRARY\_PATH} environment variable to run the +\pkgname{t1utils} programs. This is because they are compiled with C++, +and there is no standard location for the runtime libraries. (This is +not new in 2004, but wasn't previously documented.) Similarly, on +\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. + +\end{itemize} + +\subsection{Present} +\label{tlcurrent} + +2005 saw the usual huge number of updates to packages and programs. +The infrastructure stayed relatively stable from 2004, but inevitably +there were some changes there as well: + +\begin{itemize} + +\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and + \cmdname{fmtutil-sys} were introduced, which modify the + configuration in the system trees. The \cmdname{texconfig}, + \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify + user-specific files, under \dirname{$HOME/.texlive2005}. + See section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + +\item Corresponding new variables \envname{TEXMFCONFIG} and + \envname{TEXMFSYSCONFIG} to specify the trees where configuration + files (user or system, respectively) are found. Thus, you may + need to move personal versions of \filename{fmtutil.cnf} and + \filename{updmap.cfg} to these places; another option is to + redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in + \filename{texmf.cnf}. In any case the real location of these files + and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} + must agree. + See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. + +\item Last year, we kept \verb|\pdfoutput| and other primitives undefined + for DVI output, even though the \cmdname{pdfetex} program was + being used. This year, as promised, we undid that compatibility + measure. So if your document uses \verb|\ifx\pdfoutput\undefined| + to test if PDF is being output, it will need to be changed. You + can use the package \pkgname{ifpdf.sty} (which works under both + plain \TeX\ and \LaTeX) to do this, or steal its logic. + +\item Last year, we changed most formats to output (8-bit) characters as + themselves (see previous section). The new TCX file + \filename{empty.tcx} now provides an easier way to get the + original \verb|^^| notation if you so desire, as in: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item The new program \cmdname{dvipdfmx} is included for translation of + DVI to PDF; this is an actively maintained update of + \cmdname{dvipdfm} (which is also still available for now, though + no longer recommended). + +\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included + to allow reloading of pdf files in the Adobe Acrobat Reader without + restarting the program. (Other pdf readers, notably \cmdname{xpdf}, + \cmdname{gv}, and \cmdname{gsview}, have never suffered from this + problem.) + +\item For consistency, the variables \envname{HOMETEXMF} and + \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and + \envname{TEXMFSYSVAR}, respectively. There is also + \envname{TEXMFVAR}, which is by default user-specific. See the + first point above. + +\end{itemize} + +\subsection{Future} + +\emph{\TL{} is not perfect!} (And never will be.) We intend to +continue to release new versions yearly, and would like to provide more +help material, more utilities, more installation programs, and (of +course) an ever-improved and checked tree of macros and fonts. This work +is all done by hard-pressed volunteers in their limited spare time, and +a great deal remains to be done. If you can help, don't hesitate to put +your name forward! + +Please send corrections, suggestions, and offers of help to:\hfill\null +\begin{quote} +Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{document} diff --git a/Master/texmf-doc/source/english/texlive-en/archive/tex-live.sty-2005 b/Master/texmf-doc/source/english/texlive-en/archive/tex-live.sty-2005 new file mode 100644 index 00000000000..487c8b8d7a2 --- /dev/null +++ b/Master/texmf-doc/source/english/texlive-en/archive/tex-live.sty-2005 @@ -0,0 +1,429 @@ +% $Id: tex-live.sty 1513 2006-02-13 00:22:35Z karl $ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\usepackage[T1]{fontenc} +\usepackage[latin1]{inputenc} +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +\RequirePackage{relsize} +\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{2} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\texttt{#1}} +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +\def\Ucom#1{% + \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\p.{p.\,} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\textsf{\TeX\ Collection}} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{web}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + pagecolor=hypercolor,urlcolor=hypercolor, + filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf-doc/source/english/texlive-en/live.tex b/Master/texmf-doc/source/english/texlive-en/live.tex index 82347e3dcde..9872ad090df 100644 --- a/Master/texmf-doc/source/english/texlive-en/live.tex +++ b/Master/texmf-doc/source/english/texlive-en/live.tex @@ -10,14 +10,14 @@ \title{% {\huge \textit{The \protect\TL{} Guide}\\\strut} - {\LARGE \textsf{\TK{} 2005}} + {\LARGE \textsf{\TK{} 2006}} } -\author{Sebastian Rahtz \& Karl Berry, editors \\[3mm] +\author{Karl Berry, editor \\[3mm] \url{http://tug.org/texlive/} } -\date{October 2005} +\date{December 2006} \maketitle @@ -215,7 +215,7 @@ members.) Here is a brief listing and description of the top level directories in the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} -hierarchy is in a subdirectory \dirname{texlive2005}, not at the top +hierarchy is in a subdirectory \dirname{texliveYYYY}, not at the top level of the disc. \smallskip @@ -313,15 +313,14 @@ classes of marks, additional debugging features, and more) and the \eTeX{} is 100\% compatible with ordinary \TeX. See \OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. -\item [pdf\TeX] writes Acrobat \acro{PDF} format as well as \dvi{}. The -\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' -which turns on all the program features. See +\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for +writing \acro{PDF} output as well as \dvi{}. See \OnCD{texmf/doc/pdftex/manual/} for the manual, and -\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. +\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. This is the +default program for all formats except plain \TeX. -\item [pdfe\TeX] combines the pdf\TeX\ and \eTeX\ extensions. This is -the default program for all formats except plain \TeX. -See above for documentation. +\item [Xe\TeX] adds support for Unicode input and OpenType fonts, using +third-party libraries. See \url{http://scripts.sil.org/xetex}. \item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus supports working with almost all the world's scripts simultaneously. It @@ -461,19 +460,19 @@ choose a directory on the local disk to place files that the \TeX{} system itself generates, such as fonts and formats, and also to provide a place for updated configuration files, if need be. -We'll use \dirname{/opt/texlive2005} in this example. It's good to +We'll use \dirname{/opt/texlive2006} in this example. It's good to include the year in the name, as these generated files are not -compatible from release to release. (If the default value of -\dirname{/usr/local/texlive/2005} works for you, then you can skip this +in general compatible from release to release. (If the default value of +\dirname{/usr/local/texlive/2006} works for you, then you can skip this step.) \begin{alltt} Enter command: \Ucom{d} Current directories setup: -<1> TEXDIR: /usr/local/texlive/2005 +<1> TEXDIR: /usr/local/texlive/2006 ... Enter command: \Ucom{1} -New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2005} +New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2006} ... Enter command: \Ucom{r} \end{alltt} @@ -538,14 +537,14 @@ Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et al.), put the following into your \filename{$HOME/.profile} file: \begin{alltt} PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH -TEXMFSYSVAR=/opt/texlive2005/texmf-var; export TEXMFVAR +TEXMFSYSVAR=/opt/texlive2006/texmf-var; export TEXMFVAR \end{alltt} \noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), put the following into your \filename{$HOME/.cshrc} file: \begin{alltt} setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH -setenv TEXMFSYSVAR /opt/texlive2005/texmf-var +setenv TEXMFSYSVAR /opt/texlive2006/texmf-var \end{alltt} \noindent Then log out, log back in, and test your installation @@ -681,7 +680,7 @@ be changed here: \begin{ttdescription} \item [TEXDIR] The top-level directory under which everything else will be installed. The default value is -\dirname{/usr/local/texlive/2005}, and is often changed. We recommend +\dirname{/usr/local/texlive/2006}, and is often changed. We recommend including the year in the name, to keep different releases of \TL{} separate. (You may wish to make a version-independent name such \dirname{/usr/local/texlive} via a symbolic link, which you can then @@ -756,13 +755,13 @@ on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, \filename{$HOME/.profile} file: \begin{alltt} -PATH=/usr/local/texlive/2005/bin/\var{archname}:$PATH; export PATH +PATH=/usr/local/texlive/2006/bin/\var{archname}:$PATH; export PATH \end{alltt} \noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), put the following into your \filename{$HOME/.cshrc} file: \begin{alltt} -setenv PATH /usr/local/texlive/2005/bin/\var{archname}:$PATH +setenv PATH /usr/local/texlive/2006/bin/\var{archname}:$PATH \end{alltt} \textruntexconfig @@ -777,7 +776,7 @@ shell prompt as usual. \Ucom{i} # perform installation > \Ucom{texconfig} ... # see section \ref{sec:texconfig} # New PATH element, with Linux as the example: -> \Ucom{PATH=/usr/local/texlive/2005/bin/i386-linux:$PATH; export PATH} +> \Ucom{PATH=/usr/local/texlive/2006/bin/i386-linux:$PATH; export PATH} \end{alltt} \textifindoubt @@ -968,14 +967,14 @@ configuration file for the base \Webc{} programs is named default settings and useful alternatives. As of 2005, \cmdname{texconfig} alters files in a user-specific -directory, namely \dirname{$HOME/.texlive2005}. If you install \TeX\ +directory, as in \dirname{$HOME/.texlive2005}. If you install \TeX\ just for yourself, that is unlikely to make a difference. But if you install \TeX\ on a multi-user system, you will want to change the configuration for the whole system. In this case, run \cmdname{texconfig-sys} instead of \cmdname{texconfig}. Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were -changed, to work under \dirname{$HOME/.texlive2005}. To alter system +changed, to work under \dirname{$HOME/.texliveYYYY}. To alter system directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}. In particular, for multi-user systems, you will probably want to @@ -1219,7 +1218,7 @@ these operations are done there, some of them can be lengthy. So please wait until you see a statement about the successfully finished installation. The shortcut for \cmdname{tlpmgui} will be added to the -\guiseq{Start\arw Programs\arw TeXLive2005} menu. +\guiseq{Start\arw Programs\arw TeXLive2006} menu. If it is needed (Win9x/WinME), you will be asked to reboot your computer. @@ -1296,12 +1295,12 @@ conveniently view PS/PDF files. \cmdname{GSView} is available from \section{Maintenance of the installation in Windows} If you have TeX Live installed, you can use \cmdname{tlpmgui} again -for modyfying and maintaining your installation. +for modifying and maintaining your installation. \subsection{Adding/removing packages} As the \cmdname{tlpmgui} shortcut is available in the \guiseq{Start\arw -Programs\arw TeXLive2005} menu, start it from here. The maintenance window +Programs\arw TeXLive2006} menu, start it from here. The maintenance window titled \guiseq{TeX Live installation and maintenance utility} shows. It contains several tabs: \guiseq{Add Packages}, \guiseq{Remove packages}, \guiseq{Manage installation}, \guiseq{Remove installation}. @@ -1391,8 +1390,8 @@ way, you will be safe against upgrades of the \TL{} software. The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, for example, you want to add the support file for the Maple symbolic computation program, you will have to put the style files in:\\ -\path|c:\TeXLive2005\texmf-local\tex\latex\maple\|\\ and the -documentation files in:\\ \path|c:\TeXLive2005\texmf-local\doc\latex\maple\| +\path|c:\TeXLive2006\texmf-local\tex\latex\maple\|\\ and the +documentation files in:\\ \path|c:\TeXLive2006\texmf-local\doc\latex\maple\| \subsection{Running \texttt{tlmp.exe} from the command line} The \cmdname{tlpm.exe} program which is used as engine by \cmdname{tlpmgui} @@ -1491,7 +1490,7 @@ pointed out. \subsubsection{Dvips} The configuration file for dvips can be found in\\ -\verb+C:\TeXLive2005\texmf-var\dvips\config\config.ps+\\ +\verb+C:\TeXLive2006\texmf-var\dvips\config\config.ps+\\ You may open it with any editor %(\cmdname{WinShell} will do fine) and change some parameters: @@ -1532,7 +1531,7 @@ font package addition. If you add new packages by hand, edit the file If you use the program pdf{}latex to write \acro{PDF} format directly, and you are using \acro{US} letter-size paper, edit the file -\verb+C:\TeXLive2005\texmf-var\tex\generic\config\pdftexconfig.tex+ and +\verb+C:\TeXLive2006\texmf-var\tex\generic\config\pdftexconfig.tex+ and change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries should read: \begin{alltt} @@ -1593,7 +1592,7 @@ For generic verification procedures, see section~\ref{sec:test-install} Windows-specific tests. Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), -found in \path|C:\TeXLive2005\texmf-dist\tex\latex\base|. The \LaTeX\ source +found in \path|C:\TeXLive2006\texmf-dist\tex\latex\base|. The \LaTeX\ source should appear on the screen. Process it by clicking on the \guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar (WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} @@ -1774,7 +1773,7 @@ There is a different procedure to change it for Win9x, WinME and NT/2K/XP: by \path|;|. Please add the directory with the executables in this line. After this, this line could look as follows: \begin{verbatim} -PATH=c:\windows;c:\windows\system;c:\TeXLive2005\bin\win32 +PATH=c:\windows;c:\windows\system;c:\TeXLive2006\bin\win32 \end{verbatim} \item[Windows ME] You need to run the special program \path|c:\windows\system\msconfig.exe| to be able to change any @@ -1799,7 +1798,7 @@ PATH=c:\windows;c:\windows\system;c:\TeXLive2005\bin\win32 \texttt{PATH} while the field Value shows the current setting of \texttt{PATH} as a list of directories separated by \path|;|. Add the directory where the executables are located (e.g. - \path|c:\TeXLive2005\bin\win32|). If there isn't a \texttt{PATH} variable + \path|c:\TeXLive2006\bin\win32|). If there isn't a \texttt{PATH} variable for your user account, simply click in the field Variable and type in \texttt{PATH}, click in the field \textsf{Value} and type in the directory with the executables. Important: Click on @@ -1908,7 +1907,7 @@ Here are several questions to investigate: \item Is \file{tex.exe} in my \path|PATH|? \item Is the \path|TEXMFCNF| variable correctly set to -\path|c:/TeXLive2005/texmf-var/web2c| (default value)? +\path|c:/TeXLive2006/texmf-var/web2c| (default value)? \item Are there any errors in the log file generated by the \file{tlmpgui.exe} program? @@ -2769,15 +2768,14 @@ The other principal contributors are listed below. \begin{itemize*} -\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide -the hardware for the \TL{} source repository; and Rainer Sch\"opf and -Reinhard Zierke who look after it. \acro{DANTE} officers Volker Schaa -and Klaus H\"oppner coordinate production with the Lehmann's Bookstore -(\url{http://www.lob.de}). +\item The English, German, Dutch, and Polish \TeX{} user groups +(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, +respectively), which together provide the necessary technical +and administrative infrastructure. Please join your local user group! -\item The Perforce corporation (\url{http://www.perforce.com}), for providing -a free copy of their excellent change management system, which we use -to manage the \TL{} sources. +\item The \acro{CTAN} team, which distributes the \TL{} images and +provides the common infrastructure for package updates, upon which \TL{} +depends. \item Peter Breitenlohner and the \eTeX\ team for the stable foundation of future \TeX's. @@ -2795,16 +2793,36 @@ it at short notice. \item Hans Hagen, for major testing and making the \ConTeXt\ format conform to \TL's needs. +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing +enhancements of \TeX's abilities. + +\item Taco Hoekwater, for renewed development efforts on MetaPost and +\TeX\ itself. + \item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, and Tomasz {\L}uczak, for \cmdname{tlpmgui}. -\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing -enhancements of \TeX's abilities. +\item Akira Kakuto, for updated Windows binaries as part of his +\acro{W32TEX} distribution effort +(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). + +\item Jonathan Kew and his employer \acro{SIL}, for the major new +development of Xe\TeX{} and taking the time and trouble to integrate it +in \TL{}. + +\item Reinhard Kotucha, for helping with the massive task of updating +packages in \TL{}, as well as Windows research efforts, the +\texttt{getnonfreefonts} script, and more. \item Petr Olsak, who coordinated and checked all the Czech and Slovak material very carefully. -\item Fabrice Popineau, for the Windows binaries in \TL{}. +\item Fabrice Popineau, for the original Windows support in \TL{}. + +\item Norbert Preining, for helping with the \TL{} infrastructure and +package updates, and coordinating the Debian version of \TL{} (together +with Frank K\"uster), making many suggestions for improvement along the +way. \item Staszek Wawrykiewicz, the principal tester for all of \TL{}, and coordinator of the many major Polish contributions: fonts, Windows @@ -3089,8 +3107,7 @@ not new in 2004, but wasn't previously documented.) Similarly, on \end{itemize} -\subsection{Present} -\label{tlcurrent} +\subsubsection{2005} 2005 saw the usual huge number of updates to packages and programs. The infrastructure stayed relatively stable from 2004, but inevitably @@ -3151,10 +3168,32 @@ latex --translate-file=empty.tcx yourfile.tex \end{itemize} + +\subsection{Present} +\label{tlcurrent} + +In 2006, the major new addition to \TL{} was the Xe\TeX{} program, +available as the \texttt{xetex} and \texttt{xelatex} programs; see +\url{http://scripts.sil.org/xetex}. + +MetaPost also received a notable update, with more planned for the +future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} +(\url{http://tug.org/applications/pdftex}) + +Of course the year also saw (the usual) hundreds of other updates to +packages and programs. As usual, please check \acro{CTAN} +(\url{http://www.ctan.org}) for updates. + +Internally, the source tree is now stored in Subversion, with a standard +web interface for viewing the tree, as linked from our home page. +Although not visible in the final distribution, we expect this will +provide a stable development foundation for future years. + + \subsection{Future} \emph{\TL{} is not perfect!} (And never will be.) We intend to -continue to release new versions yearly, and would like to provide more +continue to release new versions, and would like to provide more help material, more utilities, more installation programs, and (of course) an ever-improved and checked tree of macros and fonts. This work is all done by hard-pressed volunteers in their limited spare time, and @@ -3163,7 +3202,6 @@ your name forward! Please send corrections, suggestions, and offers of help to:\hfill\null \begin{quote} -Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ \email{tex-live@tug.org} \\ \url{http://tug.org/texlive} \end{quote} |