From 566cd741882ea254b6697d6be666b2188247dd40 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Wed, 29 Mar 2017 17:29:34 +0000 Subject: clarifications, corrections, no must_exist, remove ex6b and ex6c; report from Gernot Hassenpflug, tex-live 30 Nov 2016 15:23:12 git-svn-id: svn://tug.org/texlive/trunk@43638 c570f23f-e606-0410-a88d-b1316a301751 --- .../doc/texlive/texlive-en/texlive-en.html | 1567 +++++++++----------- .../doc/texlive/texlive-en/texlive-en.pdf | Bin 929930 -> 928980 bytes .../doc/texlive/texlive-en/texlive-en.tex | 73 +- 3 files changed, 699 insertions(+), 941 deletions(-) diff --git a/Master/texmf-dist/doc/texlive/texlive-en/texlive-en.html b/Master/texmf-dist/doc/texlive/texlive-en/texlive-en.html index b3c988fc72b..08272cbbae7 100644 --- a/Master/texmf-dist/doc/texlive/texlive-en/texlive-en.html +++ b/Master/texmf-dist/doc/texlive/texlive-en/texlive-en.html @@ -27,11 +27,12 @@ class="ec-lmr-12">Karl Berry, editor href="http://tug.org/texlive/" class="url" >http://tug.org/texlive/
June 2016
+class="ec-lmr-12">March 2017

+

This year’s TEX Live is dedicated to our sadly departed colleagues Sebastian Rahtz and Peter Breitenlohner.

@@ -182,41 +183,41 @@ href="#x1-660007.2.3" id="QQ2-1-78">Examples of use
  7.2.4 Debugging actions
 7.3 Runtime options +href="#x1-680007.3" id="QQ2-1-81">Runtime options
8 Acknowledgements +href="#x1-690008" id="QQ2-1-82">Acknowledgements
9 Release history +href="#x1-700009" id="QQ2-1-83">Release history
 9.1 Past +href="#x1-710009.1" id="QQ2-1-84">Past
  9.1.1 2003 +href="#x1-720009.1.1" id="QQ2-1-85">2003
  9.1.2 2004 +href="#x1-730009.1.2" id="QQ2-1-86">2004
  9.1.3 2005 +href="#x1-740009.1.3" id="QQ2-1-87">2005
  9.1.4 2006–2007 +href="#x1-750009.1.4" id="QQ2-1-88">2006–2007
  9.1.5 2008 +href="#x1-760009.1.5" id="QQ2-1-89">2008
  9.1.6 2009 +href="#x1-770009.1.6" id="QQ2-1-90">2009
  9.1.7 2010 +href="#x1-780009.1.7" id="QQ2-1-91">2010
  9.1.8 2011 +href="#x1-790009.1.8" id="QQ2-1-92">2011
  9.1.9 2012 +href="#x1-800009.1.9" id="QQ2-1-93">2012
  9.1.10 2013 +href="#x1-810009.1.10" id="QQ2-1-94">2013
  9.1.11 2014 +href="#x1-820009.1.11" id="QQ2-1-95">2014
  9.1.12 2015 +href="#x1-830009.1.12" id="QQ2-1-96">2015
 9.2 Present—2016 +href="#x1-840009.2" id="QQ2-1-97">Present—2016
 9.3 Future +href="#x1-850009.3" id="QQ2-1-98">Future

1 system-wide root
can span multiple TEX Live releases:
- 2015

A previous release.

- 2016

The current release.

- bin

 

- i386-linux

GNU/Linux binaries

- ...

- universal-darwin

Mac OS X binaries

- win32

Windows binaries

- texmf-dist  
($HOME or %USERPROFILE%)
- .texlive2015

Privately generated and configuration data for a previous release.

- .texlive2016

Privately generated and configuration data for the current release.

- texmf-var  install-tl subdirectory. Net installer, Windows .exe:
Download from CTAN as above, and double-click. This starts up a - first-stage installer and unpacker; see Figure 1. It gives three choices: “Simple install” starts up the wizard installer, “Custom install” the expert GUI installer, as described in section 3.1.3. A @@ -1068,6 +1069,7 @@ class="ec-lmtt-10">> 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:
+

> /path/to/installer/install-tl class="ec-lmtk-10">/path/to/installer/install-tl if it stayed executable, or cd to the directory first, etc.; we won’t repeat all the variations.) You may have to enlarge your terminal window so that it shows the full -text installer screen (Figure 2).

To install in expert GUI mode (figure 3), you’ll need the Perl::TK module compiled with XFT support, which is generally the case with GNU/Linux, but often not so with other systems. Given that, you can run:

+

> -gui

For a complete listing of the various options:

+

>install-tl-advanced.bat instead. class="ec-lmtt-10">> denotes the prompt; user input is bold. If you are in the installer directory, run just:
+

>install-tl-windows

Or you can invoke it with an absolute location, such as:

+

>D: is the optical drive. Figure 4 displays the wizard installer, which is the default for Windows.

To install in text mode, use:

+

> -no-gui

For a complete listing of the various options:

+

> -help
  InstallingInstalling TeX Live 2016 from: ...
  Platform:Platform: i386-linux => ’GNU/Linux on Intel x86’
  Distribution:Distribution: inst (compressed)
  DirectoryDirectory for temporary files: /tmp
  ...
