From 4abb80cf6528d7d687a0384efb2ce0a80ecc149e Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Mon, 16 May 2011 23:37:49 +0000 Subject: notes on portable & iso installs from siep git-svn-id: svn://tug.org/texlive/trunk@22502 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf/doc/texlive/texlive-en/tex-live.sty | 3 +- .../texmf/doc/texlive/texlive-en/texlive-en.html | 1315 +++++++++++--------- Master/texmf/doc/texlive/texlive-en/texlive-en.pdf | Bin 1015956 -> 1020125 bytes Master/texmf/doc/texlive/texlive-en/texlive-en.tex | 115 +- 4 files changed, 786 insertions(+), 647 deletions(-) (limited to 'Master/texmf/doc') diff --git a/Master/texmf/doc/texlive/texlive-en/tex-live.sty b/Master/texmf/doc/texlive/texlive-en/tex-live.sty index ef31ad23b4b..867884ff5f9 100644 --- a/Master/texmf/doc/texlive/texlive-en/tex-live.sty +++ b/Master/texmf/doc/texlive/texlive-en/tex-live.sty @@ -206,10 +206,11 @@ \providecommand*{\DVD}{\texorpdfstring{\acro{DVD}}{DVD}\xspace} \providecommand*{\GNU}{\acro{GNU}\xspace} \providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\ISO}{\acro{ISO}\xspace} +\providecommand*{\ISO}{\texorpdfstring{\acro{ISO}}{ISO}\xspace} \providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} \providecommand*{\PS}{Post\-Script\xspace} \providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\USB}{\texorpdfstring{\acro{USB}}{USB}\xspace} \providecommand*{\dvi}{\acro{DVI}\xspace} \providecommand*{\web}{\texttt{WEB}\xspace} diff --git a/Master/texmf/doc/texlive/texlive-en/texlive-en.html b/Master/texmf/doc/texlive/texlive-en/texlive-en.html index 5aacb4ab0f0..49ca3e0f84d 100644 --- a/Master/texmf/doc/texlive/texlive-en/texlive-en.html +++ b/Master/texmf/doc/texlive/texlive-en/texlive-en.html @@ -9,7 +9,7 @@ TeX Live 2011 - + @@ -31,7 +31,7 @@ class="ec-lmr-12">Karl Berry, editor href="http://tug.org/texlive/" class="url" >http://tug.org/texlive/
May 2011
+class="ec-lmr-12">June 2011

Contents

@@ -91,7 +91,7 @@ href="#x1-240003.2" id="QQ2-1-27">Running the installer
  3.2.1 Binary systems menu (Unix only)
  3.2.2 Selecting what is going to be installed +href="#x1-260003.2.2" id="QQ2-1-30">Selecting what is to be installed
  3.2.3 Directories
  3.2.4 Testing the installation
 3.6 Links for additional downloadable software
4 Network installations +href="#x1-410004" id="QQ2-1-48">Specialized installation considerations +
 4.1 Network (shared) installations +
 4.2 Portable (USB) installations +
 4.3 ISO (or DVD) installations
5 Maximally portable TEX Live on DVD and USB -
6 tlmgr: Managing your installation -
 6.1  5.1 tlmgr GUI mode -
 6.2 Sample  5.2 Sample tlmgr command-line invocations +
6 Notes on Windows +
 6.1 Windows-specific features +
 6.2 Additional software included on Windows +
 6.3 User Profile is Home +
 6.4 The Windows registry +
 6.5 Windows permissions +
 6.6 Increasing maximum memory on Windows and Cygwin
7 Notes on Windows +href="#x1-550007" id="QQ2-1-66">A user’s guide to Web2C
 7.1 Windows-specific features +href="#x1-560007.1" id="QQ2-1-67">Kpathsea path searching +
  7.1.1 Path sources +
  7.1.2 Config files +
  7.1.3 Path expansion +
  7.1.4 Default expansion +
  7.1.5 Brace expansion +
  7.1.6 Subdirectory expansion +
  7.1.7 List of special characters and their meaning: a summary
 7.2 Additional software included on Windows +href="#x1-640007.2" id="QQ2-1-75">Filename databases +
  7.2.1 The filename database +
  7.2.2 kpsewhich: Standalone path searching +
  7.2.3 Examples of use +
  7.2.4 Debugging actions
 7.3 User Profile is Home -
 7.4 The Windows registry -
 7.5 Windows permissions -
 7.6 Increasing maximum memory on Windows and Cygwin +href="#x1-690007.3" id="QQ2-1-83">Runtime options
8 A user’s guide to Web2C -
 8.1 Kpathsea path searching -
  8.1.1 Path sources -
  8.1.2 Config files -
  8.1.3 Path expansion -
  8.1.4 Default expansion -
  8.1.5 Brace expansion -
  8.1.6 Subdirectory expansion -
  8.1.7 List of special characters and their meaning: a summary -
 8.2 Filename databases -
  8.2.1 The filename database -
  8.2.2 kpsewhich: Standalone path searching -
  8.2.3 Examples of use -
  8.2.4 Debugging actions -
 8.3 Runtime options +href="#x1-700008" id="QQ2-1-84">Acknowledgements
9 Acknowledgements -
10 Release history -
 10.1 Past -
  10.1.1 2003 -
  10.1.2 2004 -
  10.1.3 2005 -
  10.1.4 2006–2007 -
  10.1.5 2008 -
  10.1.6 2009 -
 10.2 Present -
 10.3 Future +href="#x1-710009" id="QQ2-1-85">Release history +
 9.1 Past +
  9.1.1 2003 +
  9.1.2 2004 +
  9.1.3 2005 +
  9.1.4 2006–2007 +
  9.1.5 2008 +
  9.1.6 2009 +
 9.2 Present +
 9.3 Future

1 EX Collection

class="E">EX Live software distribution — TEX and related programs for GNU/Linux and other Unix flavors, Mac OS X, and Windows systems. + +

You may have acquired TEX Live by downloading, or on the TEX Collection DVD, which TEX Collection are cooperative efforts by the EX user groups. This document mainly describes TEX Live itself. - -

TEX Live includes executables for TEX, LaTeX2e, ConT

For a brief summary of the major changes in this edition of TEX Live, see the end of the document, section 10 (p. 69). +href="#x1-710009">9 (p. 71).

1.2 Operating system support

@@ -270,7 +273,7 @@ class="E">EX Live directly from the class="E">EX Collection DVD (or its .iso image), but you can prepare a runnable installation on, e.g., a USB stick (see section 5). Installation is described in later sections (p. 4.2). Installation is described in later sections (p. 12), but here is a quick start: -

For a much longer list of packages and programs, see

For a much longer list of packages and programs, see http://tug.org/interest.html. -

+

4 Network installations

-

TSpecialized installation considerations +

The previous sections describe the basic installation process. Here we turn to some specialized +cases. +

+

4.1 Network (shared) installations

+

