Figure 2: Expert GUI installer screen (GNU/Linux)
This document describes the main features of the TEX 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 user groups distribute among their members, or in other ways. Section 2.1 briefly describes the contents of the DVD. Both TEX Live and the TEX Collection are cooperative efforts by the TEX user groups. This document mainly describes TEX Live itself.
TEX Live includes executables for TEX, LaTeX2e, ConTEXt, Metafont, MetaPost, 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.
For a brief summary of the major changes in this edition of TEX Live, see the end of the document, section 9 (p. 72).
TEX Live contains binaries for many Unix-based platforms, including GNU/Linux, Mac OS X, and Cygwin. The included sources can be compiled on platforms for which we do not provide binaries.
As to Windows: Windows XP and later are supported. Windows 2000 will probably still mostly work. There are no special 64-bit executables for Windows, but the 32-bit executables should run on 64-bit systems.
See section 2.1 for alternate solutions for Windows and Mac OS X.
You can install TEX Live either from DVD or over the Internet (http://tug.org/texlive/acquire.html). The net installer itself is small, and downloads everything requested from the Internet.
The DVD installer lets you install to a local disk. You cannot run TEX Live directly from the TEX Collection DVD (or its .iso image), but you can prepare a runnable installation on, e.g., a USB stick (see section 4.2). Installation is described in later sections (p. 12), but here is a quick start:
To the best of our knowledge, the core TEX programs themselves are (and always have been) extremely robust. However, the contributed programs in TEX Live may not reach the same level, despite everyone’s best efforts. As always, you should be careful when running programs on untrusted input; for maximum safety, use a new subdirectory.
This need for care is especially urgent on Windows, since in general Windows finds programs in the current directory before anything else, regardless of the search path. This opens up a wide variety of possible attacks. We have closed many holes, but undoubtedly some remain, especially with third-party programs. Thus, we recommend checking for suspicious files in the current directory, especially executables (binaries or scripts). Ordinarily they should not be present, and definitely should not normally be created by merely processing a document.
Finally, TEX (and its companion programs) are able to write files when processing documents, a feature that can also be abused in a wide variety of ways. Again, processing unknown documents in a new subdirectory is the safest bet.
The TEX community is active and friendly, and most 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 forgo TEX Live completely and purchase a vendor’s system; http://tug.org/interest.html#vendors has a list.)
Here is a list of resources, approximately in the order we recommend using them:
The other side of the coin is helping others who have questions. Both comp.text.tex and texhax are open to anyone, so feel free to join, start reading, and help out where you can.
This section describes the contents of TEX Live and the TEX Collection of which it is a part.
The TEX Collection DVD comprises the following:
CTAN, protext, and texmf-extra do not necessarily follow the same copying conditions as TEX Live, so be careful when redistributing or modifying.
Here is a brief listing and description of the top level directories in a TEX Live installation.
The TEX system programs, arranged by platform.
Quick overview and useful links for TEX Live, in various languages, in both HTML and plain text.
The source to all included programs, including the main Web2C-based TEX distributions.
See TEXMFMAIN below.
See TEXMFDIST below.
Scripts, programs and data for managing the installation, and special support for Windows.
In addition to the directories above, the installation scripts and README files (in various languages) are at the top level of the distribution.
For documentation, the comprehensive links in the top-level file doc.html may be helpful. The documentation for the programs (manuals, man pages, Info files) is in texmf/doc. The documentation for TEX packages and formats is in texmf-dist/doc. You can use the texdoc program to find any documentation wherever it is located.
This TEX Live documentation itself is in texmf/doc/texlive, available in several languages:
This section lists the predefined variables specifying the texmf trees used by the system, and their intended purpose, and the default layout of TEX Live. The command tlmgr conf shows the values of these variables, so that you can easily find out how they map to particular directories in your installation.
All of the trees, including the personal ones, should follow the TEX Directory Structure (TDS, http://tug.org/tds), with all its myriad subdirectories, or files may not be found. Section 3.4.6 (p. 39) describes this in more detail.
The tree which holds vital parts of the system such as configuration files, helper scripts, and program documentation.
The tree which holds the main set of macro packages, fonts, etc.
The tree which administrators can use for system-wide installation of additional or updated macros, fonts, etc.
The tree which users can use for their own individual installations of additional or updated macros, fonts, etc. The expansion of this variable dynamically adjusts for each user to their own individual directory.
The (personal) tree used by the utilities texconfig, updmap, and fmtutil to store modified configuration data.
The (site-wide) tree used by the utilities texconfig-sys, updmap-sys, and fmtutil-sys to store modified configuration data.
The (personal) tree used by texconfig, updmap and fmtutil to store (cached) runtime data such as format files and generated map files.
The (personal) tree used by ConTEXt MkIV to store (cached) runtime data. Default value in TEX Live is the same as TEXMFVAR.
The (site-wide) tree used by texconfig-sys, updmap-sys and fmtutil-sys, and also by tlmgr, to store (cached) runtime data such as format files and generated map files.
The default layout is:
A previous release.
The current release.
GNU/Linux binaries
Mac OS X binaries
Windows binaries
This is TEXMFMAIN.
TEXMFDIST
TEXMFSYSVAR
TEXMFSYSCONFIG
TEXMFLOCAL, intended to be retained from release to release.
Privately generated and configuration data for a previous release.
Privately generated and configuration data for the current release.
TEXMFVAR, TEXMFCACHE
TEXMFCONFIG
TEXMFHOME Personal macros, etc.
Knuth’s original TEX itself is frozen, apart from rare bug fixes. It is still present in TEX Live as the program tex, and will remain so for the foreseeable future. TEX Live contains several extended versions of TEX:
Here are a few other commonly-used programs included in TEX Live:
bibliography support.
index support.
convert DVI to PostScript.
DVI previewer for the X Window System.
DVI drive for the HP LaserJet family.
cut and paste pages from DVI files.
convert DVI to PDF, an alternative approach to pdfTEX (mentioned above).
PostScript utilities.
PDF utilities.
ConTEXt and PDF processor.
TEX to HTML (and XML and more) converter.
TEX Live comes with many high-quality scalable fonts. See http://tug.org/fonts and texmf-dist/doc/fonts/free-math-font-survey.
To begin, get the TEX Collection DVD or download the TEX Live net installer, and locate the installer script: install-tl for Unix, install-tl.bat for Windows. See http://tug.org/texlive/acquire.html for more information and other methods of getting the software.
The same installer program is run, whatever the source. The most visible difference between the two is that with the net installer, what you end up with is the packages that are currently available. This is in contrast to the DVD and ISO images, which are not updated between the major public releases.
The following sections explain installer start-up in more detail.
Below, > denotes the shell prompt; user input is bold. The script install-tl is a Perl script. The simplest way to start it on a Unix-compatible system is as follows:
To install in expert GUI mode (figure 2), you’ll need the Perl/TK module compiled with XFT support, which is generally the case with GNU/Linux, but not necessarily with other systems. Given that, you can run:
For a complete listing of the various options:
Warning about Unix permissions: Your umask at the time of installation will be respected by the TEX Live installer. Therefore, if you want your installation to be usable by users other than you, make sure your setting is sufficiently permissive, for instance, umask 002. For more information about umask, consult your system documentation.
Special considerations for Cygwin: Unlike other Unix-compatible systems, Cygwin does not by default include all of the prerequisite programs needed by the TEX Live installer. See Section 3.1.4 for details.
As mentioned in section 2.1, a separate distribution is prepared for Mac OS X, named MacTEX (http://tug.org/mactex). We recommend using the native MacTEX installer instead of the TEX Live installer on Mac OS X, because the native installer makes a few Mac-specific adjustments, in particular to allow easily switching between the various TEX distributions for Mac OS X (MacTEX, Fink, MacPorts, …).
MacTEX is firmly based on TEX Live, and the main TEX trees are precisely the same. It does add a few extra folders with Mac-specific documentation and applications.
If you are using the net installer, or the DVD installer failed to start automatically, double-click install-tl.bat. For more customization options, e.g., selection of specific package collections, run install-tl-advanced.bat instead.
You can also start the installer from the command-prompt. Below, > denotes the prompt; user input is bold. If you are in the installer directory, run just:
Or you can invoke it with an absolute location, such as:
To install in text mode, use:
For a complete listing of the various options:
The TEX Live installer supports only Cygwin 1.7. Before beginning the installation, use Cygwin’s setup.exe program to install the perl and wget packages if you have not already done so. The following additional packages are recommended:
Figure 1 displays the main text mode screen under Unix. The text installer is the default on Unix.
This is only a command-line installer; there is no cursor support at all. For instance, you cannot tab around checkboxes or input fields. You just type something (case-sensitive) at the prompt and press the Enter key, and then the entire terminal screen will be rewritten, with adjusted content.
The text installer interface is this primitive for a reason: it is designed to run on as many platforms as possible, even with a very barebones Perl.
Figure 2 displays the expert graphical installer under GNU/Linux. Other than using buttons and menus, this does not differ much from the text installer.
This mode can be invoked explicitly with
Under Windows, the default is to run the simplest installation method we could devise, called the “wizard” installer (figure 3). It installs everything and asks almost no questions. If you want to customize your setup, you should run one of the other installers.
This mode can be invoked explicitly with
The installer is intended to be mostly self-explanatory, but following are a few notes about the various options and submenus.
Figure 4 displays the text mode binaries menu. By default, only the binaries for your current platform will be installed. From this menu, you can select installation of binaries for other platforms as well. This can be useful if you are sharing a TEX tree across a network of heterogenous machines, or for a dual-boot system.
Figure 5 displays the TEX Live scheme menu; from here, you choose a “scheme”, which is an overall set of package collections. The default full scheme installs everything available. This is recommended, but you can also choose the basic scheme for a small system, minimal for testing purposes, and medium or teTeX to get something in between. There are also various specialized and country-specific schemes.
You can refine your scheme selection with the ‘standard collections’ and ‘language collections’ menus (figure 6, shown in GUI mode for a change).
Collections are one level more detailed than schemes — in essence, a scheme consists of several collections, a collection consists of one or more packages, and a package (the lowest level grouping in TEX Live) contains the actual TEX macro files, font files, and so on.
If you want more control than the collection menus provide, you can use the TEX Live Manager (tlmgr) program after installation (see section 5); using that, you can control the installation at the package level.
The default layout is described in section 2.3, p. 8. The default location of TEXDIR is /usr/local/texlive/2011 on Unix and %SystemDrive%\texlive\2011 on Windows.
The main reason to change this default is if you lack write permission for the default location. You don’t have to be root or administrator to install TEX Live, but you do need write access to the target directory.
A reasonable alternative choice is a directory under your home directory, especially if you will be the sole user. Use ‘~’ to indicate this, as in ‘~/texlive/2011’.
We recommend including the year in the name, to enable keeping different releases of TEX Live side by side. (You may wish to make a version-independent name such as /usr/local/texlive-cur via a symbolic link, which you can then update after testing the new release.)
Changing TEXDIR in the installer will also change TEXMFLOCAL, TEXMFSYSVAR and TEXMFSYSCONFIG.
TEXMFHOME is the recommended location for personal macro files or packages. The default value is ~/texmf. In contrast to TEXDIR, here a ~ is preserved in the newly-written configuration files, since it usefully refers to the home directory of any individual running TEX. It expands to $HOME on Unix and %USERPROFILE% on Windows. Special redundant note: TEXMFHOME, like all trees, must be organized according to the TDS, or files may not be found.
TEXMFVAR is the location for storing most cached runtime data specific to each user. TEXMFCACHE is used for that purpose by ConTEXt MkIV (see section 3.4.5, p. 39).
Figure 7 shows the text mode options menu. More info on each:
When all the settings are to your liking, you can type ‘I’ to start the installation process. When it is done, skip to section 3.4 to read what else needs to be done, if anything.
Type
If possible, use the GUI installer. This requires the Perl/Tk module (http://tug.org/texlive/distro.html#perltk) compiled with XFT support; if Perl/Tk is not available, installation continues in text mode.
Force using the text mode installer, even under Windows.
Specify the installer interface language as its standard two-letter code LL. Currently supported languages: cs (Czech), de (German), en (English, default) fr (French), it (Italian), ja (Japanese), nl (Dutch), pl (Polish), ru (Russian), sk (Slovak), sl (Slovenian), sr (Serbian), vi (Vietnamese), zh-cn (Simplified Chinese), zh-tw (Traditional Chinese). The installer tries to automatically determine the right language but if it fails, or if the right language is not available, then it uses English as a fallback.
If you already have an rsync, svn, or other copy of TEX Live (see http://tug.org/texlive/acquire-mirror.html) then this option will use what you’ve got, as-is, and do only the necessary post-install. Be warned that the file tlpkg/texlive.tlpdb may be overwritten; saving it is your responsibility. Also, package removal has to be done manually. Do not use this unless you know what you are doing. This option cannot be toggled via the installer interface.
Install for portable use on, e.g., a USB stick. Also selectable from within the GUI and text installers; see section 4.2.
The installer always writes a file texlive.profile to the tlpkg subdirectory of your installation. This option tells the installer to re-use such a profile file, so you can install in batch mode on subsequent systems, reproducing the choices you made in a prior installation.
Specify package repository from which to install; see following.
The default package repository is a CTAN mirror chosen automatically via http://mirror.ctan.org.
If you want to override that, the location value can be a url starting with ftp:, http:, or file:/, or a plain directory path. (When giving an http: or ftp: location, trailing ‘/’ characters and/or a trailing ‘/tlpkg’ component are ignored.)
For example, you could choose a particular CTAN mirror with something like: http://ctan.example.org/tex-archive/systems/texlive/tlnet/, substituting a real hostname and its particular top-level CTAN path for ctan.example.org/tex-archive. The list of CTAN mirrors is maintained at http://ctan.org/mirrors.
If the given argument is local (either a path or a file:/ url), compressed files in an archive subdirectory of the repository path are used (even if uncompressed files are available as well).
Some post-install may be required.
If you elected to create symlinks in standard directories (described in section 3.2.4), then there is no need to edit environment variables. Otherwise, on Unix systems, the directory of the binaries for your platform must be added to the search path. (On Windows, the installer takes care of this.)
Each supported platform has its own subdirectory under TEXDIR/bin. See figure 4 for the list of subdirectories and corresponding platforms.
Optionally, you can also add the documentation man and Info directories to their respective search paths, if you want the system tools to find them. The man pages might be found automatically after the addition to PATH.
For Bourne-compatible shells such as bash, and using Intel x86 GNU/Linux and a default directory setup as an example, the file to edit might be $HOME/.profile (or another file sourced by .profile, and the lines to add would look like this:
For csh or tcsh, the file to edit is typically $HOME/.cshrc, and the lines to add might look like:
If you already have settings somewhere in your “dot” files, naturally the TEX Live directories should simply be merged in as appropriate.
If you want to make these changes globally, or for a user newly added to the system, then you are on your own; there is just too much variation between systems in how and where these things are configured.
Our two hints are: 1) you may want to check for a file /etc/manpath.config and, if present, add lines such as
And 2) check for a file /etc/environment which may define the search path and other default environment variables.
In each (Unix) binary directory, we also create a symbolic link named man to the directory texmf/doc/man. Some man programs, such as the standard Mac OS X man, will automatically find that, obviating the need for any man page setup.
If you installed TEX Live from DVD and then wish to get updates from the Internet, you need to run this command—after you’ve updated your search path (as described in the previous section):
This tells tlmgr to use a nearby CTAN mirror for future updates.
If there are problems with the automatic mirror selection, you can specify a particular CTAN mirror from the list at http://ctan.org/mirrors. Use the exact path to the tlnet subdir on that mirror, as shown above.
If you have installed the xetex package on a Unix-compatible system, you need to configure your system if you want XeTEX to be able to find the fonts shipped with TEX Live. To facilitate this, when the xetex package is installed (either at initial installation or later), the necessary configuration file is created in TEXMFSYSVAR/fonts/conf/texlive-fontconfig.conf.
To set up the TEX Live fonts for system-wide use (assuming you have suitable privileges), proceed as follows:
If you do not have sufficient privileges to carry out the steps above, you can instead do the following to make the TEX Live fonts available to you as an individual XeTEX user:
The ‘old’ ConTEXt (Mark II) should run out of the box after TEX Live installation. The ‘new’ LuaTEX-based ConTEXt Mark IV requires manual setup. After installation, each MkIV user must run:
The resulting files are stored under TEXMFCACHE, with the same default value in TEX Live as TEXMFVAR, as defined in texmfcnf.lua.
For more information, see http://wiki.contextgarden.net/Running_Mark_IV and http://wiki.contextgarden.net/TeX_Live_2010.
This is already mentioned implicitly in section 2.3: TEXMFLOCAL (by default, /usr/local/texlive/texmf-local or %SystemDrive%\texlive\texmf-local on Windows) is intended for system-wide local fonts and macros; and TEXMFHOME (by default, $HOME/texmf or %USERPROFILE%\texmf), is for personal fonts and macros. These directories are intended to stick around from release to release, and have their content seen automatically by a new TEX Live release. Therefore, it is best to refrain from changing the definition of TEXMFLOCAL to be too far away from the main TEX Live directory, or you will need to manually change future releases.
For both trees, files should be placed in their proper TEX Directory Structure (TDS) subdirectories; see http://tug.org/tds or consult texmf/web2c/texmf.cnf. For instance, a LATEX class file or package should be placed in TEXMFLOCAL/tex/latex or TEXMFHOME/tex/latex, or a subdirectory thereof.
TEXMFLOCAL requires an up-to-date filename database, or files will not be found. You can update it with the command mktexlsr or use the ‘Reinit file database’ button on the configuration tab of the TEX Live Manager GUI.
By default, each of these variables is defined to be a single directory, as shown. This is not a hard-and-fast requirement. If you need to easily switch back and forth between different versions of large packages, for example, you can maintain multiple trees for your own purposes. This is done by setting TEXMFHOME to the list of directories, within braces, separated by commas:
Section 7.1.5 describes brace expansion further.
This is unfortunately a messy topic. Forget about it unless you want to delve into many details of the TEX installation. Don’t forget to check first what you get for free: see section 2.6.
A possible alternative is to use XeTEX or LuaTEX (see section 2.4), which let you use operating system fonts without any installation in TEX.
If you do need to do this, see http://tug.org/fonts/fontinstall.html for our best effort at describing the procedure. If you rigorously maintain your local font maps, tlmgr generate updmap may be useful, notably in moving from release to release; see the tlmgr documentation.
After installing TEX Live as best you can, you naturally want to test it out, so you can start creating beautiful documents and/or fonts.
This section gives some basic procedures for testing that the new system is functional. We give Unix commands here; under Mac OS X and Windows, you’re more likely to run the tests through a graphical interface, but the principles are the same.
A simpler document than sample2e, to reduce the input size if you’re having troubles.
Test if your printer introduces any offsets.
For printing font tables and tests.
Also for font tables, but using plain TEX.
The most canonical (plain) TEX test file of all. You must type ‘\bye’ to the * prompt after ‘tex story.tex’.
If you are new to TEX, or otherwise need help with actually writing TEX or LATEX documents, please visit http://tug.org/begin.html for some introductory resources.
Links for some other tools you may consider installing:
For a much longer list of packages and programs, see http://tug.org/interest.html.
The previous sections described the basic installation process. Here we turn to some specialized cases.
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 TEX Live programs are found relative to the programs. You can see this in the principal configuration file $TEXMFMAIN/web2c/texmf.cnf, which contains lines such as
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 TEX Live locally and then move the entire hierarchy afterwards to a network location.
For Windows, a sample network installation script named w32client can be downloaded through http://tug.org/texlive/w32client.html. It creates settings and menu shortcuts for using an existing TEX Live installation on a LAN. It also registers an uninstaller w32unclient, available in the same zip file. See the web page for more information.
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 run TEX using this portable installation, you need to add the appropriate binary directory to the search path during your terminal session, as usual. On Windows, you can double-click tl-tray-menu at the root of the installation to choose between a few common tasks, as shown in this screenshot:
You can use the ‘Custom Script’ entry to add items of your own. By default, it pops up a message explaining how to create one.
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 to omit the subdirectory for the release year, and 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 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.,
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.
TEX Live includes a program named tlmgr for managing TEX Live after the initial installation. The programs updmap, fmtutil and texconfig are still included and will be retained in the future, but tlmgr is now the preferred interface. Its capabilities include:
tlmgr can be started in GUI mode (figure 8) with
Figures 9 and 10 show the general and paper size option screens.
After the initial installation, you can update your system to the latest versions available with:
This more complex example adds a collection, for the engine XeTEX, from a local directory:
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):
Last and most important, for full documentation see http://tug.org/texlive/tlmgr.html, or:
Under Windows, the installer does some extra things:
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:
The Windows counterpart of a Unix home directory is the %USERPROFILE% directory. Under Windows XP, this is usually C:\Documents and Settings\<username>, and under Windows Vista and Windows 7 it is C:\Users\<username>. In the texmf.cnf file, and Kpathsea in general, ~ will expand appropriately on both Windows and Unix.
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 HKEY_LOCAL_MACHINE, HKCU and HKLM in short. The HKCU part of the registry is in the user’s home directory (see section 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, for example the location of shortcuts, it is necessary to consult the registry. Setting environment variables permanently also requires registry access.
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 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 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 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 never get precedence. As a safeguard, the installer creates a shortcut to the command-prompt in which the new TEX Live binary directory is prepended to the local search path. The new TEX Live will be always usable from within such a command-prompt. The shortcut for TEXworks, if installed, also prepends TEX Live to the search path, so it should also be immune to this path problem.
For Vista and Windows 7 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’.
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 User’s Guide (http://www.cygwin.com/cygwin-ug-net/setup-maxmem.html).
For Windows, you have to create a file, say moremem.reg, with these four lines:
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.)
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 manual and more, is http://tug.org/web2c.
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 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:
Maintaining bibliographies.
Expands virtual font references in DVI files.
DVI to MPX (MetaPost pictures).
DVI to human-readable text.
Generic font proofsheets.
Generic to packed fonts.
GF to human-readable text.
Creating typeface families.
Prettyprinting Metafont source.
Creating technical diagrams.
Creating hyphenation patterns.
Packed to generic fonts.
PK to human-readable text.
Plain text property list to TFM.
Display WEB pool files.
WEB to Pascal.
Typesetting.
TFM to plain text property list.
Virtual font to virtual property list.
Virtual property list to virtual font.
WEB to TEX.
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:
print basic usage summary.
print detailed progress report.
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 (huge) collection of TEX files. Web2C can look at many directory trees simultaneously, which is useful in maintaining TEX’s standard distribution and local and personal extensions in distinct trees. To speed up file 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.
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 ‘my-file’ along a path ‘.:/dir’, Kpathsea checks each element of the path in turn: first ./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 filename separators different from colon (‘:’) and slash (‘/’).
To check a particular path element p, Kpathsea first checks if a prebuilt database (see “Filename database” on page 62) 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 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 ‘.vf’ files and input files read by TEX’s \openin command. Such files may not exist (e.g., cmr10.vf), and so it would be wrong to search the disk for them. Therefore, if you fail to update 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 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 ‘/’ or ‘./’ or ‘../’, Kpathsea simply checks if that file exists.
A search path can come from many sources. In the order in which Kpathsea uses them:
You can see each of these values for a given search path by using the debugging options (see “Debugging actions” on page 65).
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 .../2011/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 .../2011/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 .:$TEXMF, values from ./texmf.cnf override those from $TEXMF/texmf.cnf.
A configuration file fragment illustrating most of these points is shown below:
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 foo and bar in $USER’s home directory that contain a directory or file baz. These expansions are explained in the sections below.
If the highest-priority search path (see “Path sources” on page 57) 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
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 ‘:’.
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 TEX hierarchies, by assigning a brace list to $TEXMF. For example, in texmf.cnf, a definition like this (simplified for this example) is made:
Using this you can then write something like
which means that, after looking in the current directory, the $TEXMFHOME/tex, $TEXMFLOCAL/tex, $TEXMFVAR/tex and $TEXMFMAIN/tex trees only) will be searched (the last two use using 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 $TEXMF variable in all definitions, one is sure to always search the up-to-date tree first.
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 ‘//’, only subdirectories with matching components are included. For example, ‘/a//b’ expands into directories /a/1/b, /a/2/b, /a/1/1/b, and so on, but not /a/b/c or /a/1.
Multiple ‘//’ constructs in a path are possible, but ‘//’ at the beginning of a path is ignored.
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 path expansion.
Separator on non-Unix systems (acts like :).
Variable expansion.
Represents the user’s home directory.
Brace expansion.
Subdirectory expansion (can occur anywhere in a path, except at its beginning).
Start of comment.
Continuation character (allows multi-line entries).
Search only database to locate file, do not search the disk.
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 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.
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 ‘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
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.
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).
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.
Set the resolution to num; this only affects ‘gf’ and ‘pk’ lookups. ‘-D’ is a synonym, for compatibility with dvips. Default is 600.
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
dvips configuration files, you have to specify the name as known to Kpathsea, such as tex or enc
files. Run kpsewhich --help for a list.
Set the mode name to string; this only affects ‘gf’ and ‘pk’ lookups. No default: any mode will
be found.
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.
Search along the path string (colon-separated as usual), instead of guessing the search path from
the filename. ‘//’ and all the usual expansions are supported. The options ‘--path’ and ‘--format’
are mutually exclusive.
Set the program name to name. This can affect the search paths via the .progname feature. The
default is kpsewhich.
shows the path used for file lookups of file type name. Either a filename extension (.pk, .vf, etc.)
or a name can be used, just as with ‘--format’ option.
sets the debugging options to num.
Let us now have a look at Kpathsea in action. Here’s a straightforward search:
By the way, that last is a BibTeX bibliography database for TUGboat articles.
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 TEX support, before turning our attention to the generic configuration file (config.ps) and the PostScript font map psfonts.map — as of 2004, map and encoding files have their own search paths and new location in texmf trees. As the ‘.ps’ suffix is ambiguous we have to specify explicitly which type we are considering (dvips config) for the file config.ps.
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:
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.
Sometimes it is necessary to investigate how a program resolves file references. To make this practical, Kpathsea offers various levels of debugging output:
stat calls (disk lookups). When running with an up-to-date ls-R database this should almost give no output.
References to hash tables (such as ls-R databases, map files, configuration files).
File open and close operations.
General path information for file types searched by Kpathsea. This is useful to find out where a particular path for the file was defined.
Directory list for each path element (only relevant for searches on disk).
File searches.
Variable values.
A value of -1 will set all the above options; in practice, this is usually the most convenient.
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 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 purposes you can temporarily SET KPATHSEA_DEBUG_OUTPUT=err.log).
Let us consider, as an example, a small LATEX source file, hello-world.tex, which contains the following input.
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 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 ls-R (to optimize file searching) and the file aliases, which makes it possible to declare several names (e.g., a short DOS-like 8.3 and a more natural longer version) for the same file. Then dvips goes on to find the generic configuration file config.ps before looking for the customization file .dvipsrc (which, in this case is not found). Finally, dvips locates the config file for the Computer Modern PostScript fonts config.cms (this was initiated with the -Pcms option on the 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.
At this point dvips identifies itself to the user:
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):
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:
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 the format file hugetex.fmt. Using the standard way of specifying the program name used by Kpathsea, the particular value of the main_memory variable will then be read from texmf.cnf.
Extra space for “large” TEX data structures: boxes, glue, breakpoints, etc. Especially useful if you use PI CTEX.
Number of words for font information available for TEX. This is more or less the total size of all TFM files read.
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 extremely difficult to implement in the present TEX source, these runtime parameters provide a practical compromise allowing some flexibility.
TEX Live is a joint effort by virtually all of the TEX user groups. This edition of TEX Live was overseen by Karl Berry. The other principal contributors, past and present, are listed below.
Builders of the binaries: Alan Braslau (amd64-kfreebsd, i386-kfreebsd), Peter Breitenlohner (x86_64-linux), Karl Berry (i386-linux, sparc-linux), Ken Brown (i386-cygwin), Akira Kakuto (win32), Dick Koch (universal-darwin, x86_64-darwin), Nikola Lečić (amd64-freebsd, i386-freebsd), Norbert Preining (alpha-linux), Jukka Salmi (i386-netbsd), Thomas Schmitz (powerpc-linux), Apostolos Syropoulos (i386-solaris, x86_64-solaris), Vladimir Volovich (powerpc-aix, sparc-solaris), Olaf Weber (mips-irix). For information on the TEX Live build process, see http://tug.org/texlive/build.html.
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 TEX, and then for giving it to the world.
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 ambitious a target for the time, but it did spawn not only the very successful 4AllTEX CD, but also the TUG Technical Council working group on a TEX Directory Structure (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 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 4AllTEX 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 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 Web2C, with the addition of teTEX’s texconfig script. The 3rd edition of the CD was based on a major revision of Web2C, 7.2, by Olaf Weber; at the same time, a new revision of teTEX was being made, and TEX Live included almost all of its features. The 4th edition followed the same pattern, using a new version 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 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 TEX Live is now intended to be compatible with the Debian Free Software Guidelines (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 language.dat.
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.
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, p. 7). In addition:
2004 saw many changes:
.map files are now searched for in subdirectories of fonts/map only (in each texmf tree), along the TEXFONTMAPS path. Similarly, .enc files are now searched for in subdirectories of 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 http://tug.org/texlive/mapenc.html.
It also means it’s more important than ever to use the ifpdf package (works with both plain and LATEX) or equivalent code, because simply testing whether \pdfoutput 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, \pdfoutput may be defined even when DVI is being written.
See the Web2C manual for more: texmf/doc/web2c.
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:
In 2006–2007, the major new addition to TEX Live was the XeTEX program, available as the xetex and xelatex programs; see http://scripts.sil.org/xetex.
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 TEX .fmt (high-speed format) and the similar files for MetaPost and Metafont are now stored in subdirectories of texmf/web2c, instead of in the directory itself (although the directory is still searched, for the sake of existing .fmt’s). The subdirectories are named for the ‘engine’ in use, such as tex or pdftex or xetex. This change should be invisible in normal use.
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, please check CTAN (http://mirror.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.
Finally, in May 2006 Thomas Esser announced that he would no longer be updating teTEX (http://tug.org/tetex). As a result, there was been a surge of interest in TEX Live, especially among GNU/Linux distributors. (There is a new tetex installation scheme in TEX Live, which provides an approximate equivalent.) We hope this will eventually translate to improvements in the TEX environment for everyone.
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 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 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 Perl and Lua scripts are now available on Windows, using the Perl internally distributed with TEX Live.
The new tlmgr script (section 5) 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 tlmgr, the texconfig actions to edit the format and hyphenation configuration files are now disabled.
The xindy indexing program (http://xindy.sourceforge.net/) is now included on most platforms.
The kpsewhich tool can now report all matches for a given file (option –all) and limit matches to a given subdirectory (option –subdir).
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 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 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 WEB string pool files are now compiled into the binaries, to ease upgrades.
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.
In 2009, the default output format for Lua(LA )TEX is now PDF, to take advantage of LuaTEX’s OpenType support, et al. New executables named dviluatex and dvilualatex run LuaTEX with DVI output. The LuaTEX home page is http://luatex.org.
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 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.pdf). In all cases, the metrics remain unchanged. The AMS fonts home page is http://www.ams.org/tex/amsfonts.html.
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 description language vaguely akin to MetaPost, but with advanced 3D support and other features. Its home page is http://asymptote.sourceforge.net.
The separate dvipdfm program has been replaced by dvipdfmx, which operates in a special compatibility mode under that name. dvipdfmx includes CJK support and has accumulated many other fixes over the years since the last dvipdfm release. The DVIPDFMx home page is http://project.ktug.or.kr/dvipdfmx.
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 xz compression, the stable replacement for lzma (http://tukaani.org/xz/); a literal $ is allowed in filenames when it does not introduce a known variable 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 TEX Live, along with ancillary material such as CD labels, are available at ftp://tug.org/historic/systems/texlive.
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 pdf14 LATEX package changes back to PDF 1.4, or set \pdfminorversion=4.
pdf(LA )TEX now automatically converts a requested Encapsulated PostScript (EPS) file to PDF, via the epstopdf package, when and if the LATEX graphics.cfg configuration file is loaded, and PDF is being output. The default options are intended to eliminate any chance of hand-created PDF files being overwritten, but you can also prevent epstopdf from being loaded at all by putting \newcommand{\DoNotLoadEpstopdf}{} (or \def...) before the \documentclass declaration. It is also not loaded if the pst-pdf package is used. For more details, see the epstopdf package documentation (http://ctan.org/pkg/epstopdf-pkg).
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 repstopdf, makeindex, kpsewhich, bibtex, and bibtex8; the list is defined in texmf.cnf. Environments which must disallow all such external commands can deselect this option in the installer (see section 3.2.4), or override the value after installation by running tlmgr conf texmf shell_escape 0.
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.
XeTEX now supports margin kerning along the same lines as pdfTEX. (Font expansion is not presently supported.)
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 pTEX engine and related utilities for typesetting Japanese; the BibTeXU program for Unicode-enabled BibTeX; the chktex utility (http://baruch.ev-en.org/proj/chktex) for checking (LA )TEX documents; the dvisvgm (http://dvisvgm.sourceforge.net) DVI-to-SVG translator.
Executables for these new platforms are now included: amd64-freebsd, amd64-kfreebsd, i386-freebsd, i386-kfreebsd, x86_64-darwin, x86_64-solaris.
A change in TEX Live 2009 that we failed to note: numerous TEX4ht-related executables (http://tug.org/tex4ht) were removed from the binary directories. The generic mk4ht program can be used to run any of the various tex4ht combinations.
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.
2011 saw relatively few changes.
The Mac OS X binaries (universal-darwin and x86_64-darwin) now work only on Leopard or later; Panther and Tiger are no longer supported.
The biber program for bibliography processing is included on common platforms. Its development is closely coupled with the biblatex package, which completely reimplements the bibliographical facilities provided by LaTeX.
The MetaPost (mpost) program no longer creates or uses .mem files. The needed files, such as plain.mp, are simply read on every run. This is related to supporting MetaPost as a library, which is another significant though not user-visible change.
The updmap implementation in Perl, previously used only on Windows, has been revamped and is now used on all platforms. There shouldn’t be any user-visible changes as a result, except that it runs much faster.
TEX Live is not perfect! (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 better-checked tree of macros and fonts. This work is all done by volunteers in their spare time, and so there is always more to do. Please see http://tug.org/texlive/contribute.html.
Please send corrections, suggestions, and offers of help to:
Happy TEXing!