...
   Detected platform: GNU/Linux on Intel x86
  

   <B> binary platforms: 1 out of 17 +class="ec-lmtt-8"> 17

  
   <S> set installation scheme (scheme-full)
  

   <C> customizing installation       47 collections out space required: 4268 MB
  

   <D> directories:
     TEXDIR (the main       /usr/local/texlive/2016
     ...
  

   <O> options:
     [ ] use default
     ...
   + id="x1-18046r23">
   <V> set up for portable installation
  

  Actions:
Actions:
   <I> start installation to hard disk
   <H> help
   <Q> quit

3 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

+

>4). It installs everything and asks almost no questions. If you want to customize your setup, you should run one of the other installers.

On other platforms, this mode can be invoked explicitly with

+

>  AvailableAvailable platforms:
  =============================================================================== -
===============================================================================
     a [ ] Cygwin on Intel x86 (i386-cygwin)
 (i386-cygwin) +
     b [ ] Cygwin on x86_64 (x86_64-cygwin) -
 (x86_64-cygwin)
     c [ ] MacOSX/Darwin universal binaries (universal-darwin)
 (universal-darwin) +
     d [ ] MacOSX/Darwin on x86_64 (x86_64-darwin) -
 (x86_64-darwin)
     e [ ] FreeBSD on x86_64 (amd64-freebsd)
 (amd64-freebsd) +
     f [ ] FreeBSD on Intel x86 (i386-freebsd) -
 (i386-freebsd)
     g [ ] (armel-linux)
     h [ ] GNU/Linux on ARMhf (armhf-linux)
 (armhf-linux) +
     i [X] GNU/Linux on Intel x86 (i386-linux) -
 (i386-linux)
     j [ ] (powerpc-linux)
     k [ ] (x86_64-linux) id="x1-24028r14">     l [ ] (amd64-netbsd)
     m [ ] (i386-netbsd)
     o [ ] (i386-solaris) id="x1-24034r17">     p [ ] (sparc-solaris)
     s [ ] (x86_64-solaris)
     t [ ]  SelectSelect scheme:
  ===============================================================================
===============================================================================
   a [X] full scheme (everything)
   b [ ] packages and languages)
   c [ ] few languages)
   d [ ] (plain and latex)
   e [ ] scheme (plain only)
   f [ ] ConTeXt scheme
   g [ ] Live scheme
   h [ ] nowhere near full)
   i [ ] XML scheme
   j [ ]TEXMFVAR.
  OptionsOptions setup:
  =============================================================================== +class="ec-lmtt-8">===============================================================================
   <P> use letter default: [ ]
   <E> execution of programs: [X]
   <F> create format   [X]
   <D> install font/macro  [X]
   <S> install font/macro   [X]
   <L> create symlinks       binaries to:
       manpages to:
       info to:
   <Y> after installation,TEXMFVAR tree as they are needed. In that location, th class="ec-lmbx-10">install font/macro … tree:
Omit downloading/installing the documentation and source files - included in most packages. Not recommended. +class="description">Download/install the documentation and source files included in most + packages. Unchecking is not recommended.
create symlinks in standard directories:
EX Live directories usually have to be added to PATH, MANPATH and INFOPATH. You will need write permissions to the target directories. It is - strongly advised not to overwrite a TEX system that came with your system with this option. It - is intended primarily for accessing the TEX system through directories that are already known - to users, such as INFOPATH. You will need write permissions to the target directories. This + option is intended for accessing the TEX system through directories that are already known to + users, such as /usr/local/bin, which don’t already contain any TEX files. +class="E">EX files. Do not overwrite + existing files on your system with this option, e.g., by specifying system directories. The safest + and recommended approach is to leave the option unchecked.
after installation When installing from DVD, this option is enabled by default, href="#x1-290003.3.1">3.3.1 and section 3.4.3.
-

When all the settings are to your liking, you can type ‘I’ to start the installation process. When it is done, +

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.

3.3 Command-line install-tl options

-

Type

-

+

Type

+ +

>  -help class="ec-lmtt-10">- or -- can be used to introduce option names. These are the most common ones: -

+

-gui
-

If possible, use the GUI installer. This requires the +

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

-no-gui
-

Force using the text mode installer, even under Windows. - - +

Force using the text mode installer, even under Windows.

-lang LL
-

Specify the installer interface language as a standard (usually two-letter) code. The installer tries +

Specify the installer interface language as a standard (usually two-letter) code. 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. Run install-tl --help to get the list of availa -portable

-

Install for portable use on, e.g., a USB stick. Also selectable from within the text installer with +

Install for portable use on, e.g., a USB stick. Also selectable from within the text installer with the V command, and from the GUI installer. See section 4.2. @@ -2329,7 +2206,7 @@ href="#x1-420004.2">4.2. class="ec-lmtt-10">-profile file

-

Load the installation profile

Load the installation profile file and do the installation with no user interaction. The installer always writes a file texlive.profile to the tlpkg subdirectory of your installation. That file can class="ec-lmtt-10">-repository url-or-directory

-

Specify package repository from which to install; see following. -

+

Specify package repository from which to install; see following. +

-in-place
-