TEX Live has been designed to be sharable between different users on one system, and/or between different systems on a network. With a standard directory layout, no hard paths are configured: the locations for files needed by T$TEXMFMAIN/web2c/texmf.cnf, which contains lines such as

  TEXMFMAIN = $SELFAUTOPARENT/texmf
  ...
  TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local
-

This means that adding the directory for T

This means that adding the directory for TEX Live executables for their platform to their search path is sufficient to get a working setup. -

By the same token, you can also install T

By the same token, you can also install TEX Live locally and then move the entire hierarchy afterwards to a network location. -

For Windows, a sample network installation script named

For Windows, a sample network installation script named w32client can be downloaded through EX Live installation on a LAN. It also registers an uninstaller w32unclient, available in the same zip file. See the web page for more information. -

-

5 Maximally portable TEX Live on DVD and USB

-

To use TEX Live in a “portable” way, minimizing impact on the host system, you should first install T

+

4.2 Portable (USB) installations

+

The -portable installer option creates a completely self-contained TeX Live installation under a common root +and forgoes system integration. You can create such an installation directly on a USB stick or copy it to a USB +stick afterwards. +

To actually run using this portable installation, you need to add the appropriate binary directory to the +search path during your terminal session, as usual. For Windows, you can double-click tl-tray-menu at the +root of the installation to choose between a few common tasks: + + +

+
  ...
  1 TeX Live command prompt
  2 Managing the installation
  3 TeXworks
  Q Quit
  ...
+
+

+

+

4.3 ISO (or DVD) installations

+

If you don’t need to update or otherwise modify your installation often, and/or have several systems on +which to use TEX Live, it may be convenient to create an ISO of your TEX Live installation, +because: +

+

Of course you can also burn an ISO to DVD, if that is useful for you. +

Desktop GNU/Linux/Unix systems, including Mac OS X, are able to mount an ISO. Apart from that, +nothing changes compared to a normal hard disk installation, see section 3.4.1. +

When preparing such an ISO installation, it is best not to omit the subdirectory for the release year, but +instead to have texmf-local at the same level as the other trees (texmf, texmf-dist, etc.). You can do this +with the normal directory options in the installer. +

For a physical (rather than virtual) Windows system, you can burn the ISO to DVD. However, it may be +worth your while to investigate free ISO-mounting options. For Windows XP, Microsoft offers tl-portable script (Unix) or tl-portable.bat batch file (Windows) from the resulting installation root to -start up a shell. -

You could also burn the resulting contents of the stick back to DVD if that is more convenient to (for -example) give to others. -

When the tl-portable script is run from a DVD for the first time, some files will be generated on the host -system in a directory ~/.tlportable2010, which will take some time. On subsequent runs, though, it will -start quickly. -

The rest of the system will be unaware of TEX Live. If you want your editor to be aware of this TEX Live, -then you should start it from a second, parallel, such tl-portable session. -

-

6 winxpvirtualcdcontrolpanel. +

For Windows system integration, you can include the w32client scripts described in section 4.1 and at +http://tug.org/texlive/w32client.html, which work just as well for an ISO as for a network +installation. +

On Mac OS X, TeXShop and TEXworks will be able to use the DVD installation if a symlink /usr/texbin +points to the appropriate binary directory, e.g., + + +

+
  sudo ln -s /Volumes/MyTeXLive/bin/universal-darwin /usr/texbin
+
+

+

Historical note: TEX Live 2010 was the first TEX Live edition which was no longer distributed ‘live’. +However, it always required some acrobatics to run from DVD or ISO; in particular, there was no way around +setting at least one extra environment variable. If you create your ISO from an existing installation then there +is no need for this. +

+

5 tlmgr: Managing your installation

-



+ id="x1-45001r8"> -

pict

Figure 8: tlmgr in GUI mode: main window, after ‘Load’.
+class="ec-lmss-10">tlmgr in GUI mode: main window, after ‘Load’.
-


-



+


+ id="x1-45002r9"> -

pict

Figure 9: tlmgr in GUI mode: General options
-

tlmgr in GUI mode: General options

+

pict

Figure 10: tlmgr in GUI mode: Paper -size options
+size options -


-

T


+

TEX Live includes a program named tlmgr for managing TEX Live after the initial installation. The @@ -3221,17 +3292,17 @@ the preferred interface. Its capabilities include:

  • changing installation options such as paper size and source location (see section 3.3.1).
  • -

    Warning: tlmgr has not been designed for or tested with portable installations (section 5). -

    6.1 4.2). +

    5.1 tlmgr GUI mode

    -

    tlmgr can be started in GUI mode (figure 8) with

    -

    +href="#x1-45001r8">8) with
    +

    > TeX Live 2010, TeX Live Manager. After clicking ‘Load’ it displays a list of available and installed packages. This assumes of course that the installation source is valid and reachable. -

    Figures 9 and 10 show the general and paper size option screens. -

    -

    6.2 Sample

    Figures 9 and 10 show the general and paper size option screens. +

    +

    5.2 Sample tlmgr command-line invocations

    -

    After the initial installation, you can update your system to the latest versions available with: +

    After the initial installation, you can update your system to the latest versions available with:

    -

    +

    >  update -all
    If this makes you nervous, first try
    -

    +

    >  -all -dry-run
    or (less verbose):
    -

    +

    >  update -list
    -

    This more complex example adds a collection, for the engine XeT

    This more complex example adds a collection, for the engine XeTEX, from a local directory:

    -

    +

    >  collection-xetex
    It generates the following output (abridged): -
      install: collection-xetex
      install: arabxetex
      ...
      install: xetex
      install: xetexconfig
      install: xetex.i386-linux
      running post install action for xetex
      install: xetex-def
      ...
      running mktexlsr
      mktexlsr: Updating /usr/local/texlive/2010/texmf/ls-R...
      ...
      running fmtutil-sys --missing
      ...
      Transcript written on xelatex.log.
      fmtutil: /usr/local/texlive/2010/texmf-var/web2c/xetex/xelatex.fmt installed.
    -

    As you can see,

    As you can see, tlmgr installs dependencies, and takes care of any necessary post-install actions, including updating the filename database and (re)generating formats. In the above, we generated new formats for XeTEX. -

    To describe a package (or collection or scheme):

    -

    +

    To describe a package (or collection or scheme):

    +

    >  show collection-latexextra
    which produces -
      package:    collection-latexextra
      category:   Collection
      shortdesc:  LaTeX supplementary packages
      longdesc:  add-on packages for LaTeX.
      installed:  Yes
      revision:   14675
    -

    Last and most important, for full documentation see

    Last and most important, for full documentation see http://tug.org/texlive/tlmgr.html, or:

    -

    +

    > tlmgr -help
    -

    -

    7 Notes on Windows

    -

    T

    +

    6 Notes on Windows

    +

    TEX Live has a single installer which runs on both Windows and Unix. This was only possible by dropping support for older Windows versions, so TEX Live can now be installed only on Windows 2000 and later. -

    -

    7.1 Windows-specific features

    -

    Under Windows, the installer does some extra things: +

    +

    6.1 Windows-specific features

    +

    Under Windows, the installer does some extra things:

    Menus and shortcuts.
    EX Live. The uninstall class="E">EX Live Manager GUI refers to this.
    -

    -

    7.2 Additional software included on Windows

    -

    To be complete, a T

    +

    6.2 Additional software included on Windows

    +

    To be complete, a TEX Live installation needs support packages that are not commonly found on a Windows machine. TEX Live provides the missing pieces: @@ -3501,16 +3572,16 @@ class="E">EX Live programs that need them know where to find them, PS_View.

    Also installed is PS_View, a PostScript and PDF viewer; see figure 11. -


    11. +


    pict
    Figure 11: PS_View: very high magnifications available!
    -


    +class="content">PS_View: very high magnifications available!
    +


    dviout.
    \font command. If necessary, run fc-cache first to update font information.
    -

    -

    7.3 User Profile is Home

    -

    The Windows counterpart of a Unix home directory is the

    +

    6.3 User Profile is Home

    +

    The Windows counterpart of a Unix home directory is the %USERPROFILE% directory. Under Windows XP and Windows 2000, this is usually C:\DocumentsC:\Users\<username>. In th class="ec-lmtt-10">texmf.cnf file, and Kpathsea in general, ~ will expand appropriately on both Windows and Unix. -

    -

    7.4 The Windows registry

    -

    Windows stores nearly all configuration data in its registry. The registry contains a set of hierarchically +

    +

    6.4 The Windows registry

    +

    Windows stores nearly all configuration data in its registry. The registry contains a set of hierarchically organized keys, with several root keys. The most important ones for installation programs are HKEY_CURRENT_USER and HKCU and HKLM in short. The HKCU part of the registry is in the user’s home directory (see section 7.3). 6.3). HKLM is normally in a subdirectory of the Windows directory. -

    In some cases, system information could be obtained from environment variables but for other information, +

    In some cases, system information could be obtained from environment variables but for other information, for example the location of shortcuts, it is necessary to consult the registry. Setting environment variables permanently also requires registry access. -

    -

    7.5 Windows permissions

    -

    In later versions of Windows, a distinction is made between regular users and administrators, where only the +

    +

    6.5 Windows permissions

    +

    In later versions of Windows, a distinction is made between regular users and administrators, where only the latter have free access to the entire operating system. In practice, though, you could better describe these classes of users as unprivileged users and normal users: being an administrator is the rule, not the exception. Nevertheless, we have made an effort to make TEX Live installable without administrative privileges. -

    If the user is an administrator, there is an option to install for all users. If this option is chosen, shortcuts +

    If the user is an administrator, there is an option to install for all users. If this option is chosen, shortcuts are created for all users, and the system environment is modified. Otherwise, shortcuts and menu entries are created for the current user, and the user environment is modified. -

    Regardless of administrator status, the default root of T

    Regardless of administrator status, the default root of TEX Live proposed by the installer is always under %SystemDrive%. The installer always tests whether the root is writable for the current user. -

    A problem may arise if the user is not an administrator and T

    A problem may arise if the user is not an administrator and TEX already exists in the search path. Since the effective path consists of the system path followed by the user path, the new TEX Live would @@ -3625,14 +3696,14 @@ class="E">EXworks, if installed, also prepends TEX Live to the search path, so it should also be immune to this path problem. -

    For Vista there is another twist: even if you are logged in as administrator, you need to explicitly ask for +

    For Vista there is another twist: even if you are logged in as administrator, you need to explicitly ask for administrator privileges. In fact, there is not much point in logging in as administrator. Instead, right-clicking on the program or shortcut that you want to run usually gives you a choice ‘Run as administrator’. -

    -

    7.6 Increasing maximum memory on Windows and Cygwin

    -

    Windows and Cygwin (see section 

    +

    6.6 Increasing maximum memory on Windows and Cygwin

    +

    Windows and Cygwin (see section 3.1.4 for Cygwin installation specifics) users may find that they run out of memory when running some of the programs shipped with TEX Live. For example, asy might run out of memory if you try to allocate an array of 25,000,000 reals, and LuaTEX might run out of memory if you try to process a document with a lot of big fonts. -

    For Cygwin, you can increase the amount of available memory by following the instructions in the Cygwin +

    For Cygwin, you can increase the amount of available memory by following the instructions in the Cygwin User’s Guide (http://www.cygwin.com/cygwin-ug-net/setup-maxmem.html). -

    For Windows, you have to create a file, say

    For Windows, you have to create a file, say moremem.reg, with these four lines: -

    -

    +

      Windows Registry Editor Version 5.00
      
      [HKEY_LOCAL_MACHINE\Software\Cygwin]
      "heap_chunk_in_mb"=dword:ffffff00
    -

    and then execute the command

    and then execute the command regedit /s moremem.reg as administrator. (If you want to change memory only for the current user instead of system-wide, use HKEY_CURRENT_USER.) -

    -

    8 A user’s guide to Web2C

    -

    Web2C is an integrated collection of T

    +

    7 A user’s guide to Web2C

    +

    Web2C is an integrated collection of TEX-related programs: TEX itself, Metafont, MetaPost, BibTeX, etc. It is the heart of TEX Live. The home page for Web2C, with the current manua http://tug.org/web2c. -

    A bit of history: The original implementation was by Tomas Rokicki who, in 1987, developed a first +

    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, who returned it to Karl in 2006. -

    The Web2C system runs on Unix, 32-bit Windows systems, Mac OS X, and other operating systems. It uses +

    The Web2C system runs on Unix, 32-bit Windows systems, Mac OS X, and other operating systems. It uses Knuth’s original sources for TEX and other basic programs written in the WEB literate programming system and translates them into C source code. The core TEX programs handled in this way are: -

    +

    bibtex
    -

    Maintaining bibliographies. +

    Maintaining bibliographies.

    dvicopy
    -

    Expands virtual font references in DVI files. +

    Expands virtual font references in DVI files.

    dvitomp
    -

    DVI to MPX (MetaPost pictures). +

    DVI to MPX (MetaPost pictures).

    dvitype
    -

    DVI to human-readable text. +

    DVI to human-readable text.

    gftodvi
    -

    Generic font proofsheets. +

    Generic font proofsheets.

    gftopk
    -

    Generic to packed fonts. +

    Generic to packed fonts.

    gftype
    -

    GF to human-readable text. +

    GF to human-readable text.

    mf
    -

    Creating typeface families. +

    Creating typeface families.

    mft
    -

    Prettyprinting Metafont source. +

    Prettyprinting Metafont source.

    mpost
    -

    Creating technical diagrams. +

    Creating technical diagrams.

    patgen
    -

    Creating hyphenation patterns. +

    Creating hyphenation patterns.

    pktogf
    -

    Packed to generic fonts. +

    Packed to generic fonts.

    pktype
    -

    PK to human-readable text. +

    PK to human-readable text.

    pltotf
    -

    Plain text property list to TFM. +

    Plain text property list to TFM.

    pooltype
    -

    Display

    Display WEB pool files.

    tangle
    -

    WEB to Pascal. @@ -3784,49 +3855,49 @@ class="ec-lmtt-10">WEB to Pascal. tex

    -

    Typesetting. +

    Typesetting.

    tftopl
    -

    TFM to plain text property list. +

    TFM to plain text property list.

    vftovp
    -

    Virtual font to virtual property list. +

    Virtual font to virtual property list.

    vptovf
    -

    Virtual property list to virtual font. +

    Virtual property list to virtual font.

    weave
    -

    WEB to TEX.

    -

    The precise functions and syntax of these programs are described in the documentation of the individual +

    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. -

    All programs honor these standard GNU options: +

    All programs honor these standard GNU options:

    --help
    -

    print basic usage summary. +

    print basic usage summary.

    --verbose
    -

    print detailed progress report. +

    print detailed progress report.

    --version
    -

    print version information, then exit.

    -

    For locating files the Web2C programs use the path searching library Kpathsea (

    print version information, then exit. +

    For locating files the Web2C programs use the path searching library Kpathsea (http://tug.org/kpathsea). This library uses a combination of environment variables and a configuration files to optimize searching the @@ -3837,11 +3908,11 @@ class="E">EX’s standard distribution and local and personal searches, the root of each tree has a file ls-R, containing an entry showing the name and relative pathname for all files under that root. -

    -

    8.1 Kpathsea path searching

    -

    Let us first describe the generic path searching mechanism of the Kpathsea library. -

    We call a

    +

    7.1 Kpathsea path searching

    +

    Let us first describe the generic path searching mechanism of the Kpathsea library. +

    We call a search path a colon- or semicolon-separated list of path elements, which are basically directory names. A search path can come from (a combination of) many sources. To look up a file ‘.:/dir’, Kpathsea checks each element of the pat class="ec-lmtt-10">./my-file, then /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 Kpathsea can use +

    In order to adapt optimally to all operating systems’ conventions, on non-Unix systems Kpathsea can use filename separators different from colon (‘:’) and slash (‘/’). -

    To check a particular path element

    To check a particular path element p, Kpathsea first checks if a prebuilt database (see “Filename database” on page 59) applies to 61) applies to p, i.e., if the database is in a directory that is a prefix of 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 +

    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 ‘!!’ 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. -

    The “file must exist” condition comes into play with ‘

    The “file must exist” condition comes into play with ‘.vf’ files and input files read by TEX’s \openin @@ -3880,25 +3951,25 @@ class="ec-lmtt-10">ls-R when you install a new ‘.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, Kpathsea supports additional +

    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 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 ‘

    Note that if the filename being searched for is absolute or explicitly relative, i.e., starts with ‘/’ or ‘./’ or ‘../’, Kpathsea simply checks if that file exists. -

    -

    8.1.1 Path sources
    -

    A search path can come from many sources. In the order in which Kpathsea uses them: -

    +

    +

    7.1.1 Path sources
    +

    A search path can come from many sources. In the order in which Kpathsea uses them: +

    1. A user-set environment variable, for instance, A user-set environment variable, for instance, TEXINPUTS. Environment variables with a period and a program name appended override; e.g., if ‘latex’ is the name of the program being run, @@ -3907,37 +3978,37 @@ class="ec-lmtt-10">TEXINPUTS.latex will override TEXINPUTS.
    2. A program-specific configuration file, for example, a line ‘A program-specific configuration file, for example, a line ‘S /a:/b’ in dvips’s config.ps.
    3. A Kpathsea configuration file A Kpathsea configuration file texmf.cnf, containing a line like ‘TEXINPUTS=/c:/d’ (see below).
    4. The compile-time default.
    -

    You can see each of these values for a given search path by using the debugging options (see “Debugging actions” + class="enumerate" id="x1-57008x4">The compile-time default. +

    You can see each of these values for a given search path by using the debugging options (see “Debugging actions” on page 62). -

    -

    8.1.2 Config files
    -

    Kpathsea reads 64). +

    +

    7.1.2 Config files
    +

    Kpathsea reads runtime configuration files named texmf.cnf for search path and other definitions. The search path used to look for these files is named TEXMFCNF, but we do not recommend setting this (or any) environment variable. -

    Instead, normal installation results in a file

    Instead, normal installation results in a file .../2010/texmf.cnf. If you must make changes to the defaults (not normally necessary), this is the place to put them. The main configuration file is in .../2010/texmf/web2c/texmf.cnf. You should not edit this latter file, as your changes will be lost when the distributed version is updated. -

    All texmf.cnf files in the search path will be read and definitions in earlier files override those in later files. For example, with a search path of \ at the end of a line acts as a continuation characte

  • Each remaining line has the form:
    -

    +

      texmf.cnf for Unix, MS-DOS and Windows
  • All definitions are read before anything is expanded, so variables can be referenced before they are defined.
  • -

    A configuration file fragment illustrating most of these points is shown below: -

    -

    +

    A configuration file fragment illustrating most of these points is shown below: +

    +

      TEXMF   = {$TEXMFLOCAL,!!$TEXMFMAIN}
      TEXINPUTS.latex   = .;$TEXMF/tex/{latex,generic;}//
      TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm//
      % e-TeX related files
      TEXINPUTS.elatex   = .;$TEXMF/{etex,tex}/{latex,generic;}//
      TEXINPUTS.etex   = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}//
    -

    -

    8.1.3 Path expansion
    -

    Kpathsea recognizes certain special characters and constructions in search paths, similar to those available in +

    +

    7.1.3 Path expansion
    +

    Kpathsea recognizes certain special characters and constructions in search paths, similar to those available in Unix shells. As a general example, the complex path, ~$USER/{foo,bar}//baz, expands to all subdirectories under directories bar in $USER’s home directory that contain a directory or file baz. These expansions are explained in the sections below. -

    8.1.4 Default expansion
    -

    If the highest-priority search path (see “Path sources” on page 54) contains an 7.1.4 Default expansion

    +

    If the highest-priority search path (see “Path sources” on page 56) contains an extra colon (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

    -

    +

    >  /home/karl: class="ec-lmtt-10">TEXINPUTS value from texmf.cnf of
    -

    +

      .:$TEXMF//tex @@ -4113,23 +4184,23 @@ class="ec-lmtt-10"> .:$TEXMF//tex
    then the final value used for searching will be:
    -

    +

      /home/karl:.:$TEXMF//tex
    -

    Since it would be useless to insert the default value in more than one place, Kpathsea changes only one +

    Since it would be useless to insert the default value in more than one place, Kpathsea changes only one extra ‘:’ and leaves any others in place. It checks first for a leading ‘:’, then a trailing ‘:’, then a doubled ‘:’. -

    -

    8.1.5 Brace expansion
    -

    A useful feature is brace expansion, which means that, for instance,

    +

    7.1.5 Brace expansion
    +

    A useful feature is brace expansion, which means that, for instance, v{a,b}w expands to vaw:vbw. Nesting is allowed. This is used to implement multiple Ttexmf.cnf, a definition like this (simplified for this made: -

    -
        TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN}
    +
    +
        TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN}
    -

    Using this you can then write something like +

    Using this you can then write something like -

    -
        TEXINPUTS = .;$TEXMF/tex//
    +
    +
        TEXINPUTS = .;$TEXMF/tex//
    -

    which means that, after looking in the current directory, the

    which means that, after looking in the current directory, the $TEXMFHOME/tex, $TEXMFLOCAL/tex, $TEXMF variable in all definitions, one is sure to always search the up-to-date tree first. -

    -

    8.1.6 Subdirectory expansion
    -

    Two or more consecutive slashes in a path element following a directory

    +

    7.1.6 Subdirectory expansion
    +

    Two or more consecutive slashes in a path element following a directory d is replaced by all subdirectories of d: first those subdirectories directly under d, then the subsubdirectories under those, and so on. At each level, the order in which the directories are searched is unspecified. -

    If you specify any filename components after the ‘

    If you specify any filename components after the ‘//’, only subdirectories with matching components are included. For example, ‘/a//b’ expands into directories /a/1/1/b, and so on, but not /a/b/c or /a/1. -

    Multiple ‘

    Multiple ‘//’ constructs in a path are possible, but ‘//’ at the beginning of a path is ignored. -

    -

    8.1.7 List of special characters and their meaning: a summary
    -

    The following list summarizes the special characters in Kpathsea configuration files. -

    +

    +

    7.1.7 List of special characters and their meaning: a summary
    +

    The following list summarizes the special characters in Kpathsea configuration files. +

    :
    -

    Separator in path specification; at the beginning or the end of a path it substitutes the default +

    Separator in path specification; at the beginning or the end of a path it substitutes the default path expansion.

    ;
    -

    Separator on non-Unix systems (acts like

    Separator on non-Unix systems (acts like :).

    $
    -

    Variable expansion. +

    Variable expansion.

    ~
    -

    Represents the user’s home directory. +

    Represents the user’s home directory.

    {...}
    -

    Brace expansion. +

    Brace expansion.

    //
    -

    Subdirectory expansion (can occur anywhere in a path, except at its beginning). +

    Subdirectory expansion (can occur anywhere in a path, except at its beginning).

    %
    -

    Start of comment. +

    Start of comment.

    \
    -

    Continuation character (allows multi-line entries). +

    Continuation character (allows multi-line entries).

    !!
    -

    Search

    Search only database to locate file, do not search the disk.

    -

    -

    8.2 Filename databases

    -

    Kpathsea goes to some lengths to minimize disk accesses for searches. Nevertheless, at installations with +

    +

    7.2 Filename databases

    +

    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 ls-R that maps files to directories, thus avoiding the need to exhaustively search the disk. -

    A second database file

    A second database file aliases allows you to give additional names to the files listed in ls-R. This can be helpful to confirm to DOS 8.3 filename conventions in source files. -

    -

    8.2.1 The filename database
    -

    As explained above, the name of the main filename database must be

    +

    7.2.1 The filename database
    +

    As explained above, the name of the main filename database must be ls-R. You can put one at the root of each TEX hierarchy in your installation that you wish to be searched ($TEXMF by default). Kpathsea looks for ls-R files along the TEXMFDBS path. -

    The recommended way to create and maintain ‘

    The recommended way to create and maintain ‘ls-R’ is to run the mktexlsr script included with the distribution. It is invoked by the various ‘mktex’… scripts. In principle, this script just runs the command

    -

    +

    cd 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 Kpathsea goes ahead and searches the disk. If a particular +

    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 ‘!!’, however, only the database will be searched for that element, never the disk. -

    -

    8.2.2 kpsewhich: Standalone path searching
    -

    The

    +

    7.2.2 kpsewhich: Standalone path searching
    +

    The kpsewhich program exercises path searching independent of any particular application. This can be useful as a sort of find program to locate files in TEX hierarchies (this is used heavily in the distributed ‘mktex’… scripts).

    -

    +

    > option start with either ‘-’ or ‘--’, and any unambiguous abbreviation is accepted. -

    Kpathsea looks up each non-option argument on the command line as a filename, and returns the first file +

    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 ‘find’ utility for that). -

    The most common options are described next. -

    +

    The most common options are described next. +

    --dpi=num
    -

    Set the resolution to

    Set the resolution to num; this only affects ‘gf’ and ‘pk’ lookups. ‘dvips. Default is 600. class="ec-lmtt-10">--format=name

    -



    Set the format for lookup to name. By default, the format is guessed from the filename. For formats which do not have an associated unambiguous suffix, such as MetaPost support files and @@ -4369,7 +4440,7 @@ class="ec-lmtt-10">kpsewhich --help for a list. class="ec-lmtt-10">--mode=string

    -



    Set the mode name to string; this only affects ‘gf’ and ‘pk’ lookups. No default: any mode will --must-exist

    -



    Do everything possible to find the files, notably including searching the disk. By default, only the ls-R database is checked, in the interest of efficiency. @@ -4388,7 +4459,7 @@ class="ec-lmtt-10">ls-R database is checked, in the interest of efficienc class="ec-lmtt-10">--path=string

    -



    Search along the path string (colon-separated as usual), instead of guessing the search path from the filename. ‘--format’ class="ec-lmtt-10">--progname=name

    -



    Set the program name to name. This can affect the search paths via the .kpsewhich. class="ec-lmtt-10">--show-path=name

    -



    shows the path used for file lookups of file type name. Either a filename extension (.pk, --format’ option. class="ec-lmtt-10">--debug=num

    -



    sets the debugging options to num.

    -

    -

    8.2.3 Examples of use
    -

    Let us now have a look at Kpathsea in action. Here’s a straightforward search: +

    +

    7.2.3 Examples of use
    +

    Let us now have a look at Kpathsea in action. Here’s a straightforward search:

    -

    +

    > EX Live directory. Similarly, all of the followin problems thanks to their unambiguous suffix.
    -

    +

    >   /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib
    -

    By the way, that last is a BibTeX bibliography database for

    By the way, that last is a BibTeX bibliography database for TUGboat articles.

    -

    +

    > .pk’ files in TEX Live — the Type 1 variants are used by default.
    -

    +

    > .pk’ files, and since the default Metafont mode on our installation is ljfour with a base resolution of 600dpi (dots per inch), this instantiation is returned.
    -

    +

    > xdvi would go off and actually build the required .pk files using the script mktexpk. -

    Next we turn our attention to

    Next we turn our attention to dvips’s header and configuration files. We first look at one of the commonly used files, the general prologue tex.pro for Tdvips config) for the file config.ps.

    -

    +

    >  /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map
    -

    We now take a closer look at the URW Times PostScript support files. The prefix for these in the standard +

    We now take a closer look at the URW Times PostScript support files. The prefix for these in the standard font naming scheme is ‘utm’. The first file we look at is the configuration file, which contains the name of the map file:

    -

    +

    >   /usr/local/texmf-dist/dvips/psnfss/config.utm
    The contents of that file is
    -

    +

      p +utm.map
    which points to the file utm.map, which we want to locate next.
    -

    +

    >  /usr/local/texmf-dist/fonts/map/dvips/times/utm.map
    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):
    -

    +

    utmb8r  <utmr8a.pfb class="ec-lmtt-10">utmr8a.pfb and find its position in the texmf directory tree with a search for Type 1 font files:
    -

    +

    >   /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb
    -

    It should be evident from these examples how you can easily locate the whereabouts of a given file. This is +

    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 kpsewhich will show you the first file encountered. -

    -

    8.2.4 Debugging actions
    -

    Sometimes it is necessary to investigate how a program resolves file references. To make this practical, +

    +

    7.2.4 Debugging actions
    +

    Sometimes it is necessary to investigate how a program resolves file references. To make this practical, Kpathsea offers various levels of debugging output: -

    +

     1
    -

    stat calls (disk lookups). When running with an up-to-date ls-R database this should almost give no output. @@ -4727,68 +4798,68 @@ class="ec-lmtt-10">ls-R database this should almost  2

    -

    References to hash tables (such as

    References to hash tables (such as ls-R databases, map files, configuration files).

     4
    -

    File open and close operations. +

    File open and close operations.

     8
    -

    General path information for file types searched by Kpathsea. This is useful to find out where a +

    General path information for file types searched by Kpathsea. This is useful to find out where a particular path for the file was defined.

    16
    -

    Directory list for each path element (only relevant for searches on disk). +

    Directory list for each path element (only relevant for searches on disk).

    32
    -

    File searches. +

    File searches.

    64
    -

    Variable values.

    -

    A value of

    Variable values. +

    A value of -1 will set all the above options; in practice, this is usually the most convenient. -

    Similarly, with the

    Similarly, with the 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 Kpathsea library internally, one can select a debug option by +

    Generally speaking, as most programs call the Kpathsea library internally, one can select a debug option by using the 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 +

    (Note for Windows users: it is not easy to redirect all messages to a file in this system. For diagnostic purposes you can temporarily SET KPATHSEA_DEBUG_OUTPUT=err.log). -

    Let us consider, as an example, a small LAT

    Let us consider, as an example, a small LATEX source file, hello-world.tex, which contains the following input. -

    -
        \documentclass{article}
        \begin{document}
        Hello World!
        \end{document}
    +
    +
        \documentclass{article}
        \begin{document}
        Hello World!
        \end{document}
    -

    This little file only uses the font

    This little file only uses the font cmr10, so let us look at how dvips prepares the PostScript file (we want to use the Type 1 version of the Computer Modern fonts, hence the option -Pcms).

    -

    +

    > dvips’s debug class 4 (font paths) with Kpathsea class="ec-lmss-10">dvips Reference Manual, texmf/doc/dvips/dvips.pdf). The output (slightly rearranged) appears in Figure 12. -


    12. +


    @@ -4882,7 +4953,7 @@ class="ec-lmtt-9">kdebug:search(config.cms)
    =>/usr/local/texmf/dvips/cms/config.cms
    Figure 12: Finding configuration files
    +class="content">Finding configuration files
    kdebug:start search(file=texc.pro, => /usr/local/texmf/dvips/base/texc.pro
    Figure 13: Finding the prolog file
    +class="content">Finding the prolog file
    kdebug:start search(file=cmr10.tfm, /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb<cmr10.pfb>[1]
    Figure 14: Finding the font file
    +class="content">Finding the font file

    -

    dvips starts by locating its working files. First, texmf.cnf is found, which gives the definitions of the search paths for the other files, then the file database dvips command). This file contains the list of the map files which define the relation between the TEX, PostScript and file system names of the fonts.

    -

    +

    >  +amsbkm.map class="ec-lmss-10">dvips thus goes on to find all these files, plus the generic map file psfonts.map, which is always loaded (it contains declarations for commonly used PostScript fonts; see the last part of Section 8.2.3 for more details +href="#x1-670007.2.3">7.2.3 for more details about PostScript map file handling). -

    At this point

    At this point dvips identifies itself to the user:

    -

    +

    This is (www.radicaleye.com)
    Then it goes on to look for the prolog file texc.pro:
    -

    +


    kdebug:start search(file=texc.pro, => /usr/local/texmf/dvips/base/texc.pro
    -

    After having found the file in question,

    After having found the file in question, dvips outputs the date and time, and informs us that it will generate the file hello-world.ps, then that it needs the font file cmr10, and that the latter is declared as “resident” (no bitmaps needed):

    -

    +


    TeX outputcmr10.tfm, which is found, then a few more prolog file referenced, and finally the Type 1 instance cmr10.pfb of the font is located and included in the output file (see last line).
    -

    +


    kdebug:start search(file=cmr10.tfm, /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb<cmr10.pfb>[1]
    -

    8.3 Runtime options

    -

    Another useful feature of Web2C is its possibility to control a number of memory parameters (in particular, +

    7.3 Runtime options

    +

    Another useful feature of Web2C is its possibility to control a number of memory parameters (in particular, array sizes) via the runtime file texmf.cnf read by Kpathsea. The memory settings can be found in Part 3 of that file in the TEX Live distribution. The more important are: -

    +

    main_memory
    -

    Total words of memory available, for T

    Total words of memory available, for TEX, Metafont and MetaPost. You must make a new format file for each different setting. For instance, you could generate a “huge” version of TEX, and call @@ -5161,7 +5232,7 @@ class="ec-lmtt-10">texmf.cnf. extra_mem_bot

    -

    Extra space for “large” T

    Extra space for “large” TEX data structures: boxes, glue, breakpoints, etc. Especially useful if you use PI CTEX. @@ -5169,27 +5240,27 @@ class="E">EX. font_mem_size

    -

    Number of words for font information available for T

    Number of words for font information available for TEX. This is more or less the total size of all TFM files read.

    hash_extra
    -

    Additional space for the hash table of control sequence names. Only

    Additional space for the hash table of control sequence names. Only 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 hash_extra is 50000.

    -

    Of course, this facility is no substitute for truly dynamic arrays and memory allocation, but since these are +

    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. -

    -

    9 Acknowledgements

    -

    T

    +

    8 Acknowledgements

    +

    TEX Live is a joint effort by virtually all of the TEX user groups. This edition of TEX Live was overseen by @@ -5353,7 +5424,7 @@ class="E">EX Live, and coordinator of the many

  • Graham Williams, on whose work the TEX Catalogue of packages depends.
  • -

    Builders of the binaries: Alan Braslau (

    Builders of the binaries: Alan Braslau (amd64-kfreebsd, i386-kfreebsd), Peter Breitenlohner (x86_64-linux), @@ -5381,23 +5452,23 @@ class="E">EX Live build process, see http://tug.org/texlive/build.html. -

    Current documentation translators: Boris Veytsman (Russian), Jjgod Jiang, Jinsong Zhao, Yue Wang, & +

    Current documentation translators: Boris Veytsman (Russian), Jjgod Jiang, Jinsong Zhao, Yue Wang, & Helin Gai (Chinese), Klaus Höppner (German), Manuel Pégourié-Gonnard (French), Marco Pallante (Italian), Nikola Lečić (Serbian), Petr Sojka & Jan Busa (Czech/Slovak), Staszek Wawrykiewicz (Polish). The TEX Live documentation web page is http://tug.org/texlive/doc.html. -

    Of course the most important acknowledgement must go to Donald Knuth, first for inventing T

    Of course the most important acknowledgement must go to Donald Knuth, first for inventing TEX, and then for giving it to the world. -

    -

    10 Release history

    -

    -

    10.1 Past

    -

    Discussion began in late 1993 when the Dutch T

    +

    9 Release history

    +

    +

    9.1 Past

    +

    Discussion began in late 1993 when the Dutch TEX Users Group was starting work on its 4AllTEX CD for MS-DOS users, and it was hoped at that time to issue a single, rational, CD for all systems. This was too @@ -5421,7 +5492,7 @@ class="E">EX CD showed that Unix users would benefit from a similarly easy system, and this is the other main strand of TEX Live. -

    We first undertook to make a new Unix-based TDS CD in the autumn of 1995, and quickly identified +

    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 @@ -5441,7 +5512,7 @@ included almost all of its features. The 4th edition followed the same pattern, of teTEX, and a new release of Web2C (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 +

    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 Thttp://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 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 language.dat. -

    The 7th edition of 2002 had the notable addition of Mac OS X support, and the usual myriad of updates to +

    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 teTEX, to correct the drift apart in versions 5 and 6. -

    -

    10.1.1 2003
    -

    In 2003, with the continuing flood of updates and additions, we found that T

    +

    9.1.1 2003
    +

    In 2003, with the continuing flood of updates and additions, we found that TEX 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 2.1, @@ -5520,16 +5591,16 @@ class="ec-lmtt-10">texmf/web2c/cp8bit.tcx. (Future releases class="E">EX Live 2003. -

    -

    10.1.2 2004
    -

    2004 saw many changes: +

    +

    9.1.2 2004
    +

    2004 saw many changes:

    • If you have locally-installed fonts which use their own .map or (much less likely) .enc support files, you may need to move those support files. -

      .map files are now searched for in subdirectories of fonts/map only (in each texmf tree), along @@ -5540,7 +5611,7 @@ class="ec-lmtt-10">fonts/enc only, along the ENCFONTS path. updmap will attempt to warn about problematic files. -

      For methods of handling this and other information, please see +

      For methods of handling this and other information, please see http://tug.org/texlive/mapenc.html. @@ -5616,7 +5687,7 @@ class="E">EXt, etc., as well as the e-TEX features (texmf-dist/doc/etex/base/). -

      It also means it’s

      It also means it’s more important than ever to use the ifpdf package (works with both plain and LATmpost) now accepts double quotes containing spaces and special characters. Typical examples: -

      -
        \input "filename with spaces"   % plain
        \input{"filename with spaces"}  % latex
      +
      +
        \input "filename with spaces"   % plain
        \input{"filename with spaces"}  % latex
      -

      See the Web2C manual for more:

      See the Web2C manual for more: texmf/doc/web2c.

    • encTt1utils programs. This is because they are compiled wi class="ec-lmss-10">mips-irix, the MIPSpro 7.4 runtimes are required.
    -

    -

    10.1.3 2005
    -

    2005 saw the usual huge number of updates to packages and programs. The infrastructure stayed relatively +

    +

    9.1.3 2005
    +

    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:

    • New scripts ^^ notation if you so desire, as in: -
      -
        latex --translate-file=empty.tcx yourfile.tex
      +
      +
        latex --translate-file=empty.tcx yourfile.tex
      -

      +

    • The new program dvipdfmx is included for translation of DVI to PDF; this is an actively maintained @@ -5829,10 +5900,10 @@ class="ec-lmtt-10">TEXMFSYSVAR, respectively. There is also TEXMFVAR, which is by default user-specific. See the first point above.
    -

    -

    10.1.4 2006–2007
    -

    In 2006–2007, the major new addition to T

    +

    9.1.4 2006–2007
    +

    In 2006–2007, the major new addition to TEX Live was the XeTEX program, available as the xetex and @@ -5840,14 +5911,14 @@ class="ec-lmtt-10">xetex and class="ec-lmtt-10">xelatex programs; see http://scripts.sil.org/xetex. -

    MetaPost also received a notable update, with more planned for the future (

    MetaPost also received a notable update, with more planned for the future (http://tug.org/metapost/articles), likewise pdfTEX (http://tug.org/applications/pdftex). -

    The T

    The TEX .fmt (high-speed format) and the similar files for MetaPost and Metafont are now stored in subdirectories of tex or pdftex or xetex. This change should be invisible in normal use. -

    The (plain)

    The (plain) tex program no longer reads %& first lines to determine what format to run; it is the pure Knuthian TEX. (LATEX and everything else do still read %& lines). -

    Of course the year also saw (the usual) hundreds of other updates to packages and programs. As usual, +

    Of course the year also saw (the usual) hundreds of other updates to packages and programs. As usual, please check CTAN (http://www.ctan.org) for updates. -

    Internally, the source tree is now stored in Subversion, with a standard web interface for viewing the tree, +

    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. -

    Finally, in May 2006 Thomas Esser announced that he would no longer be updating teT

    Finally, in May 2006 Thomas Esser announced that he would no longer be updating teTEX (EX Live, which provides an approximate equivalent.) We hope this will eventually translate to improvements in the TEX environment for everyone. -

    -

    10.1.5 2008
    -

    In 2008, the entire T

    +

    9.1.5 2008
    +

    In 2008, the entire TEX Live infrastructure was redesigned and reimplemented. Complete information about an installation is now stored in a plain text file tlpkg/texlive.tlpdb. -

    Among other things, this finally makes possible upgrading a T

    Among other things, this finally makes possible upgrading a TEX Live installation over the Internet after the initial installation, a feature MiKTEX has provided for many years. We expect to regularly update new packages as they are released to CTAN. -

    The major new engine LuaT

    The major new engine LuaTEX (http://luatex.org) is included; besides a new level of flexibility in typesetting, this provides an excellent scripting language for use both inside and outside of TEX documents. -

    Support among Windows and the Unix-based platforms is now much more uniform. In particular, most +

    Support among Windows and the Unix-based platforms is now much more uniform. In particular, most Perl and Lua scripts are now available on Windows, using the Perl internally distributed with TEX Live. -

    The new

    The new tlmgr script (section 6) is the general interface for managing T5) is the general interface for managing TEX Live after the initial installation. It handles package updates and consequent regeneration of formats, map files, and language files, optionally including local additions. -

    With the advent of

    With the advent of tlmgr, the texconfig actions to edit the format and hyphenation configuration files are now disabled. -

    The

    The xindy indexing program (http://xindy.sourceforge.net/) is now included on most platforms. -

    The

    The kpsewhich tool can now report all matches for a given file (option –all) and limit matches to a given subdirectory (option –subdir). -

    The

    The dvipdfmx program now includes functionality to extract bounding box information, via the command name extractbb; this was one of the last features provided by dvipdfm not in dvipdfmx. -

    The font aliases

    The font aliases Times-Roman, Helvetica, and so on have been removed. Different packages expected them to behave differently (in particular, to have different encodings), and there was no good way to resolve this. -

    The

    The platex format has been removed, to resolve a name conflict with a completely different Japanese platex; the polski package is now the main Polish support. -

    Internally, the

    Internally, the WEB string pool files are now compiled into the binaries, to ease upgrades. -

    Finally, the changes made by Donald Knuth in his ‘T

    Finally, the changes made by Donald Knuth in his ‘TEX tuneup of 2008’ are included in this release. See http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf. -

    -

    10.1.6 2009
    -

    In 2009, the default output format for Lua(L

    +

    9.1.6 2009
    +

    In 2009, the default output format for Lua(LA )TEX is now PDF, to take advantage of LuaTEX’s OpenType @@ -5967,9 +6038,9 @@ LuaTEX home page is http://luatex.org. -

    The original Omega engine and Lambda format have been excised, after discussions with the Omega +

    The original Omega engine and Lambda format have been excised, after discussions with the Omega authors. The updated Aleph and Lamed remain, as do the Omega utilities. -

    A new release of the AMS Type 1 fonts is included, including Computer Modern: a few shape +

    A new release of the AMS Type 1 fonts is included, including Computer Modern: a few shape changes made over the years by Knuth in the Metafont sources have been integrated, and the hinting has been updated. The Euler fonts have been thoroughly reshaped by Hermann Zapf (see http://tug.org/TUGboat/Articles/tb29-2/tb92hagen-euler.pdfhttp://www.ams.org/tex/amsfonts.html. -

    The new GUI front end T

    The new GUI front end TEXworks is included for Windows, and also in MacTEX. For other platforms, and more information, see the TEXworks home page, http://tug.org/texworks. It is a cross-platform front end inspired by the Mac OS X TeXShop editor, aiming at ease-of-use. -

    The graphics program Asymptote is included for several platforms. This implements a text-based graphics +

    The graphics program Asymptote is included for several platforms. This implements a text-based graphics description language vaguely akin to MetaPost, but with advanced 3D support and other features. Its home page is http://asymptote.sourceforge.net. -

    The separate

    The separate dvipdfm program has been replaced by dvipdfmx, which operates in a special compatibility mode under that name. dvipdfm release. The DVIPDFMx home page is http://project.ktug.or.kr/dvipdfmx. -

    Executables for the

    Executables for the cygwin and i386-netbsd platforms are now included, while we were advised that OpenBSD users get TEX through their package systems, plus there were difficulties in making binaries that have a chance of working on more than one version. -

    A miscellany of smaller changes: we now use

    A miscellany of smaller changes: we now use xz compression, the stable replacement for lzma ($ is allowed in filenames when it does n name; the Kpathsea library is now multi-threaded (made use of in MetaPost); the entire TEX Live build is now based on Automake. -

    Final note on the past: all releases of T

    Final note on the past: all releases of TEX Live, along with ancillary material such as CD labels, are available at ftp://tug.org/historic/systems/texlive. -

    -

    10.2 Present

    -

    In 2010, the default version for PDF output is now 1.5, enabling more compression. This applies to all the +

    +

    9.2 Present

    +

    In 2010, the default version for PDF output is now 1.5, enabling more compression. This applies to all the TEX engines when used to produce PDF and to dvipdfmx. Loading the \pdfminorversion=4. -

    pdf(L

    pdf(LA )TEX now automatically converts a requested Encapsulated PostScript (EPS) file to PDF, via the @@ -6055,7 +6126,7 @@ class="ec-lmss-10">epstopdf package documentation (http://ctan.org/pkg/epstopdf-pkg). -

    A related change is that execution of a very few external commands from T

    A related change is that execution of a very few external commands from TEX, via the \write18 feature, is now enabled by default. These are commands are  conf texmf shell_escape 0. -

    Yet another related change is that BibTeX and Makeindex now refuse to write their output files to an +

    Yet another related change is that BibTeX and Makeindex now refuse to write their output files to an arbitrary directory (like TEX itself), by default. This is so they can now be enabled for use by the restricted \write18. To change this, the TEXMFOUTPUT environment variable can be set, or the openout_any setting changed. -

    XeT

    XeTEX now supports margin kerning along the same lines as pdfTEX. (Font expansion is not presently supported.) -

    By default,

    By default, tlmgr now saves one backup of each package updated (tlmgr option autobackup 1), so broken packages updates can be easily reverted with tlmgr restore. If you do post-install updates, and don’t have the disk space for the backups, run tlmgr option autobackup 0. -

    New programs included: the pT

    New programs included: the pTEX engine and related utilities for typesetting Japanese; the BibTeXU program for Unicode-enabled BibTeX; the chktex utility (dvisvgm (http://dvisvgm.sourceforge.net) DVI-to-SVG translator. -

    Executables for these new platforms are now included:

    Executables for these new platforms are now included: amd64-freebsd, amd64-kfreebsd, i386-freebsd, @@ -6114,7 +6185,7 @@ class="ec-lmtt-10">i386-freebsd, class="ec-lmtt-10">i386-kfreebsd, x86_64-darwin, x86_64-solaris. -

    A change in T

    A change in TEX Live 2009 that we failed to note: numerous TEX4ht-related executables (http://tug.org/tex4ht) were removed from the binar class="ec-lmtt-10">mk4ht program can be used to run any of the various tex4ht combinations. -

    Finally, the T

    Finally, the TEX Live release on the TEX Collection DVD can no longer be run live (oddly enough). A single DVD no longer has enough room. One beneficial side effect is that installation from the physical DVD is much faster. -

    -

    10.3 Future

    -

    +

    9.3 Future

    +

    TEhttp://tug.org/texlive/contribute.html. -

    Please send corrections, suggestions, and offers of help to: +

    Please send corrections, suggestions, and offers of help to:

    -

    Happy T