(Documented only for completeness: Do not use this unless you know what you +

(Documented only for completeness: Do not use this unless you know what you are doing.) If you already have an rsync, svn, or other copy of TEX Live (see http://tug.org/texlive/acquire-mirror.html) then t class="ec-lmtt-10">tlpkg/texlive.tlpdb may be overwritten; saving it is your responsibility. Also, package removal has to be done manually. This option cannot be toggled via the installer interface.

-

+

3.3.1 The -repository option
-

The default network package repository is a CTAN mirror chosen automatically via

The default network 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

If you want to override that, the location value can be a url starting with ftp:, http:, or file:/, or a @@ -2375,7 +2252,7 @@ class="ec-lmtt-10">ftp: location, trailing ‘/’ characters and/or a trailing ‘/tlpkg’ component are ignored.) -

For example, you could choose a particular CTAN mirror with something like: +

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 @@ -2384,95 +2261,88 @@ class="ec-lmtt-10">ctan.example.org/tex-archive. The list o maintained at http://ctan.org/mirrors. -

If the given argument is local (either a path or a

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

+

3.4 Post-install actions

-

Some post-installation may be required. -

+

Some post-installation may be required. + + +

3.4.1 Environment variables for Unix
-

If you elected to create symlinks in standard directories (described in section 

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

Each supported platform has its own subdirectory under TEXDIR/bin. See figure 5 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 +

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

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

+

  PATH=/usr/local/texlive/2016/bin/i386-linux:$PATH;PATH=/usr/local/texlive/2016/bin/i386-linux:$PATH; export PATH
  MANPATH=/usr/local/texlive/2016/texmf-dist/doc/man:$MANPATH;MANPATH=/usr/local/texlive/2016/texmf-dist/doc/man:$MANPATH; export MANPATH
  INFOPATH=/usr/local/texlive/2016/texmf-dist/doc/info:$INFOPATH;INFOPATH=/usr/local/texlive/2016/texmf-dist/doc/info:$INFOPATH; export INFOPATH
-

For csh or tcsh, the file to edit is typically

For csh or tcsh, the file to edit is typically $HOME/.cshrc, and the lines to add might look like: -

+

  setenvsetenv PATH /usr/local/texlive/2016/bin/i386-linux:$PATH
  setenvsetenv MANPATH /usr/local/texlive/2016/texmf-dist/doc/man:$MANPATH
  setenvsetenv INFOPATH /usr/local/texlive/2016/texmf-dist/doc/info:$INFOPATH
-

If you already have settings somewhere in your “dot” files, naturally the T

If you already have settings somewhere in your “dot” files, naturally the TEX Live directories should be merged in as appropriate. -

+

3.4.2 Environment variables: Global configuration
-

If you want to make these changes globally, or for a user newly added to the system, then you are on +

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

Our two hints are: 1) you may want to check for a file /etc/manpath.config and, if present, add lines such as -

+

  MANPATH_MAPMANPATH_MAP /usr/local/texlive/2016/bin/i386-linux \
       /usr/local/texlive/2016/texmf-dist/doc/man
-

And 2) check for a file

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

In each (Unix) binary directory, we also create a symbolic link named man to the directory texmf-dist/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. -

+

3.4.3 Internet updates after DVD installation
-

If you installed T

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):

-

+ +

> tlmgr option repository http://mirror.ctan.org/systems/texlive/tlnet + +
-

This tells

This tells tlmgr to use a nearby CTAN mirror for future updates. This is done by default when installing from DVD, via the option described in section 3.2.4. -

If there are problems with the automatic mirror selection, you can specify a particular CTAN mirror from +

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

- - +

3.4.4 System font configuration for XeTEX and LuaTEX
-

XeT

XeTEX and LuaTEX can use any font installed on the system, not just those in the TEX trees. They do these via related but not identical methods. -

On Windows, fonts shipped with T

On Windows, fonts shipped with TEX Live are automatically made available to XeTEX by font name. On Mac OS X, supporting font name lookups requires additional steps; please see the MacThttp://tug.org/mactex). For other Unix systems, the procedure to be able to find the fonts shipped with TEX Live via font name follows. -

To facilitate this, when the

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 T

To set up the TEX Live fonts for system-wide use (assuming you have suitable privileges), proceed as follows:

    @@ -2566,7 +2435,7 @@ class="ec-lmtt-10">/etc/fonts/conf.d/09-texlive.conf.
  1. Run fc-cache -fsv.
-

If you do not have sufficient privileges to carry out the steps above, or if you want to make the T

If you do not have sufficient privileges to carry out the steps above, or if you want to make the TEX Live fonts available to only one user, you can do the following:

    @@ -2579,50 +2448,51 @@ class="ec-lmtt-10">~ is your home directory.
  1. Run fc-cache -fv.
-

You can run

You can run fc-list to see the names of the system fonts. The incantation fc-list : family style file spacing (all arguments are literal strings) shows some generally interesting information. -

+

3.4.5 ConTEXt Mark IV
-

Both the ‘old’ ConT

Both the ‘old’ ConTEXt (Mark II) and the ‘new’ ConTEXt (Mark IV) should run out of the box after TEX Live installation, and should need no special attention as long as you stick to using tlmgr for updates. -

However, because ConT

However, because ConTEXt MkIV does not use the kpathsea library, some setup will be required whenever you install new files manually (without using tlmgr). After each such installation, each MkIV user must run:

  contextcontext --generate
-

to refresh the ConT

to refresh the ConTEXt disk cache data. The resulting files are stored under TEXMFCACHE. whose default value in +class="ec-lmtt-10">TEXMFCACHE, whose default value in TEX Live is TEXMSYSVAR;TEXMFVAR. -

ConTTEXMFSYSVAR;TEXMFVAR. +

ConTEXt MkIV will read from all paths mentioned in TEXMFCACHE, and write to the first path that is writable. While reading, the last found match will take precedence in the case of duplicated cache data. -

For more information, see

For more information, see http://wiki.contextgarden.net/Running_Mark_IV. -

+

3.4.6 Integrating local and personal macros
-

This is already mentioned implicitly in section 

This is already mentioned implicitly in section 2.3: TEXMFLOCAL (by default, /usr/local/texlive/texmf-local @@ -2639,7 +2509,7 @@ class="ec-lmtt-10">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 T

For both trees, files should be placed in their proper TEX Directory Structure (TDS) subdirectories; see 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 +

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 @@ -2667,36 +2535,36 @@ of directories, within braces, separated by commas:

    TEXMFHOME = {/my/dir1,/mydir2,/a/third/dir}
+ id="x1-36002r1">  TEXMFHOME = {/my/dir1,/mydir2,/a/third/dir}
-

-

Section 

+

Section 7.1.5 describes brace expansion further. -

+

3.4.7 Integrating third-party fonts
-

This is unfortunately a messy topic. Forget about it unless you want to delve into many details of the T

This is unfortunately a messy topic. Forget about it unless you want to delve into many details of the TEX installation. Many fonts are included in TEX Live already, so take a look if you don’t already know that what you want isn’t there. -

A possible alternative is to use XeT

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

If you do need to do this, see http://tug.org/fonts/fontinstall.html for our best effort at describing the procedure. -

+

3.5 Testing the installation

-

After installing T

After installing TEX Live, you naturally want to test it out, so you can start creating beautiful documents and/or fonts. -

One thing you may immediately be looking for is a front-end with which to edit files. T

One thing you may immediately be looking for is a front-end with which to edit files. TEX Live installs TEXworks (http://tug.org/interest.html#editors. Any plain text editor will work; something TEX-specific is not required. -

The rest of this section gives some basic procedures for testing that the new system is functional. We give +

The rest of 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. -

+

  1. Make sure that you can run the tex program in the first place:
    -

    + +

    > ... class="ec-lmtt-10">bin subdirectory in your PATH. See the environment-setting information on p. 39. +href="#x1-310003.4.1">40.
  2. Process a basic LATEX file:
    -

    + +

    > 68.)
  3. Preview the result online:
    -

    + +

    > display’.
  4. Create a PostScript file for printing or display:
    -

    + +

    >  sample2e.ps class="enumerate" id="x1-38010x5">Create a PDF file instead of DVI; this processes the .tex file and writes PDF directly:
    -

    + +

    >  sample2e.tex
  5. Preview the PDF file:
    -

    + +

    > http://blog.kowalczyk.info/software/sumatrapdf).
  6. Standard test files you may find useful in addition to sample2e.tex: -

    +

    - small2e.tex
    -

    A simpler document than

    A simpler document than sample2e, to reduce the input size if you’re having troubles.

    - testpage.tex
    -

    Test if your printer introduces any offsets. +

    Test if your printer introduces any offsets.

    - nfssfont.tex
    -

    For printing font tables and tests. +

    For printing font tables and tests.

    - testfont.tex
    -

    Also for font tables, but using plain T

    Also for font tables, but using plain TEX.

    - story.tex
    -

    The most canonical (plain) T

    The most canonical (plain) TEX test file of all. You must type ‘\bye’ to the * prompt after @@ -2920,7 +2794,8 @@ class="ec-lmtt-10">tex story.tex’.

    class="enumerate" id="x1-38016x8">If you have installed the xetex package, you can test its access to system fonts as follows:
    -

    + +

    >  on opentype-info.log.
    -

    If you get an error message saying “Invalid fontname ‘Latin Modern Roman/ICU’…”, then you +

    If you get an error message saying “Invalid fontname ‘Latin Modern Roman/ICU’…”, then you need to configure your system so that the fonts shipped with TEX Live can be found. See Section 3.4.4.

-

+

3.6 Links for additional downloadable software

-

If you are new to T

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: +

Links for some other tools you may consider installing:

Ghostscript
WinShell is available from http://www.winshell.de.
-

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 Specialized installations

-

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

The previous sections described the basic installation process. Here we turn to some specialized cases. -

+

4.1 Shared-user (or cross-machine) installations

-

T

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$TEXMFDIST/web2c/texmf.cnf, which contains lines such as

  TEXMFROOTTEXMFROOT = $SELFAUTOPARENT
  ...
...
  TEXMFDISTTEXMFDIST = $TEXMFROOT/texmf-dist
  ...
...
  TEXMFLOCALTEXMFLOCAL = $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 launcher

For Windows, a launcher tlaunch is available at http://tug.org/texlive/w32client.html. Its main window contains menu entries and buttons for various TEX-related programs and documentation. -

On first use, it modifies the searchpath for T

On first use, it modifies the searchpath for TEX Live and creates some file associations. It also creates a Start menu entry to undo these configurations, in addition to such an entry in the launcher menu. -

All this is set up in an ini file. You can add yourself entries for e.g. SumatraPDF or some LATEX-editor. -See the web page above for more information. -

+

All this is set up in an ini file. You can add yourself entries for, e.g., SumatraPDF or a LATEX-editor. See +the web page above for more information. +

4.2 Portable (USB) installations

-

The

The -portable installer option (or V command in the text installer or corresponding GUI 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 T

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

pict -

The ‘More…’ entry explains how you can customize this menu. -

+

The ‘More…’ entry explains how you can customize this menu. +

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 +

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, @@ -3175,50 +3044,50 @@ class="E">EX Live supported filesystems (FAT32, NTFS, HFS+).

  • Virtual machines can simply mount such an ISO.
    • -

    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. Windows 8 is the +

    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. Windows 8 is the first(!) Windows version which can do this. 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 +

    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-dist, texmf-var, 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 +

    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 such as WinCDEmu at http://wincdemu.sysprogs.org/. -

    For Windows system integration, you can include the

    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 will be able to use the DVD installation if a symlink

    On Mac OS X, TeXShop 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
    + id="x1-43002r1">sudo ln -s /Volumes/MyTeXLive/bin/universal-darwin /usr/texbin
    -

    -

    Historical note: T

    +

    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

    -

    @@ -3227,7 +3096,7 @@ class="ec-lmss-10">tlmgr: Managing your installation

    -

    pict

    tlmgr in GUI mode: main window, after ‘Load’.
    -

    -

    +

    @@ -3247,14 +3116,14 @@ class="ec-lmss-10">tlmgr in GUI mode: main window, after ‘Lo -

    pict

    Figure 10: tlmgr in GUI mode: General options
    -

    pict

    tlmgr in GUI mode: Paper size options
    -

    -

    T

    +

    TEX Live includes a program named tlmgr for managing TEX Live after the initial installation. Its @@ -3280,7 +3149,7 @@ capabilities include:

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

    tlmgr’s functionality completely subsumes the texconfig program. We still distribute and maintain texconfig @@ -3289,10 +3158,11 @@ class="ec-lmss-10">tlmgr nowadays.

    5.1 tlmgr GUI mode

    -

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

    -

    + +

    > TeX Live ..., 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 

    Figures 10 and 11 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:install: collection-xetex
      install:install: arabxetex
      ...
    ...
      install:install: xetex
      install: xetexconfig -
    install: xetexconfig
      install: xetex.i386-linux
    install: xetex.i386-linux +
      runningrunning post install action for xetex
      install:install: xetex-def
      ...
    ...
      running mktexlsr -
    running mktexlsr
      mktexlsr:mktexlsr: Updating /usr/local/texlive/2016/texmf-dist/ls-R...
      ...
    ... +
      runningrunning fmtutil-sys --missing
      ... -
    ...
      TranscriptTranscript written on xelatex.log.
      fmtutil:fmtutil: /usr/local/texlive/2016/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):

    + +

    >  collection-latexextra
    which produces output like this:
      package:package:    collection-latexextra
      category:category:   Collection
      shortdesc:shortdesc:  LaTeX supplementary packages
      longdesc:longdesc:   A packages for LaTeX.
      installed:installed:  Yes
      revision:revision:   32768
    -

    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
    -

    +

    6 Notes on Windows

    -

    +

    6.1 Windows-specific features

    -

    Under Windows, the installer does some extra things: +

    Under Windows, the installer does some extra things:

    Menus and shortcuts.
    EX Live is installed on a normal NTFS-formatted non-removable disk.
    -

    +

    6.2 Additional software included on Windows

    -

    To be complete, a T

    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. These programs are all installed as part of TEX Live only on Windows. -

    +

    Perl and Ghostscript.
    EX Live programs that need them know where to find them, class="ec-lmbx-10">PS_View.
    Also installed is PS_View, a PostScript and PDF viewer; see figure 12. -

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

    +

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

    +

    6.3 User Profile is Home

    -

    The Windows counterpart of a Unix home directory is the

    The Windows counterpart of a Unix home directory is the %USERPROFILE% directory. Under Windows XP, 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. -

    +

    6.4 The Windows registry

    -

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

    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 HKLM is normally in a subdirectory of the Windo 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. -

    +

    6.5 Windows permissions

    -

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

    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. We have made an effort to make TEX Live installable without administrative privileges. -

    If the installer is started with administrative permissions, there is an option to install for all users. If this +

    If the installer is started with administrative permissions, 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 @@ -3707,14 +3560,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 Windows Vista and later, you should be aware that even if you are logged in as administrator, you need +

    For Windows Vista and later, you should be aware that 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’. -

    +

    6.6 Increasing maximum memory on Windows and Cygwin

    -

    Windows and Cygwin (see section 

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

    +

      WindowsWindows Registry Editor Version 5.00
      

      [HKEY_LOCAL_MACHINE\Software\Cygwin]
    [HKEY_LOCAL_MACHINE\Software\Cygwin]
      "heap_chunk_in_mb"=dword:ffffff00
    -

    and then execute the command "heap_chunk_in_mb"=dword:ffffff00

    +

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

    +

    7 A user’s guide to Web2C

    -

    Web2C is an integrated collection of T

    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 @@ -3770,89 +3618,89 @@ additional contributors, and in 1997 he handed the baton to Olaf Weber, who retu 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
    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. @@ -3860,58 +3708,58 @@ class="ec-lmtt-10">WEB pool files. tangle

    -

    WEB to Pascal.

    tex
    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 +This library uses a combination of environment variables and 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 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. -

    +

    7.1 Kpathsea path searching

    -

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

    We call a

    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 65) applies to 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 +

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

    +

    7.1.1 Path sources
    -

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

    +

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

    1. A user-set environment variable, for instance, TEXINPUTS=/c:/d’ (see below).
    2. The compile-time default.
    -

    You can see each of these values for a given search path by using the debugging options (see “Debugging actions” +

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

    +

    7.1.2 Config files
    -

    Kpathsea reads

    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 .../2016/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 .../2016/texmf-dist/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/texmf.cnf. class="ec-lmtt-10">% and continue to the end of the line.

  • Blank lines are ignored. - -
  • A \ at the end of a line acts as a continuation character, i.e., the next line is appended. Whitespace at the beginning of continuation lines is not ignored.
  • Each remaining line has the form:
    -

    + +

      ] [=] value + +
    where the ‘=’ and surrounding whitespace are optional. @@ -4090,13 +3923,12 @@ class="ec-lmtt-10">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: +

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

    +

    7.1.3 Path expansion
    -

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

    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 baz. These expansions are explained in the sections below.

    7.1.4 Default expansion
    -

    If the highest-priority search path (see “Path sources” on page 

    If the highest-priority search path (see “Path sources” on page 60) 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

    -

    + +

    > setenv TEXINPUTS /home/karl: - -
    and a TEXINPUTS value from texmf.cnf of
    -

    + +

      .:$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 ‘:’. -

    +

    7.1.5 Brace expansion
    -

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

    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 T

        TEXMF = {$TEXMFVAR,$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFDIST}
    + id="x1-60002r1">  TEXMF = {$TEXMFVAR,$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFDIST}
    -

    We can then use this to define, for example, the T

    We can then use this to define, for example, the TEX input path:

        TEXINPUTS = .;$TEXMF/tex//
    + id="x1-60004r1">  TEXINPUTS = .;$TEXMF/tex//
    -

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

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

    +

    7.1.6 Subdirectory expansion
    -

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

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

    +

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

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

    +

    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.

    -

    +

    7.2 Filename databases

    -

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

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

    +

    7.2.1 The filename database
    -

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

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

    +

    7.2.2 kpsewhich: Standalone path searching
    -

    The

    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 @@ -4452,7 +4284,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. @@ -4471,7 +4303,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.

    -

    +

    7.2.3 Examples of use
    -

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

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

    +

    7.2.4 Debugging actions
    -

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

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

    +

     1
     1
    -

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

     2
     2
    -

    References to hash tables (such as

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

     4
     4
    -

    File open and close operations. +

    File open and close operations.

     8
     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
    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
    32
    -

    File searches. +

    File searches.

    64
    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. @@ -4860,18 +4703,19 @@ input.

        \documentclass{article}
        \begin{document}
        Hello World!
        \end{document}
    + id="x1-67002r1">  \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 the dvips reference manual). The output (slightly rearranged) appears in Figure 13. -

    @@ -4964,75 +4806,10 @@ class="ec-lmtt-9">=>/usr/local/texmf/dvips/cms/config.cms
    Figure 13: Finding configuration files
    -
    kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0,
      path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//:
           ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//).
    kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro
    -
    Figure 14: Finding the prolog file
    -
    kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0,
      path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//:
           /var/tex/fonts/tfm//).
    kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm
    kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0,
       ...
    <texps.pro>
    kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0,
      path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//:
           ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//).
    kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb
    <cmr10.pfb>[1]
    -
    Figure 15: 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.

    -

    + +

    > psfonts.map, which is always loaded (it contains declarations for commonly used PostScript fonts; see the last part of Section 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,<cmr10.pfb>[1]

    7.3 Runtime options

    -

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

    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 @@ -5242,7 +5024,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. @@ -5250,27 +5032,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. -

    +

    8 Acknowledgements

    -

    T

    TEX Live is a joint effort by virtually all of the TEX user groups. This edition of TEX Live was overseen by @@ -5323,7 +5105,7 @@ class="E">EX4ht is used to create the HTML version of this documen 2009, and we dedicate this documentation to his memory.

  • Hans Hagen, for much testing and making his ConTEXt format (EXt package (http://pragma-ade.com) work within TEX Live, and coordinator of the many
  • Graham Williams, the originator of the TEX Catalogue.
    • -

    Builders of the binaries: Ettore Aldrovandi (

    Builders of the binaries: Ettore Aldrovandi (i386-solaris, x86_64-solaris), Marc Baudoin (amd64-netbsd, @@ -5472,23 +5254,23 @@ class="E">EX Live build process, see http://tug.org/texlive/build.html. -

    Translators of this manual: Denis Bitouzé (French), Carlos Enriquez Figueras (Spanish), Jjgod Jiang, +

    Translators of this manual: Denis Bitouzé (French), Carlos Enriquez Figueras (Spanish), Jjgod Jiang, Jinsong Zhao, Yue Wang, & Helin Gai (Chinese), Nikola Lečić (Serbian), Marco Pallante (Italian), Petr Sojka & Jan Busa (Czech/Slovak), Boris Veytsman (Russian), Staszek Wawrykiewicz (Polish), Uwe Ziegenhagen (German). 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. -

    +

    9 Release history

    -

    +

    9.1 Past

    -

    Discussion began in late 1993 when the Dutch T

    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 @@ -5514,25 +5296,25 @@ 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 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 -teTTEX, 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 teTtexconfig 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 +class="E">EX 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, thanks to Fabrice +Popineau. +

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

    +

    9.1.1 2003
    -

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

    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, @@ -5611,16 +5393,16 @@ class="ec-lmtt-10">texmf/web2c/cp8bit.tcx. (Future releases

  • Finally, since the edition numbers had grown unwieldy, the version is now simply identified by the year: TEX Live 2003.
    • -

    +

    9.1.2 2004
    -

    2004 saw many changes: +

    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 @@ -5631,7 +5413,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. @@ -5707,7 +5489,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

        \input "filename with spaces"   % plain
        \input{"filename with spaces"}  % latex
      + id="x1-73002r1">\input "filename with spaces"   % plain
      \input{"filename with spaces"}  % latex
    -

    See the Web2C manual for more:

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

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

    +

    9.1.3 2005
    -

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

    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,
        latex --translate-file=empty.tcx yourfile.tex
      + id="x1-74002r1">latex --translate-file=empty.tcx yourfile.tex
    -

    +

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

    +

    9.1.4 2006–2007
    -

    In 2006–2007, the major new addition to T

    In 2006–2007, the major new addition to TEX Live was the XeTEX program, available as the xetex and @@ -5933,14 +5715,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://mirror.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 (http://tug.org/tetex). As a result, there was been a surge of interest in Thttp://tug.org/tetex). As a result, there was 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. -

    +

    9.1.5 2008
    -

    In 2008, the entire T

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

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

    +

    9.1.6 2009
    -

    In 2009, the default output format for Lua(L

    In 2009, the default output format for Lua(LA )TEX is now PDF, to take advantage of LuaTEX’s OpenType @@ -6060,9 +5842,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. dvipdfmx includes CJK support and has accumulated many other fixes over the years since the last dvipdfm release. -

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

    +

    9.1.7 2010
    -

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

    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 @@ -6146,16 +5928,16 @@ 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 repstopdf, makeindex, kpsewhich, bibtex, and bibtex8; -the list is defined in 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 @@ -6165,7 +5947,7 @@ class="ec-lmtt-10"> 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, @@ -6205,7 +5987,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. -

    +

    9.1.8 2011
    -

    The Mac OS X binaries (

    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

    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 (

    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

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

    The

    The initex and inimf programs were restored (but no other ini* variants). -

    +

    9.1.9 2012
    -

    tlmgr supports updates from multiple network repositories. The section on multiple repositories in the tlmgr help output has more. -

    The parameter

    The parameter \XeTeXdashbreakstate is set to 1 by default, for both xetex and xelatex. This allows line @@ -6267,53 +6049,53 @@ class="E">EX documents which must retain perfect line-break class="ec-lmtt-10">\XeTeXdashbreakstate to 0 explicitly. -

    The output files generated by

    The output files generated by pdftex and dvips, among others, can now exceed 2gb. -

    The 35 standard PostScript fonts are included in the output of dvips, among others, can now exceed 2 gigabytes. +

    The 35 standard PostScript fonts are included in the output of dvips by default, since so many different versions of them are extant. -

    In the restricted

    In the restricted \write18 execution mode, set by default, mpost is now an allowed program. -

    A

    A texmf.cnf file is also found in ../texmf-local, e.g., /usr/local/texlive/texmf-local/web2c/texmf.cnf, if it exists. -

    The

    The updmap script reads a per-tree updmap.cfg instead of one global config. This change should be invisible, unless you edited your updmap.cfg’s directly. The updmap --help output has more. -

    Platforms:

    Platforms: armel-linux and mipsel-linux added; sparc-linux and i386-netbsd are no longer in the main distribution. -

    +

    9.1.10 2013
    -

    Distribution layout: the top-level

    Distribution layout: the top-level texmf/ directory has been merged into texmf-dist/, for simplicity. Both the TEXMFMAIN and TEXMFDIST Kpathsea variables now point to texmf-dist. -

    Many small language collections have been merged together, to simplify installation. -

    MetaPost: native support for PNG output and floating-point (IEEE double) has been added. -

    LuaT

    Many small language collections have been merged together, to simplify installation. +

    MetaPost: native support for PNG output and floating-point (IEEE double) has been added. +

    LuaTEX: updated to Lua 5.2, and includes a new library (pdfscanner) to process external PDF page content, among much else (see its web pages). -

    XeT

    XeTEX (also see its web pages for more):

      -
    • The HarfBuzz library now used for font layout instead of ICU. (ICU is still used to support input - encodings, bidirectionality, and the optional Unicode line breaking.) +
    • The HarfBuzz library is now used for font layout instead of ICU. (ICU is still used to support + input encodings, bidirectionality, and the optional Unicode line breaking.)
    • Graphite2 and HarfBuzz are used instead of SilGraphite for Graphite layout.
      • @@ -6326,15 +6108,15 @@ class="E">EX and xdvipdfmx.
    • Support OpenType math cut-ins.
    -

    xdvi: now uses FreeType instead of t1lib for rendering. -

    microtype.sty: some support for XeTEX (protrusion) and LuaTEX (protrusion, font expansion, tracking), among other enhancements. -

    tlmgr: new pinning action to ease configuring multiple repositories; that section in tlmgr --help has more, online at http://tug.org/texlive/doc/tlmgr.html#MULTIPLE-REPOSITORIES. -

    Platforms:

    Platforms: armhf-linux, mips-irix, i386-netbsd, and amd64-netbsd added or revived; powerpc-aix removed. -

    +

    9.1.11 2014
    -

    2014 saw another T

    2014 saw another TEX tune-up from Knuth; this affected all engines, but the only visible change likely is the restoration of the preloaded format string on the banner line. Per Knuth, this now reflects the format that would be loaded by default, rather than an undumped format that is actually preloaded in the binary; it may be overridden in various ways. -

    pdfT

    pdfTEX: new warning-suppression parameter \pdfsuppresswarningpagegroup; new primitives for fake interword spaces to help with PDF text reflowing: \pdfinterwordspaceoff, class="ec-lmtt-10">\pdffakespace. -

    LuaT

    LuaTEX: Notable changes and fixes were made to font loading and hyphenation. The biggest addition is a new engine variant, luajittex (luatex. Neither we nor its developers recommend using it except for the specific purpose of experimenting with jit on Lua code. -

    XeT

    XeTEX: The same image formats are now supported on all platforms (including Mac); avoid Unicode compatibility decomposition fallback (but not other variants); prefer OpenType to Graphite fonts, for compatibility with previous XeTEX versions. -

    MetaPost: A new numbersystem

    MetaPost: A new numbersystem decimal is supported, along with a companion internal numberprecision; a new definition of drawdot in plain.mp, per Knuth; bug fixes in SVG and PNG output, among others. -

    The

    The pstopdf ConTEXt utility will be removed as a standalone command at some point after the release, due to conflicts with OS utilities of the same name. It can still (and now) be invoked as mtxrun –script pstopdf. -

    psutils has been substantially revised by a new maintainer. As a result, several seldom-used utilities (fix*, scripts/ directory rather than being user-level executables (this can be reversed if it turns out to be problematic). A new script, psjoin, has been added. -

    The MacT

    The MacTEX redistribution of TEX Live (section 3.1.2) no longer includes the optional Mac-only @@ -6428,17 +6210,17 @@ class="ec-lmss-10">convert program from ImageMagick has also been excised class="E">EX4ht (specifically tex4ht.env) now uses Ghostscript directly. -

    The

    The langcjk collection for Chinese, Japanese, and Korean support has been split into individual language collections for the sake of more moderate sizes. -

    Platforms:

    Platforms: x86_64-cygwin added, mips-irix removed; Microsoft no longer supports Windows XP, so our programs may start failing there at any time. -

    +

    9.1.12 2015
    -

    LaTeX2e now incorporates, by default, changes previously included only by explicitly loading the

    LaTeX2e now incorporates, by default, changes previously included only by explicitly loading the fixltx2e package, which is now a no-op. A new latexrelease package and other mechanisms allow for controlling what is @@ -6450,34 +6232,34 @@ and psnfss packages, while core parts of LATEX, are maintained separately and are not affected by these changes (and should still work). -

    Internally, LaTeX2e now includes Unicode-related engine configuration (what characters are letters, +

    Internally, LaTeX2e now includes Unicode-related engine configuration (what characters are letters, naming of primitives, etc.) which was previously part of TEX Live. This change is intended to be invisible to users; a few low-level internal control sequences have been renamed or removed, but the behavior should be just the same. -

    pdfT

    pdfTEX: Support JPEG Exif as well as JFIF; do not emit a warning if \pdfinclusionerrorlevel is negative; sync with xpdf 3.04. -

    LuaT

    LuaTEX: New library newtokenlib for scanning tokens; bug fixes in the normal random number generator and other places. -

    XeT

    XeTEX: Image handling fixes; xdvipdfmx binary looked for first as a sibling to xetex; internal XDV opcodes changed. -

    MetaPost: New numbersystem

    MetaPost: New numbersystem binary; new Japanese-enabled upmpost and updvitomp programs, analogous to up*tex. -

    MacT

    MacTEX: Updates to the included Ghostscript package for CJK support. The TEX Distribution Preference Pane now works in Yosemite (Mac OS X 10.10). Resource-fork font suitcases (generally @@ -6485,7 +6267,7 @@ without an extension) are no longer supported by XeTEX; data-fork suitcases (.dfont) remain supported. -

    Infrastructure: The

    Infrastructure: The fmtutil script has been reimplemented to read fmtutil.cnf on a per-tree basis, analogous to mktextfm, mktexpk) now prefer programs in their own directory, instead of always using the existing PATH. -

    Platforms:

    Platforms: *-kfreebsd removed, since TEX Live is now easily available through the system platform mechanisms. Support for some additional platforms is available as custom binaries @@ -6506,10 +6288,10 @@ class="ec-lmtt-10">http://tug.org/texlive/custom-bin.html). In additi DVD (simply to save space), but can be installed normally over the net. -

    +

    9.2 Present—2016

    -

    LuaT

    LuaTEX: Sweeping changes to primitives, both renames and removals, along with some node structure rearrangements. The changes are summarized in an article by Hans Hagen, “LuaTEX 0.90 backend changes for @@ -6519,10 +6301,10 @@ class="ec-lmtt-10">http://tug.org/TUGboat/tb37-1/tb115hagen-pdf.pdf); LuaTEX manual, texmf-dist/doc/luatex/base/luatex.pdf. -

    Metafont: New highly experimental sibling programs MFlua and MFluajit, integrating Lua with Metafont, +

    Metafont: New highly experimental sibling programs MFlua and MFluajit, integrating Lua with Metafont, for trial testing purposes. -

    MetaPost: Bug fixes and internal preparations for MetaPost 2.0. -

    MetaPost: Bug fixes and internal preparations for MetaPost 2.0. +

    SOURCE_DATE_EPOCH support in all engines except LuaTEX (which will come in the next release) and original \day, \time. The pdfTEX manual has examples and details. -

    pdfT

    pdfTEX: new primitives \pdfinfoomitdate, \pdftrailerid, \pdfsuppressptexinfo, to control values appearing in the output which normally change with each run. These features are for PDF output only, not DVI. -

    XeT

    XeTEX: New primitives \XeTeXhyphenatablelength, \XeTeXgenerateactualtext,
    \XeTeXinterwordspaceshaping, \mdfivesum; character class limit increased to 4096; DVI id byte incremented. -

    Other utilities: +

    Other utilities:

    • gregorio is a new program, part of the -a omits all
    • ps2pk can handle extended PK/GF fonts.
    -

    MacT

    MacTEX: The TEX Distribution Preference Pane is gone; its functionality is now in TeX Live Utility; bundled GUI applications upgraded; new script cjk-gs-integrate to be run by users who wish to incorporate various CJK fonts into Ghostscript. -

    Infrastructure: System-level

    Infrastructure: System-level tlmgr configuration file supported; verify package checksums; if GPG is available, verify signature of network updates. These checks happen with both the installer and +tlmgr. (If GPG is not available, updates proceed as usual.) -

    Platforms:

    Platforms: alpha-linux and mipsel-linux removed. -

    +

    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:

    -

    tex-live@tug.org
    http://tug.org/texlive

    -

    Happy T