pdftex[903] branches/stable/source/src: sync from tl 66039
commits+karl at tug.org
commits+karl at tug.org
Tue Feb 21 23:38:25 CET 2023
Revision: 903
http://tug.org/svn/pdftex?view=revision&revision=903
Author: karl
Date: 2023-02-21 23:38:24 +0100 (Tue, 21 Feb 2023)
Log Message:
-----------
sync from tl 66039
Modified Paths:
--------------
branches/stable/source/src/build-aux/config.sub
branches/stable/source/src/configure
branches/stable/source/src/doc/build-tools.txt
branches/stable/source/src/doc/tlbuild.info
branches/stable/source/src/doc/tlbuild.texi
branches/stable/source/src/libs/README
branches/stable/source/src/libs/configure
branches/stable/source/src/libs/libpng/ChangeLog
branches/stable/source/src/libs/libpng/Makefile.in
branches/stable/source/src/libs/libpng/aclocal.m4
branches/stable/source/src/libs/libpng/configure
branches/stable/source/src/libs/libpng/configure.ac
branches/stable/source/src/libs/libpng/include/Makefile.in
branches/stable/source/src/texk/README
branches/stable/source/src/texk/configure
branches/stable/source/src/texk/kpathsea/ChangeLog
branches/stable/source/src/texk/kpathsea/NEWS
branches/stable/source/src/texk/kpathsea/c-auto.in
branches/stable/source/src/texk/kpathsea/configure
branches/stable/source/src/texk/kpathsea/doc/kpathsea.info
branches/stable/source/src/texk/kpathsea/doc/kpathsea.texi
branches/stable/source/src/texk/kpathsea/kpsewhich.c
branches/stable/source/src/texk/kpathsea/texmf.cnf
branches/stable/source/src/texk/kpathsea/version.ac
branches/stable/source/src/texk/tests/TeXLive/TLConfig.pm
branches/stable/source/src/texk/tests/TeXLive/TLUtils.pm
branches/stable/source/src/texk/web2c/ChangeLog
branches/stable/source/src/texk/web2c/Makefile.in
branches/stable/source/src/texk/web2c/NEWS
branches/stable/source/src/texk/web2c/ac/web2c.ac
branches/stable/source/src/texk/web2c/configure
branches/stable/source/src/texk/web2c/doc/web2c.info
branches/stable/source/src/texk/web2c/doc/web2c.texi
branches/stable/source/src/texk/web2c/enctexdir/enctex-pdftex.ch
branches/stable/source/src/texk/web2c/enctexdir/enctex2.ch
branches/stable/source/src/texk/web2c/pdftexdir/ChangeLog
branches/stable/source/src/texk/web2c/pdftexdir/NEWS
branches/stable/source/src/texk/web2c/pdftexdir/mapfile.c
branches/stable/source/src/texk/web2c/pdftexdir/pdftex.ch
branches/stable/source/src/texk/web2c/pdftexdir/pdftex.defines
branches/stable/source/src/texk/web2c/pdftexdir/pdftex.web
branches/stable/source/src/texk/web2c/pdftexdir/pdftex_version.h
branches/stable/source/src/texk/web2c/pdftexdir/ptexlib.h
branches/stable/source/src/texk/web2c/pdftexdir/tounicode.c
branches/stable/source/src/texk/web2c/pdftexdir/wcfname.test
branches/stable/source/src/texk/web2c/pdftexdir/writet1.c
branches/stable/source/src/texk/web2c/tests/fn-generate.perl
branches/stable/source/src/texk/web2c/web2c/configure
branches/stable/source/src/utils/README
branches/stable/source/src/utils/configure
branches/stable/source/src/version.ac
Modified: branches/stable/source/src/build-aux/config.sub
===================================================================
--- branches/stable/source/src/build-aux/config.sub 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/build-aux/config.sub 2023-02-21 22:38:24 UTC (rev 903)
@@ -4,7 +4,7 @@
# shellcheck disable=SC2006,SC2268 # see below for rationale
-timestamp='2023-01-01'
+timestamp='2023-01-21'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -1075,7 +1075,7 @@
pentium-* | p5-* | k5-* | k6-* | nexgen-* | viac3-*)
cpu=i586
;;
- pentiumpro-* | p6-* | 6x86-* | athlon-* | athalon_*-*)
+ pentiumpro-* | p6-* | 6x86-* | athlon-* | athlon_*-*)
cpu=i686
;;
pentiumii-* | pentium2-* | pentiumiii-* | pentium3-*)
Modified: branches/stable/source/src/configure
===================================================================
--- branches/stable/source/src/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1664,11 +1664,11 @@
--enable-tex-synctex build TeX with SyncTeX support
--enable-etex compile and install e-TeX
--disable-etex-synctex build e-TeX without SyncTeX support
- --disable-ptex do not compile and install pTeX
+ --enable-ptex compile and install pTeX
--disable-ptex-synctex build pTeX without SyncTeX support
--disable-eptex do not compile and install e-pTeX
--disable-eptex-synctex build e-pTeX without SyncTeX support
- --disable-uptex do not compile and install upTeX
+ --enable-uptex compile and install upTeX
--disable-uptex-synctex build upTeX without SyncTeX support
--disable-euptex do not compile and install e-upTeX
--disable-euptex-synctex build e-upTeX without SyncTeX support
@@ -5408,7 +5408,7 @@
yes | no) :
;; #(
*) :
- enable_ptex=yes ;;
+ enable_ptex=no ;;
esac
# Check whether --enable-ptex-synctex was given.
@@ -5452,7 +5452,7 @@
yes | no) :
;; #(
*) :
- enable_uptex=yes ;;
+ enable_uptex=no ;;
esac
# Check whether --enable-uptex-synctex was given.
@@ -26430,11 +26430,11 @@
test "x$srcdir" = x. || msg_compiling="$msg_compiling
from sources in $kpse_src"
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result:
-** Configuration summary for $PACKAGE_STRING (2023/dev$with_banner_add):
+** Configuration summary for $PACKAGE_STRING (2023$with_banner_add):
$msg_compiling" >&5
printf "%s\n" "
-** Configuration summary for $PACKAGE_STRING (2023/dev$with_banner_add):
+** Configuration summary for $PACKAGE_STRING (2023$with_banner_add):
$msg_compiling" >&6; }
case $kpse_src$kpse_bld in
Modified: branches/stable/source/src/doc/build-tools.txt
===================================================================
--- branches/stable/source/src/doc/build-tools.txt 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/doc/build-tools.txt 2023-02-21 22:38:24 UTC (rev 903)
@@ -2,6 +2,6 @@
automake (GNU automake) 1.16.5
bison (GNU Bison) 3.8.2
flex 2.6.0
-ltmain.sh (GNU libtool) 2.4.6
+ltmain.sh (GNU libtool) 2.4.7
m4 (GNU M4) 1.4.19
-makeinfo (GNU texinfo) 6.7
+makeinfo (GNU texinfo) 7.0.2
Modified: branches/stable/source/src/doc/tlbuild.info
===================================================================
--- branches/stable/source/src/doc/tlbuild.info 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/doc/tlbuild.info 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,10 +1,10 @@
-This is tlbuild.info, produced by makeinfo version 5.1 from
+This is tlbuild.info, produced by makeinfo version 7.0.2 from
tlbuild.texi.
This file documents the TeX Live build system and more.
-Copyright (C) 2016-2022 Karl Berry.
-Copyright (C) 2013-2015 Karl Berry & Peter Breitenlohner.
+Copyright © 2016–2023 Karl Berry.
+Copyright © 2013–2015 Karl Berry & Peter Breitenlohner.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
@@ -33,7 +33,7 @@
File: tlbuild.info, Node: Top, Next: Introduction, Up: (dir)
-Building TeX Live (2022)
+Building TeX Live (2023)
************************
For an overview of this manual, *note Introduction::.
@@ -59,17 +59,18 @@
1 Introduction
**************
-This manual (dated May 2022) corresponds to the TeX Live 2022 release.
+This manual (dated February 2023) corresponds to the TeX Live 2023
+release.
This manual is aimed at system installers and programmers, and
focuses on how to configure, build, and develop the TeX Live (TL)
sources. It is also available as plain text files in the source tree:
-'source/README.*'.
+‘source/README.*’.
- The main 'source/README' file in the TL source tree provides
+ The main ‘source/README’ file in the TL source tree provides
maximally-terse information for doing a build, and portability
information for different systems, along with
-'source/doc/README.solaris'.
+‘source/doc/README.solaris’.
For information on acquiring the TL sources, see
<https://tug.org/texlive/svn>. The canonical source repository uses
@@ -78,27 +79,27 @@
This manual does not duplicate the information found in other TL
documentation resources, such as:
- * The TeX Live web pages: <https://tug.org/texlive>.
+ • The TeX Live web pages: <https://tug.org/texlive>.
- * The web page describing how to build the binaries which are
+ • The web page describing how to build the binaries which are
distributed with TeX Live: <https://tug.org/texlive/build.html>.
- * The TeX Live user manual: <https://tug.org/texlive/doc.html>, or
- run 'texdoc texlive'.
+ • The TeX Live user manual: <https://tug.org/texlive/doc.html>, or
+ run ‘texdoc texlive’.
- * Other TeX-related Texinfo manuals (*note (web2c)::, *note
+ • Other TeX-related Texinfo manuals (*note (web2c)::, *note
(kpathsea)::, etc.): <https://tug.org/texinfohtml/>, or check the
- 'TeX' category in the GNU Info system.
+ ‘TeX’ category in the GNU Info system.
- * Package documentation:
- <https://tug.org/texlive/Contents/live/doc.html>, or the 'doc.html'
+ • Package documentation:
+ <https://tug.org/texlive/Contents/live/doc.html>, or the ‘doc.html’
file at the top level of the installed TL.
- As an exception, the full documentation for 'install-tl' and 'tlmgr'
+ As an exception, the full documentation for ‘install-tl’ and ‘tlmgr’
is included here as appendices, simply because it is easy to do so. The
same text is available online (linked from
<https://tug.org/texlive/doc.html>, or by invoking the program with
-'--help' (or look at the end of the source).
+‘--help’ (or look at the end of the source).
File: tlbuild.info, Node: Overview of build system, Next: Prerequisites, Prev: Introduction, Up: Top
@@ -108,34 +109,34 @@
The TeX Live build system was redesigned in 2009 to consistently use
Autoconf, Automake, and Libtool. Thus, running
- 'configure && make && make check && make install'
-or the essentially-equivalent top-level 'Build' script suffices to build
-and install the TL programs. The 'make check' clause performs various
-tests of the generated programs--not strictly required but strongly
-recommended. Running 'configure --help' will display a comprehensive
-list of all 'configure' options.
+ ‘configure && make && make check && make install’
+or the essentially-equivalent top-level ‘Build’ script suffices to build
+and install the TL programs. The ‘make check’ clause performs various
+tests of the generated programs—not strictly required but strongly
+recommended. Running ‘configure --help’ will display a comprehensive
+list of all ‘configure’ options.
The main components of the TL build system are:
-'libs/LIB'
+‘libs/LIB’
Generic libraries.
-'texk/LIB'
- TeX-specific libraries in subdirectories, notably LIB='kpathsea'.
- (The other one is 'texk/ptexenc'.)
+‘texk/LIB’
+ TeX-specific libraries in subdirectories, notably LIB=‘kpathsea’.
+ (The other one is ‘texk/ptexenc’.)
-'texk/PROG'
+‘texk/PROG’
TeX-specific programs (that use Kpathsea).
-'utils/PROG'
- Other programs (that don't use Kpathsea).
+‘utils/PROG’
+ Other programs (that don’t use Kpathsea).
The primary design goal of the build system is modularity. Each
program and library module (or package) specifies its own requirements
and properties, such as required libraries, whether an installed
-(system) version of a library can be used, 'configure' options to be
+(system) version of a library can be used, ‘configure’ options to be
seen at the top level, and more. An explicit list of all available
-modules is kept in a single central place: 'm4/kpse-pkgs.m4'.
+modules is kept in a single central place: ‘m4/kpse-pkgs.m4’.
A second, related goal is to configure and build each library before
configuring any other (program or library) module which uses that
@@ -158,60 +159,60 @@
***************
Overall, building the TeX Live programs, when using all libraries from
-the TL source tree, requires C and C++11 compilers, GNU 'make', and
+the TL source tree, requires C and C++11 compilers, GNU ‘make’, and
Python.
- * If 'make' from your 'PATH' is not GNU 'make', you can set the
- 'MAKE' environment variable to whatever is necessary.
+ • If ‘make’ from your ‘PATH’ is not GNU ‘make’, you can set the
+ ‘MAKE’ environment variable to whatever is necessary.
- GNU 'make' is required only because of third-party libraries,
+ GNU ‘make’ is required only because of third-party libraries,
notably FreeType. Automake/Autoconf output in general, and the
- TL-maintained directories, work with any reasonable 'make'.(1)
+ TL-maintained directories, work with any reasonable ‘make’.(1)
- * A C++11 compiler is similarly required because of the third-party
- libraries ICU and HarfBuzz (at least); the program 'dvisvgm' also
+ • A C++11 compiler is similarly required because of the third-party
+ libraries ICU and HarfBuzz (at least); the program ‘dvisvgm’ also
requires C++11. It is possible to build what remains with older
compilers, but you have to remove the C++11-dependent sources.
*Note Build one package::.
- * Python is required by ICU tests. (If you know how to disable these
+ • Python is required by ICU tests. (If you know how to disable these
tests and thus eliminate the requirement, please write.)
A few programs in the tree have additional requirements:
-'web2c'
- requires 'perl' for some tests run by 'make check'. Incidentally,
- the TeX Live installer ('install-tl') and manager ('tlmgr') are
+‘web2c’
+ requires ‘perl’ for some tests run by ‘make check’. Incidentally,
+ the TeX Live installer (‘install-tl’) and manager (‘tlmgr’) are
also written in Perl, but this does not matter for compiling the
sources.
-'xdvik'
-'xpdfopen'
+‘xdvik’
+‘xpdfopen’
require X11 headers and libraries, typically in devel(opment)
packages that are not installed by default.
-'xetex'
- requires 'fontconfig' (again both headers and library), or, for
- MacOS only, the 'ApplicationServices' and 'Cocoa' frameworks.
+‘xetex’
+ requires ‘fontconfig’ (again both headers and library), or, for
+ MacOS only, the ‘ApplicationServices’ and ‘Cocoa’ frameworks.
-'xindy'
- requires GNU 'clisp', 'libsigsegv', and 'libiconv'; additionally,
- to build the rules and/or documentation: 'perl', 'latex',
- 'pdflatex'.
+‘xindy’
+ requires GNU ‘clisp’, ‘libsigsegv’, and ‘libiconv’; additionally,
+ to build the rules and/or documentation: ‘perl’, ‘latex’,
+ ‘pdflatex’.
Lacking the required tools, building these programs must avoided, e.g.,
-'configure --without-x --disable-xetex --disable-xindy'
+‘configure --without-x --disable-xetex --disable-xindy’
Modifying source files induces more requirements, as one might
expect:
- * Modification of any '.y' or '.l' source files requires 'bison' or
- 'flex' to update the corresponding C sources.
+ • Modification of any ‘.y’ or ‘.l’ source files requires ‘bison’ or
+ ‘flex’ to update the corresponding C sources.
- * Modification of the sources for '.info' files requires 'makeinfo'.
+ • Modification of the sources for ‘.info’ files requires ‘makeinfo’.
- * Modification of any part of the build system (M4 macros,
- 'configure.ac', 'Makefile.am', or their fragments) requires GNU M4,
+ • Modification of any part of the build system (M4 macros,
+ ‘configure.ac’, ‘Makefile.am’, or their fragments) requires GNU M4,
GNU Autoconf, GNU Automake, and GNU Libtool to update the generated
files. Furthermore, to reliably reproduce the build files, the
original GNU releases of these tools must be used, not any distro
@@ -218,18 +219,18 @@
packaging of them. *Note Build system tools::, for more
discussion.
- If you haven't modified any source files, and infrastructure tools
-such as 'autoconf' or 'makeinfo' are still being run, check your
-timestamps--notably, 'use-commit-times' must be set to 'yes' in your
+ If you haven’t modified any source files, and infrastructure tools
+such as ‘autoconf’ or ‘makeinfo’ are still being run, check your
+timestamps—notably, ‘use-commit-times’ must be set to ‘yes’ in your
Subversion configuration (*note Build system tools::). No
infrastructure tools are needed to do a normal build (barring bugs).
---------- Footnotes ----------
- (1) There is one exception in TL: the 'tangle-sh' and related rules
-use '$@' to mean the target name, a feature not present in all 'make's.
-This could be alleviated by laborious editing, but since there's no way
-to avoid GNU 'make' for builds of the entire tree, it does not seem
+ (1) There is one exception in TL: the ‘tangle-sh’ and related rules
+use ‘$@’ to mean the target name, a feature not present in all ‘make’s.
+This could be alleviated by laborious editing, but since there’s no way
+to avoid GNU ‘make’ for builds of the entire tree, it does not seem
worth the trouble.
@@ -238,25 +239,25 @@
4 Building
**********
-The top-level 'Build' script is intended to simplify building the
-binaries distributed with TeX Live itself--we call this the "native" TL
-build. It runs 'configure && make world', which builds everything in a
-subdirectory of the main source tree (default 'Work/'), installs
-everything in another subdirectory (default 'inst/'), and finally runs
-'make check'. The exact directory and command names can be specified
+The top-level ‘Build’ script is intended to simplify building the
+binaries distributed with TeX Live itself—we call this the “native” TL
+build. It runs ‘configure && make world’, which builds everything in a
+subdirectory of the main source tree (default ‘Work/’), installs
+everything in another subdirectory (default ‘inst/’), and finally runs
+‘make check’. The exact directory and command names can be specified
via environment variables and a few leading options. All remaining
-arguments (assignments or options) are passed to the 'configure' script.
-Please take a look at the './Build' source file for more information; it
+arguments (assignments or options) are passed to the ‘configure’ script.
+Please take a look at the ‘./Build’ source file for more information; it
is a straightforward shell script.
An alternative, and the one we will mainly discuss here, is to run
-'configure' and 'make' in a suitable empty subdirectory. Building in
+‘configure’ and ‘make’ in a suitable empty subdirectory. Building in
the source directory itself is not supported (sorry).
* Menu:
-* Build iteration:: What 'configure' and 'make' do in TL.
-* Build in parallel:: Simultaneous 'make' processes.
+* Build iteration:: What ‘configure’ and ‘make’ do in TL.
+* Build in parallel:: Simultaneous ‘make’ processes.
* Build distribution:: Making a distribution tarball.
* Build one package:: Example of working on just one program.
* Build one engine:: Example of building just one TeX engine.
@@ -268,22 +269,22 @@
4.1 Build iteration
===================
-Running the top-level 'configure' script configures the top level and
-the subdirectories 'libs', 'utils', and 'texk'. Running 'make' at the
+Running the top-level ‘configure’ script configures the top level and
+the subdirectories ‘libs’, ‘utils’, and ‘texk’. Running ‘make’ at the
top level first iterates over the TeX-specific libraries, and then runs
-'make' in 'libs', 'utils', and 'texk' to iterate over the generic
+‘make’ in ‘libs’, ‘utils’, and ‘texk’ to iterate over the generic
libraries, utility programs, and TeX-specific programs, respectively.
These iterations consist of two steps:
1. For each library or program module not yet configured, run
- 'configure', adding the configure option '--disable-build' if the
- module need not be built, otherwise running 'make all'.
+ ‘configure’, adding the configure option ‘--disable-build’ if the
+ module need not be built, otherwise running ‘make all’.
- 2. For each library or program module that must be built, run 'make'
- for the selected target(s): 'default' or 'all' to (re-)build,
- 'check' to run tests, 'install', etc.
+ 2. For each library or program module that must be built, run ‘make’
+ for the selected target(s): ‘default’ or ‘all’ to (re-)build,
+ ‘check’ to run tests, ‘install’, etc.
- Running the top-level 'make' a second time iterates again over all
+ Running the top-level ‘make’ a second time iterates again over all
the library and program modules, and finds (should find) nothing to be
done.
@@ -293,14 +294,14 @@
4.2 Build in parallel
=====================
-The TL build system carefully formulates dependencies as well as 'make'
-rules when a tool (such as 'tangle', 'ctangle', and 'convert') creates
-several output files. This allows for parallel builds ('make -j N' with
-N>1 or even 'make -j') that can considerably speed up the TL build.
+The TL build system carefully formulates dependencies as well as ‘make’
+rules when a tool (such as ‘tangle’, ‘ctangle’, and ‘convert’) creates
+several output files. This allows for parallel builds (‘make -j N’ with
+N>1 or even ‘make -j’) that can considerably speed up the TL build.
Incidentally, a noticeable speed-up can be independently gained by
-using a configure cache file, i.e., specifying the 'configure' option
-'-C' (recommended).
+using a configure cache file, i.e., specifying the ‘configure’ option
+‘-C’ (recommended).
File: tlbuild.info, Node: Build distribution, Next: Build one package, Prev: Build in parallel, Up: Building
@@ -308,9 +309,9 @@
4.3 Build distribution
======================
-Running 'make dist' at the top level creates a tarball
-'tex-live-YYYY-MM-DD.tar.xz' from the TL source tree. Running 'make
-distcheck' also verifies that this tarball suffices to build and install
+Running ‘make dist’ at the top level creates a tarball
+‘tex-live-YYYY-MM-DD.tar.xz’ from the TL source tree. Running ‘make
+distcheck’ also verifies that this tarball suffices to build and install
all of TL.
This is useful for checking consistency of the source tree and
@@ -324,14 +325,14 @@
4.4 Build one package
=====================
-To build one package, the basic idea is to use the 'configure' option
-'--disable-all-pkgs' (*note '--disable-all-pkgs'::). Then all program
-and library modules are configured but none are made. However, the
-'Makefile's still contain all build rules and dependencies and can be
+To build one package, the basic idea is to use the ‘configure’ option
+‘--disable-all-pkgs’ (*note --disable-all-pkgs::). Then all program and
+library modules are configured but none are made. However, the
+‘Makefile’s still contain all build rules and dependencies and can be
invoked to build an individual program or library, first building any
required libraries.
- Here is an example from start to finish for working on 'dvipdfm-x'.
+ Here is an example from start to finish for working on ‘dvipdfm-x’.
Unfortunately, this does not suffice for building the TeX engines; see
the next section.
@@ -362,20 +363,20 @@
TEXMFCNF=$TEXMFROOT/texmf-dist/web2c \
./xdvipdfmx ...
- Then you can modify source files in 'mydir/texk/dvipdfm-x' and rerun
-'make' in 'mydir/Work/texk/dvipdfm-x' to rebuild; that build directory
+ Then you can modify source files in ‘mydir/texk/dvipdfm-x’ and rerun
+‘make’ in ‘mydir/Work/texk/dvipdfm-x’ to rebuild; that build directory
is where the binary ends up and where you can run a debugger, etc.
- The second line of the 'configure' invocation shows examples of extra
+ The second line of the ‘configure’ invocation shows examples of extra
things you likely want to specify if you intend to hack the sources (and
-not just build binaries): the '-C' speeds 'configure' by enabling a
-cache file, and the 'CFLAGS' and 'CXXFLAGS' settings eliminate compiler
+not just build binaries): the ‘-C’ speeds ‘configure’ by enabling a
+cache file, and the ‘CFLAGS’ and ‘CXXFLAGS’ settings eliminate compiler
optimization for debugging purposes.
Of course, you need to actually look at the output and check that
-things are working. There are many 'configure' options you can tweak as
-desired; check the output from 'configure --help'. It is also a good
-idea to run 'make check' after making any changes, to ensure that
+things are working. There are many ‘configure’ options you can tweak as
+desired; check the output from ‘configure --help’. It is also a good
+idea to run ‘make check’ after making any changes, to ensure that
whatever tests have been written still pass.
Reducing source download size
@@ -385,10 +386,10 @@
megabytes). It is natural to ask if this is really necessary. Strictly
speaking, the answer is no, but it is vastly more convenient to do so.
If you cut down the source tree, you must also give additional
-'configure' flags to individually disable using system versions of
-libraries, or the intricacies of the dependencies (such as 'teckit'
-requiring 'zlib') will have undesired side effects. For an example of
-this approach, see the 'build-pdftex.sh' script in the 'pdftex'
+‘configure’ flags to individually disable using system versions of
+libraries, or the intricacies of the dependencies (such as ‘teckit’
+requiring ‘zlib’) will have undesired side effects. For an example of
+this approach, see the ‘build-pdftex.sh’ script in the ‘pdftex’
development source (details at <http://pdftex.org>), which is indeed
such a cut-down TL source tree.
@@ -395,10 +396,10 @@
GCC used by default
...................
-By default, the 'gcc' compilers will be used if present; otherwise,
+By default, the ‘gcc’ compilers will be used if present; otherwise,
individual packages may use something different. You can explicitly
-specify the compilers to be used with the environment variables 'CC',
-'CXX', and 'OBJCXX'.
+specify the compilers to be used with the environment variables ‘CC’,
+‘CXX’, and ‘OBJCXX’.
Removing C+11 dependency
........................
@@ -405,28 +406,28 @@
Some libraries and programs require C++11; one such is XeTeX. If you
want to build with an older compiler lacking such support, you need to
-(re)move those source directories; unfortunately, specifying '--disable'
-for them does not suffice. It's also necessary to specify
-'--disable-xetex' explicitly. Specifically, before running 'configure
---disable-xetex ...':
+(re)move those source directories; unfortunately, specifying ‘--disable’
+for them does not suffice. It’s also necessary to specify
+‘--disable-xetex’ explicitly. Specifically, before running ‘configure
+--disable-xetex ...’:
rm -rf libs/icu libs/graphite2 texk/dvisvgm texk/web2c/xetexdir
- Also, even with '--disable-all-pkgs', dependencies are (currently)
+ Also, even with ‘--disable-all-pkgs’, dependencies are (currently)
checked. One notable case: if a (non-MacOS) system does not have
-'fontconfig', XeTeX cannot be built (*note Prerequisites::), and
-'configure' will terminate even with '--disable-xetex'. To proceed
-without such dependencies, specify '--enable-missing' also.
+‘fontconfig’, XeTeX cannot be built (*note Prerequisites::), and
+‘configure’ will terminate even with ‘--disable-xetex’. To proceed
+without such dependencies, specify ‘--enable-missing’ also.
As of 2022, HarfBuzz also requires C++11. Therefore even more would
-have to be disabled and removed, notably including 'luahbtex', the
+have to be disabled and removed, notably including ‘luahbtex’, the
standard engine used for LuaLaTeX. Removing that would not be
acceptable for builds intended for distribution; but perhaps for testing
the above information could still be useful.
- In general, the TL 'configure' will run in all directories.
+ In general, the TL ‘configure’ will run in all directories.
Therefore a general workaround for build problems is to remove failing
-directories from the tree, and also specify the relevant '--disable-...'
+directories from the tree, and also specify the relevant ‘--disable-...’
option(s).
Patches to improve all this would be most welcome.
@@ -454,21 +455,21 @@
cd texk/web2c # cd engine build directory
make tex # must specify target
- The first 'make' run will configure everything, and even build the
+ The first ‘make’ run will configure everything, and even build the
libraries, even though the packages are disabled.
The source tree can be cut down to just what is needed for the given
engine (the separate pdfTeX and LuaTeX source repositories do this, for
example), but see caveats in previous section. When the
-'--disable-xetex' and '--enable-missing' options are needed is also
+‘--disable-xetex’ and ‘--enable-missing’ options are needed is also
explained in the previous section.
If you want to debug an X-related program or shared library setup, or
-other variants, change the 'configure' options accordingly. Either
-'../Build' or '../configure' can be run.
+other variants, change the ‘configure’ options accordingly. Either
+‘../Build’ or ‘../configure’ can be run.
- Then it is necessary to again specify the target engine ('tex', in
-the above) in the 'make'.
+ Then it is necessary to again specify the target engine (‘tex’, in
+the above) in the ‘make’.
All these complications are rather unfortunate. Patches are welcome.
@@ -475,24 +476,24 @@
Testing one engine
..................
-To run only the tests for a given engine, say 'hitex':
+To run only the tests for a given engine, say ‘hitex’:
make -C $ww check SUBDIRS=. TESTS='$(hitex_tests)'
-where '$ww' is the web2c build directory, that is,
-'ww=/wherever/Build/source/Work/texk/web2c'.
+where ‘$ww’ is the web2c build directory, that is,
+‘ww=/wherever/Build/source/Work/texk/web2c’.
- It's also possible to run individual tests the same way, using the
-test name exactly as specified in the '.am' file:
+ It’s also possible to run individual tests the same way, using the
+test name exactly as specified in the ‘.am’ file:
make -C $ww check SUBDIRS=. TESTS=hitexdir/tests/hello.test
- If you get tired of looking at the 'Entering'/'Leaving directory'
-lines, you can add the (GNU) make option '--no-print-dir'.
+ If you get tired of looking at the ‘Entering’/‘Leaving directory’
+lines, you can add the (GNU) make option ‘--no-print-dir’.
You may find it useful to put lengthy incantations like this into a
-trivial shell script with a short name (say, 'hitst'). Then you just
-run 'hitst' and edit the file when necessary to change things around.
+trivial shell script with a short name (say, ‘hitst’). Then you just
+run ‘hitst’ and edit the file when necessary to change things around.
File: tlbuild.info, Node: Cross compilation, Prev: Build one engine, Up: Building
@@ -500,21 +501,21 @@
4.6 Cross compilation
=====================
-In a cross compilation a "build" system is used to create binaries to be
-executed on a "host" system with different hardware and/or operating
+In a cross compilation a “build” system is used to create binaries to be
+executed on a “host” system with different hardware and/or operating
system.
In simple cases, the build system can execute binaries for the host
system. This typically occurs for bi-arch systems where, e.g.,
-'i386-linux' binaries can run on 'x86_64-linux' systems and 'win32'
-binaries can run on 'win64' systems. Although sometimes called "native
-cross", technically this is not cross compilation at all. In most such
+‘i386-linux’ binaries can run on ‘x86_64-linux’ systems and ‘win32’
+binaries can run on ‘win64’ systems. Although sometimes called “native
+cross”, technically this is not cross compilation at all. In most such
cases it suffices to specify suitable compiler flags. It might be
-useful to add the configure option '--build=HOST' to get the correct
-canonical host name, but note that this should _not_ be '--host=HOST'
+useful to add the configure option ‘--build=HOST’ to get the correct
+canonical host name, but note that this should _not_ be ‘--host=HOST’
(*note (autoconf)Hosts and Cross-Compilation::).
- In order to build, e.g., 32-bit binaries with 'clang' on a 64-bit
+ In order to build, e.g., 32-bit binaries with ‘clang’ on a 64-bit
MacOS system one could use:
TL_BUILD_ENV="CC='clang -arch i386' \
@@ -535,13 +536,13 @@
In a standard cross compilation, binaries for the host system cannot
execute on the build system and it is necessary to specify the configure
-options '--host=HOST' and '--build=BUILD' with two different values.
+options ‘--host=HOST’ and ‘--build=BUILD’ with two different values.
- Building binaries requires suitable "cross" tools, e.g., compiler,
-linker, and archiver, and perhaps a "cross" version of 'pkg-config' and
+ Building binaries requires suitable “cross” tools, e.g., compiler,
+linker, and archiver, and perhaps a “cross” version of ‘pkg-config’ and
similar to locate host system libraries. Autoconf expects that these
cross tools are given by their usual variables or found under their
-usual name prefixed with 'HOST-'. Here a list of such tools and
+usual name prefixed with ‘HOST-’. Here a list of such tools and
corresponding variables:
ar AR
@@ -554,8 +555,8 @@
ranlib RANLIB
strip STRIP
-In order to, e.g., build 'mingw32' binaries on 'x86_64-linux' with a
-cross compiler found as 'i386-pc-mingw32-gcc' one would specify
+In order to, e.g., build ‘mingw32’ binaries on ‘x86_64-linux’ with a
+cross compiler found as ‘i386-pc-mingw32-gcc’ one would specify
--host=i386-pc-mingw32 --build=x86_64-linux-gnu
@@ -563,9 +564,9 @@
--host=mingw32 --build=x86_64-linux CC=i386-pc-mingw32-gcc
-but this latter, especially, might require adding 'CXX' and others.
+but this latter, especially, might require adding ‘CXX’ and others.
- Configure arguments such as 'CFLAGS=...' refer to the cross compiler.
+ Configure arguments such as ‘CFLAGS=...’ refer to the cross compiler.
If necessary, you can specify compilers and flags for the few auxiliary
C and C++ programs required for the build process as configure arguments
@@ -585,7 +586,7 @@
The fact that binaries for the host system cannot be executed on the
build system causes some problems.
- One problem is that configure tests using 'AC_RUN_IFELSE' can compile
+ One problem is that configure tests using ‘AC_RUN_IFELSE’ can compile
and link the test program but cannot execute it. Such tests should be
avoided if possible and otherwise must supply a pessimistic test result.
@@ -592,24 +593,24 @@
Another problem arises if the build process must execute some
(auxiliary or installable) programs. Auxiliary programs can be placed
into a subdirectory that is configured natively as is done for
-'texk/web2c/web2c', 'texk/dvipsk/squeeze', and 'texk/xdvik/squeeze'.
-The module 'libs/freetype2' uses the value of 'CC_BUILD', 'BUILD-gcc',
-'gcc', or 'cc' as the compiler for the auxiliary program.
+‘texk/web2c/web2c’, ‘texk/dvipsk/squeeze’, and ‘texk/xdvik/squeeze’.
+The module ‘libs/freetype2’ uses the value of ‘CC_BUILD’, ‘BUILD-gcc’,
+‘gcc’, or ‘cc’ as the compiler for the auxiliary program.
The situation for installable programs needed by the build process is
somewhat different. A rather expensive possibility, chosen for the ICU
-libraries in module 'libs/icu', is to first compile natively for the
+libraries in module ‘libs/icu’, is to first compile natively for the
build system and in a second step to use these (uninstalled) programs
during the cross compilation.
- This approach would also be possible for the tools such as 'tangle'
-used in the module 'texk/web2c' to build the WEB programs, but that
-would require first building a native 'kpathsea' library. To avoid this
+ This approach would also be possible for the tools such as ‘tangle’
+used in the module ‘texk/web2c’ to build the WEB programs, but that
+would require first building a native ‘kpathsea’ library. To avoid this
complication, cross compilation of programs written in (C)WEB requires
-sufficiently recent installed versions of 'tangle', 'ctangle',
-'otangle', and 'tie'.
+sufficiently recent installed versions of ‘tangle’, ‘ctangle’,
+‘otangle’, and ‘tie’.
- Building 'xindy' requires running the host system 'clisp' binary,
+ Building ‘xindy’ requires running the host system ‘clisp’ binary,
thus cross compilation is painful, but possible.
@@ -618,22 +619,22 @@
5 Installing
************
-This section discusses the results of 'make install' in the source tree.
+This section discusses the results of ‘make install’ in the source tree.
- The main consideration is that 'make install' is not enough to make a
+ The main consideration is that ‘make install’ is not enough to make a
usable TeX installation. Beyond the compiled binaries, (thousands of)
-support files are needed; just as a first example, 'plain.tex' is not in
+support files are needed; just as a first example, ‘plain.tex’ is not in
the source tree.
These support files are maintained completely independently and are
not present in the TL source tree. The best basis for dealing with them
-is the TeX Live (plain text) database in 'Master/tlpkg/texlive.tlpdb',
-and/or the TeX Live installer, 'install-tl'. More information is under
-'Master/tlpkg' and at <https://tug.org/texlive/distro.html>.
+is the TeX Live (plain text) database in ‘Master/tlpkg/texlive.tlpdb’,
+and/or the TeX Live installer, ‘install-tl’. More information is under
+‘Master/tlpkg’ and at <https://tug.org/texlive/distro.html>.
* Menu:
-* Installation directories:: The prefix, 'bindir', etc., directories.
+* Installation directories:: The prefix, ‘bindir’, etc., directories.
* Linked scripts:: Scripts not maintained in the sources.
* Distro builds:: Configuring and building for OS distributions.
@@ -643,15 +644,15 @@
5.1 Installation directories
============================
-Running 'make install' (or 'make install-strip') installs executables in
-'BINDIR', libraries in 'LIBDIR', headers in 'INCLUDEDIR', general data
-(including "linked scripts", *note Linked scripts::) in
-'DATAROOTDIR/texmf-dist', man pages in 'MANDIR', and Info files in
-'INFODIR'.
+Running ‘make install’ (or ‘make install-strip’) installs executables in
+‘BINDIR’, libraries in ‘LIBDIR’, headers in ‘INCLUDEDIR’, general data
+(including “linked scripts”, *note Linked scripts::) in
+‘DATAROOTDIR/texmf-dist’, man pages in ‘MANDIR’, and Info files in
+‘INFODIR’.
- The values of these directories are determined by 'configure' and can
-be specified explicitly as options such as '--prefix=PREFIX' or
-'--bindir=BINDIR'; otherwise, they are given by their usual Autoconf
+ The values of these directories are determined by ‘configure’ and can
+be specified explicitly as options such as ‘--prefix=PREFIX’ or
+‘--bindir=BINDIR’; otherwise, they are given by their usual Autoconf
defaults:
PREFIX /usr/local
@@ -665,22 +666,22 @@
except possibly modified as follows:
- * If the option '--enable-multiplatform' is given, '/PLATFORM' (i.e.,
- the canonical platform name) is appended to 'BINDIR' and 'LIBDIR'.
+ • If the option ‘--enable-multiplatform’ is given, ‘/PLATFORM’ (i.e.,
+ the canonical platform name) is appended to ‘BINDIR’ and ‘LIBDIR’.
This is implied for a native TL build.
- * In a native TL build, 'DATAROOTDIR' is set to 'PREFIX', 'INFODIR'
- is set to 'PREFIX/texmf-dist/doc/info', and 'MANDIR' to
- 'PREFIX/texmf-dist/doc/man', corresponding to the directories used
+ • In a native TL build, ‘DATAROOTDIR’ is set to ‘PREFIX’, ‘INFODIR’
+ is set to ‘PREFIX/texmf-dist/doc/info’, and ‘MANDIR’ to
+ ‘PREFIX/texmf-dist/doc/man’, corresponding to the directories used
in the TL distribution.
-The top-level 'configure' script displays all these installation paths.
+The top-level ‘configure’ script displays all these installation paths.
- For the native TL build, the 'Build' script leaves the binaries in
-'./inst/bin/STD-SYSTEM-TRIPLET'. The new binaries are not directly
+ For the native TL build, the ‘Build’ script leaves the binaries in
+‘./inst/bin/STD-SYSTEM-TRIPLET’. The new binaries are not directly
usable from that location; they need to be copied to
-'Master/bin/TL-PLATFORM'. The other files and directories that end up
-in './inst/' are ignored.
+‘Master/bin/TL-PLATFORM’. The other files and directories that end up
+in ‘./inst/’ are ignored.
File: tlbuild.info, Node: Linked scripts, Next: Distro builds, Prev: Installation directories, Up: Installing
@@ -691,26 +692,26 @@
Quite a few executables are architecture-independent shell, Perl, or
other interpreted scripts, rather than compiled binaries. A few are
maintained as part of the TL source tree, but most are maintained
-elsewhere with copies under 'texk/texlive/linked_scripts'.
+elsewhere with copies under ‘texk/texlive/linked_scripts’.
- These so-called "linked scripts" are installed under
-'DATAROOTDIR/texmf-dist/scripts'; for Unix-like systems a symbolic link
-is made in 'BINDIR'. For example, a symlink points from 'BINDIR/ps2eps'
-to 'DATAROOTDIR/texmf-dist/scripts/ps2eps/ps2eps.pl'. For Windows, a
-standard wrapper binary (copied to, e.g., 'BINDIR/ps2eps.exe') serves
+ These so-called “linked scripts” are installed under
+‘DATAROOTDIR/texmf-dist/scripts’; for Unix-like systems a symbolic link
+is made in ‘BINDIR’. For example, a symlink points from ‘BINDIR/ps2eps’
+to ‘DATAROOTDIR/texmf-dist/scripts/ps2eps/ps2eps.pl’. For Windows, a
+standard wrapper binary (copied to, e.g., ‘BINDIR/ps2eps.exe’) serves
the same purpose. The source for the wrapper is in
-'texk/texlive/w32_wrapper'.
+‘texk/texlive/w32_wrapper’.
One reason for this is to avoid having many copies of the same
script; a more important reason is that it guarantees the scripts will
stay in sync across the different supported operating systems.
- Most important of all, we want the 'BINDIR' resulting from the build
+ Most important of all, we want the ‘BINDIR’ resulting from the build
to be as close as possible to what is in the TL distribution. At
-present, there are a few exceptions--Asymptote, Biber, Xindy--and each
-one creates considerable extra work. We don't want to add more. (See
+present, there are a few exceptions—Asymptote, Biber, Xindy—and each one
+creates considerable extra work. We don’t want to add more. (See
<https://tug.org/texlive/build.html> for information about building
-those exceptions, as well as the 'xz' and 'wget' programs that are used
+those exceptions, as well as the ‘xz’ and ‘wget’ programs that are used
in the TL infrastructure.)
@@ -721,50 +722,50 @@
Although they use the same code base, building for the native TL
distribution as shipped by the TeX user groups is typically quite
-different from a "distro" build needed by, e.g., a full GNU/Linux or BSD
+different from a “distro” build needed by, e.g., a full GNU/Linux or BSD
operating system distribution.
The native TL distribution uses shared libraries only when absolutely
-necessary ('libc', 'libm', X11 libraries, and 'libfontconfig'). In
+necessary (‘libc’, ‘libm’, X11 libraries, and ‘libfontconfig’). In
contrast, a distro typically wants to use as many shared libraries as
possible from elsewhere on the system, including TeX-specific libraries
-such as 'libkpathsea' (even though Kpathsea has never officially been
+such as ‘libkpathsea’ (even though Kpathsea has never officially been
released as a shared library). In addition, the installation paths
will, in general, be completely different.
- Here are the 'configure' options that distro builds are likely to
+ Here are the ‘configure’ options that distro builds are likely to
find most relevant:
-'--disable-native-texlive-build'
+‘--disable-native-texlive-build’
This must be specified to avoid interference from the many tweaks
we do for the native TL build.
-'--with-banner-add=/SOMEDISTRO'
- This isn't technically required, but is strongly recommended, so
+‘--with-banner-add=/SOMEDISTRO’
+ This isn’t technically required, but is strongly recommended, so
your build and your distro can be distinguished from others.
-'--enable-shared'
+‘--enable-shared’
Build shared versions of the TeX-specific libraries (uses
- 'libtool').
+ ‘libtool’).
-'--disable-static'
+‘--disable-static’
Do not build the static versions of the TeX-specific libraries.
-'--with-system-LIB'
- Look for and use a system version of the library LIB. 'configure
- --help' will give you the list of possibilities.
+‘--with-system-LIB’
+ Look for and use a system version of the library LIB. ‘configure
+ --help’ will give you the list of possibilities.
-'--with-LIB-includes=DIR'
-'--with-LIB-libdir=DIR'
+‘--with-LIB-includes=DIR’
+‘--with-LIB-libdir=DIR’
If needed, allows you to specify where the headers/code are for the
given library LIB.
-'--prefix=/usr'
-'--prefix=/opt/TeXLive'
- Or whatever your convention is. The default is '/usr/local' and
- you shouldn't install there for a distro.
+‘--prefix=/usr’
+‘--prefix=/opt/TeXLive’
+ Or whatever your convention is. The default is ‘/usr/local’ and
+ you shouldn’t install there for a distro.
-'--libdir=\${exec_prefix}/lib64'
+‘--libdir=\${exec_prefix}/lib64’
May be needed for 64-bit bi-architecture (GNU/Linux) systems.
You will need to take care of the support files mentioned above
@@ -781,9 +782,9 @@
6 Layout and infrastructure
***************************
-The TeX Live source tree is the subtree rooted at 'Build/source' of the
+The TeX Live source tree is the subtree rooted at ‘Build/source’ of the
complete TL distribution and contains the sources for all executables
-distributed by TL, as well as 'configure' scripts and 'make' rules to
+distributed by TL, as well as ‘configure’ scripts and ‘make’ rules to
build and install them together with some of their support files.
* Menu:
@@ -803,15 +804,15 @@
As mentioned above (*note Prerequisites::), a normal build has few
requirements. On the other hand, if you want to modify the TeX Live
-infrastructure sources, such as 'configure.ac' or 'Makefile.am' files,
+infrastructure sources, such as ‘configure.ac’ or ‘Makefile.am’ files,
you will need to have several additional tools installed.
In general, the TL build system uses the latest released versions of
the GNU build tools, installed directly from the original GNU releases
-(e.g., by building them with 'configure --prefix=/usr/local/gnu' and
-having 'PATH' start with '/usr/local/gnu/bin'). We have found that
+(e.g., by building them with ‘configure --prefix=/usr/local/gnu’ and
+having ‘PATH’ start with ‘/usr/local/gnu/bin’). We have found that
trying to use the versions of these tools packaged for distros causes
-many extra hassles, so don't do that, tempting as it may be.
+many extra hassles, so don’t do that, tempting as it may be.
Currently the versions we use are:
@@ -819,30 +820,30 @@
automake (GNU automake) 1.16.5
bison (GNU Bison) 3.8.2
flex 2.6.0
- ltmain.sh (GNU libtool) 2.4.6
+ ltmain.sh (GNU libtool) 2.4.7
m4 (GNU M4) 1.4.19
- makeinfo (GNU texinfo) 6.7
+ makeinfo (GNU texinfo) 7.0.2
These versions should be used to update the generated files (e.g.,
-'configure' or 'Makefile.in') in all or parts of the TL tree after their
+‘configure’ or ‘Makefile.in’) in all or parts of the TL tree after their
dependencies have been changed. This can be done explicitly with the
-top-level 'reautoconf' script or implicitly by using the configure
-option '--enable-maintainer-mode'.
+top-level ‘reautoconf’ script or implicitly by using the configure
+option ‘--enable-maintainer-mode’.
It has often turned out that the bison and flex versions are not
-critical; however, the autotools versions are. If you don't have the
+critical; however, the autotools versions are. If you don’t have the
given versions, get them before modifying the build infrastructure.
The files in the Subversion repository (see
<https://tug.org/texlive/svn>) are all up to date (barring bugs). For
this to be reflected by their timestamps in your checkout, be sure to
-set 'use-commit-times=yes' in '~/.subversion/config' or the equivalent.
+set ‘use-commit-times=yes’ in ‘~/.subversion/config’ or the equivalent.
If timestamps are wrong, you may also be able to avoid unnecessary
-runs of 'bison', 'flex', or 'makeinfo' with 'touch' of the generated
-('.c', '.h', or '.info') files. With '--enable-maintainer-mode' it may
-also be necessary to 'touch' first 'aclocal.m4', then 'configure' and
-'config.h.in' (or 'c-auto.in'), and finally all 'Makefile.in' files.
+runs of ‘bison’, ‘flex’, or ‘makeinfo’ with ‘touch’ of the generated
+(‘.c’, ‘.h’, or ‘.info’) files. With ‘--enable-maintainer-mode’ it may
+also be necessary to ‘touch’ first ‘aclocal.m4’, then ‘configure’ and
+‘config.h.in’ (or ‘c-auto.in’), and finally all ‘Makefile.in’ files.
File: tlbuild.info, Node: Top-level directories, Next: Autoconf macros, Prev: Build system tools, Up: Layout and infrastructure
@@ -854,39 +855,39 @@
source tree.
As mentioned at the beginning of *note Overview of build system::,
-the main source directories are 'texk/' (TeX-specific programs and
-libraries), 'utils/' (additional programs), and 'libs/' (generic
+the main source directories are ‘texk/’ (TeX-specific programs and
+libraries), ‘utils/’ (additional programs), and ‘libs/’ (generic
libraries).
- In addition, the top-level directories 'am/' and 'm4/' contain
-'Makefile.am' fragments and Autoconf macros, respectively, used in many
-places. Specifically, the file 'm4/kpse-pkgs.m4' contains lists of all
+ In addition, the top-level directories ‘am/’ and ‘m4/’ contain
+‘Makefile.am’ fragments and Autoconf macros, respectively, used in many
+places. Specifically, the file ‘m4/kpse-pkgs.m4’ contains lists of all
program and library modules; missing modules are silently ignored.
(This helps in creating cut-down source trees.)
Each module contributes fragments (in separate files) defining its
-capabilities and requirements to the 'configure.ac' scripts at the
-top-level and in the subdirectories 'libs', 'utils', and 'texk'. The
-fragments from program modules supply 'configure' options to disable or
+capabilities and requirements to the ‘configure.ac’ scripts at the
+top-level and in the subdirectories ‘libs’, ‘utils’, and ‘texk’. The
+fragments from program modules supply ‘configure’ options to disable or
enable building them; those from library modules specify if an installed
(system) version of that library can be used. This ultimately
-determines which modules need to be built--although all modules must be
-configured for the benefit of 'make' targets such as 'dist' or
-'distcheck'.
+determines which modules need to be built—although all modules must be
+configured for the benefit of ‘make’ targets such as ‘dist’ or
+‘distcheck’.
- The top-level 'build-aux/' directory contains the common files
-'compile', 'config.guess', 'config.sub', 'depcomp', etc. used by most
+ The top-level ‘build-aux/’ directory contains the common files
+‘compile’, ‘config.guess’, ‘config.sub’, ‘depcomp’, etc. used by most
packages. These are taken from the GNU Gnulib sources
(<https://www.gnu.org/software/gnulib>), which in turn synchronizes with
any ultimate upstream repository. There are independent copies of some
of these in a few other places, e.g.,
-'libs/freetype2/freetype-*/builds/unix/'. The 'reautoconf' script does
+‘libs/freetype2/freetype-*/builds/unix/’. The ‘reautoconf’ script does
not touch those, but a TL cron job keeps them in sync (nightly).
- When the top-level './Build' script is used to build TL, two more two
-more top-level directories appear: 'Work/' for the build tree, and
-'inst/' for the install tree (from 'make install'). These names (and
-everything else about 'Build''s operation) can be changed by setting
+ When the top-level ‘./Build’ script is used to build TL, two more two
+more top-level directories appear: ‘Work/’ for the build tree, and
+‘inst/’ for the install tree (from ‘make install’). These names (and
+everything else about ‘Build’’s operation) can be changed by setting
environment variables before running it; see the script source.
@@ -896,9 +897,9 @@
===================
Here we describe a few of the Autoconf macros used in several
-modules--many more are defined in the sources; see the top-level 'm4/'
+modules—many more are defined in the sources; see the top-level ‘m4/’
directory. These general macros are supplemented by module-specific
-macros in directories such as 'texk/dvipng/m4/'; some of those are
+macros in directories such as ‘texk/dvipng/m4/’; some of those are
described in following sections (*note Library modules:: and *note
Program modules::).
@@ -921,18 +922,18 @@
-- Macro: KPSE_BASIC (NAME, [MORE-OPTIONS])
Initialize the basic TL infrastructure for module NAME:
- 'AM_INIT_AUTOMAKE([foreign MORE-OPTIONS])'
- 'AM_MAINTAINER_MODE'
- 'KPSE_COMPILER_WARNINGS'
+ ‘AM_INIT_AUTOMAKE([foreign MORE-OPTIONS])’
+ ‘AM_MAINTAINER_MODE’
+ ‘KPSE_COMPILER_WARNINGS’
and make sure the C compiler understands function prototypes. This
is used for all generic library and program modules.
-- Macro: KPSE_COMMON (NAME, [MORE-OPTIONS])
- Like 'KPSE_BASIC' but add:
- 'LT_PREREQ([2.2.6])'
- 'LT_INIT([win32-dll])'
- 'AC_SYS_LARGEFILE'
- 'AC_FUNC_FSEEKO'
+ Like ‘KPSE_BASIC’ but add:
+ ‘LT_PREREQ([2.2.6])’
+ ‘LT_INIT([win32-dll])’
+ ‘AC_SYS_LARGEFILE’
+ ‘AC_FUNC_FSEEKO’
along with checks for frequently used functions, headers, types,
and structures. This is used for TeX-specific modules.
@@ -945,20 +946,20 @@
Macros for program checks:
-- Macro: KPSE_CHECK_LATEX
- Set 'LATEX' to the first of 'latex', 'elatex', or 'lambda' which
- exists in 'PATH', or to 'no' if none of them exists. Call
- 'AC_SUBST' for 'LATEX'. The result of this test can be overridden
- by setting the 'LATEX' environment variable or the cache variable
- 'ac_cv_prog_LATEX'.
+ Set ‘LATEX’ to the first of ‘latex’, ‘elatex’, or ‘lambda’ which
+ exists in ‘PATH’, or to ‘no’ if none of them exists. Call
+ ‘AC_SUBST’ for ‘LATEX’. The result of this test can be overridden
+ by setting the ‘LATEX’ environment variable or the cache variable
+ ‘ac_cv_prog_LATEX’.
-- Macro: KPSE_CHECK_PDFLATEX
- Check for 'pdflatex' in 'PATH' and set 'PDFLATEX'.
+ Check for ‘pdflatex’ in ‘PATH’ and set ‘PDFLATEX’.
-- Macro: KPSE_CHECK_PERL
- Check for 'perl' or 'perl5' in 'PATH' and set 'PERL'.
+ Check for ‘perl’ or ‘perl5’ in ‘PATH’ and set ‘PERL’.
-- Macro: KPSE_PROG_LEX
- Call 'AC_PROG_LEX' and add the flag '-l' for 'flex'.
+ Call ‘AC_PROG_LEX’ and add the flag ‘-l’ for ‘flex’.
File: tlbuild.info, Node: Macros for compilers, Next: Macros for libraries, Prev: Macros for programs, Up: Autoconf macros
@@ -970,30 +971,30 @@
-- Macro: KPSE_COMPILER_WARNINGS
When using the (Objective) C/C++ compiler, set
- 'WARNING_[OBJ]C[XX]FLAGS' to suitable warning flags (depending on
- the value given to or implied for '--enable-compiler-warnings').
- Call 'AC_SUBST' for them. At present this assumes GNU compiler
+ ‘WARNING_[OBJ]C[XX]FLAGS’ to suitable warning flags (depending on
+ the value given to or implied for ‘--enable-compiler-warnings’).
+ Call ‘AC_SUBST’ for them. At present this assumes GNU compiler
warning options, but could be extended to others if necessary.
- This macro caches its results in the 'kpse_cv_warning_cflags', ...
+ This macro caches its results in the ‘kpse_cv_warning_cflags’, ...
variables.
-- Macro: KPSE_COMPILER_VISIBILITY
When using the C or C++ compiler, try to set
- 'VISIBILITY_C[XX]FLAGS' to flags to hide external symbols. Call
- 'AC_SUBST' for this variable. At present this only tests for the
- compiler option '-fvisibility=hidden', but could be extended if
+ ‘VISIBILITY_C[XX]FLAGS’ to flags to hide external symbols. Call
+ ‘AC_SUBST’ for this variable. At present this only tests for the
+ compiler option ‘-fvisibility=hidden’, but could be extended if
necessary.
- This macro caches its results in the 'kpse_cv_visibility_cflags' or
- 'kpse_cv_visibility_cxxflags' variable.
+ This macro caches its results in the ‘kpse_cv_visibility_cflags’ or
+ ‘kpse_cv_visibility_cxxflags’ variable.
-- Macro: KPSE_CXX_HACK
- Provide the configure option '--enable-cxx-runtime-hack'. If
- enabled and when using 'g++', try to statically link with
- 'libstdc++', notably improving portability of the resulting binary.
+ Provide the configure option ‘--enable-cxx-runtime-hack’. If
+ enabled and when using ‘g++’, try to statically link with
+ ‘libstdc++’, notably improving portability of the resulting binary.
- This macro caches its result in the 'kpse_cv_cxx_hack' variable.
+ This macro caches its result in the ‘kpse_cv_cxx_hack’ variable.
File: tlbuild.info, Node: Macros for libraries, Next: Macros for library and header flags, Prev: Macros for compilers, Up: Autoconf macros
@@ -1004,8 +1005,8 @@
One macro for a library check:
-- Macro: KPSE_LARGEFILE (VARIABLE, [EXTRA-DEFINE])
- Call 'AC_SYS_LARGEFILE' and 'AC_FUNC_FSEEKO' and append suitable
- '-D' flags (optionally including '-DEXTRA-DEFINE') to VARIABLE.
+ Call ‘AC_SYS_LARGEFILE’ and ‘AC_FUNC_FSEEKO’ and append suitable
+ ‘-D’ flags (optionally including ‘-DEXTRA-DEFINE’) to VARIABLE.
File: tlbuild.info, Node: Macros for library and header flags, Next: Macros for Windows, Prev: Macros for libraries, Up: Autoconf macros
@@ -1013,33 +1014,33 @@
6.3.5 Macros for library and header flags
-----------------------------------------
-Each library module 'libs/LIB' or 'texk/LIB' is supplemented by a macro
-'KPSE_LIB_FLAGS' (all uppercase) that provides make variables for that
-library. E.g., for 'libs/libpng':
+Each library module ‘libs/LIB’ or ‘texk/LIB’ is supplemented by a macro
+‘KPSE_LIB_FLAGS’ (all uppercase) that provides make variables for that
+library. E.g., for ‘libs/libpng’:
-- Macro: KPSE_LIBPNG_FLAGS
- Provide the configure option '--with-system-libpng'. Set and
- 'AC_SUBST' 'make' variables for modules using this library (either
+ Provide the configure option ‘--with-system-libpng’. Set and
+ ‘AC_SUBST’ ‘make’ variables for modules using this library (either
an installed version or from the TeX Live tree):
- 'LIBPNG_INCLUDES' for use in 'CPPFLAGS',
- 'LIBPNG_LIBS' for use in 'LDADD',
- 'LIBPNG_DEPEND' for use as a Makefile dependency,
- 'LIBPNG_RULE' for the 'make' rules to rebuild the library.
+ ‘LIBPNG_INCLUDES’ for use in ‘CPPFLAGS’,
+ ‘LIBPNG_LIBS’ for use in ‘LDADD’,
+ ‘LIBPNG_DEPEND’ for use as a Makefile dependency,
+ ‘LIBPNG_RULE’ for the ‘make’ rules to rebuild the library.
-- Macro: KPSE_ADD_FLAGS (NAME)
- Temporarily extend 'CPPFLAGS' and 'LIBS' with the values required
- for the library module 'NAME'.
+ Temporarily extend ‘CPPFLAGS’ and ‘LIBS’ with the values required
+ for the library module ‘NAME’.
-- Macro: KPSE_RESTORE_FLAGS
- Restore 'CPPFLAGS' and 'LIBS' to their original values.
+ Restore ‘CPPFLAGS’ and ‘LIBS’ to their original values.
- As an example, the 'configure.ac' file for a hypothetical program
-'utils/foo' using 'libpng', and hence 'zlib', would contain
+ As an example, the ‘configure.ac’ file for a hypothetical program
+‘utils/foo’ using ‘libpng’, and hence ‘zlib’, would contain
KPSE_ZLIB_FLAGS
KPSE_LIBPNG_FLAGS
-and its 'Makefile.am' would be along these lines:
+and its ‘Makefile.am’ would be along these lines:
bin_PROGRAMS = foo
AM_CPPFLAGS = ${LIBPNG_INCLUDES} ${ZLIB_INCLUDES}
foo_LDADD = ${LIBPNG_LIBS} ${ZLIB_LIBS}
@@ -1049,13 +1050,13 @@
## Rebuild libpng
@LIBPNG_RULE@
- If it were necessary to examine whether certain 'zlib' or 'libpng'
-features were available, 'configure.ac' should be continued this way:
+ If it were necessary to examine whether certain ‘zlib’ or ‘libpng’
+features were available, ‘configure.ac’ should be continued this way:
KPSE_ADD_FLAGS([zlib])
- ... # tests for 'zlib' features, if any
+ ... # tests for ‘zlib’ features, if any
KPSE_ADD_FLAGS([libpng])
- ... # tests for 'libpng' features
- KPSE_RESTORE_FLAGS # restore 'CPPFLAGS' and 'LIBS'
+ ... # tests for ‘libpng’ features
+ KPSE_RESTORE_FLAGS # restore ‘CPPFLAGS’ and ‘LIBS’
File: tlbuild.info, Node: Macros for Windows, Prev: Macros for library and header flags, Up: Autoconf macros
@@ -1067,33 +1068,33 @@
due to the lack of symbolic links.
-- Macro: KPSE_CHECK_WIN32
- Check if compiling for a Windows system. The result is either 'no'
- for Unix-like systems (including Cygwin), 'mingw32' for Windows
- with GCC, or 'native' for Windows with MSVC. The result is cached
- in the 'kpse_cv_have_win32' variable.
+ Check if compiling for a Windows system. The result is either ‘no’
+ for Unix-like systems (including Cygwin), ‘mingw32’ for Windows
+ with GCC, or ‘native’ for Windows with MSVC. The result is cached
+ in the ‘kpse_cv_have_win32’ variable.
-- Macro: KPSE_COND_WIN32
- Call 'KPSE_CHECK_WIN32' and define the Automake conditional 'WIN32'
- ('true' if the value of 'kpse_cv_have_win32' is not 'no').
+ Call ‘KPSE_CHECK_WIN32’ and define the Automake conditional ‘WIN32’
+ (‘true’ if the value of ‘kpse_cv_have_win32’ is not ‘no’).
-- Macro: KPSE_COND_MINGW32
- Call 'KPSE_COND_WIN32' and define the Automake conditional
- 'MINGW32' ('true' if the value of 'kpse_cv_have_win32' is
- 'mingw32').
+ Call ‘KPSE_COND_WIN32’ and define the Automake conditional
+ ‘MINGW32’ (‘true’ if the value of ‘kpse_cv_have_win32’ is
+ ‘mingw32’).
-- Macro: KPSE_COND_WIN32_WRAP
- Call 'KPSE_COND_WIN32' and define the Automake conditional
- 'WIN32_WRAP' ('true' if the standard Windows wrapper
- ('texk/texlive/w32_wrapper/runscript.exe') exists. This wrapper is
- used on Windows instead of symlinks for the "linked scripts" (*note
+ Call ‘KPSE_COND_WIN32’ and define the Automake conditional
+ ‘WIN32_WRAP’ (‘true’ if the standard Windows wrapper
+ (‘texk/texlive/w32_wrapper/runscript.exe’) exists. This wrapper is
+ used on Windows instead of symlinks for the “linked scripts” (*note
Linked scripts::).
-- Macro: KPSE_WIN32_CALL
- Call 'KPSE_COND_WIN32' and check if the file
- 'texk/texlive/w32_wrapper/callexe.c' exists; if it does, create a
- symlink in the build tree. Compiling 'callexe.c' with
- '-DEXEPROG='"FOO.exe"'' and installing 'callexe.exe' as 'BAR.exe'
- is used on Windows instead of a symlink 'BAR->FOO' for Unix-like
+ Call ‘KPSE_COND_WIN32’ and check if the file
+ ‘texk/texlive/w32_wrapper/callexe.c’ exists; if it does, create a
+ symlink in the build tree. Compiling ‘callexe.c’ with
+ ‘-DEXEPROG='"FOO.exe"'’ and installing ‘callexe.exe’ as ‘BAR.exe’
+ is used on Windows instead of a symlink ‘BAR->FOO’ for Unix-like
systems.
@@ -1108,27 +1109,27 @@
* Menu:
-* 'png' library:: 'libs/libpng'
-* 'zlib' library:: 'libs/zlib'
-* 'freetype' library:: 'libs/freetype2'
-* 'kpathsea' library:: 'texk/kpathsea'
+* png library:: ‘libs/libpng’
+* zlib library:: ‘libs/zlib’
+* freetype library:: ‘libs/freetype2’
+* kpathsea library:: ‘texk/kpathsea’
-File: tlbuild.info, Node: 'png' library, Next: 'zlib' library, Up: Library modules
+File: tlbuild.info, Node: png library, Next: zlib library, Up: Library modules
-6.4.1 The 'png' library in 'libs/libpng'
+6.4.1 The ‘png’ library in ‘libs/libpng’
----------------------------------------
-The "generic" 'png' library uses the source tree in the subdirectory
-'libpng-src/', with all modifications for TL recorded in 'TLpatches/*'.
-The 'configure.ac' fragment 'ac/withenable.ac' contains
+The “generic” ‘png’ library uses the source tree in the subdirectory
+‘libpng-src/’, with all modifications for TL recorded in ‘TLpatches/*’.
+The ‘configure.ac’ fragment ‘ac/withenable.ac’ contains
KPSE_WITH_LIB([libpng], [zlib])
-to specify the module name and indicate the dependency on 'zlib'. A
-third literal argument ''tree'' would specify that the library from the
+to specify the module name and indicate the dependency on ‘zlib’. A
+third literal argument ‘‘tree’’ would specify that the library from the
TeX Live tree cannot be replaced by a system version. That not being
-the case here, a second fragment 'ac/libpng.ac' contains
+the case here, a second fragment ‘ac/libpng.ac’ contains
KPSE_TRY_LIB([libpng],
[#include <png.h>],
@@ -1144,85 +1145,85 @@
return 0; }
which Autoconf uses to verify the usability of a system version with C
-code. The analogous macro 'KPSE_TRY_LIBXX' would check using C++.
-These fragments are included by the 'configure.ac' at the top level of
-TL ('Build/source/configure.ac').
+code. The analogous macro ‘KPSE_TRY_LIBXX’ would check using C++.
+These fragments are included by the ‘configure.ac’ at the top level of
+TL (‘Build/source/configure.ac’).
For this library, like many other modules, a proxy build system for
-TL is used, consisting of our own 'configure.ac', 'Makefile.am',
-'include/Makefile.am'; the distributed build system is not used.
+TL is used, consisting of our own ‘configure.ac’, ‘Makefile.am’,
+‘include/Makefile.am’; the distributed build system is not used.
(Consequently, a few generated files and auxiliary scripts are removed
from the distributed source tree.)
- The public headers 'png.h', 'pngconf.h', and 'pnglibconf.h' are
-"installed" (as symlinks) under 'include/' in the build tree exactly as
-they are for a system version under, e.g., '/usr/include/'.
+ The public headers ‘png.h’, ‘pngconf.h’, and ‘pnglibconf.h’ are
+“installed” (as symlinks) under ‘include/’ in the build tree exactly as
+they are for a system version under, e.g., ‘/usr/include/’.
- The module is supplemented by the file 'm4/kpse-libpng-flags.m4' that
-defines the M4 macro 'KPSE_LIBPNG_FLAGS' used by all modules depending
-on this library in their 'configure.ac' to generate the 'make' variables
-'LIBPNG_INCLUDES' for use in 'CPPFLAGS', 'LIBPNG_LIBS' for use in
-'LDADD', 'LIBPNG_DEPEND' for use as dependencies, and 'LIBPNG_RULE' for
-the 'make' rules to rebuild the library.
+ The module is supplemented by the file ‘m4/kpse-libpng-flags.m4’ that
+defines the M4 macro ‘KPSE_LIBPNG_FLAGS’ used by all modules depending
+on this library in their ‘configure.ac’ to generate the ‘make’ variables
+‘LIBPNG_INCLUDES’ for use in ‘CPPFLAGS’, ‘LIBPNG_LIBS’ for use in
+‘LDADD’, ‘LIBPNG_DEPEND’ for use as dependencies, and ‘LIBPNG_RULE’ for
+the ‘make’ rules to rebuild the library.
- 'm4/kpse-libpng-flags.m4' also supplies the configure option
-'--with-system-libpng', which then uses 'pkg-config' to determine the
+ ‘m4/kpse-libpng-flags.m4’ also supplies the configure option
+‘--with-system-libpng’, which then uses ‘pkg-config’ to determine the
flags required for the system library.
-File: tlbuild.info, Node: 'zlib' library, Next: 'freetype' library, Prev: 'png' library, Up: Library modules
+File: tlbuild.info, Node: zlib library, Next: freetype library, Prev: png library, Up: Library modules
-6.4.2 The 'zlib' library in 'libs/zlib'
+6.4.2 The ‘zlib’ library in ‘libs/zlib’
---------------------------------------
-This generic library is very much analogous to 'libpng', but without the
-dependency on any other library. The file 'm4/kpse-zlib-flags.m4'
-supplies the configure option '--with-system-zlib', as well as
-'--with-zlib-includes' and '--with-zlib-libdir' to specify non-standard
-locations of the 'zlib' headers and/or library.
+This generic library is very much analogous to ‘libpng’, but without the
+dependency on any other library. The file ‘m4/kpse-zlib-flags.m4’
+supplies the configure option ‘--with-system-zlib’, as well as
+‘--with-zlib-includes’ and ‘--with-zlib-libdir’ to specify non-standard
+locations of the ‘zlib’ headers and/or library.
-File: tlbuild.info, Node: 'freetype' library, Next: 'kpathsea' library, Prev: 'zlib' library, Up: Library modules
+File: tlbuild.info, Node: freetype library, Next: kpathsea library, Prev: zlib library, Up: Library modules
-6.4.3 The 'freetype' library in 'libs/freetype2'
+6.4.3 The ‘freetype’ library in ‘libs/freetype2’
------------------------------------------------
This module uses a wrapper build system. In contrast to the proxy build
described earlier, the wrapper build has an almost trivial
-'configure.ac' and a 'Makefile.am' which invokes the 'configure' and
-'make' in the distributed source, followed by 'make install' with the TL
+‘configure.ac’ and a ‘Makefile.am’ which invokes the ‘configure’ and
+‘make’ in the distributed source, followed by ‘make install’ with the TL
build tree as destination. In other words, this actually uses the build
system provided by upstream (possibly patched).
The flags required for the system library are obtained through
-'freetype-config'.
+‘freetype-config’.
-File: tlbuild.info, Node: 'kpathsea' library, Prev: 'freetype' library, Up: Library modules
+File: tlbuild.info, Node: kpathsea library, Prev: freetype library, Up: Library modules
-6.4.4 The 'kpathsea' library in 'texk/kpathsea'
+6.4.4 The ‘kpathsea’ library in ‘texk/kpathsea’
-----------------------------------------------
This is one of the TeX-specific libraries that are maintained as part of
-TeX Live (*note (kpathsea)::); the other is 'ptexenc'. These TeX
+TeX Live (*note (kpathsea)::); the other is ‘ptexenc’. These TeX
libraries are Libtool libraries (static and/or shared) and are installed
-by 'make install' together with the programs. They are, however, not
+by ‘make install’ together with the programs. They are, however, not
part of the TL DVD as distributed by TeX user groups, and have never
been officially released for standalone use.
It is possible, and probably useful for distro builds (*note Distro
-builds::), to specify the configure option '--with-system-kpathsea' in
+builds::), to specify the configure option ‘--with-system-kpathsea’ in
order to use a system version of the library. Programs outside the TL
-tree should use 'pkg-config' for the required flags.
+tree should use ‘pkg-config’ for the required flags.
- In addition to 'kpathsea/ac/withenable.ac' and
-'kpathsea/ac/kpathsea.ac' here there is a third fragment
-'kpathsea.ac/mktex.ac', included by both 'withenable.ac' and
-'configure.ac', which supplies configure options such as
-'--enable-mktextfm-default'. These determine the compile time default
-of whether or not to run 'mktextfm' (and similar) to generate a missing
-'.tfm' (or whatever) file. In any case, however, the command line
-options '-mktex=tfm' or '-no-mktex=tfm' for the TeX-like engines
+ In addition to ‘kpathsea/ac/withenable.ac’ and
+‘kpathsea/ac/kpathsea.ac’ here there is a third fragment
+‘kpathsea.ac/mktex.ac’, included by both ‘withenable.ac’ and
+‘configure.ac’, which supplies configure options such as
+‘--enable-mktextfm-default’. These determine the compile time default
+of whether or not to run ‘mktextfm’ (and similar) to generate a missing
+‘.tfm’ (or whatever) file. In any case, however, the command line
+options ‘-mktex=tfm’ or ‘-no-mktex=tfm’ for the TeX-like engines
override this default.
@@ -1236,85 +1237,85 @@
* Menu:
-* 't1utils' package:: 'utils/t1utils'
-* 'xindy' package:: 'utils/xindy'
-* 'xdvik' package:: 'texk/xdvik'
-* 'asymptote':: 'utils/asymptote'
+* t1utils package:: ‘utils/t1utils’
+* xindy package:: ‘utils/xindy’
+* xdvik package:: ‘texk/xdvik’
+* asymptote:: ‘utils/asymptote’
-File: tlbuild.info, Node: 't1utils' package, Next: 'xindy' package, Up: Program modules
+File: tlbuild.info, Node: t1utils package, Next: xindy package, Up: Program modules
-6.5.1 The 't1utils' package in 'utils/t1utils'
+6.5.1 The ‘t1utils’ package in ‘utils/t1utils’
----------------------------------------------
-Here we use the distributed source tree 't1utils-src' with modifications
-documented in 'TLpatches/*' and a proxy build system consisting of
-'configure.ac' and 'Makefile.am'. The fragment 'ac/withenable.ac'
+Here we use the distributed source tree ‘t1utils-src’ with modifications
+documented in ‘TLpatches/*’ and a proxy build system consisting of
+‘configure.ac’ and ‘Makefile.am’. The fragment ‘ac/withenable.ac’
contains
KPSE_ENABLE_PROG([t1utils])
specifying the module name without any dependencies, and supplies the
-configure option '--disable-t1utils'.
+configure option ‘--disable-t1utils’.
-File: tlbuild.info, Node: 'xindy' package, Next: 'xdvik' package, Prev: 't1utils' package, Up: Program modules
+File: tlbuild.info, Node: xindy package, Next: xdvik package, Prev: t1utils package, Up: Program modules
-6.5.2 The 'xindy' package in 'utils/xindy'
+6.5.2 The ‘xindy’ package in ‘utils/xindy’
------------------------------------------
-This module uses the distributed source tree 'xindy-src/' with
-modifications documented in 'TLpatches/*', and a wrapper 'configure.ac'
-and 'Makefile.am' that descends into 'xindy-src'.
+This module uses the distributed source tree ‘xindy-src/’ with
+modifications documented in ‘TLpatches/*’, and a wrapper ‘configure.ac’
+and ‘Makefile.am’ that descends into ‘xindy-src’.
- The 'xindy' build requires a 'make' that supports a 'VPATH' build,
-can handle all targets, and does not refer to '${top_srcdir}' or
-'${top_builddir}'. The fragment 'xindy/ac/withenable.ac' contains
+ The ‘xindy’ build requires a ‘make’ that supports a ‘VPATH’ build,
+can handle all targets, and does not refer to ‘${top_srcdir}’ or
+‘${top_builddir}’. The fragment ‘xindy/ac/withenable.ac’ contains
KPSE_ENABLE_PROG([xindy], , [disable])
m4_include(kpse_TL[utils/xindy/ac/xindy.ac])
m4_include(kpse_TL[utils/xindy/ac/clisp.ac])
-where 'disable' in the third argument indicates that 'xindy' is only
-built if explicitly enabled by the user with 'configure --enable-xindy'
-(the need for 'clisp' makes it too painful to enable by default).
+where ‘disable’ in the third argument indicates that ‘xindy’ is only
+built if explicitly enabled by the user with ‘configure --enable-xindy’
+(the need for ‘clisp’ makes it too painful to enable by default).
- The additional fragments 'ac/xindy.ac' and 'ac/clisp.ac' specify more
-'configure' options to be seen at the top level, with 'ac/xindy.ac' also
-included by 'configure.ac'.
+ The additional fragments ‘ac/xindy.ac’ and ‘ac/clisp.ac’ specify more
+‘configure’ options to be seen at the top level, with ‘ac/xindy.ac’ also
+included by ‘configure.ac’.
-File: tlbuild.info, Node: 'xdvik' package, Next: 'asymptote', Prev: 'xindy' package, Up: Program modules
+File: tlbuild.info, Node: xdvik package, Next: asymptote, Prev: xindy package, Up: Program modules
-6.5.3 The 'xdvik' package in 'texk/xdvik'
+6.5.3 The ‘xdvik’ package in ‘texk/xdvik’
-----------------------------------------
This package is maintained as part of the TeX Live tree with sources in
-its own directory ('texk/xdvik/'). The fragment
-'xdvik/ac/withenable.ac' contains
+its own directory (‘texk/xdvik/’). The fragment
+‘xdvik/ac/withenable.ac’ contains
dnl extra_dirs = texk/xdvik/squeeze
KPSE_ENABLE_PROG([xdvik], [kpathsea freetype2], [x])
m4_include(kpse_TL[texk/xdvik/ac/xdvik.ac])
-thus specifying dependencies on the 'kpathsea', 'freetype', and X11
-libraries. The M4 comment (following 'dnl') signals the subsidiary
-'squeeze/configure.ac'. This is needed because the main executable
-'xdvi-bin' (to be installed as, e.g., 'xdvi-xaw') is for the 'host'
-system whereas the auxiliary program 'squeeze/squeeze' has to run on the
-'build' system; in a cross compilation, these differ.
+thus specifying dependencies on the ‘kpathsea’, ‘freetype’, and X11
+libraries. The M4 comment (following ‘dnl’) signals the subsidiary
+‘squeeze/configure.ac’. This is needed because the main executable
+‘xdvi-bin’ (to be installed as, e.g., ‘xdvi-xaw’) is for the ‘host’
+system whereas the auxiliary program ‘squeeze/squeeze’ has to run on the
+‘build’ system; in a cross compilation, these differ.
- The additional fragment 'ac/xdvik.ac' is also included by
-'configure.ac' and supplies the configure option '--with-xdvi-x-toolkit'
+ The additional fragment ‘ac/xdvik.ac’ is also included by
+‘configure.ac’ and supplies the configure option ‘--with-xdvi-x-toolkit’
also seen at the top level.
-File: tlbuild.info, Node: 'asymptote', Prev: 'xdvik' package, Up: Program modules
+File: tlbuild.info, Node: asymptote, Prev: xdvik package, Up: Program modules
-6.5.4 The subdirectory 'utils/asymptote'
+6.5.4 The subdirectory ‘utils/asymptote’
----------------------------------------
-This subdirectory contains the sources for 'asy' and 'xasy' but due to
+This subdirectory contains the sources for ‘asy’ and ‘xasy’ but due to
its complexity and prerequisites (e.g., OpenGL) it is not part of the TL
build system. These programs must be built and installed independently,
but are included on the TL DVD together with their support files. See
@@ -1329,12 +1330,12 @@
This section outlines the basic process for adding new packages to the
TL build system.
- In any case, a new package directory 'foo' should contain the
+ In any case, a new package directory ‘foo’ should contain the
original sources, modified only with changes necessary for TL, in
-'foo/foo-src'. The changes should be documented in 'foo/TLpatches/*',
-and also be submitted upstream whenever reasonable. In addition, 'foo/'
-will need the usual Automake build-related files ('configure.ac',
-'Makefile.am', etc. Please maintain 'foo/ChangeLog' for all TL changes.
+‘foo/foo-src’. The changes should be documented in ‘foo/TLpatches/*’,
+and also be submitted upstream whenever reasonable. In addition, ‘foo/’
+will need the usual Automake build-related files (‘configure.ac’,
+‘Makefile.am’, etc. Please maintain ‘foo/ChangeLog’ for all TL changes.
* Menu:
@@ -1349,102 +1350,102 @@
6.6.1 Adding a new program module
---------------------------------
-A TeX-specific program module in a subdirectory 'texk/PROG' may use the
-TeX-specific libraries and is included by adding its name 'PROG' to the
-M4 list 'kpse_texk_pkgs' defined in 'm4/kpse-pkgs.m4'.
+A TeX-specific program module in a subdirectory ‘texk/PROG’ may use the
+TeX-specific libraries and is included by adding its name ‘PROG’ to the
+M4 list ‘kpse_texk_pkgs’ defined in ‘m4/kpse-pkgs.m4’.
- A generic program module in a subdirectory 'utils/PROG' must not use
-the TeX-specific libraries and is included by adding its name 'PROG' to
-the M4 list 'kpse_utils_pkgs' in 'm4/kpse-pkgs.m4'.
+ A generic program module in a subdirectory ‘utils/PROG’ must not use
+the TeX-specific libraries and is included by adding its name ‘PROG’ to
+the M4 list ‘kpse_utils_pkgs’ in ‘m4/kpse-pkgs.m4’.
- In either case, the subdirectory 'texk/PROG' or 'utils/PROG' must
-provide a fragment 'ac/withenable.ac' that contains the M4 macro
-'KPSE_ENABLE_PROG' defined in 'm4/kpse-setup.m4' with 'PROG' as the
+ In either case, the subdirectory ‘texk/PROG’ or ‘utils/PROG’ must
+provide a fragment ‘ac/withenable.ac’ that contains the M4 macro
+‘KPSE_ENABLE_PROG’ defined in ‘m4/kpse-setup.m4’ with ‘PROG’ as the
mandatory first argument and three optional arguments:
1. a list of required libraries from the TL tree;
- 2. a list of options: 'disable' if this module is not to be built
- without the configure option '--enable-PROG', 'native' if cross
- compilation is not possible, 'x' if the program requires X11
+ 2. a list of options: ‘disable’ if this module is not to be built
+ without the configure option ‘--enable-PROG’, ‘native’ if cross
+ compilation is not possible, ‘x’ if the program requires X11
libraries;
- 3. a comment added to the help text for the 'configure' option
- '--enable-PROG' or '--disable-PROG'.
+ 3. a comment added to the help text for the ‘configure’ option
+ ‘--enable-PROG’ or ‘--disable-PROG’.
- If the module requires specific 'configure' options to be seen at the
-top level, they should be defined in an additional fragment 'ac/PROG.ac'
-included from 'ac/withenable.ac' and 'configure.ac'.
+ If the module requires specific ‘configure’ options to be seen at the
+top level, they should be defined in an additional fragment ‘ac/PROG.ac’
+included from ‘ac/withenable.ac’ and ‘configure.ac’.
Usually, the new program is maintained somewhere outside of TeX Live.
In that case, as above, we put the upstream sources into a subdirectory
-'PROG-src' (e.g., 'utils/newprog/newprog-src'). We do not typically run
-'configure' in this original '...-src' directory, but only in our own
-directory; but we do compile using the source files in '...-src'.
+‘PROG-src’ (e.g., ‘utils/newprog/newprog-src’). We do not typically run
+‘configure’ in this original ‘...-src’ directory, but only in our own
+directory; but we do compile using the source files in ‘...-src’.
So, to summarize the files that must (usually) be created inside a
-new TL source directory ('texk/newprog' or 'utils/newprog'):
+new TL source directory (‘texk/newprog’ or ‘utils/newprog’):
-'ac/withenable.ac'
- The 'KPSE_ENABLE_PROG' call just explained.
+‘ac/withenable.ac’
+ The ‘KPSE_ENABLE_PROG’ call just explained.
-'configure.ac'
-'Makefile.am'
- By merging the contents of the original 'configure.ac' (if
+‘configure.ac’
+‘Makefile.am’
+ By merging the contents of the original ‘configure.ac’ (if
provided) and a comparable program already in TL. In the above
- example, one line that will be needed in 'configure.ac' (can be
- added before the 'AC_CONFIG_FILES' at the end) is:
+ example, one line that will be needed in ‘configure.ac’ (can be
+ added before the ‘AC_CONFIG_FILES’ at the end) is:
AC_SUBST([NEWPROG_TREE], [newprog-src])
- and then use '@NEWPROG_TREE@' in 'Makefile.am' where needed.
+ and then use ‘@NEWPROG_TREE@’ in ‘Makefile.am’ where needed.
In general, there is no magic recipe for this part of the job.
- It's necessary to think about what needs to be done in the original
- vs. in TeX Live. It's useful to look at the setup for the most
- comparable programs already in TL that you can find. It's also
- useful to grep the entire 'Build/source' tree for whatever you can
+ It’s necessary to think about what needs to be done in the original
+ vs. in TeX Live. It’s useful to look at the setup for the most
+ comparable programs already in TL that you can find. It’s also
+ useful to grep the entire ‘Build/source’ tree for whatever you can
think of to investigate how something is done. Most of the
- TL-specific macros are defined in 'Build/source/m4/*'.
+ TL-specific macros are defined in ‘Build/source/m4/*’.
-'TLpatches/TL-Changes'
+‘TLpatches/TL-Changes’
First actions taken after getting the original source tree;
typically removal of derived or unused common files.
-'TLpatches/patch-...'
+‘TLpatches/patch-...’
If any changes are needed to the original sources, record the
patches here so they can be applied next time. Also, send them
- upstream so that we don't have to maintain them forever.
+ upstream so that we don’t have to maintain them forever.
-'ChangeLog'
+‘ChangeLog’
Record all TL-specific changes, now and in the future.
- After populating the new TL source directory ('.../newprog/', in the
-above), run GNU 'autoreconf' there (*note Build system tools::). Once
-that works, if you are the one who's eventually going to commit the new
-package, 'svn add' the necessary files, including the generated
-'Makefile.in aclocal.m4 configure', and 'svn:ignore' the Automake cache
-'autom4te.cache'. (This is so people checking out the TL source tree do
-not have to run any autotools, but can simply run 'configure'.)
+ After populating the new TL source directory (‘.../newprog/’, in the
+above), run GNU ‘autoreconf’ there (*note Build system tools::). Once
+that works, if you are the one who’s eventually going to commit the new
+package, ‘svn add’ the necessary files, including the generated
+‘Makefile.in aclocal.m4 configure’, and ‘svn:ignore’ the Automake cache
+‘autom4te.cache’. (This is so people checking out the TL source tree do
+not have to run any autotools, but can simply run ‘configure’.)
- To reiterate: do not fail to commit the generated 'configure' and
-other files. The m4 code in 'kpse-pkgs.m4' uses the existence of
-'configure' to determine whether to descend into (and configure) a given
+ To reiterate: do not fail to commit the generated ‘configure’ and
+other files. The m4 code in ‘kpse-pkgs.m4’ uses the existence of
+‘configure’ to determine whether to descend into (and configure) a given
subdirectory.
- Then, run the TL tool 'reautoconf' in the top-level TL
-'Build/source/' directory, to incorporate the new program into the build
-tree. It is good to then rebuild the whole tree (e.g., using TL's
-'Build/Build' script) to get all the necessary files generated.
+ Then, run the TL tool ‘reautoconf’ in the top-level TL
+‘Build/source/’ directory, to incorporate the new program into the build
+tree. It is good to then rebuild the whole tree (e.g., using TL’s
+‘Build/Build’ script) to get all the necessary files generated.
It will probably fail. So then you need to keep at it until the
program compiles and tests successfully. The most efficient way is to
-rerun 'autoreconf' as needed in the new source directory
-('Build/source/.../newprog'), then 'make' in the corresponding build
-directory ('Build/work/.../newprog'), then 'make check', etc. In the
+rerun ‘autoreconf’ as needed in the new source directory
+(‘Build/source/.../newprog’), then ‘make’ in the corresponding build
+directory (‘Build/work/.../newprog’), then ‘make check’, etc. In the
end, also make sure that the whole tree builds from scratch.
- After final success, don't forget to commit. (Or email the TL
+ After final success, don’t forget to commit. (Or email the TL
maintainers with the patch.)
@@ -1454,32 +1455,32 @@
-------------------------
Adding a new TeX engine is not completely different from adding a
-program, but it's not all that similar, either. In this case, the main
-work is done by creating a new subdirectory of 'texk/web2c/' for the
-engine. The subdirectory is conventionally named ending in 'dir', like
-'pdftexdir' and 'xetexdir', to avoid clashes with executable names.
+program, but it’s not all that similar, either. In this case, the main
+work is done by creating a new subdirectory of ‘texk/web2c/’ for the
+engine. The subdirectory is conventionally named ending in ‘dir’, like
+‘pdftexdir’ and ‘xetexdir’, to avoid clashes with executable names.
The source files for the new engine should be put in this
-'NEWENGINEdir' subdirectory. Also, a file
-'NEWENGINEdir/am/NEWENGINE.am' (e.g., 'pdftexdir/am/pdftex.am' is needed
+‘NEWENGINEdir’ subdirectory. Also, a file
+‘NEWENGINEdir/am/NEWENGINE.am’ (e.g., ‘pdftexdir/am/pdftex.am’ is needed
with the Makefile fragment needed to build it.
- The overall 'web2c/Makefile.am' needs to have an 'include' statement
-added to insert that 'NEWENGINE.am' file.
+ The overall ‘web2c/Makefile.am’ needs to have an ‘include’ statement
+added to insert that ‘NEWENGINE.am’ file.
- In 'web2c/ac/web2c.ac', a line needs to be added in the definition of
-the 'kpse_tex_progs' variable to include it in the build. That line
+ In ‘web2c/ac/web2c.ac’, a line needs to be added in the definition of
+the ‘kpse_tex_progs’ variable to include it in the build. That line
specifies whether the new engine is built by default, and the additional
libraries requires.
For examples of building engines in CWEB, you can check the existing
-'hitexdir' and 'mplibdir' directories; these are somewhat simpler than
+‘hitexdir’ and ‘mplibdir’ directories; these are somewhat simpler than
LuaTeX. Of course, every engine will have its own unique features and
requirements, so existing examples will only take you so far.
- Web2c is built as one "package", with each subdirectory's '.am'
-fragment inserted with an Automake 'include'. This means that, for
-instance, '$(srcdir)' is '.../web2c', not '.../webdir/enginedir'. It is
+ Web2c is built as one “package”, with each subdirectory’s ‘.am’
+fragment inserted with an Automake ‘include’. This means that, for
+instance, ‘$(srcdir)’ is ‘.../web2c’, not ‘.../webdir/enginedir’. It is
a difficult setup to come to terms with, but the alternative is to
recurse into each engine subdirectory, and that would be far worse
(*note (automake)Directories::).
@@ -1490,41 +1491,41 @@
6.6.3 Adding a new generic library module
-----------------------------------------
-A generic library module in a subdirectory 'libs/LIB' must not depend on
+A generic library module in a subdirectory ‘libs/LIB’ must not depend on
TeX-specific libraries, by definition. It is included by adding its
-name 'LIB' to the M4 macro 'kpse_libs_pkgs' in 'm4/kpse-pkgs.m4'--before
+name ‘LIB’ to the M4 macro ‘kpse_libs_pkgs’ in ‘m4/kpse-pkgs.m4’—before
any other libraries from the TeX Live tree on which it depends.
- As with program modules, the subdirectory 'libs/LIB' must contain the
+ As with program modules, the subdirectory ‘libs/LIB’ must contain the
sources and build system for the library (and any installable support
-programs) and a fragment 'ac/withenable.ac' that contains the M4 macro
-'KPSE_WITH_LIB' defined in 'm4/kpse-setup.m4' with 'LIB' as the
+programs) and a fragment ‘ac/withenable.ac’ that contains the M4 macro
+‘KPSE_WITH_LIB’ defined in ‘m4/kpse-setup.m4’ with ‘LIB’ as the
mandatory first argument and two optional arguments: a list of required
libraries from the TL tree, and a list of options: for libraries,
-currently there is only one--specify 'tree' if this library cannot be
+currently there is only one—specify ‘tree’ if this library cannot be
replaced by a system version.
- If a system version can be used, a second fragment 'ac/LIB.ac' is
-needed, containing the M4 macro 'KPSE_TRY_LIB' (or 'KPSE_TRY_LIBXX')
-with 'LIB' as the mandatory first argument and two additional arguments
-for the Autoconf macro 'AC_LANG_PROGRAM' used to compile and link a
+ If a system version can be used, a second fragment ‘ac/LIB.ac’ is
+needed, containing the M4 macro ‘KPSE_TRY_LIB’ (or ‘KPSE_TRY_LIBXX’)
+with ‘LIB’ as the mandatory first argument and two additional arguments
+for the Autoconf macro ‘AC_LANG_PROGRAM’ used to compile and link a
small C (or C++) program as sanity check for using the system library.
- In addition a file 'm4/kpse-LIB-flags' (at the top level) must define
-the M4 macro 'KPSE_LIB_FLAGS' (all uppercase) setting up the 'make'
-variables 'LIB_INCLUDES', 'LIB_LIBS', 'LIB_DEPEND', and 'LIB_RULE' with
-the values required for 'CPPFLAGS', 'LDADD', dependencies, and a
-(multi-line) 'make' rule to rebuild the library when necessary. All of
+ In addition a file ‘m4/kpse-LIB-flags’ (at the top level) must define
+the M4 macro ‘KPSE_LIB_FLAGS’ (all uppercase) setting up the ‘make’
+variables ‘LIB_INCLUDES’, ‘LIB_LIBS’, ‘LIB_DEPEND’, and ‘LIB_RULE’ with
+the values required for ‘CPPFLAGS’, ‘LDADD’, dependencies, and a
+(multi-line) ‘make’ rule to rebuild the library when necessary. All of
that is needed for the library from the TL tree and, if supported, for a
system version.
- If a system library is allowed, 'KPSE_LIB_FLAGS' also provides the
-configure option '--with-system-LIB' and uses the additional M4 macro
-'KPSE_LIB_SYSTEM_FLAGS' to generate the 'make' variables for a system
+ If a system library is allowed, ‘KPSE_LIB_FLAGS’ also provides the
+configure option ‘--with-system-LIB’ and uses the additional M4 macro
+‘KPSE_LIB_SYSTEM_FLAGS’ to generate the ‘make’ variables for a system
library. In addition, the definition of the M4 macro
-'KPSE_ALL_SYSTEM_FLAGS' in 'm4/kpse-pkgs.m4' must be extended by the
+‘KPSE_ALL_SYSTEM_FLAGS’ in ‘m4/kpse-pkgs.m4’ must be extended by the
line:
- 'AC_REQUIRE([KPSE_LIB_SYSTEM_FLAGS])'
+ ‘AC_REQUIRE([KPSE_LIB_SYSTEM_FLAGS])’
File: tlbuild.info, Node: Adding a new TeX-specific library module, Prev: Adding a new generic library module, Up: Extending TeX Live
@@ -1532,15 +1533,15 @@
6.6.4 Adding a new TeX-specific library module
----------------------------------------------
-A TeX-specific library module in a subdirectory 'texk/LIB' may depend on
+A TeX-specific library module in a subdirectory ‘texk/LIB’ may depend on
other TeX-specific libraries but must not depend on any generic library
from the TL tree. It is included in the same general ways as a generic
library (see the previous section), with these modifications:
- * The library name 'LIB' is added to the M4 macro
- 'kpse_texlibs_pkgs', which is also in 'm4/kpse-pkgs.m4'.
+ • The library name ‘LIB’ is added to the M4 macro
+ ‘kpse_texlibs_pkgs’, which is also in ‘m4/kpse-pkgs.m4’.
- * The fragment 'ac/withenable.ac' must use 'KPSE_WITH_TEXLIB'.
+ • The fragment ‘ac/withenable.ac’ must use ‘KPSE_WITH_TEXLIB’.
File: tlbuild.info, Node: Configure options, Next: Coding conventions, Prev: Layout and infrastructure, Up: Top
@@ -1549,13 +1550,13 @@
*******************
Corresponding to the large number of program and library modules there
-are a large number 'configure' options, most of which are described
+are a large number ‘configure’ options, most of which are described
here. The command
- 'configure --help'
+ ‘configure --help’
at the top level gives an exhaustive list of all global options and a
few important module-specific ones, whereas, e.g.,
- 'texk/lcdf-typetools/configure --help'
-also displays the 'lcdf-typetools' specific options, which are not shown
+ ‘texk/lcdf-typetools/configure --help’
+also displays the ‘lcdf-typetools’ specific options, which are not shown
at the top level.
The help text also mentions several influential environment
@@ -1562,10 +1563,10 @@
variables, but for TeX Live it is better to specify them as assignments
on the command line.
- The './Build' script used to make the binaries shipped with TeX Live
-invokes the top-level 'configure' with a few additional options (*note
+ The ‘./Build’ script used to make the binaries shipped with TeX Live
+invokes the top-level ‘configure’ with a few additional options (*note
Building::). The defaults discussed below are those for the actual
-'configure' script; invoking 'configure' via './Build' yields different
+‘configure’ script; invoking ‘configure’ via ‘./Build’ yields different
results.
Defaults for most options are set at the top level and propagated
@@ -1589,71 +1590,71 @@
* Menu:
-* '--disable-native-texlive-build'::
-* '--prefix' '--bindir' ...::
-* '--disable-largefile'::
-* '--disable-missing'::
-* '--enable-compiler-warnings='LEVEL::
-* '--enable-cxx-runtime-hack'::
-* '--enable-maintainer-mode'::
-* '--enable-multiplatform'::
-* '--enable-shared'::
-* '--enable-silent-rules'::
-* '--without-ln-s'::
-* '--without-x'::
+* --disable-native-texlive-build::
+* --prefix --bindir ...::
+* --disable-largefile::
+* --disable-missing::
+* --enable-compiler-warnings=LEVEL::
+* --enable-cxx-runtime-hack::
+* --enable-maintainer-mode::
+* --enable-multiplatform::
+* --enable-shared::
+* --enable-silent-rules::
+* --without-ln-s::
+* --without-x::
-File: tlbuild.info, Node: '--disable-native-texlive-build', Next: '--prefix' '--bindir' ..., Up: Global configure options
+File: tlbuild.info, Node: --disable-native-texlive-build, Next: --prefix --bindir ..., Up: Global configure options
-7.1.1 '--disable-native-texlive-build'
+7.1.1 ‘--disable-native-texlive-build’
--------------------------------------
If enabled (the default), build for a TL binary distribution as shipped
-by the TeX user groups. This requires GNU 'make' and implies
-'--enable-multiplatform' and '--enable-cxx-runtime-hack' (unless they
-are explicitly disabled), and enforces '--disable-shared'.
+by the TeX user groups. This requires GNU ‘make’ and implies
+‘--enable-multiplatform’ and ‘--enable-cxx-runtime-hack’ (unless they
+are explicitly disabled), and enforces ‘--disable-shared’.
If building TL for a GNU/Linux or other distribution, this should be
disabled and system versions of most libraries should be used (*note
Distro builds::).
- A related option, '--enable-texlive-build', is automatically passed
+ A related option, ‘--enable-texlive-build’, is automatically passed
to all subdirectories (and cannot be disabled). Subdirectories that can
-also be built independently from the TL tree (such as 'utils/xindy' and
-'texk/dvipng') but cooperate with TL can use this option to enable
+also be built independently from the TL tree (such as ‘utils/xindy’ and
+‘texk/dvipng’) but cooperate with TL can use this option to enable
TL-specific adaptations, such as installation paths.
-File: tlbuild.info, Node: '--prefix' '--bindir' ..., Next: '--disable-largefile', Prev: '--disable-native-texlive-build', Up: Global configure options
+File: tlbuild.info, Node: --prefix --bindir ..., Next: --disable-largefile, Prev: --disable-native-texlive-build, Up: Global configure options
-7.1.2 '--prefix', '--bindir', ...
+7.1.2 ‘--prefix’, ‘--bindir’, ...
---------------------------------
These standard Autoconf options specify various installation directories
as usual. For the complete list, *note Installation directories::.
- Also as usual, all values are prefixed by the value of 'DESTDIR', if
-set, on the 'make' command line (*note Installation in a temporary
+ Also as usual, all values are prefixed by the value of ‘DESTDIR’, if
+set, on the ‘make’ command line (*note Installation in a temporary
location: (automake)Staged Installs.).
-File: tlbuild.info, Node: '--disable-largefile', Next: '--disable-missing', Prev: '--prefix' '--bindir' ..., Up: Global configure options
+File: tlbuild.info, Node: --disable-largefile, Next: --disable-missing, Prev: --prefix --bindir ..., Up: Global configure options
-7.1.3 '--disable-largefile'
+7.1.3 ‘--disable-largefile’
---------------------------
Omit large file support (LFS), which is needed on most 32-bit Unix
systems for files with 2GB or more. Regardless of this option, the size
-of 'DVI' and 'GF' files must always be <2GB, due to the file format
+of ‘DVI’ and ‘GF’ files must always be <2GB, due to the file format
specifications.
With LFS, there is no fixed limit on the size of PDF files created by
-'pdftex' or PostScript files created by 'dvips'.
+‘pdftex’ or PostScript files created by ‘dvips’.
-File: tlbuild.info, Node: '--disable-missing', Next: '--enable-compiler-warnings='LEVEL, Prev: '--disable-largefile', Up: Global configure options
+File: tlbuild.info, Node: --disable-missing, Next: --enable-compiler-warnings=LEVEL, Prev: --disable-largefile, Up: Global configure options
-7.1.4 '--disable-missing'
+7.1.4 ‘--disable-missing’
-------------------------
Immediately terminate the build process if a requested program or
@@ -1661,88 +1662,88 @@
when figuring out a specific (sub)set of modules to enable.
-File: tlbuild.info, Node: '--enable-compiler-warnings='LEVEL, Next: '--enable-cxx-runtime-hack', Prev: '--disable-missing', Up: Global configure options
+File: tlbuild.info, Node: --enable-compiler-warnings=LEVEL, Next: --enable-cxx-runtime-hack, Prev: --disable-missing, Up: Global configure options
-7.1.5 '--enable-compiler-warnings='LEVEL
+7.1.5 ‘--enable-compiler-warnings=’LEVEL
----------------------------------------
Enable various levels of compiler warnings for C, C++, and/or
-Objective C: the LEVEL value can be one of: 'no min yes max all'. The
-default is 'yes' in 'maintainer-mode' (see below) and 'min' otherwise.
-This option defines the variables 'WARNING_[OBJ]C[XX]FLAGS', but these
+Objective C: the LEVEL value can be one of: ‘no min yes max all’. The
+default is ‘yes’ in ‘maintainer-mode’ (see below) and ‘min’ otherwise.
+This option defines the variables ‘WARNING_[OBJ]C[XX]FLAGS’, but these
variables are not consistently used in all library and program modules.
At present, these warning flags assume options from the GNU compilers.
-File: tlbuild.info, Node: '--enable-cxx-runtime-hack', Next: '--enable-maintainer-mode', Prev: '--enable-compiler-warnings='LEVEL, Up: Global configure options
+File: tlbuild.info, Node: --enable-cxx-runtime-hack, Next: --enable-maintainer-mode, Prev: --enable-compiler-warnings=LEVEL, Up: Global configure options
-7.1.6 '--enable-cxx-runtime-hack'
+7.1.6 ‘--enable-cxx-runtime-hack’
---------------------------------
-If enabled (as it is for the native TL build), when using 'g++', try to
-statically link with 'libstdc++', thus improving portability of the
+If enabled (as it is for the native TL build), when using ‘g++’, try to
+statically link with ‘libstdc++’, thus improving portability of the
resulting binary. *Note Macros for compilers::.
-File: tlbuild.info, Node: '--enable-maintainer-mode', Next: '--enable-multiplatform', Prev: '--enable-cxx-runtime-hack', Up: Global configure options
+File: tlbuild.info, Node: --enable-maintainer-mode, Next: --enable-multiplatform, Prev: --enable-cxx-runtime-hack, Up: Global configure options
-7.1.7 '--enable-maintainer-mode'
+7.1.7 ‘--enable-maintainer-mode’
--------------------------------
-Enable 'make' rules and dependencies not useful (and sometimes
+Enable ‘make’ rules and dependencies not useful (and sometimes
confusing) to the casual user. This requires current versions of the
GNU build tools (*note Build system tools::), as it automatically
-rebuilds infrastructure files as needed. *Note 'missing' and
-'AM_MAINTAINER_MODE': (automake)maintainer-mode.
+rebuilds infrastructure files as needed. *Note ‘missing’ and
+‘AM_MAINTAINER_MODE’: (automake)maintainer-mode.
-File: tlbuild.info, Node: '--enable-multiplatform', Next: '--enable-shared', Prev: '--enable-maintainer-mode', Up: Global configure options
+File: tlbuild.info, Node: --enable-multiplatform, Next: --enable-shared, Prev: --enable-maintainer-mode, Up: Global configure options
-7.1.8 '--enable-multiplatform'
+7.1.8 ‘--enable-multiplatform’
------------------------------
-If enabled (as it is for the native TL build) and '--bindir=DIR' or
-'--libdir=DIR' are not specified, install executables and libraries in
-per-platform subdirectories of 'EPREFIX/bin' and 'EPREFIX/lib' where
-EPREFIX is the value given or implied for 'exec_prefix'. In any case,
-the values for 'bindir' and 'libdir' are automatically propagated to all
+If enabled (as it is for the native TL build) and ‘--bindir=DIR’ or
+‘--libdir=DIR’ are not specified, install executables and libraries in
+per-platform subdirectories of ‘EPREFIX/bin’ and ‘EPREFIX/lib’ where
+EPREFIX is the value given or implied for ‘exec_prefix’. In any case,
+the values for ‘bindir’ and ‘libdir’ are automatically propagated to all
subdirectories.
-File: tlbuild.info, Node: '--enable-shared', Next: '--enable-silent-rules', Prev: '--enable-multiplatform', Up: Global configure options
+File: tlbuild.info, Node: --enable-shared, Next: --enable-silent-rules, Prev: --enable-multiplatform, Up: Global configure options
-7.1.9 '--enable-shared'
+7.1.9 ‘--enable-shared’
-----------------------
Build shared versions of the TeX-specific libraries such as
-'libkpathsea'. This is not allowed for a native TL build (i.e.,
-'--disable-native-texlive-build' must also be specified).
+‘libkpathsea’. This is not allowed for a native TL build (i.e.,
+‘--disable-native-texlive-build’ must also be specified).
-File: tlbuild.info, Node: '--enable-silent-rules', Next: '--without-ln-s', Prev: '--enable-shared', Up: Global configure options
+File: tlbuild.info, Node: --enable-silent-rules, Next: --without-ln-s, Prev: --enable-shared, Up: Global configure options
-7.1.10 '--enable-silent-rules'
+7.1.10 ‘--enable-silent-rules’
------------------------------
-Enable the use of less verbose build rules. When using GNU 'make' (or
-any 'make' implementation supporting nested variable expansions), you
-can specify 'V=1' on the 'make' command line to get more verbosity, or
-'V=0' to get less, regardless of this option.
+Enable the use of less verbose build rules. When using GNU ‘make’ (or
+any ‘make’ implementation supporting nested variable expansions), you
+can specify ‘V=1’ on the ‘make’ command line to get more verbosity, or
+‘V=0’ to get less, regardless of this option.
-File: tlbuild.info, Node: '--without-ln-s', Next: '--without-x', Prev: '--enable-silent-rules', Up: Global configure options
+File: tlbuild.info, Node: --without-ln-s, Next: --without-x, Prev: --enable-silent-rules, Up: Global configure options
-7.1.11 '--without-ln-s'
+7.1.11 ‘--without-ln-s’
-----------------------
-Required when using a system without a working 'ln -s' to build binaries
-for a Unix-like system. However, 'make install' will not create
+Required when using a system without a working ‘ln -s’ to build binaries
+for a Unix-like system. However, ‘make install’ will not create
anything useful, and might fail.
-File: tlbuild.info, Node: '--without-x', Prev: '--without-ln-s', Up: Global configure options
+File: tlbuild.info, Node: --without-x, Prev: --without-ln-s, Up: Global configure options
-7.1.12 '--without-x'
+7.1.12 ‘--without-x’
--------------------
Disable all programs using the X Window System.
@@ -1753,214 +1754,214 @@
7.2 Program-specific configure options
======================================
-Here are (some of) the program-specific 'configure' options.
+Here are (some of) the program-specific ‘configure’ options.
* Menu:
-* '--enable-PROG' '--disable-PROG'::
-* '--disable-all-pkgs'::
-* Configure options for 'texk/web2c'::
-* Configure options for 'texk/bibtex-x'::
-* Configure options for 'texk/dvipdfm-x'::
-* Configure options for 'texk/dvisvgm'::
-* Configure options for 'texk/texlive'::
-* Configure options for 'texk/xdvik'::
-* Configure options for 'utils/xindy'::
+* --enable-PROG --disable-PROG::
+* --disable-all-pkgs::
+* Configure options for texk/web2c::
+* Configure options for texk/bibtex-x::
+* Configure options for texk/dvipdfm-x::
+* Configure options for texk/dvisvgm::
+* Configure options for texk/texlive::
+* Configure options for texk/xdvik::
+* Configure options for utils/xindy::
-File: tlbuild.info, Node: '--enable-PROG' '--disable-PROG', Next: '--disable-all-pkgs', Up: Program-specific configure options
+File: tlbuild.info, Node: --enable-PROG --disable-PROG, Next: --disable-all-pkgs, Up: Program-specific configure options
-7.2.1 '--enable-PROG', '--disable-PROG'
+7.2.1 ‘--enable-PROG’, ‘--disable-PROG’
---------------------------------------
-Do or do not build and install the program(s) of module 'PROG'.
+Do or do not build and install the program(s) of module ‘PROG’.
-File: tlbuild.info, Node: '--disable-all-pkgs', Next: Configure options for 'texk/web2c', Prev: '--enable-PROG' '--disable-PROG', Up: Program-specific configure options
+File: tlbuild.info, Node: --disable-all-pkgs, Next: Configure options for texk/web2c, Prev: --enable-PROG --disable-PROG, Up: Program-specific configure options
-7.2.2 '--disable-all-pkgs'
+7.2.2 ‘--disable-all-pkgs’
--------------------------
-Do not build any program modules by default--only those explicitly
+Do not build any program modules by default—only those explicitly
enabled. This is useful when one wants to work on only a single
-program, which is specified with an additional '--enable' option, e.g.,
-'--enable-dvipdfm-x'. It's still simplest to check out and configure
+program, which is specified with an additional ‘--enable’ option, e.g.,
+‘--enable-dvipdfm-x’. It’s still simplest to check out and configure
the whole source tree, but at least only the program you are interested
in, and its dependencies, are built. *Note Build one package::.
Without this option, all modules are built except those that are
-explicitly disabled or specify 'disable' in their 'ac/withenable.ac'
+explicitly disabled or specify ‘disable’ in their ‘ac/withenable.ac’
fragment.
-File: tlbuild.info, Node: Configure options for 'texk/web2c', Next: Configure options for 'texk/bibtex-x', Prev: '--disable-all-pkgs', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for texk/web2c, Next: Configure options for texk/bibtex-x, Prev: --disable-all-pkgs, Up: Program-specific configure options
-7.2.3 Configure options for 'texk/web2c'
+7.2.3 Configure options for ‘texk/web2c’
----------------------------------------
-'--with-banner-add=STR'
-Add 'STR' to the default version string (which is ''TeX Live YEAR'' or
-''Web2C YEAR'') appended to banner lines. This is ignored for a native
-TL build, but distro builds should specify, e.g., '/SOMEDISTRO'.
+‘--with-banner-add=STR’
+Add ‘STR’ to the default version string (which is ‘‘TeX Live YEAR’’ or
+‘‘Web2C YEAR’’) appended to banner lines. This is ignored for a native
+TL build, but distro builds should specify, e.g., ‘/SOMEDISTRO’.
-'--with-editor=CMD'
-Specify the command 'CMD' to invoke from the 'e' option of TeX and
-friends, replacing the default 'vi +%d '%s'' for Unix or 'texworks
---position=%d "%s"' for Windows.
+‘--with-editor=CMD’
+Specify the command ‘CMD’ to invoke from the ‘e’ option of TeX and
+friends, replacing the default ‘vi +%d '%s'’ for Unix or ‘texworks
+--position=%d "%s"’ for Windows.
-'--with-fontconfig-includes=DIR', '--with-fontconfig-libdir=DIR'
-Building XeTeX on non-Mac systems requires the 'fontconfig' library
+‘--with-fontconfig-includes=DIR’, ‘--with-fontconfig-libdir=DIR’
+Building XeTeX on non-Mac systems requires the ‘fontconfig’ library
headers and code. If one or both of these options are given, the
required flags are derived from them; otherwise, they are determined via
-'pkg-config' (if present).
+‘pkg-config’ (if present).
-'--with-mf-x-toolkit'
-Use the X toolkit ('libXt') for Metafont (the default is to use the
-lowest-level 'Xlib' support; it seems this has the best chance of
+‘--with-mf-x-toolkit’
+Use the X toolkit (‘libXt’) for Metafont (the default is to use the
+lowest-level ‘Xlib’ support; it seems this has the best chance of
working across X installations nowadays).
-'--disable-dump-share'
-Make the 'fmt'/'base' dump files architecture dependent (somewhat faster
+‘--disable-dump-share’
+Make the ‘fmt’/‘base’ dump files architecture dependent (somewhat faster
on LittleEndian architectures).
-'--disable-ipc'
-Disable TeX's '--ipc' option.
+‘--disable-ipc’
+Disable TeX’s ‘--ipc’ option.
-'--disable-mf-nowin'
-Do not build a separate non-graphically-capable Metafont ('mf-nowin').
+‘--disable-mf-nowin’
+Do not build a separate non-graphically-capable Metafont (‘mf-nowin’).
-'--disable-tex', '--enable-etex', ...
+‘--disable-tex’, ‘--enable-etex’, ...
Do not or do build the various TeX, Metafont, and MetaPost engines
-(defaults are defined in the fragment 'texk/web2c/ac/web2c.ac').
+(defaults are defined in the fragment ‘texk/web2c/ac/web2c.ac’).
-'--disable-web-progs'
-Do not build the original WEB programs 'bibtex', ..., 'weave'. Useful
+‘--disable-web-progs’
+Do not build the original WEB programs ‘bibtex’, ..., ‘weave’. Useful
if, e.g., you only want to (re)build some engines.
-'--enable-auto-core'
+‘--enable-auto-core’
This option causes TeX and Metafont to produce a core dump when a
particular hacky filename is encountered, for use in creating preloaded
binaries. This is rarely done nowadays.
-'--enable-libtool-hack'
-If enabled (which is the default for all platforms), prevents 'libtool'
-from linking explicitly with dependencies of 'libfontconfig' such as
-'libexpat'.
+‘--enable-libtool-hack’
+If enabled (which is the default for all platforms), prevents ‘libtool’
+from linking explicitly with dependencies of ‘libfontconfig’ such as
+‘libexpat’.
-'--enable-*win'
+‘--enable-*win’
Include various types of non-X window support for Metafont (EPSF output,
-'mftalk', old graphics terminals, ...).
+‘mftalk’, old graphics terminals, ...).
-'--enable-tex-synctex', '--disable-etex-synctex', ...
-Build the TeX engines with or without 'SyncTeX' support; ignored for a
+‘--enable-tex-synctex’, ‘--disable-etex-synctex’, ...
+Build the TeX engines with or without ‘SyncTeX’ support; ignored for a
native TeX Live build. Defaults are defined in
-'texk/web2c/ac/web2c.ac'.
+‘texk/web2c/ac/web2c.ac’.
-'--disable-synctex'
-Do not build the 'SyncTeX' library and tool.
+‘--disable-synctex’
+Do not build the ‘SyncTeX’ library and tool.
-File: tlbuild.info, Node: Configure options for 'texk/bibtex-x', Next: Configure options for 'texk/dvipdfm-x', Prev: Configure options for 'texk/web2c', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for texk/bibtex-x, Next: Configure options for texk/dvipdfm-x, Prev: Configure options for texk/web2c, Up: Program-specific configure options
-7.2.4 Configure options for 'texk/bibtex-x'
+7.2.4 Configure options for ‘texk/bibtex-x’
-------------------------------------------
-The programs 'bibtex8' and 'bibtexu' have been merged into the module
-'bibtex-x' (extended BibTeX).
+The programs ‘bibtex8’ and ‘bibtexu’ have been merged into the module
+‘bibtex-x’ (extended BibTeX).
-'--disable-bibtex8'
-Do not build the 'bibtex8' program.
+‘--disable-bibtex8’
+Do not build the ‘bibtex8’ program.
-'--disable-bibtexu'
-Do not build the 'bibtexu' program (building 'bibtexu' requires 'ICU'
+‘--disable-bibtexu’
+Do not build the ‘bibtexu’ program (building ‘bibtexu’ requires ‘ICU’
libraries).
-File: tlbuild.info, Node: Configure options for 'texk/dvipdfm-x', Next: Configure options for 'texk/dvisvgm', Prev: Configure options for 'texk/bibtex-x', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for texk/dvipdfm-x, Next: Configure options for texk/dvisvgm, Prev: Configure options for texk/bibtex-x, Up: Program-specific configure options
-7.2.5 Configure options for 'texk/dvipdfm-x'
+7.2.5 Configure options for ‘texk/dvipdfm-x’
--------------------------------------------
-The former modules 'dvipdfmx' (extended DVI to PDF converter) and
-'xdvipdfmx' (the same, as used by XeTeX) have been merged into
-'dvipdfm-x' at the source level. Two separate binaries are still
-created by default. In addition, 'dvipdfm' is created as a symlink to
-'dvipdfmx', with backward-compatible (very slightly different) behavior.
+The former modules ‘dvipdfmx’ (extended DVI to PDF converter) and
+‘xdvipdfmx’ (the same, as used by XeTeX) have been merged into
+‘dvipdfm-x’ at the source level. Two separate binaries are still
+created by default. In addition, ‘dvipdfm’ is created as a symlink to
+‘dvipdfmx’, with backward-compatible (very slightly different) behavior.
-'--disable-dvipdfmx'
-Do not build the 'dvipdfmx' program or make the 'dvipdfm' symlink.
+‘--disable-dvipdfmx’
+Do not build the ‘dvipdfmx’ program or make the ‘dvipdfm’ symlink.
-'--disable-xdvipdfmx'
-Do not build the 'xdvipdfmx' program.
+‘--disable-xdvipdfmx’
+Do not build the ‘xdvipdfmx’ program.
-File: tlbuild.info, Node: Configure options for 'texk/dvisvgm', Next: Configure options for 'texk/texlive', Prev: Configure options for 'texk/dvipdfm-x', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for texk/dvisvgm, Next: Configure options for texk/texlive, Prev: Configure options for texk/dvipdfm-x, Up: Program-specific configure options
-7.2.6 Configure options for 'texk/dvisvgm'
+7.2.6 Configure options for ‘texk/dvisvgm’
------------------------------------------
-'--with-system-libgs'
-Build 'dvisvgm' using installed Ghostscript ('gs') headers and library
-(not allowed for a native TL build). The default is to load the 'gs'
+‘--with-system-libgs’
+Build ‘dvisvgm’ using installed Ghostscript (‘gs’) headers and library
+(not allowed for a native TL build). The default is to load the ‘gs’
library at runtime if possible, else to disable support for PostScript
specials.
-'--without-libgs'
-Build 'dvisvgm' without PostScript support at all. Because the dynamic
+‘--without-libgs’
+Build ‘dvisvgm’ without PostScript support at all. Because the dynamic
loading just mentioned defeats all attempts at static linking, the
result can crash due to library incompatibilities, e.g., on CentOS 5.
-'--with-libgs-includes=DIR', '--with-libgs-libdir=DIR'
+‘--with-libgs-includes=DIR’, ‘--with-libgs-libdir=DIR’
Specify non-standard locations of the Ghostscript headers and library.
-File: tlbuild.info, Node: Configure options for 'texk/texlive', Next: Configure options for 'texk/xdvik', Prev: Configure options for 'texk/dvisvgm', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for texk/texlive, Next: Configure options for texk/xdvik, Prev: Configure options for texk/dvisvgm, Up: Program-specific configure options
-7.2.7 Configure options for 'texk/texlive'
+7.2.7 Configure options for ‘texk/texlive’
------------------------------------------
-'--disable-linked-scripts'
-Do not install the "linked scripts" (*note Linked scripts::), except for
-the TL scripts required to run 'texlinks'.
+‘--disable-linked-scripts’
+Do not install the “linked scripts” (*note Linked scripts::), except for
+the TL scripts required to run ‘texlinks’.
-File: tlbuild.info, Node: Configure options for 'texk/xdvik', Next: Configure options for 'utils/xindy', Prev: Configure options for 'texk/texlive', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for texk/xdvik, Next: Configure options for utils/xindy, Prev: Configure options for texk/texlive, Up: Program-specific configure options
-7.2.8 Configure options for 'texk/xdvik'
+7.2.8 Configure options for ‘texk/xdvik’
----------------------------------------
-'--with-gs=FILENAME'
-Hardwire the location of Ghostscript ('gs') as called by Xdvik.
+‘--with-gs=FILENAME’
+Hardwire the location of Ghostscript (‘gs’) as called by Xdvik.
-'--with-xdvi-x-toolkit=KIT'
-Use toolkit 'KIT' for 'xdvik', one of: 'motif xaw xaw3d neXtaw'. The
-default is 'motif' if available, else 'xaw'.
+‘--with-xdvi-x-toolkit=KIT’
+Use toolkit ‘KIT’ for ‘xdvik’, one of: ‘motif xaw xaw3d neXtaw’. The
+default is ‘motif’ if available, else ‘xaw’.
-'--enable-xi2-scrolling'
-Use XInput 2.1 "smooth scrolling" if available (default: yes, except for
+‘--enable-xi2-scrolling’
+Use XInput 2.1 “smooth scrolling” if available (default: yes, except for
a native TL build).
-File: tlbuild.info, Node: Configure options for 'utils/xindy', Prev: Configure options for 'texk/xdvik', Up: Program-specific configure options
+File: tlbuild.info, Node: Configure options for utils/xindy, Prev: Configure options for texk/xdvik, Up: Program-specific configure options
-7.2.9 Configure options for 'utils/xindy'
+7.2.9 Configure options for ‘utils/xindy’
-----------------------------------------
-'--enable-xindy-rules'
-Build and install 'xindy' rules (default: yes, except for a native TL
+‘--enable-xindy-rules’
+Build and install ‘xindy’ rules (default: yes, except for a native TL
build).
-'--enable-xindy-docs'
-Build and install 'xindy' documentation (default: yes, except for a
+‘--enable-xindy-docs’
+Build and install ‘xindy’ documentation (default: yes, except for a
native TL build).
-'--with-clisp-runtime=FILENAME'
-Specifies the full path for the Clisp runtime file ('lisp.run' or
-'lisp.exe') to be installed. When specified as 'default' (the default
+‘--with-clisp-runtime=FILENAME’
+Specifies the full path for the Clisp runtime file (‘lisp.run’ or
+‘lisp.exe’) to be installed. When specified as ‘default’ (the default
for a native TL build) the path is determined by the Clisp executable;
-the value 'system' (not allowed for a native TL build, but the default
-otherwise) indicates that 'xindy' will use the installed version of
-'clisp' (which must be identical to the one used to build 'xindy').
+the value ‘system’ (not allowed for a native TL build, but the default
+otherwise) indicates that ‘xindy’ will use the installed version of
+‘clisp’ (which must be identical to the one used to build ‘xindy’).
File: tlbuild.info, Node: Library-specific configure options, Next: Variables for configure, Prev: Program-specific configure options, Up: Configure options
@@ -1968,53 +1969,53 @@
7.3 Library-specific configure options
======================================
-Here are (some of) the library-specific 'configure' options, starting
+Here are (some of) the library-specific ‘configure’ options, starting
with this generic one:
-'--with-system-LIB'
+‘--with-system-LIB’
- Use an installed (system) version of the library 'LIB'; this option
+ Use an installed (system) version of the library ‘LIB’; this option
exists for most libraries, but is not allowed for a native TL build.
Using a system version implies also using the system versions of all
libraries that LIB depends on.
- For many libraries '--with-LIB-includes=DIR' and
-'--with-LIB-libdir=DIR' can specify non-standard search locations;
-others use 'pkg-config' or similar to determine the required flags.
+ For many libraries ‘--with-LIB-includes=DIR’ and
+‘--with-LIB-libdir=DIR’ can specify non-standard search locations;
+others use ‘pkg-config’ or similar to determine the required flags.
- The top-level 'configure' script performs a consistency check for all
+ The top-level ‘configure’ script performs a consistency check for all
required system libraries and bails out if tests fail.
* Menu:
-* Configure options for 'kpathsea'::
+* Configure options for kpathsea::
-File: tlbuild.info, Node: Configure options for 'kpathsea', Up: Library-specific configure options
+File: tlbuild.info, Node: Configure options for kpathsea, Up: Library-specific configure options
-7.3.1 Configure options for 'kpathsea'
+7.3.1 Configure options for ‘kpathsea’
--------------------------------------
-'--enable-CMD-default', '--disable-CMD-default'
+‘--enable-CMD-default’, ‘--disable-CMD-default’
Determine the compile time default for whether or not to run CMD, which
is one of:
-'mkocp'
+‘mkocp’
(Omega compiled translation process file)
-'mkofm'
+‘mkofm’
(Omega font metrics file)
-'mktexfmt'
+‘mktexfmt’
(format/base dump file)
-'mktexmf'
+‘mktexmf’
(Metafont source)
-'mktexpk'
+‘mktexpk’
(PK bitmap font)
-'mktextex'
+‘mktextex’
(TeX source)
-'mktextfm'
+‘mktextfm’
(TFM file)
to generate the specified type of file dynamically. The default can be
-overridden by the user in any case (*note 'kpathsea' library::).
+overridden by the user in any case (*note kpathsea library::).
File: tlbuild.info, Node: Variables for configure, Prev: Library-specific configure options, Up: Configure options
@@ -2022,44 +2023,44 @@
7.4 Variables for configure
===========================
-The values for these variables can be specified as 'configure' arguments
-of the form 'VAR=VALUE'. They can also be defined in the environment,
+The values for these variables can be specified as ‘configure’ arguments
+of the form ‘VAR=VALUE’. They can also be defined in the environment,
but that might not work for cross compilations.
-'CC'
-'CXX'
-'CPPFLAGS'
+‘CC’
+‘CXX’
+‘CPPFLAGS’
And plenty more. As usual with Autoconf, these variables specify
the name (or full path) of compilers, preprocessor flags, and
similar. *Note (autoconf)Preset Output Variables::.
-'CLISP'
- Name (or full path) of the 'clisp' executable, used to build
- 'xindy'.
+‘CLISP’
+ Name (or full path) of the ‘clisp’ executable, used to build
+ ‘xindy’.
-'FT2_CONFIG'
-'ICU_CONFIG'
-'PKG_CONFIG'
- These specify the name (or path) for the 'freetype-config',
- 'icu-config', and 'pkg-config' commands used to determine the flags
- required for system versions of 'libfreetype', the ICU libraries,
+‘FT2_CONFIG’
+‘ICU_CONFIG’
+‘PKG_CONFIG’
+ These specify the name (or path) for the ‘freetype-config’,
+ ‘icu-config’, and ‘pkg-config’ commands used to determine the flags
+ required for system versions of ‘libfreetype’, the ICU libraries,
and other libraries, respectively.
-'KPSEWHICH'
- Name (or path) of an installed 'kpsewhich' binary, used by 'make
- check' to determine the location of, e.g., 'cmbx10.tfm'.
+‘KPSEWHICH’
+ Name (or path) of an installed ‘kpsewhich’ binary, used by ‘make
+ check’ to determine the location of, e.g., ‘cmbx10.tfm’.
-'MAKE'
-'SED'
- And more. Name (or path) of the 'make', 'sed', and similar
+‘MAKE’
+‘SED’
+ And more. Name (or path) of the ‘make’, ‘sed’, and similar
programs; used at the top level and propagated to all
subdirectories.
-'PERL'
-'LATEX'
-'PDFLATEX'
- Name (or full path) for the 'perl', 'latex', and 'pdflatex'
- commands used, e.g., to build the 'xindy' documentation.
+‘PERL’
+‘LATEX’
+‘PDFLATEX’
+ Name (or full path) for the ‘perl’, ‘latex’, and ‘pdflatex’
+ commands used, e.g., to build the ‘xindy’ documentation.
File: tlbuild.info, Node: Coding conventions, Next: Continuous integration, Prev: Configure options, Up: Top
@@ -2067,12 +2068,12 @@
8 Coding conventions
********************
-Ideally, building all of TeX Live with '--enable-compiler-warnings=max'
+Ideally, building all of TeX Live with ‘--enable-compiler-warnings=max’
should produce no (GCC) compiler warnings at all. In spite of
considerable efforts into that direction we are still far from that goal
and there are reasons that we may never fully reach it. Below are some
rules about declarations of functions or variables and the use of
-'const'. These rules should be applied to the code maintained in the
+‘const’. These rules should be applied to the code maintained in the
TeX Live tree and for other packages whose maintainers are willing to
accept patches.
@@ -2092,7 +2093,7 @@
The TeX Live build system no longer supports pre-ANSI C compilers. Thus
all function prototypes and definitions must conform to the ANSI C
-standard (including 'void' in the declaration of C functions with no
+standard (including ‘void’ in the declaration of C functions with no
parameters). On the other hand, TL is built for a wide variety of
systems, not all of which support the C99 standard. Therefore using C99
features should be avoided if that can easily be done. In particular, C
@@ -2101,10 +2102,10 @@
If some C99 (or later) constructs must be used, the module should
verify that they are available and otherwise provide an alternative.
-For example, the module 'texk/chktex' uses the C99 function 'stpcpy()'
+For example, the module ‘texk/chktex’ uses the C99 function ‘stpcpy()’
that may or may not be available on a particular system. It uses
-'AC_CHECK_DECLS([stpcpy])' in 'configure.ac' to test this, and provides
-a perhaps less efficient alternative (in the file 'Utility.h'):
+‘AC_CHECK_DECLS([stpcpy])’ in ‘configure.ac’ to test this, and provides
+a perhaps less efficient alternative (in the file ‘Utility.h’):
#if !(defined HAVE_DECL_STPCPY && HAVE_DECL_STPCPY)
static inline char *stpcpy(char *dest, const char *src)
@@ -2116,17 +2117,17 @@
Static functions
................
-Functions used in only one file should be declared 'static'; they
+Functions used in only one file should be declared ‘static’; they
require no prototype except in forward declarations.
Extern functions
................
-Functions not declared 'static', usually because they are used in
-several files, require an ('extern') prototype in exactly one header
+Functions not declared ‘static’, usually because they are used in
+several files, require an (‘extern’) prototype in exactly one header
file, which is included in the file defining the function and in all
-files using that function--this is the only way to guarantee consistency
-between definition and use. There should be no 'extern' declarations
+files using that function—this is the only way to guarantee consistency
+between definition and use. There should be no ‘extern’ declarations
sprinkled throughout the C code (with or without comments as to where
that function is defined).
@@ -2134,7 +2135,7 @@
.....................
The declaration of global variables follows analogous rules: they are
-either declared 'static' if used in only one file or declared 'extern'
+either declared ‘static’ if used in only one file or declared ‘extern’
in exactly one header and instantiated in exactly one file.
@@ -2143,39 +2144,39 @@
8.2 Const
=========
-The 'const' feature of C is valuable, but easy to mis-use.
+The ‘const’ feature of C is valuable, but easy to mis-use.
Function parameters
...................
Ideally, a function parameter not modified by the function should be
-declared as 'const'. This is important in particular for strings
-('char*') because the actual arguments are often string literals. It is
-perfectly legitimate and safe to use a type 'char*' value for a type
-'const char*' variable (in an assignment, as initializer, as function
+declared as ‘const’. This is important in particular for strings
+(‘char*’) because the actual arguments are often string literals. It is
+perfectly legitimate and safe to use a type ‘char*’ value for a type
+‘const char*’ variable (in an assignment, as initializer, as function
argument, or as return value). It is equally safe to use a type
-'char**' value for a type 'const char*const*' variable, but not for a
-type 'const char**' variable since that might cause modification of a
+‘char**’ value for a type ‘const char*const*’ variable, but not for a
+type ‘const char**’ variable since that might cause modification of a
quantity supposed to be constant.
- Getting all 'const' qualifiers right can get quite involved but can
+ Getting all ‘const’ qualifiers right can get quite involved but can
almost always be done. There are only a couple notable exceptions: the
-X11 headers are full of declarations that ought to use 'const' but do
-not; at one time, 'libfreetype' also did not fully specify 'const', but
+X11 headers are full of declarations that ought to use ‘const’ but do
+not; at one time, ‘libfreetype’ also did not fully specify ‘const’, but
this has not been checked recently.
-What must be avoided with 'const'
+What must be avoided with ‘const’
.................................
-The GCC compiler warnings "assignment discards qualifiers..." and
-analogous warnings for "initialization", "passing arg", or "return" must
+The GCC compiler warnings “assignment discards qualifiers...” and
+analogous warnings for “initialization”, “passing arg”, or “return” must
be strenuously avoided in our own code. The only exception is when they
are caused by X11 declarations or other third party code.
-What should be avoided with 'const'
+What should be avoided with ‘const’
...................................
-A type cast, e.g., from 'const char*' to 'char*' does not solve any
+A type cast, e.g., from ‘const char*’ to ‘char*’ does not solve any
problems; depending on warning options, it may only hide them.
Therefore such casts should be avoided whenever possible and otherwise
must be carefully analyzed to make sure that they cannot cause the
@@ -2208,7 +2209,7 @@
======================================
The git-svn program (<https://git-scm.com/docs/git-svn>) is used to
-check out the subtree 'Build/source' of the canonical Subversion
+check out the subtree ‘Build/source’ of the canonical Subversion
repository. The author index file used is not maintained in either Git
or Subversion but can be provided on request.
@@ -2216,7 +2217,7 @@
git svn --authors-file usermap clone \
svn://USER@tug.org/texlive/trunk/Build/source
-where the 'usermap' file maps Subversion user names to name and emails
+where the ‘usermap’ file maps Subversion user names to name and emails
of the authors. Anonymous checkout is also possible:
git svn --authors-file usermap clone \
svn://tug.org/texlive/trunk/Build/source
@@ -2223,29 +2224,29 @@
In the following, we will use _admin_ to refer to a user who has
read/write access to the TeX Live subversion repository, and is also an
-administrator of the ''TeX-Live'' team at Github. The above initial
-checkout has been carried out by _admin_ on the server 'texlive.info'.
+administrator of the ‘‘TeX-Live’’ team at Github. The above initial
+checkout has been carried out by _admin_ on the server ‘texlive.info’.
- On Github, a new git repository named 'texlive-source' was created by
-_admin_ within the 'TeX-Live' "organization"
+ On Github, a new git repository named ‘texlive-source’ was created by
+_admin_ within the ‘TeX-Live’ “organization”
(<https://github.com/TeX-Live>). The remote was added to the checkout
-with 'git remote add origin git at github.com:TeX-Live/texlive-source.git'.
+with ‘git remote add origin git at github.com:TeX-Live/texlive-source.git’.
To automate the update on Github, a new ssh key was generated and
-added to the 'texlive-source' repository on Github as deployment key.
-Thus, pushes using this key can only go to the 'texlive-source'
+added to the ‘texlive-source’ repository on Github as deployment key.
+Thus, pushes using this key can only go to the ‘texlive-source’
repository and not anywhere else.
- The usage of 'git-svn' requires a strict discipline to keep a linear
+ The usage of ‘git-svn’ requires a strict discipline to keep a linear
history in the master branch. Since we are aiming at a pure mirror
-facility on Github, we have decided to further restrict the 'master'
-branch of the 'texlive-source' repository on Github to changes by
+facility on Github, we have decided to further restrict the ‘master’
+branch of the ‘texlive-source’ repository on Github to changes by
_admin_.
- This setup allows other developers to branch off 'master' and push
+ This setup allows other developers to branch off ‘master’ and push
their branches to the Github repository, but all updates need to come
-from the local 'master' (not the one on Github) to Subversion, back to
-'master' on 'texlive.info', and from there to Github.
+from the local ‘master’ (not the one on Github) to Subversion, back to
+‘master’ on ‘texlive.info’, and from there to Github.
File: tlbuild.info, Node: Automatic update of the Git mirror, Next: CI testing on Travis-CI, Prev: Transfer from Subversion to Github, Up: Continuous integration
@@ -2253,10 +2254,10 @@
9.2 Automatic update of the Git mirror
======================================
-_admin_ has installed a cron job on 'texlive.info' running every 30
-minute which essentially runs 'git svn rebase' and 'git push' in the
-'master' branch of the checkout. The first command fetches the changes
-from the Subversion repository and updates the 'master' branch with
+_admin_ has installed a cron job on ‘texlive.info’ running every 30
+minute which essentially runs ‘git svn rebase’ and ‘git push’ in the
+‘master’ branch of the checkout. The first command fetches the changes
+from the Subversion repository and updates the ‘master’ branch with
them, and the second pushes changes (if any) to Github.
@@ -2265,10 +2266,10 @@
9.3 CI testing on Travis-CI
===========================
-The 'source' tree of TeX Live contains a top-level file '.travis.yml'
+The ‘source’ tree of TeX Live contains a top-level file ‘.travis.yml’
which controls the automatic testing on Travis-CI. _admin_ has
-registered with Travis-CI and allowed access to the Github's 'TeX-Live'
-organization's 'texlive-source' repository. The default settings are to
+registered with Travis-CI and allowed access to the Github’s ‘TeX-Live’
+organization’s ‘texlive-source’ repository. The default settings are to
build the last commit of each push. No further action is necessary on
Travis-CI.
@@ -2281,7 +2282,7 @@
9.4 Releases on Github
======================
-Given a git checkout of 'texlive-source':
+Given a git checkout of ‘texlive-source’:
git pull
git tag build-svnNNNN
@@ -2289,7 +2290,7 @@
and the result will appear at
<https://github.com/TeX-Live/texlive-source/releases>. Releases can
-also be made manually from that web page (see 'tl-update-bindir' for
+also be made manually from that web page (see ‘tl-update-bindir’ for
hints).
@@ -2346,10 +2347,10 @@
Within the installer, you can choose a scheme, and further customize
the set of collections to install, but not the set of the packages. To
-work at the package level, use 'tlmgr' (reference just below) after the
+work at the package level, use ‘tlmgr’ (reference just below) after the
initial installation is complete.
- The default is 'scheme-full', which installs everything, and this is
+ The default is ‘scheme-full’, which installs everything, and this is
highly recommended.
@@ -2375,8 +2376,8 @@
===========
As usual, all options can be specified in any order, and with either a
-leading '-' or '--'. An argument value can be separated from its option
-by either a space or '='.
+leading ‘-’ or ‘--’. An argument value can be separated from its option
+by either a space or ‘=’.
*-gui* [[=]_module_]
@@ -2386,18 +2387,18 @@
If _module_ is given loads the given installer module. Currently
the following modules are supported:
- 'text'
+ ‘text’
The text mode user interface (default on Unix systems,
- including Macs). Same as the '-no-gui' option.
+ including Macs). Same as the ‘-no-gui’ option.
- 'tcl' (or "perltk" or "wizard" or "expert" or nothing)
+ ‘tcl’ (or "perltk" or "wizard" or "expert" or nothing)
The Tcl/Tk user interface (default on Windows). It starts
with a small number of configuration options, roughly
equivalent to what the former wizard option offers, but a
- button 'Advanced' takes you to a screen with roughly the same
- options as the former 'perltk' interface.
+ button ‘Advanced’ takes you to a screen with roughly the same
+ options as the former ‘perltk’ interface.
The default GUI requires Tcl/Tk. This is standard on Macs
(although it is considered deprecated since Catalina) and is often
@@ -2425,13 +2426,13 @@
Specify the package repository to be used as the source of the
installation. In short, this can be a directory name or a url
- using http(s), ftp, or scp. The documentation for 'tlmgr' has the
+ using http(s), ftp, or scp. The documentation for ‘tlmgr’ has the
details (<https://tug.org/texlive/doc/tlmgr.html#OPTIONS>).
For installation, the default is to pick a mirror automatically,
using <https://mirror.ctan.org/systems/texlive/tlnet>; the chosen
mirror is used for the entire download. You can use the special
- argument 'ctan' as an abbreviation for this. (See
+ argument ‘ctan’ as an abbreviation for this. (See
<https://ctan.org> for more about CTAN and its mirrors.)
After installation is complete, you can use that installation as
@@ -2443,9 +2444,9 @@
This option allows you to choose a particular mirror from the
current list of active CTAN mirrors. This option is supported in
- the 'text' and 'gui' installer modes, and will also offer to
+ the ‘text’ and ‘gui’ installer modes, and will also offer to
install from local media if available, or from a repository
- specified on the command line. It's useful when the (default)
+ specified on the command line. It’s useful when the (default)
automatic redirection does not choose a good host for you.
*-all-options*
@@ -2462,10 +2463,10 @@
box), this option allows you to specify the _path_ to a directory
where the binaries for the current system are present. The
installation will continue as usual, but at the end all files from
- _path_ are copied over to 'bin/custom/' under your installation
- directory and this 'bin/custom/' directory is what will be added to
+ _path_ are copied over to ‘bin/custom/’ under your installation
+ directory and this ‘bin/custom/’ directory is what will be added to
the path for the post-install actions. To install multiple custom
- binary sets, manually rename 'custom' before doing each.
+ binary sets, manually rename ‘custom’ before doing each.
For more information on custom binaries, see
<https://tug.org/texlive/custom-bin.html>. For general information
@@ -2473,7 +2474,7 @@
*-debug-fakenet*
- Pretend we're doing a network install, for the sole purpose of
+ Pretend we’re doing a network install, for the sole purpose of
testing broken downloads via moving package files aside in a tlnet
mirror.
@@ -2488,17 +2489,17 @@
Instead of auto-detecting the current platform, use _platform_.
Binaries for this platform must be present and they must actually
- be runnable, or installation will fail. '-force-arch' is a
+ be runnable, or installation will fail. ‘-force-arch’ is a
synonym.
-*-help*, *-help*, *-?*
+*-help*, *–help*, *-?*
Display this help and exit. (This help is also on the web at
<https://tug.org/texlive/doc/install-tl.html>). Sometimes the
- 'perldoc' and/or 'PAGER' programs on the system have problems,
+ ‘perldoc’ and/or ‘PAGER’ programs on the system have problems,
possibly resulting in control characters being literally output.
- This can't always be detected, but you can set the 'NOPERLDOC'
- environment variable and 'perldoc' will not be used.
+ This can’t always be detected, but you can set the ‘NOPERLDOC’
+ environment variable and ‘perldoc’ will not be used.
*-in-place*
@@ -2505,7 +2506,7 @@
This is a quick-and-dirty installation option in case you already
have an rsync or svn checkout of TeX Live. It will use the
checkout as-is and will just do the necessary post-install. Be
- warned that the file 'tlpkg/texlive.tlpdb' may be rewritten, that
+ warned that the file ‘tlpkg/texlive.tlpdb’ may be rewritten, that
removal has to be done manually, and that the only realistic way to
maintain this installation is to redo it from time to time. This
option is not available via the installer interfaces. USE AT YOUR
@@ -2525,7 +2526,7 @@
If this option is not given, the installer will create a log file
in the root of the writable installation tree, for example,
- '/usr/local/texlive/YYYY/install-tl.log' for the _YYYY_ release.
+ ‘/usr/local/texlive/YYYY/install-tl.log’ for the _YYYY_ release.
*-no-cls*
@@ -2537,7 +2538,7 @@
*-persistent-downloads*
For network installs, activating this option makes the installer
- try to set up a persistent connection using the 'Net::LWP' Perl
+ try to set up a persistent connection using the ‘Net::LWP’ Perl
module. This opens only one connection between your computer and
the server per session and reuses it, instead of initiating a new
download for each package, which typically yields a significant
@@ -2544,16 +2545,16 @@
speed-up.
This option is turned on by default, and the installation program
- will fall back to using 'wget' if this is not possible. To disable
+ will fall back to using ‘wget’ if this is not possible. To disable
usage of LWP and persistent connections, use
- '-no-persistent-downloads'.
+ ‘-no-persistent-downloads’.
*-no-verify-downloads*
- By default, if a GnuPG 'gpg' binary is found in PATH, downloads are
+ By default, if a GnuPG ‘gpg’ binary is found in PATH, downloads are
verified against a cryptographic signature. This option disables
such verification. The full description is in the Crytographic
- Verification section of the 'tlmgr' documentation, e.g.,
+ Verification section of the ‘tlmgr’ documentation, e.g.,
<https://tug.org/texlive/doc/tlmgr.html#CRYPTOGRAPHIC-VERIFICATION>
*-non-admin*
@@ -2570,7 +2571,7 @@
Print the TeX Live identifier for the detected platform
(hardware/operating system) combination to standard output, and
- exit. '-print-arch' is a synonym.
+ exit. ‘-print-arch’ is a synonym.
*-profile* _profile_file_
@@ -2586,10 +2587,10 @@
*-scheme* _scheme_
Schemes are the highest level of package grouping in TeX Live; the
- default is to use the 'full' scheme, which includes everything.
+ default is to use the ‘full’ scheme, which includes everything.
This option overrides that default. You can change the scheme
again before the actual installation with the usual menu. The
- _scheme_ argument may optionally have a prefix 'scheme-'. The list
+ _scheme_ argument may optionally have a prefix ‘scheme-’. The list
of supported scheme names depends on what your package repository
provides; see the interactive menu list.
@@ -2596,11 +2597,11 @@
*-v*
Include verbose debugging messages; repeat for maximum debugging:
- '-v -v'. (Further repeats are accepted but ignored.)
+ ‘-v -v’. (Further repeats are accepted but ignored.)
-*-version*, *-version*
+*-version*, *–version*
- Output version information and exit. If '-v' is also given, the
+ Output version information and exit. If ‘-v’ is also given, the
versions of the TeX Live modules used are also reported.
@@ -2611,11 +2612,11 @@
A _profile_ file contains all the values needed to perform an
installation. After a normal installation has finished, a profile for
-that exact installation is written to the file 'tlpkg/texlive.profile'.
-In addition, from the text menu one can select 'P' to save the current
+that exact installation is written to the file ‘tlpkg/texlive.profile’.
+In addition, from the text menu one can select ‘P’ to save the current
setup as a profile at any time.
- Such a profile file can be given as the argument to '-profile', for
+ Such a profile file can be given as the argument to ‘-profile’, for
example to redo the exact same installation on a different system.
Alternatively, you can use a custom profile, most easily created by
starting from a generated one and changing values, or an empty file,
@@ -2623,7 +2624,7 @@
As mentioned above, the installer only supports selection by scheme
and collections, not individual packages, so packages cannot be
-specified in profile files either. Use 'tlmgr' to work at the package
+specified in profile files either. Use ‘tlmgr’ to work at the package
level.
Within a profile file, each line consists of
@@ -2630,12 +2631,12 @@
_variable_ [_value_]
- except for comment lines starting with '#'. The possible variable
-names are listed below. Values, when present, are either '0' or '1' for
+ except for comment lines starting with ‘#’. The possible variable
+names are listed below. Values, when present, are either ‘0’ or ‘1’ for
booleans, or strings (which must be specified without any quote
characters). Leading whitespace is ignored.
- If the variable 'selected_scheme' is defined and _no_ collection
+ If the variable ‘selected_scheme’ is defined and _no_ collection
variables at all are defined, then the collections required by the
specified scheme (which might change over time) are installed, without
explicitly listing them. This eases maintenance of profile files. If
@@ -2648,21 +2649,21 @@
along with definitions for the installation directories (given below
under "path options") suffices to install the "small" scheme with all
-default options. The schemes are described in the 'S' menu in the text
+default options. The schemes are described in the ‘S’ menu in the text
installer, or equivalent.
- Besides 'selected_scheme', here is the list of variable names
+ Besides ‘selected_scheme’, here is the list of variable names
supported in a profile:
- *collection options* (prefix 'collection-')
+ *collection options* (prefix ‘collection-’)
Collections are specified with a variable name with the prefix
-'collection-' followed by a collection name; there is no value. For
-instance, 'collection-basic'. The collections are described in the 'C'
+‘collection-’ followed by a collection name; there is no value. For
+instance, ‘collection-basic’. The collections are described in the ‘C’
menu.
Schemes and collections (and packages) are ultimately defined by the
-files in the 'tlpkg/tlpsrc/' source directory.
+files in the ‘tlpkg/tlpsrc/’ source directory.
*path options*
@@ -2678,34 +2679,34 @@
TEXMFSYSCONFIG
TEXMFSYSVAR
- *installer options* (prefix 'instopt_')
+ *installer options* (prefix ‘instopt_’)
-'instopt_adjustpath' (default 0 on Unix, 1 on Windows)
+‘instopt_adjustpath’ (default 0 on Unix, 1 on Windows)
- Adjust 'PATH' environment variable.
+ Adjust ‘PATH’ environment variable.
-'instopt_adjustrepo' (default 1)
+‘instopt_adjustrepo’ (default 1)
Set remote repository to a multiplexed CTAN mirror after
- installation; see '-repository' above.
+ installation; see ‘-repository’ above.
-'instopt_letter' (default 0)
+‘instopt_letter’ (default 0)
Set letter size paper as the default, instead of a4.
-'instopt_portable' (default 0)
+‘instopt_portable’ (default 0)
Install for portable use, e.g., on a USB stick.
-'instopt_write18_restricted' (default 1)
+‘instopt_write18_restricted’ (default 1)
- Enable '\write18' for a restricted set of programs.
+ Enable ‘\write18’ for a restricted set of programs.
- *tlpdb options* (prefix 'tlpdbopt_')
+ *tlpdb options* (prefix ‘tlpdbopt_’)
- The definitive list is given in 'tlpkg/TeXLive/TLConfig.pm', in the
-hash '%TeXLive::TLConfig::TLPDBOptions', together with explanations.
-All items given there _except_ for 'tlpdbopt_location' can be specified.
+ The definitive list is given in ‘tlpkg/TeXLive/TLConfig.pm’, in the
+hash ‘%TeXLive::TLConfig::TLPDBOptions’, together with explanations.
+All items given there _except_ for ‘tlpdbopt_location’ can be specified.
Here is the current list:
tlpdbopt_autobackup
@@ -2722,18 +2723,18 @@
tlpdbopt_sys_man
tlpdbopt_w32_multi_user
- *platform options* (prefix 'binary_')
+ *platform options* (prefix ‘binary_’)
- For each supported platform in TeX Live (directories under 'bin/'),
-the variable 'binary_'_PLATFORM_ can be set with value 1. For example:
+ For each supported platform in TeX Live (directories under ‘bin/’),
+the variable ‘binary_’_PLATFORM_ can be set with value 1. For example:
binary_x86_64-linux 1
- If no 'binary_' settings are made, the default is whatever the
+ If no ‘binary_’ settings are made, the default is whatever the
current machine is running.
In releases before 2017, many profile variables had different names
-(not documented here; see the 'install-tl' source). They are accepted
+(not documented here; see the ‘install-tl’ source). They are accepted
and transformed to the names given above. When a profile is written,
the names above are always used.
@@ -2746,72 +2747,72 @@
A.7 ENVIRONMENT VARIABLES
=========================
-For ease in scripting and debugging, 'install-tl' looks for the
+For ease in scripting and debugging, ‘install-tl’ looks for the
following environment variables. They are not of interest for normal
user installations.
-'TEXLIVE_DOWNLOADER'
+‘TEXLIVE_DOWNLOADER’
-'TL_DOWNLOAD_PROGRAM'
+‘TL_DOWNLOAD_PROGRAM’
-'TL_DOWNLOAD_ARGS'
+‘TL_DOWNLOAD_ARGS’
These override the normal choice of a download program; see the
- 'tlmgr' documentation, e.g.,
+ ‘tlmgr’ documentation, e.g.,
<https://tug.org/texlive/doc/tlmgr.html#ENVIRONMENT-VARIABLES>.
-'TEXLIVE_INSTALL_ENV_NOCHECK'
+‘TEXLIVE_INSTALL_ENV_NOCHECK’
Omit the check for environment variables containing the string
- 'tex'. People developing TeX-related software are likely to have
+ ‘tex’. People developing TeX-related software are likely to have
many such variables.
-'TEXLIVE_INSTALL_NO_CONTEXT_CACHE'
+‘TEXLIVE_INSTALL_NO_CONTEXT_CACHE’
Omit creating the ConTeXt cache. This is useful for
redistributors.
-'TEXLIVE_INSTALL_NO_RESUME'
+‘TEXLIVE_INSTALL_NO_RESUME’
Omit check for installing on top of a previous installation and
then asking about importing previous settings.
-'TEXLIVE_INSTALL_NO_WELCOME'
+‘TEXLIVE_INSTALL_NO_WELCOME’
Omit printing the welcome message after successful installation,
e.g., when testing.
-'TEXLIVE_INSTALL_PAPER'
+‘TEXLIVE_INSTALL_PAPER’
Set the default paper size for all relevant programs; must be
- either 'letter' or 'a4'. The default is 'a4'.
+ either ‘letter’ or ‘a4’. The default is ‘a4’.
-'TEXLIVE_INSTALL_PREFIX'
+‘TEXLIVE_INSTALL_PREFIX’
-'TEXLIVE_INSTALL_TEXMFCONFIG'
+‘TEXLIVE_INSTALL_TEXMFCONFIG’
-'TEXLIVE_INSTALL_TEXMFVAR'
+‘TEXLIVE_INSTALL_TEXMFVAR’
-'TEXLIVE_INSTALL_TEXMFHOME'
+‘TEXLIVE_INSTALL_TEXMFHOME’
-'TEXLIVE_INSTALL_TEXMFLOCAL'
+‘TEXLIVE_INSTALL_TEXMFLOCAL’
-'TEXLIVE_INSTALL_TEXMFSYSCONFIG'
+‘TEXLIVE_INSTALL_TEXMFSYSCONFIG’
-'TEXLIVE_INSTALL_TEXMFSYSVAR'
+‘TEXLIVE_INSTALL_TEXMFSYSVAR’
- Specify the respective directories. 'TEXLIVE_INSTALL_PREFIX'
- defaults to '/usr/local/texlive'. All the defaults can be seen by
- running the installer interactively and then typing 'D' for the
+ Specify the respective directories. ‘TEXLIVE_INSTALL_PREFIX’
+ defaults to ‘/usr/local/texlive’. All the defaults can be seen by
+ running the installer interactively and then typing ‘D’ for the
directory menu.
- To override the so-called 'TEXDIR', which defaults to the release
- directory within that prefix, e.g., '/usr/local/texlive/2020', use
+ To override the so-called ‘TEXDIR’, which defaults to the release
+ directory within that prefix, e.g., ‘/usr/local/texlive/2020’, use
a profile file (q.v.).
-'NOPERLDOC'
+‘NOPERLDOC’
- Don't try to run the '--help' message through 'perldoc'.
+ Don’t try to run the ‘--help’ message through ‘perldoc’.
File: tlbuild.info, Node: install-tl AUTHORS AND COPYRIGHT, Prev: install-tl ENVIRONMENT VARIABLES, Up: install-tl
@@ -2877,7 +2878,7 @@
The most up-to-date version of this documentation (updated nightly
from the development sources) is available at
<https://tug.org/texlive/tlmgr.html>, along with procedures for updating
-'tlmgr' itself and information about test versions.
+‘tlmgr’ itself and information about test versions.
TeX Live is organized into a few top-level _schemes_, each of which
is specified as a different set of _collections_ and _packages_, where a
@@ -2896,39 +2897,39 @@
============
After successfully installing TeX Live, here are a few common operations
-with 'tlmgr':
+with ‘tlmgr’:
-'tlmgr option repository ctan'
+‘tlmgr option repository ctan’
-'tlmgr option repository https://mirror.ctan.org/systems/texlive/tlnet'
+‘tlmgr option repository https://mirror.ctan.org/systems/texlive/tlnet’
- Tell 'tlmgr' to use a nearby CTAN mirror for future updates; useful
+ Tell ‘tlmgr’ to use a nearby CTAN mirror for future updates; useful
if you installed TeX Live from the DVD image and want to have
- continuing updates. The two commands are equivalent; 'ctan' is
+ continuing updates. The two commands are equivalent; ‘ctan’ is
just an alias for the given url.
- Caveat: 'mirror.ctan.org' resolves to many different hosts, and
+ Caveat: ‘mirror.ctan.org’ resolves to many different hosts, and
they are not perfectly synchronized; we recommend updating only
daily (at most), and not more often. You can choose a particular
mirror if problems; the list of all CTAN mirrors with the status of
each is at <https://ctan.org/mirrors/mirmon>.
-'tlmgr update --list'
+‘tlmgr update --list’
Report what would be updated without actually updating anything.
-'tlmgr update --all'
+‘tlmgr update --all’
Make your local TeX installation correspond to what is in the
package repository (typically useful when updating from CTAN).
-'tlmgr info' _what_
+‘tlmgr info’ _what_
Display detailed information about a package _what_, such as the
installation status and description, of searches for _what_ in all
packages.
- For all the capabilities and details of 'tlmgr', please read the
+ For all the capabilities and details of ‘tlmgr’, please read the
following voluminous information.
@@ -2937,23 +2938,23 @@
B.5 OPTIONS
===========
-The following options to 'tlmgr' are global options, not specific to any
+The following options to ‘tlmgr’ are global options, not specific to any
action. All options, whether global or action-specific, can be given
anywhere on the command line, and in any order. The first non-option
-argument will be the main action. In all cases, '--'_option_ and
-'-'_option_ are equivalent, and an '=' is optional between an option
+argument will be the main action. In all cases, ‘--’_option_ and
+‘-’_option_ are equivalent, and an ‘=’ is optional between an option
name and its value.
-*-repository* _url|path_
+*–repository* _url|path_
Specify the package repository from which packages should be
installed or updated, either a local directory or network location,
as below. This overridesthe default package repository found in
- the installation's TeX Live Package Database (a.k.a. the TLPDB,
- which is given entirely in the file 'tlpkg/texlive.tlpdb').
+ the installation’s TeX Live Package Database (a.k.a. the TLPDB,
+ which is given entirely in the file ‘tlpkg/texlive.tlpdb’).
- This '--repository' option changes the location only for the
- current run; to make a permanent change, use 'option repository'
+ This ‘--repository’ option changes the location only for the
+ current run; to make a permanent change, use ‘option repository’
(see the *note option: tlmgr option. action).
As an example, you can choose a particular CTAN mirror with
@@ -2965,75 +2966,75 @@
directory have to be specified. The list of CTAN mirrors is
available at <https://ctan.org/mirrors/mirmon>.
- Here's an example of using a local directory:
+ Here’s an example of using a local directory:
-repository /local/TL/repository
- For backward compatibility and convenience, '--location' and
- '--repo' are accepted as aliases for this option.
+ For backward compatibility and convenience, ‘--location’ and
+ ‘--repo’ are accepted as aliases for this option.
Locations can be specified as any of the following:
- '/some/local/dir'
+ ‘/some/local/dir’
- 'file:/some/local/dir'
+ ‘file:/some/local/dir’
Equivalent ways of specifying a local directory.
- 'ctan'
+ ‘ctan’
- 'https://mirror.ctan.org/systems/texlive/tlnet'
+ ‘https://mirror.ctan.org/systems/texlive/tlnet’
Pick a CTAN mirror automatically, trying for one that is both
nearby and up-to-date. The chosen mirror is used for the
- entire download. The bare 'ctan' is merely an alias for the
+ entire download. The bare ‘ctan’ is merely an alias for the
full url. (See <https://ctan.org> for more about CTAN and its
mirrors.)
- 'http://server/path/to/tlnet'
+ ‘http://server/path/to/tlnet’
Standard HTTP. If the (default) LWP method is used, persistent
- connections are supported. TL can also use 'curl' or 'wget'
+ connections are supported. TL can also use ‘curl’ or ‘wget’
to do the downloads, or an arbitrary user-specified program,
- as described in the 'tlmgr' documentation
+ as described in the ‘tlmgr’ documentation
(<https://tug.org/texlive/doc/tlmgr.html#ENVIRONMENT-VARIABLES>).
- 'https://server/path/to/tlnet'
+ ‘https://server/path/to/tlnet’
Again, if the (default) LWP method is used, this supports
persistent connections. Unfortunately, some versions of
- 'wget' and 'curl' do not support https, and even when 'wget'
+ ‘wget’ and ‘curl’ do not support https, and even when ‘wget’
supports https, certificates may be rejected even when the
certificate is fine, due to a lack of local certificate roots.
The simplest workaround for this problem is to use http or
ftp.
- 'ftp://server/path/to/tlnet'
+ ‘ftp://server/path/to/tlnet’
If the (default) LWP method is used, persistent connections
are supported.
- 'user at machine:/path/to/tlnet'
+ ‘user at machine:/path/to/tlnet’
- 'scp://user@machine/path/to/tlnet'
+ ‘scp://user@machine/path/to/tlnet’
- 'ssh://user@machine/path/to/tlnet'
+ ‘ssh://user@machine/path/to/tlnet’
- These forms are equivalent; they all use 'scp' to transfer
- files. Using 'ssh-agent' is recommended. (Info:
+ These forms are equivalent; they all use ‘scp’ to transfer
+ files. Using ‘ssh-agent’ is recommended. (Info:
<https://en.wikipedia.org/wiki/OpenSSH>,
<https://en.wikipedia.org/wiki/Ssh-agent>.)
- If the repository is on the network, trailing '/' characters and/or
- trailing '/tlpkg' and/or '/archive' components are ignored.
+ If the repository is on the network, trailing ‘/’ characters and/or
+ trailing ‘/tlpkg’ and/or ‘/archive’ components are ignored.
-*-gui* [_action_]
+*–gui* [_action_]
- Two notable GUI front-ends for 'tlmgr', 'tlshell' and 'tlcockpit',
+ Two notable GUI front-ends for ‘tlmgr’, ‘tlshell’ and ‘tlcockpit’,
are started up as separate programs; see their own documentation.
- 'tlmgr' itself has a graphical interface as well as the command
- line interface. You can give the option to invoke it, '--gui',
+ ‘tlmgr’ itself has a graphical interface as well as the command
+ line interface. You can give the option to invoke it, ‘--gui’,
together with an action to be brought directly into the respective
screen of the GUI. For example, running
@@ -3044,14 +3045,14 @@
TLMGR: tlmgr GUI FOR TLMGR.
However, the native GUI requires Perl/TK, which is no longer
- included in TeX Live's Perl distribution for Windows. You may find
- 'tlshell' or 'tlcockpit' easier to work with.
+ included in TeX Live’s Perl distribution for Windows. You may find
+ ‘tlshell’ or ‘tlcockpit’ easier to work with.
-*-gui-lang* _llcode_
+*–gui-lang* _llcode_
By default, the GUI tries to deduce your language from the
environment (on Windows via the registry, on Unix via
- 'LC_MESSAGES'). If that fails you can select a different language
+ ‘LC_MESSAGES’). If that fails you can select a different language
by giving this option with a language code (based on ISO 639-1).
Currently supported (but not necessarily completely translated)
are: English (en, default), Czech (cs), German (de), French (fr),
@@ -3062,20 +3063,20 @@
tlshell shares its message catalog with tlmgr.
-*-command-logfile* _file_
+*–command-logfile* _file_
- 'tlmgr' logs the output of all programs invoked (mktexlr, mtxrun,
+ ‘tlmgr’ logs the output of all programs invoked (mktexlr, mtxrun,
fmtutil, updmap) to a separate log file, by default
- 'TEXMFSYSVAR/web2c/tlmgr-commands.log'. This option allows you to
+ ‘TEXMFSYSVAR/web2c/tlmgr-commands.log’. This option allows you to
specify a different file for the log.
-*-debug-translation*
+*–debug-translation*
- In GUI mode, this switch tells 'tlmgr' to report any untranslated
+ In GUI mode, this switch tells ‘tlmgr’ to report any untranslated
(or missing) messages to standard error. This can help translators
to see what remains to be done.
-*-machine-readable*
+*–machine-readable*
Instead of the normal output intended for human consumption, write
(to standard output) a fixed format more suitable for machine
@@ -3082,72 +3083,72 @@
parsing. See the *note MACHINE-READABLE OUTPUT: tlmgr
MACHINE-READABLE OUTPUT. section below.
-*-no-execute-actions*
+*–no-execute-actions*
Suppress the execution of the execute actions as defined in the
tlpsrc files. Documented only for completeness, as this is only
useful in debugging.
-*-package-logfile* _file_
+*–package-logfile* _file_
- 'tlmgr' logs all package actions (install, remove, update, failed
+ ‘tlmgr’ logs all package actions (install, remove, update, failed
updates, failed restores) to a separate log file, by default
- 'TEXMFSYSVAR/web2c/tlmgr.log'. This option allows you to specify a
+ ‘TEXMFSYSVAR/web2c/tlmgr.log’. This option allows you to specify a
different file for the log.
-*-pause*
+*–pause*
- This option makes 'tlmgr' wait for user input before exiting.
+ This option makes ‘tlmgr’ wait for user input before exiting.
Useful on Windows to avoid disappearing command windows.
-*-persistent-downloads*
+*–persistent-downloads*
-*-no-persistent-downloads*
+*–no-persistent-downloads*
For network-based installations, this option (on by default) makes
- 'tlmgr' try to set up a persistent connection (using the 'LWP' Perl
+ ‘tlmgr’ try to set up a persistent connection (using the ‘LWP’ Perl
module). The idea is to open and reuse only one connection per
session between your computer and the server, instead of initiating
a new download for each package.
- If this is not possible, 'tlmgr' will fall back to using 'wget'.
+ If this is not possible, ‘tlmgr’ will fall back to using ‘wget’.
To disable these persistent connections, use
- '--no-persistent-downloads'.
+ ‘--no-persistent-downloads’.
-*-pin-file*
+*–pin-file*
Change the pinning file location from
- 'TEXMFLOCAL/tlpkg/pinning.txt' (see *note Pinning: tlmgr Pinning.
+ ‘TEXMFLOCAL/tlpkg/pinning.txt’ (see *note Pinning: tlmgr Pinning.
below). Documented only for completeness, as this is only useful
in debugging.
-*-usermode*
+*–usermode*
- Activates user mode for this run of 'tlmgr'; see *note USER MODE:
+ Activates user mode for this run of ‘tlmgr’; see *note USER MODE:
tlmgr USER MODE. below.
-*-usertree* _dir_
+*–usertree* _dir_
Uses _dir_ for the tree in user mode; see *note USER MODE: tlmgr
USER MODE. below.
-*-verify-repo=[none|main|all]*
+*–verify-repo=[none|main|all]*
- Defines the level of verification done: If 'none' is specified, no
- verification whatsoever is done. If 'main' is given and a working
- GnuPG ('gpg') binary is available, all repositories are checked,
- but only the main repository is required to be signed. If 'all' is
+ Defines the level of verification done: If ‘none’ is specified, no
+ verification whatsoever is done. If ‘main’ is given and a working
+ GnuPG (‘gpg’) binary is available, all repositories are checked,
+ but only the main repository is required to be signed. If ‘all’ is
given, then all repositories need to be signed. See *note
CRYPTOGRAPHIC VERIFICATION: tlmgr CRYPTOGRAPHIC VERIFICATION. below
for details.
The standard options for TeX Live programs are also accepted:
-'--help/-h/-?', '--version', '-q' (no informational messages), '-v'
+‘--help/-h/-?’, ‘--version’, ‘-q’ (no informational messages), ‘-v’
(debugging messages, can be repeated). For the details about these, see
-the 'TeXLive::TLUtils' documentation.
+the ‘TeXLive::TLUtils’ documentation.
- The '--version' option shows version information about the TeX Live
-release and about the 'tlmgr' script itself. If '-v' is also given,
+ The ‘--version’ option shows version information about the TeX Live
+release and about the ‘tlmgr’ script itself. If ‘-v’ is also given,
revision number for the loaded TeX Live Perl modules are shown, too.
@@ -3195,12 +3196,12 @@
B.6.1 help
----------
-Display this help information and exit (same as '--help', and on the web
-at <https://tug.org/texlive/doc/tlmgr.html>). Sometimes the 'perldoc'
-and/or 'PAGER' programs on the system have problems, resulting in
-control characters being literally output. This can't always be
-detected, but you can set the 'NOPERLDOC' environment variable and
-'perldoc' will not be used.
+Display this help information and exit (same as ‘--help’, and on the web
+at <https://tug.org/texlive/doc/tlmgr.html>). Sometimes the ‘perldoc’
+and/or ‘PAGER’ programs on the system have problems, resulting in
+control characters being literally output. This can’t always be
+detected, but you can set the ‘NOPERLDOC’ environment variable and
+‘perldoc’ will not be used.
File: tlbuild.info, Node: tlmgr version, Next: tlmgr backup, Prev: tlmgr help, Up: tlmgr ACTIONS
@@ -3208,9 +3209,9 @@
B.6.2 version
-------------
-Gives version information (same as '--version').
+Gives version information (same as ‘--version’).
- If '-v' has been given the revisions of the used modules are
+ If ‘-v’ has been given the revisions of the used modules are
reported, too.
@@ -3219,51 +3220,51 @@
B.6.3 backup
------------
-*backup [_option_...] -all*
+*backup [_option_...] –all*
*backup [_option_...] _pkg_...*
- If the '--clean' option is not specified, this action makes a
- backup of the given packages, or all packages given '--all'. These
- backups are saved to the value of the '--backupdir' option, if that
- is an existing and writable directory. If '--backupdir' is not
- given, the 'backupdir' option setting in the TLPDB is used, if
+ If the ‘--clean’ option is not specified, this action makes a
+ backup of the given packages, or all packages given ‘--all’. These
+ backups are saved to the value of the ‘--backupdir’ option, if that
+ is an existing and writable directory. If ‘--backupdir’ is not
+ given, the ‘backupdir’ option setting in the TLPDB is used, if
present. If both are missing, no backups are made. (The installer
- sets 'backupdir' to '.../tlpkg/backups', under the TL root
+ sets ‘backupdir’ to ‘.../tlpkg/backups’, under the TL root
installation directory, so it is usually defined; see the *note
option: tlmgr option. description for more information.)
- If the '--clean' option is specified, backups are pruned (removed)
+ If the ‘--clean’ option is specified, backups are pruned (removed)
instead of saved. The optional integer value _N_ may be specified
to set the number of backups that will be retained when cleaning.
- If 'N' is not given, the value of the 'autobackup' option is used.
+ If ‘N’ is not given, the value of the ‘autobackup’ option is used.
If both are missing, an error is issued. For more details of
- backup pruning, see the 'option' action.
+ backup pruning, see the ‘option’ action.
Options:
- *-backupdir* _directory_
+ *–backupdir* _directory_
- Overrides the 'backupdir' option setting in the TLPDB. The
+ Overrides the ‘backupdir’ option setting in the TLPDB. The
_directory_ argument is required and must specify an existing,
writable directory where backups are to be placed.
- *-all*
+ *–all*
- If '--clean' is not specified, make a backup of all packages
+ If ‘--clean’ is not specified, make a backup of all packages
in the TeX Live installation; this will take quite a lot of
- space and time. If '--clean' is specified, all packages are
+ space and time. If ‘--clean’ is specified, all packages are
pruned.
- *-clean*[=_N_]
+ *–clean*[=_N_]
Instead of making backups, prune the backup directory of old
backups, as explained above. The optional integer argument
- _N_ overrides the 'autobackup' option set in the TLPDB. You
- must use '--all' or a list of packages together with this
+ _N_ overrides the ‘autobackup’ option set in the TLPDB. You
+ must use ‘--all’ or a list of packages together with this
option, as desired.
- *-dry-run*
+ *–dry-run*
Nothing is actually backed up or removed; instead, the actions
to be performed are written to the terminal.
@@ -3285,7 +3286,7 @@
Execute one (or all) check(s) of the consistency of the installation.
If no problems are found, there will be no output. (To get a view of
-what is being done, run 'tlmgr -v check'.)
+what is being done, run ‘tlmgr -v check’.)
*depends*
@@ -3293,17 +3294,17 @@
collection, but are themselves not installed, and those packages
which are not contained in any collection.
- If you call 'tlmgr check collections' this test will be carried out
- instead since former versions for 'tlmgr' called it that way.
+ If you call ‘tlmgr check collections’ this test will be carried out
+ instead since former versions for ‘tlmgr’ called it that way.
*executes*
- Check that the files referred to by 'execute' directives in the TeX
+ Check that the files referred to by ‘execute’ directives in the TeX
Live Database are present.
*files*
- Checks that all files listed in the local TLPDB ('texlive.tlpdb')
+ Checks that all files listed in the local TLPDB (‘texlive.tlpdb’)
are actually present, and lists those missing.
*runfiles*
@@ -3313,23 +3314,23 @@
*texmfdbs*
- Checks related to the 'ls-R' files. If you have defined new trees,
- or changed the 'TEXMF' or 'TEXMFDBS' variables, it can't hurt to
+ Checks related to the ‘ls-R’ files. If you have defined new trees,
+ or changed the ‘TEXMF’ or ‘TEXMFDBS’ variables, it can’t hurt to
run this. It checks that:
- - all items in 'TEXMFDBS' have the '!!' prefix.
+ - all items in ‘TEXMFDBS’ have the ‘!!’ prefix.
- - all items in 'TEXMFBDS' have an 'ls-R' file (if they exist at all).
+ - all items in ‘TEXMFBDS’ have an ‘ls-R’ file (if they exist at all).
- - all items in 'TEXMF' with '!!' are listed in 'TEXMFDBS'.
+ - all items in ‘TEXMF’ with ‘!!’ are listed in ‘TEXMFDBS’.
- - all items in 'TEXMF' with an 'ls-R' file are listed in 'TEXMFDBS'.
+ - all items in ‘TEXMF’ with an ‘ls-R’ file are listed in ‘TEXMFDBS’.
Options:
-*-use-svn*
+*–use-svn*
- Use the output of 'svn status' instead of listing the files; for
+ Use the output of ‘svn status’ instead of listing the files; for
checking the TL development repository. (This is run nightly.)
@@ -3338,22 +3339,22 @@
B.6.6 conf
----------
-*conf [texmf|tlmgr|updmap [-conffile _file_] [-delete] [_key_ [_value_]]]*
+*conf [texmf|tlmgr|updmap [–conffile _file_] [–delete] [_key_ [_value_]]]*
-*conf auxtrees [-conffile _file_] [show|add|remove] [_value_]*
+*conf auxtrees [–conffile _file_] [show|add|remove] [_value_]*
- With only 'conf', show general configuration information for TeX
+ With only ‘conf’, show general configuration information for TeX
Live, including active configuration files, path settings, and
- more. This is like running 'texconfig conf', but works on all
+ more. This is like running ‘texconfig conf’, but works on all
supported platforms.
- With one of 'conf texmf', 'conf tlmgr', or 'conf updmap', shows all
- key/value pairs (i.e., all settings) as saved in 'ROOT/texmf.cnf',
- the user-specific 'tlmgr' configuration file (see below), or the
- first found (via 'kpsewhich') 'updmap.cfg' file, respectively.
+ With one of ‘conf texmf’, ‘conf tlmgr’, or ‘conf updmap’, shows all
+ key/value pairs (i.e., all settings) as saved in ‘ROOT/texmf.cnf’,
+ the user-specific ‘tlmgr’ configuration file (see below), or the
+ first found (via ‘kpsewhich’) ‘updmap.cfg’ file, respectively.
If _key_ is given in addition, shows the value of only that _key_
- in the respective file. If option _-delete_ is also given, the
+ in the respective file. If option _–delete_ is also given, the
value in the given configuration file is entirely removed (not just
commented out).
@@ -3360,30 +3361,30 @@
If _value_ is given in addition, _key_ is set to _value_ in the
respective file. _No error checking is done!_
- The 'PATH' value shown by 'conf' is as used by 'tlmgr'. The
- directory in which the 'tlmgr' executable is found is automatically
+ The ‘PATH’ value shown by ‘conf’ is as used by ‘tlmgr’. The
+ directory in which the ‘tlmgr’ executable is found is automatically
prepended to the PATH value inherited from the environment.
Here is a practical example of changing configuration values. If
- the execution of (some or all) system commands via '\write18' was
+ the execution of (some or all) system commands via ‘\write18’ was
left enabled during installation, you can disable it afterwards:
tlmgr conf texmf shell_escape 0
- The subcommand 'auxtrees' allows adding and removing arbitrary
- additional texmf trees, completely under user control. 'auxtrees
- show' shows the list of additional trees, 'auxtrees add' _tree_
- adds a tree to the list, and 'auxtrees remove' _tree_ removes a
+ The subcommand ‘auxtrees’ allows adding and removing arbitrary
+ additional texmf trees, completely under user control. ‘auxtrees
+ show’ shows the list of additional trees, ‘auxtrees add’ _tree_
+ adds a tree to the list, and ‘auxtrees remove’ _tree_ removes a
tree from the list (if present). The trees should not contain an
- 'ls-R' file (or files will not be found if the 'ls-R' becomes
+ ‘ls-R’ file (or files will not be found if the ‘ls-R’ becomes
stale). This works by manipulating the Kpathsea variable
- 'TEXMFAUXTREES', in (by default) 'ROOT/texmf.cnf'. Example:
+ ‘TEXMFAUXTREES’, in (by default) ‘ROOT/texmf.cnf’. Example:
tlmgr conf auxtrees add /quick/test/tree
tlmgr conf auxtrees remove /quick/test/tree
In all cases the configuration file can be explicitly specified via
- the option '--conffile' _file_, e.g., if you don't want to change
+ the option ‘--conffile’ _file_, e.g., if you don’t want to change
the system-wide configuration.
Warning: The general facility for changing configuration values is
@@ -3394,30 +3395,30 @@
File: tlbuild.info, Node: tlmgr dump-tlpdb [_option_...] [--json], Next: tlmgr generate, Prev: tlmgr conf, Up: tlmgr ACTIONS
-B.6.7 dump-tlpdb [_option_...] [-json]
+B.6.7 dump-tlpdb [_option_...] [–json]
--------------------------------------
Dump complete local or remote TLPDB to standard output, as-is. The
-output is analogous to the '--machine-readable' output; see *note
+output is analogous to the ‘--machine-readable’ output; see *note
MACHINE-READABLE OUTPUT: tlmgr MACHINE-READABLE OUTPUT. section.
Options:
-*-local*
+*–local*
Dump the local TLPDB.
-*-remote*
+*–remote*
Dump the remote TLPDB.
-*-json*
+*–json*
Instead of dumping the actual content, the database is dumped as
JSON. For the format of JSON output see
- 'tlpkg/doc/JSON-formats.txt', format definition 'TLPDB'.
+ ‘tlpkg/doc/JSON-formats.txt’, format definition ‘TLPDB’.
- Exactly one of '--local' and '--remote' must be given.
+ Exactly one of ‘--local’ and ‘--remote’ must be given.
In either case, the first line of the output specifies the repository
location, in this format:
@@ -3424,7 +3425,7 @@
"location-url" "\t" location
- where 'location-url' is the literal field name, followed by a tab,
+ where ‘location-url’ is the literal field name, followed by a tab,
and _location_ is the file or url to the repository.
Line endings may be either LF or CRLF depending on the current
@@ -3444,34 +3445,34 @@
*generate [_option_...] language.dat.lua*
- The 'generate' action overwrites any manual changes made in the
+ The ‘generate’ action overwrites any manual changes made in the
respective files: it recreates them from scratch based on the
information of the installed packages, plus local adaptions. The TeX
-Live installer and 'tlmgr' routinely call 'generate' for all of these
+Live installer and ‘tlmgr’ routinely call ‘generate’ for all of these
files.
- For managing your own fonts, please read the 'updmap --help'
+ For managing your own fonts, please read the ‘updmap --help’
information and/or <https://tug.org/fonts/fontinstall.html>.
- For managing your own formats, please read the 'fmtutil --help'
+ For managing your own formats, please read the ‘fmtutil --help’
information.
- In more detail: 'generate' remakes any of the configuration files
-'language.dat', 'language.def', and 'language.dat.lua' from the
+ In more detail: ‘generate’ remakes any of the configuration files
+‘language.dat’, ‘language.def’, and ‘language.dat.lua’ from the
information present in the local TLPDB, plus locally-maintained files.
- The locally-maintained files are 'language-local.dat',
-'language-local.def', or 'language-local.dat.lua', searched for in
-'TEXMFLOCAL' in the respective directories. If local additions are
+ The locally-maintained files are ‘language-local.dat’,
+‘language-local.def’, or ‘language-local.dat.lua’, searched for in
+‘TEXMFLOCAL’ in the respective directories. If local additions are
present, the final file is made by starting with the main file, omitting
any entries that the local file specifies to be disabled, and finally
appending the local file.
- (Historical note: The formerly supported 'updmap-local.cfg' and
-'fmtutil-local.cnf' are no longer read, since 'updmap' and 'fmtutil' now
+ (Historical note: The formerly supported ‘updmap-local.cfg’ and
+‘fmtutil-local.cnf’ are no longer read, since ‘updmap’ and ‘fmtutil’ now
reads and supports multiple configuration files. Thus, local additions
-can and should be put into an 'updmap.cfg' of 'fmtutil.cnf' file in
-'TEXMFLOCAL'. The 'generate updmap' and 'generate fmtutil' actions no
+can and should be put into an ‘updmap.cfg’ of ‘fmtutil.cnf’ file in
+‘TEXMFLOCAL’. The ‘generate updmap’ and ‘generate fmtutil’ actions no
longer exist.)
Local files specify entries to be disabled with a comment line,
@@ -3480,15 +3481,15 @@
%!NAME
--!NAME
- where 'language.dat' and 'language.def' use '%', and
-'language.dat.lua' use '--'. In all cases, the _name_ is the respective
+ where ‘language.dat’ and ‘language.def’ use ‘%’, and
+‘language.dat.lua’ use ‘--’. In all cases, the _name_ is the respective
format name or hyphenation pattern identifier. Examples:
%!german
--!usenglishmax
- (Of course, you're not likely to actually want to disable those
-particular items. They're just examples.)
+ (Of course, you’re not likely to actually want to disable those
+particular items. They’re just examples.)
After such a disabling line, the local file can include another entry
for the same item, if a different definition is desired. In general,
@@ -3495,35 +3496,35 @@
except for the special disabling lines, the local files follow the same
syntax as the master files.
- The form 'generate language' recreates all three files
-'language.dat', 'language.def', and 'language.dat.lua', while the forms
+ The form ‘generate language’ recreates all three files
+‘language.dat’, ‘language.def’, and ‘language.dat.lua’, while the forms
with an extension recreates only that given language file.
Options:
-*-dest* _output_file_
+*–dest* _output_file_
specifies the output file (defaults to the respective location in
- 'TEXMFSYSVAR'). If '--dest' is given to 'generate language', it
- serves as a basename onto which '.dat' will be appended for the
- name of the 'language.dat' output file, '.def' will be appended to
- the value for the name of the 'language.def' output file, and
- '.dat.lua' to the name of the 'language.dat.lua' file. (This is
+ ‘TEXMFSYSVAR’). If ‘--dest’ is given to ‘generate language’, it
+ serves as a basename onto which ‘.dat’ will be appended for the
+ name of the ‘language.dat’ output file, ‘.def’ will be appended to
+ the value for the name of the ‘language.def’ output file, and
+ ‘.dat.lua’ to the name of the ‘language.dat.lua’ file. (This is
just to avoid overwriting; if you want a specific name for each
- output file, we recommend invoking 'tlmgr' twice.)
+ output file, we recommend invoking ‘tlmgr’ twice.)
-*-localcfg* _local_conf_file_
+*–localcfg* _local_conf_file_
specifies the (optional) local additions (defaults to the
- respective location in 'TEXMFLOCAL').
+ respective location in ‘TEXMFLOCAL’).
-*-rebuild-sys*
+*–rebuild-sys*
- tells 'tlmgr' to run necessary programs after config files have
- been regenerated. These are: 'fmtutil-sys --all' after 'generate
- fmtutil', 'fmtutil-sys --byhyphen .../language.dat' after 'generate
- language.dat', and 'fmtutil-sys --byhyphen .../language.def' after
- 'generate language.def'.
+ tells ‘tlmgr’ to run necessary programs after config files have
+ been regenerated. These are: ‘fmtutil-sys --all’ after ‘generate
+ fmtutil’, ‘fmtutil-sys --byhyphen .../language.dat’ after ‘generate
+ language.dat’, and ‘fmtutil-sys --byhyphen .../language.def’ after
+ ‘generate language.def’.
These subsequent calls cause the newly-generated files to actually
take effect. This is not done by default since those calls are
@@ -3557,9 +3558,9 @@
*info [_option_...] schemes*
With no argument, lists all packages available at the package
- repository, prefixing those already installed with 'i'.
+ repository, prefixing those already installed with ‘i’.
- With the single word 'collections' or 'schemes' as the argument,
+ With the single word ‘collections’ or ‘schemes’ as the argument,
lists the request type instead of all packages.
With any other arguments, display information about _pkg_: the
@@ -3580,70 +3581,70 @@
It also displays information taken from the TeX Catalogue, namely
the package version, date, and license. Consider these, especially
the package version, as approximations only, due to timing skew of
- the updates of the different pieces. By contrast, the 'revision'
+ the updates of the different pieces. By contrast, the ‘revision’
value comes directly from TL and is reliable.
- The former actions 'show' and 'list' are merged into this action,
+ The former actions ‘show’ and ‘list’ are merged into this action,
but are still supported for backward compatibility.
Options:
- *-list*
+ *–list*
- If the option '--list' is given with a package, the list of
+ If the option ‘--list’ is given with a package, the list of
contained files is also shown, including those for
platform-specific dependencies. When given with schemes and
- collections, '--list' outputs their dependencies in a similar
+ collections, ‘--list’ outputs their dependencies in a similar
way.
- *-only-installed*
+ *–only-installed*
If this option is given, the installation source will not be
used; only locally installed packages, collections, or schemes
are listed.
- *-only-remote*
+ *–only-remote*
Only list packages from the remote repository. Useful when
- checking what is available in a remote repository using 'tlmgr
- --repo ... --only-remote info'. Note that '--only-installed'
- and '--only-remote' cannot both be specified.
+ checking what is available in a remote repository using ‘tlmgr
+ --repo ... --only-remote info’. Note that ‘--only-installed’
+ and ‘--only-remote’ cannot both be specified.
- *-data 'item1,item2,...'*
+ *–data ‘item1,item2,...’*
- If the option '--data' is given, its argument must be a comma
- or colon separated list of field names from: 'name',
- 'category', 'localrev', 'remoterev', 'shortdesc', 'longdesc',
- 'installed', 'size', 'relocatable', 'depends', 'cat-version',
- 'cat-date', 'cat-license', plus various 'cat-contact-*' fields
+ If the option ‘--data’ is given, its argument must be a comma
+ or colon separated list of field names from: ‘name’,
+ ‘category’, ‘localrev’, ‘remoterev’, ‘shortdesc’, ‘longdesc’,
+ ‘installed’, ‘size’, ‘relocatable’, ‘depends’, ‘cat-version’,
+ ‘cat-date’, ‘cat-license’, plus various ‘cat-contact-*’ fields
(see below).
- The 'cat-*' fields all come from the TeX Catalogue
+ The ‘cat-*’ fields all come from the TeX Catalogue
(<https://ctan.org/pkg/catalogue>). For each, there are two
- more variants with prefix 'l' and 'r', e.g., 'lcat-version'
- and 'rcat-version', which indicate the local and remote
- information, respectively. The variants without 'l' and 'r'
+ more variants with prefix ‘l’ and ‘r’, e.g., ‘lcat-version’
+ and ‘rcat-version’, which indicate the local and remote
+ information, respectively. The variants without ‘l’ and ‘r’
show the most current one, which is normally the remote value.
- The requested packages' information is listed in CSV format,
+ The requested packages’ information is listed in CSV format,
one package per line, and the column information is given by
- the 'itemN'. The 'depends' column contains the names of all
- the dependencies separated by ':' characters.
+ the ‘itemN’. The ‘depends’ column contains the names of all
+ the dependencies separated by ‘:’ characters.
- At this writing, the 'cat-contact-*' fields include: 'home',
- 'repository', 'support', 'bugs', 'announce', 'development'.
+ At this writing, the ‘cat-contact-*’ fields include: ‘home’,
+ ‘repository’, ‘support’, ‘bugs’, ‘announce’, ‘development’.
Each may be empty or a url value. A brief description is on
the CTAN upload page for new packages:
<https://ctan.org/upload>.
- *-json*
+ *–json*
- In case '--json' is specified, the output is a JSON encoded
+ In case ‘--json’ is specified, the output is a JSON encoded
array where each array element is the JSON representation of a
- single 'TLPOBJ' but with additional information. For details
- see 'tlpkg/doc/JSON-formats.txt', format definition:
- 'TLPOBJINFO'. If both '--json' and '--data' are given,
- '--json' takes precedence.
+ single ‘TLPOBJ’ but with additional information. For details
+ see ‘tlpkg/doc/JSON-formats.txt’, format definition:
+ ‘TLPOBJINFO’. If both ‘--json’ and ‘--data’ are given,
+ ‘--json’ takes precedence.
File: tlbuild.info, Node: tlmgr init-usertree, Next: tlmgr install [_option_...] _pkg_..., Prev: tlmgr info, Up: tlmgr ACTIONS
@@ -3652,8 +3653,8 @@
--------------------
Sets up a texmf tree for so-called user mode management, either the
-default user tree ('TEXMFHOME'), or one specified on the command line
-with '--usertree'. See *note USER MODE: tlmgr USER MODE. below.
+default user tree (‘TEXMFHOME’), or one specified on the command line
+with ‘--usertree’. See *note USER MODE: tlmgr USER MODE. below.
File: tlbuild.info, Node: tlmgr install [_option_...] _pkg_..., Next: tlmgr key, Prev: tlmgr init-usertree, Up: tlmgr ACTIONS
@@ -3662,44 +3663,44 @@
-------------------------------------
Install each _pkg_ given on the command line, if it is not already
-installed. It does not touch existing packages; see the 'update' action
+installed. It does not touch existing packages; see the ‘update’ action
for how to get the latest version of a package.
By default this also installs all packages on which the given _pkg_s
are dependent. Options:
-*-dry-run*
+*–dry-run*
Nothing is actually installed; instead, the actions to be performed
are written to the terminal.
-*-file*
+*–file*
Instead of fetching a package from the installation repository, use
the package files given on the command line. These files must be
standard TeX Live package files (with contained tlpobj file).
-*-force*
+*–force*
- If updates to 'tlmgr' itself (or other parts of the basic
- infrastructure) are present, 'tlmgr' will bail out and not perform
+ If updates to ‘tlmgr’ itself (or other parts of the basic
+ infrastructure) are present, ‘tlmgr’ will bail out and not perform
the installation unless this option is given. Not recommended.
-*-no-depends*
+*–no-depends*
Do not install dependencies. (By default, installing a package
ensures that all dependencies of this package are fulfilled.)
-*-no-depends-at-all*
+*–no-depends-at-all*
Normally, when you install a package which ships binary files the
respective binary package will also be installed. That is, for a
- package 'foo', the package 'foo.i386-linux' will also be installed
- on an 'i386-linux' system. This option suppresses this behavior,
- and also implies '--no-depends'. Don't use it unless you are sure
+ package ‘foo’, the package ‘foo.i386-linux’ will also be installed
+ on an ‘i386-linux’ system. This option suppresses this behavior,
+ and also implies ‘--no-depends’. Don’t use it unless you are sure
of what you are doing.
-*-reinstall*
+*–reinstall*
Reinstall a package (including dependencies for collections) even
if it already seems to be installed (i.e, is present in the TLPDB).
@@ -3709,22 +3710,22 @@
When re-installing, only dependencies on normal packages are
followed (i.e., not those of category Scheme or Collection).
-*-with-doc*
+*–with-doc*
-*-with-src*
+*–with-src*
- While not recommended, the 'install-tl' program provides an option
+ While not recommended, the ‘install-tl’ program provides an option
to omit installation of all documentation and/or source files. (By
default, everything is installed.) After such an installation, you
may find that you want the documentation or source files for a
given package after all. You can get them by using these options
- in conjunction with '--reinstall', as in (using the 'fontspec'
+ in conjunction with ‘--reinstall’, as in (using the ‘fontspec’
package as the example):
tlmgr install --reinstall --with-doc --with-src fontspec
This action does not automatically add new symlinks in system
-directories; you need to run 'tlmgr path add' (*note path: tlmgr path.)
+directories; you need to run ‘tlmgr path add’ (*note path: tlmgr path.)
yourself if you are using this feature and want new symlinks added.
@@ -3739,18 +3740,18 @@
*key remove _keyid_*
- The action 'key' allows listing, adding and removing additional GPG
+ The action ‘key’ allows listing, adding and removing additional GPG
keys to the set of trusted keys, that is, those that are used to
verify the TeX Live databases.
- With the 'list' argument, 'key' lists all keys.
+ With the ‘list’ argument, ‘key’ lists all keys.
- The 'add' argument requires another argument, either a filename or
- '-' for stdin, from which the key is added. The key is added to
- the local keyring 'GNUPGHOME/repository-keys.gpg', which is
- normally 'tlpkg/gpg/repository-keys.gpg'.
+ The ‘add’ argument requires another argument, either a filename or
+ ‘-’ for stdin, from which the key is added. The key is added to
+ the local keyring ‘GNUPGHOME/repository-keys.gpg’, which is
+ normally ‘tlpkg/gpg/repository-keys.gpg’.
- The 'remove' argument requires a key id and removes the requested
+ The ‘remove’ argument requires a key id and removes the requested
id from the local keyring.
@@ -3767,29 +3768,29 @@
B.6.15 option
-------------
-*option [-json] [show]*
+*option [–json] [show]*
-*option [-json] showall|help*
+*option [–json] showall|help*
*option _key_ [_value_]*
- The first form, 'show', shows the global TeX Live settings currently
-saved in the TLPDB with a short description and the 'key' used for
+ The first form, ‘show’, shows the global TeX Live settings currently
+saved in the TLPDB with a short description and the ‘key’ used for
changing it in parentheses.
- The second form, 'showall', is similar, but also shows options which
-can be defined but are not currently set to any value ('help' is a
+ The second form, ‘showall’, is similar, but also shows options which
+can be defined but are not currently set to any value (‘help’ is a
synonym).
- Both 'show...' forms take an option '--json', which dumps the option
+ Both ‘show...’ forms take an option ‘--json’, which dumps the option
information in JSON format. In this case, both forms dump the same
data. For the format of the JSON output see
-'tlpkg/doc/JSON-formats.txt', format definition 'TLOPTION'.
+‘tlpkg/doc/JSON-formats.txt’, format definition ‘TLOPTION’.
In the third form, with _key_, if _value_ is not given, the setting
for _key_ is displayed. If _value_ is present, _key_ is set to _value_.
- Possible values for _key_ are (run 'tlmgr option showall' for the
+ Possible values for _key_ are (run ‘tlmgr option showall’ for the
definitive list):
repository (default package repository),
@@ -3806,26 +3807,26 @@
fileassocs (Windows-only: change file associations)
multiuser (Windows-only: install for all users)
- One common use of 'option' is to permanently change the installation
+ One common use of ‘option’ is to permanently change the installation
to get further updates from the Internet, after originally installing
from DVD. To do this, you can run
tlmgr option repository https://mirror.ctan.org/systems/texlive/tlnet
- The 'install-tl' documentation has more information about the
-possible values for 'repository'. (For backward compatibility,
-'location' can be used as a synonym for 'repository'.)
+ The ‘install-tl’ documentation has more information about the
+possible values for ‘repository’. (For backward compatibility,
+‘location’ can be used as a synonym for ‘repository’.)
- If 'formats' is set (this is the default), then formats are
+ If ‘formats’ is set (this is the default), then formats are
regenerated when either the engine or the format files have changed.
Disable this only when you know how and want to regenerate formats
yourself whenever needed (which is often, in practice).
- The 'postcode' option controls execution of per-package
+ The ‘postcode’ option controls execution of per-package
postinstallation action code. It is set by default, and again disabling
is not likely to be of interest except to developers doing debugging.
- The 'docfiles' and 'srcfiles' options control the installation of
+ The ‘docfiles’ and ‘srcfiles’ options control the installation of
their respective file groups (documentation, sources; grouping is
approximate) per package. By default both are enabled (1). Either or
both can be disabled (set to 0) if disk space is limited or for minimal
@@ -3832,38 +3833,38 @@
testing installations, etc. When disabled, the respective files are not
downloaded at all.
- The options 'autobackup' and 'backupdir' determine the defaults for
-the actions 'update', 'backup' and 'restore'. These three actions need
-a directory in which to read or write the backups. If '--backupdir' is
-not specified on the command line, the 'backupdir' option value is used
-(if set). The TL installer sets 'backupdir' to '.../tlpkg/backups',
+ The options ‘autobackup’ and ‘backupdir’ determine the defaults for
+the actions ‘update’, ‘backup’ and ‘restore’. These three actions need
+a directory in which to read or write the backups. If ‘--backupdir’ is
+not specified on the command line, the ‘backupdir’ option value is used
+(if set). The TL installer sets ‘backupdir’ to ‘.../tlpkg/backups’,
under the TL root installation directory.
- The 'autobackup' option (de)activates automatic generation of
-backups. Its value is an integer. If the 'autobackup' value is '-1',
-no backups are removed. If 'autobackup' is 0 or more, it specifies the
+ The ‘autobackup’ option (de)activates automatic generation of
+backups. Its value is an integer. If the ‘autobackup’ value is ‘-1’,
+no backups are removed. If ‘autobackup’ is 0 or more, it specifies the
number of backups to keep. Thus, backups are disabled if the value is
-0. In the '--clean' mode of the 'backup' action this option also
+0. In the ‘--clean’ mode of the ‘backup’ action this option also
specifies the number to be kept. The default value is 1, so that
backups are made, but only one backup is kept.
- To setup 'autobackup' to '-1' on the command line, use:
+ To setup ‘autobackup’ to ‘-1’ on the command line, use:
tlmgr option -- autobackup -1
- The '--' avoids having the '-1' treated as an option. (The '--'
+ The ‘--’ avoids having the ‘-1’ treated as an option. (The ‘--’
stops parsing for options at the point where it appears; this is a
general feature across most Unix programs.)
- The 'sys_bin', 'sys_man', and 'sys_info' options are used on Unix
+ The ‘sys_bin’, ‘sys_man’, and ‘sys_info’ options are used on Unix
systems to control the generation of links for executables, Info files
-and man pages. See the 'path' action for details.
+and man pages. See the ‘path’ action for details.
The last three options affect behavior on Windows installations. If
-'desktop_integration' is set, then some packages will install items in a
-sub-folder of the Start menu for 'tlmgr gui', documentation, etc. If
-'fileassocs' is set, Windows file associations are made (see also the
-'postaction' action). Finally, if 'multiuser' is set, then adaptions to
+‘desktop_integration’ is set, then some packages will install items in a
+sub-folder of the Start menu for ‘tlmgr gui’, documentation, etc. If
+‘fileassocs’ is set, Windows file associations are made (see also the
+‘postaction’ action). Finally, if ‘multiuser’ is set, then adaptions to
the registry and the menus are done for all users on the system instead
of only the current user. All three options are on by default.
@@ -3875,36 +3876,36 @@
*paper [a4|letter]*
-*<[xdvi|pdftex|dvips|dvipdfmx|context|psutils] paper [_papersize_|-list]*>
+*<[xdvi|pdftex|dvips|dvipdfmx|context|psutils] paper [_papersize_|–list]*>
-*paper -json*
+*paper –json*
- With no arguments ('tlmgr paper'), shows the default paper size
+ With no arguments (‘tlmgr paper’), shows the default paper size
setting for all known programs.
- With one argument (e.g., 'tlmgr paper a4'), sets the default for all
+ With one argument (e.g., ‘tlmgr paper a4’), sets the default for all
known programs to that paper size.
With a program given as the first argument and no paper size
-specified (e.g., 'tlmgr dvips paper'), shows the default paper size for
+specified (e.g., ‘tlmgr dvips paper’), shows the default paper size for
that program.
With a program given as the first argument and a paper size as the
-last argument (e.g., 'tlmgr dvips paper a4'), set the default for that
+last argument (e.g., ‘tlmgr dvips paper a4’), set the default for that
program to that paper size.
- With a program given as the first argument and '--list' given as the
-last argument (e.g., 'tlmgr dvips paper --list'), shows all valid paper
+ With a program given as the first argument and ‘--list’ given as the
+last argument (e.g., ‘tlmgr dvips paper --list’), shows all valid paper
sizes for that program. The first size shown is the default.
- If '--json' is specified without other options, the paper setup is
+ If ‘--json’ is specified without other options, the paper setup is
dumped in JSON format. For the format of JSON output see
-'tlpkg/doc/JSON-formats.txt', format definition 'TLPAPER'.
+‘tlpkg/doc/JSON-formats.txt’, format definition ‘TLPAPER’.
Incidentally, this syntax of having a specific program name before
-the 'paper' keyword is unusual. It is inherited from the longstanding
-'texconfig' script, which supports other configuration settings for some
-programs, notably 'dvips'. 'tlmgr' does not support those extra
+the ‘paper’ keyword is unusual. It is inherited from the longstanding
+‘texconfig’ script, which supports other configuration settings for some
+programs, notably ‘dvips’. ‘tlmgr’ does not support those extra
settings.
@@ -3913,9 +3914,9 @@
B.6.17 path
-----------
-*path [-w32mode=user|admin] add*
+*path [–w32mode=user|admin] add*
-*path [-w32mode=user|admin] remove*
+*path [–w32mode=user|admin] remove*
On Unix, adds or removes symlinks for executables, man pages, and
info pages in the system directories specified by the respective
@@ -3928,22 +3929,22 @@
On Windows, the registry part where the binary directory is added
or removed is determined in the following way:
- If the user has admin rights, and the option '--w32mode' is not
+ If the user has admin rights, and the option ‘--w32mode’ is not
given, the setting _w32_multi_user_ determines the location (i.e.,
if it is on then the system path, otherwise the user path is
changed).
- If the user has admin rights, and the option '--w32mode' is given,
+ If the user has admin rights, and the option ‘--w32mode’ is given,
this option determines the path to be adjusted.
- If the user does not have admin rights, and the option '--w32mode'
+ If the user does not have admin rights, and the option ‘--w32mode’
is not given, and the setting _w32_multi_user_ is off, the user
path is changed, while if the setting _w32_multi_user_ is on, a
warning is issued that the caller does not have enough privileges.
- If the user does not have admin rights, and the option '--w32mode'
- is given, it must be 'user' and the user path will be adjusted. If
- a user without admin rights uses the option '--w32mode admin' a
+ If the user does not have admin rights, and the option ‘--w32mode’
+ is given, it must be ‘user’ and the user path will be adjusted. If
+ a user without admin rights uses the option ‘--w32mode admin’ a
warning is issued that the caller does not have enough privileges.
@@ -3952,24 +3953,24 @@
B.6.18 pinning
--------------
-The 'pinning' action manages the pinning file, see *note Pinning: tlmgr
+The ‘pinning’ action manages the pinning file, see *note Pinning: tlmgr
Pinning. below.
-'pinning show'
+‘pinning show’
Shows the current pinning data.
-'pinning add' _repo_ _pkgglob_...
+‘pinning add’ _repo_ _pkgglob_...
Pins the packages matching the _pkgglob_(s) to the repository
_repo_.
-'pinning remove' _repo_ _pkgglob_...
+‘pinning remove’ _repo_ _pkgglob_...
Any packages recorded in the pinning file matching the <pkgglob>s
for the given repository _repo_ are removed.
-'pinning remove _repo_ --all'
+‘pinning remove _repo_ --all’
Remove all pinning data for repository _repo_.
@@ -3985,31 +3986,31 @@
*platform set auto*
- 'platform list' lists the TeX Live names of all the platforms
- (a.k.a. architectures), ('i386-linux', ...) available at the
+ ‘platform list’ lists the TeX Live names of all the platforms
+ (a.k.a. architectures), (‘i386-linux’, ...) available at the
package repository.
- 'platform add' _platform_... adds the executables for each given
+ ‘platform add’ _platform_... adds the executables for each given
platform _platform_ to the installation from the repository.
- 'platform remove' _platform_... removes the executables for each
+ ‘platform remove’ _platform_... removes the executables for each
given platform _platform_ from the installation, but keeps the
currently running platform in any case.
- 'platform set' _platform_ switches TeX Live to always use the given
+ ‘platform set’ _platform_ switches TeX Live to always use the given
platform instead of auto detection.
- 'platform set auto' switches TeX Live to auto detection mode for
+ ‘platform set auto’ switches TeX Live to auto detection mode for
platform.
- Platform detection is needed to select the proper 'xz' and 'wget'
+ Platform detection is needed to select the proper ‘xz’ and ‘wget’
binaries that are shipped with TeX Live.
- 'arch' is a synonym for 'platform'.
+ ‘arch’ is a synonym for ‘platform’.
Options:
- *-dry-run*
+ *–dry-run*
Nothing is actually installed; instead, the actions to be
performed are written to the terminal.
@@ -4024,30 +4025,30 @@
*postaction [_option_...] remove [shortcut|fileassoc|script] [_pkg_...]*
- Carry out the postaction 'shortcut', 'fileassoc', or 'script' given
+ Carry out the postaction ‘shortcut’, ‘fileassoc’, or ‘script’ given
as the second required argument in install or remove mode (which is
the first required argument), for either the packages given on the
- command line, or for all if '--all' is given.
+ command line, or for all if ‘--all’ is given.
Options:
- *-w32mode=[user|admin]*
+ *–w32mode=[user|admin]*
- If the option '--w32mode' is given the value 'user', all
+ If the option ‘--w32mode’ is given the value ‘user’, all
actions will only be carried out in the user-accessible parts
- of the registry/filesystem, while the value 'admin' selects
+ of the registry/filesystem, while the value ‘admin’ selects
the system-wide parts of the registry for the file
associations. If you do not have enough permissions, using
- '--w32mode=admin' will not succeed.
+ ‘--w32mode=admin’ will not succeed.
- *-fileassocmode=[1|2]*
+ *–fileassocmode=[1|2]*
- '--fileassocmode' specifies the action for file associations.
+ ‘--fileassocmode’ specifies the action for file associations.
If it is set to 1 (the default), only new associations are
added; if it is set to 2, all associations are set to the TeX
- Live programs. (See also 'option fileassocs'.)
+ Live programs. (See also ‘option fileassocs’.)
- *-all*
+ *–all*
Carry out the postactions for all packages
@@ -4059,7 +4060,7 @@
Print the TeX Live identifier for the detected platform
(hardware/operating system) combination to standard output, and exit.
-'--print-arch' is a synonym.
+‘--print-arch’ is a synonym.
File: tlbuild.info, Node: tlmgr print-platform-info, Next: tlmgr remove [_option_...] _pkg_..., Prev: tlmgr print-platform, Up: tlmgr ACTIONS
@@ -4077,21 +4078,21 @@
------------------------------------
Remove each _pkg_ specified. Removing a collection removes all package
-dependencies (unless '--no-depends' is specified), but not any
+dependencies (unless ‘--no-depends’ is specified), but not any
collection dependencies of that collection. However, when removing a
package, dependencies are never removed. Options:
-*-all*
+*–all*
Uninstalls all of TeX Live, asking for confirmation unless
- '--force' is also specified.
+ ‘--force’ is also specified.
-*-backup*
+*–backup*
-*-backupdir* _directory_
+*–backupdir* _directory_
- These options behave just as with the *note update: (update)tlmgr
- update [_option_...] [...]. action (q.v.), except they apply to
+ These options behave just as with the *note update: (update)tlmgr
+ update [_option_...] [...]. action (q.v.), except they apply to
making backups of packages before they are removed. The default is
to make such a backup, that is, to save a copy of packages before
removal.
@@ -4099,34 +4100,34 @@
The *note restore: tlmgr restore. action explains how to restore
from a backup.
-*-no-depends*
+*–no-depends*
Do not remove dependent packages.
-*-no-depends-at-all*
+*–no-depends-at-all*
- See above under *note install: tlmgr install [_option_...] _pkg_...
- (and beware).
+ See above under *note install: tlmgr install [_option_...]
+ _pkg_.... (and beware).
-*-force*
+*–force*
By default, removal of a package or collection that is a dependency
of another collection or scheme is not allowed. With this option,
the package will be removed unconditionally. Use with care.
- A package that has been removed using the '--force' option because
+ A package that has been removed using the ‘--force’ option because
it is still listed in an installed collection or scheme will not be
- updated, and will be mentioned as 'forcibly removed' in the output
- of 'tlmgr update --list'.
+ updated, and will be mentioned as ‘forcibly removed’ in the output
+ of ‘tlmgr update --list’.
-*-dry-run*
+*–dry-run*
Nothing is actually removed; instead, the actions to be performed
are written to the terminal.
- Except with '--all', this 'remove' action does not automatically
+ Except with ‘--all’, this ‘remove’ action does not automatically
remove symlinks to executables from system directories; you need to run
-'tlmgr path remove' (*note path: tlmgr path.) yourself if you remove an
+‘tlmgr path remove’ (*note path: tlmgr path.) yourself if you remove an
individual package with a symlink in a system directory.
@@ -4150,24 +4151,24 @@
This action manages the list of repositories. See *note
(MULTIPLE_REPOSITORIES):: below for detailed explanations.
- The first form, 'repository list', lists all configured
+ The first form, ‘repository list’, lists all configured
repositories and the respective tags if set. If a path, url, or
- tag is given after the 'list' keyword, it is interpreted as the
+ tag is given after the ‘list’ keyword, it is interpreted as the
source from which to initialize a TL database and lists the
contained packages. This can also be an otherwise-unused
repository, either local or remote. If the option
- '--with-platforms' is specified in addition, for each package the
+ ‘--with-platforms’ is specified in addition, for each package the
available platforms (if any) are also listed.
- The form 'repository add' adds a repository (optionally attaching a
- tag) to the list of repositories, while 'repository remove' removes
+ The form ‘repository add’ adds a repository (optionally attaching a
+ tag) to the list of repositories, while ‘repository remove’ removes
a repository, either by full path/url, or by tag.
- The form 'repository set' sets the list of available repositories
+ The form ‘repository set’ sets the list of available repositories
to the items given on the command line, overwriting previous
settings.
- The form 'repository status' reports the verification status of the
+ The form ‘repository status’ reports the verification status of the
loaded repositories with the format of one repository per line with
fields separated by a single space:
@@ -4184,7 +4185,7 @@
That is, in normal (not machine-readable) output, the third field
(numeric verification status) is not present.
- In all cases, one of the repositories must be tagged as 'main';
+ In all cases, one of the repositories must be tagged as ‘main’;
otherwise, all operations will fail!
@@ -4195,11 +4196,11 @@
*restore [_option_...] _pkg_ [_rev_]*
-*restore [_option_...] -all*
+*restore [_option_...] –all*
Restore a package from a previously-made backup.
- If '--all' is given, try to restore the latest revision of all
+ If ‘--all’ is given, try to restore the latest revision of all
package backups found in the backup directory.
Otherwise, if neither _pkg_ nor _rev_ are given, list the available
@@ -4206,7 +4207,7 @@
backup revisions for all packages. With _pkg_ given but no _rev_,
list all available backup revisions of _pkg_.
- When listing available packages, 'tlmgr' shows the revision, and in
+ When listing available packages, ‘tlmgr’ shows the revision, and in
parenthesis the creation time if available (in format yyyy-mm-dd
hh:mm).
@@ -4215,34 +4216,34 @@
Options:
- *-all*
+ *–all*
Try to restore the latest revision of all package backups
found in the backup directory. Additional non-option
arguments (like _pkg_) are not allowed.
- *-backupdir* _directory_
+ *–backupdir* _directory_
Specify the directory where the backups are to be found. If
not given it will be taken from the configuration setting in
the TLPDB.
- *-dry-run*
+ *–dry-run*
Nothing is actually restored; instead, the actions to be
performed are written to the terminal.
- *-force*
+ *–force*
- Don't ask questions.
+ Don’t ask questions.
- *-json*
+ *–json*
- When listing backups, the option '--json' turn on JSON output.
- The format is an array of JSON objects ('name', 'rev',
- 'date'). For details see 'tlpkg/doc/JSON-formats.txt', format
- definition: 'TLBACKUPS'. If both '--json' and '--data' are
- given, '--json' takes precedence.
+ When listing backups, the option ‘--json’ turn on JSON output.
+ The format is an array of JSON objects (‘name’, ‘rev’,
+ ‘date’). For details see ‘tlpkg/doc/JSON-formats.txt’, format
+ definition: ‘TLBACKUPS’. If both ‘--json’ and ‘--data’ are
+ given, ‘--json’ takes precedence.
File: tlbuild.info, Node: tlmgr search, Next: tlmgr shell, Prev: tlmgr restore, Up: tlmgr ACTIONS
@@ -4252,9 +4253,9 @@
*search [_option_...] _what_*
-*search [_option_...] -file _what_*
+*search [_option_...] –file _what_*
-*search [_option_...] -all _what_*
+*search [_option_...] –all _what_*
By default, search the names, short descriptions, and long
descriptions of all locally installed packages for the argument
@@ -4262,26 +4263,26 @@
Options:
- *-file*
+ *–file*
List all filenames containing _what_.
- *-all*
+ *–all*
Search everything: package names, descriptions and filenames.
- *-global*
+ *–global*
Search the TeX Live Database of the installation medium,
instead of the local installation.
- *-word*
+ *–word*
Restrict the search of package names and descriptions (but not
filenames) to match only full words. For example, searching
- for 'table' with this option will not output packages
- containing the word 'tables' (unless they also contain the
- word 'table' on its own).
+ for ‘table’ with this option will not output packages
+ containing the word ‘tables’ (unless they also contain the
+ word ‘table’ on its own).
File: tlbuild.info, Node: tlmgr shell, Next: tlmgr show, Prev: tlmgr search, Up: tlmgr ACTIONS
@@ -4291,12 +4292,12 @@
Starts an interactive mode, where tlmgr prompts for commands. This can
be used directly, or for scripting. The first line of output is
-'protocol' _n_, where _n_ is an unsigned number identifying the protocol
+‘protocol’ _n_, where _n_ is an unsigned number identifying the protocol
version (currently 1).
In general, tlmgr actions that can be given on the command line
translate to commands in this shell mode. For example, you can say
-'update --list' to see what would be updated. The TLPDB is loaded the
+‘update --list’ to see what would be updated. The TLPDB is loaded the
first time it is needed (not at the beginning), and used for the rest of
the session.
@@ -4304,7 +4305,7 @@
protocol
- Print 'protocol _n_', the current protocol version.
+ Print ‘protocol _n_’, the current protocol version.
help
@@ -4320,8 +4321,8 @@
restart
- Restart 'tlmgr shell' with the original command line; most useful
- when developing 'tlmgr'.
+ Restart ‘tlmgr shell’ with the original command line; most useful
+ when developing ‘tlmgr’.
load [local|remote]
@@ -4335,12 +4336,12 @@
get [_var_] =item set [_var_ [_val_]]
Get the value of _var_, or set it to _val_. Possible _var_ names:
- 'debug-translation', 'machine-readable', 'no-execute-actions',
- 'require-verification', 'verify-downloads', 'repository', and
- 'prompt'. All except 'repository' and 'prompt' are booleans,
+ ‘debug-translation’, ‘machine-readable’, ‘no-execute-actions’,
+ ‘require-verification’, ‘verify-downloads’, ‘repository’, and
+ ‘prompt’. All except ‘repository’ and ‘prompt’ are booleans,
taking values 0 and 1, and behave like the corresponding command
- line option. The 'repository' variable takes a string, and sets
- the remote repository location. The 'prompt' variable takes a
+ line option. The ‘repository’ variable takes a string, and sets
+ the remote repository location. The ‘prompt’ variable takes a
string, and sets the current default prompt.
If _var_ or then _val_ is not specified, it is prompted for.
@@ -4359,7 +4360,7 @@
B.6.29 uninstall
----------------
-Synonym for *note remove: tlmgr remove [_option_...] _pkg_....
+Synonym for *note remove: tlmgr remove [_option_...] _pkg_....
File: tlbuild.info, Node: tlmgr update [_option_...] [_pkg_...], Prev: tlmgr uninstall, Up: tlmgr ACTIONS
@@ -4368,14 +4369,14 @@
--------------------------------------
Updates the packages given as arguments to the latest version available
-at the installation source. Either '--all' or at least one _pkg_ name
+at the installation source. Either ‘--all’ or at least one _pkg_ name
must be specified. Options:
-*-all*
+*–all*
- Update all installed packages except for 'tlmgr' itself. If
- updates to 'tlmgr' itself are present, this gives an error, unless
- also the option '--force' or '--self' is given. (See below.)
+ Update all installed packages except for ‘tlmgr’ itself. If
+ updates to ‘tlmgr’ itself are present, this gives an error, unless
+ also the option ‘--force’ or ‘--self’ is given. (See below.)
In addition to updating the installed packages, during the update
of a collection the local installation is (by default) synchronized
@@ -4383,45 +4384,45 @@
and removals.
This means that if a package has been removed on the server (and
- thus has also been removed from the respective collection), 'tlmgr'
+ thus has also been removed from the respective collection), ‘tlmgr’
will remove the package in the local installation. This is called
- "auto-remove" and is announced as such when using the option
- '--list'. This auto-removal can be suppressed using the option
- '--no-auto-remove' (not recommended, see option description).
+ “auto-remove” and is announced as such when using the option
+ ‘--list’. This auto-removal can be suppressed using the option
+ ‘--no-auto-remove’ (not recommended, see option description).
Analogously, if a package has been added to a collection on the
server that is also installed locally, it will be added to the
- local installation. This is called "auto-install" and is announced
- as such when using the option '--list'. This auto-installation can
- be suppressed using the option '--no-auto-install' (also not
+ local installation. This is called “auto-install” and is announced
+ as such when using the option ‘--list’. This auto-installation can
+ be suppressed using the option ‘--no-auto-install’ (also not
recommended).
An exception to the collection dependency checks (including the
auto-installation of packages just mentioned) are those that have
- been "forcibly removed" by you, that is, you called 'tlmgr remove
- --force' on them. (See the 'remove' action documentation.) To
+ been “forcibly removed” by you, that is, you called ‘tlmgr remove
+ --force’ on them. (See the ‘remove’ action documentation.) To
reinstall any such forcibly removed packages use
- '--reinstall-forcibly-removed'.
+ ‘--reinstall-forcibly-removed’.
To reiterate: automatic removals and additions are entirely
determined by comparison of collections. Thus, if you manually
- install an individual package 'foo' which is later removed from the
- server, 'tlmgr' will not notice and will not remove it locally.
+ install an individual package ‘foo’ which is later removed from the
+ server, ‘tlmgr’ will not notice and will not remove it locally.
(It has to be this way, without major rearchitecture work, because
the tlpdb does not record the repository from which packages come
from.)
If you want to exclude some packages from the current update run
- (e.g., due to a slow link), see the '--exclude' option below.
+ (e.g., due to a slow link), see the ‘--exclude’ option below.
-*-self*
+*–self*
- Update 'tlmgr' itself (that is, the infrastructure packages) if
+ Update ‘tlmgr’ itself (that is, the infrastructure packages) if
updates to it are present. On Windows this includes updates to the
private Perl interpreter shipped inside TeX Live.
- If this option is given together with either '--all' or a list of
- packages, then 'tlmgr' will be updated first and, if this update
+ If this option is given together with either ‘--all’ or a list of
+ packages, then ‘tlmgr’ will be updated first and, if this update
succeeds, the new version will be restarted to complete the rest of
the updates.
@@ -4432,26 +4433,26 @@
tlmgr update --force --all # update all packages but *not* infrastructure
# ... this last at your own risk, not recommended!
-*-dry-run*
+*–dry-run*
Nothing is actually installed; instead, the actions to be performed
are written to the terminal. This is a more detailed report than
- '--list'.
+ ‘--list’.
-*-list* [_pkg_]
+*–list* [_pkg_]
Concisely list the packages which would be updated, newly
installed, or removed, without actually changing anything. If
- '--all' is also given, all available updates are listed. If
- '--self' is given, but not '--all', only updates to the critical
+ ‘--all’ is also given, all available updates are listed. If
+ ‘--self’ is given, but not ‘--all’, only updates to the critical
packages (tlmgr, texlive infrastructure, perl on Windows, etc.)
- are listed. If neither '--all' nor '--self' is given, and in
- addition no _pkg_ is given, then '--all' is assumed (thus, 'tlmgr
- update --list' is the same as 'tlmgr update --list --all'). If
- neither '--all' nor '--self' is given, but specific package names
+ are listed. If neither ‘--all’ nor ‘--self’ is given, and in
+ addition no _pkg_ is given, then ‘--all’ is assumed (thus, ‘tlmgr
+ update --list’ is the same as ‘tlmgr update --list --all’). If
+ neither ‘--all’ nor ‘--self’ is given, but specific package names
are given, those packages are checked for updates.
-*-exclude* _pkg_
+*–exclude* _pkg_
Exclude _pkg_ from the update process. If this option is given
more than once, its arguments accumulate.
@@ -4461,37 +4462,37 @@
tlmgr update --all --exclude a2ping
- will not update 'a2ping', 'a2ping.i386-linux', or any other
- 'a2ping.'_ARCH_ package.
+ will not update ‘a2ping’, ‘a2ping.i386-linux’, or any other
+ ‘a2ping.’_ARCH_ package.
If this option specifies a package that would otherwise be a
candidate for auto-installation, auto-removal, or reinstallation of
- a forcibly removed package, 'tlmgr' quits with an error message.
+ a forcibly removed package, ‘tlmgr’ quits with an error message.
Excludes are not supported in these circumstances.
This option can also be set permanently in the tlmgr config file
- with the key 'update-exclude'.
+ with the key ‘update-exclude’.
-*-no-auto-remove* [_pkg_...]
+*–no-auto-remove* [_pkg_...]
- By default, 'tlmgr' tries to remove packages in an existing
+ By default, ‘tlmgr’ tries to remove packages in an existing
collection which have disappeared on the server, as described above
- under '--all'. This option prevents such removals, either for all
- packages (with '--all'), or for just the given _pkg_ names. This
+ under ‘--all’. This option prevents such removals, either for all
+ packages (with ‘--all’), or for just the given _pkg_ names. This
can lead to an inconsistent TeX installation, since packages are
not infrequently renamed or replaced by their authors. Therefore
this is not recommended.
-*-no-auto-install* [_pkg_...]
+*–no-auto-install* [_pkg_...]
- Under normal circumstances 'tlmgr' will install packages which are
- new on the server, as described above under '--all'. This option
+ Under normal circumstances ‘tlmgr’ will install packages which are
+ new on the server, as described above under ‘--all’. This option
prevents any such automatic installation, either for all packages
- (with '--all'), or the given _pkg_ names.
+ (with ‘--all’), or the given _pkg_ names.
- Furthermore, after the 'tlmgr' run using this has finished, the
+ Furthermore, after the ‘tlmgr’ run using this has finished, the
packages that would have been auto-installed _will be considered as
- forcibly removed_. So, if 'foobar' is the only new package on the
+ forcibly removed_. So, if ‘foobar’ is the only new package on the
server, then
tlmgr update --all --no-auto-install
@@ -4504,29 +4505,29 @@
Again, since packages are sometimes renamed or replaced, using this
option is not recommended.
-*-reinstall-forcibly-removed*
+*–reinstall-forcibly-removed*
- Under normal circumstances 'tlmgr' will not install packages that
+ Under normal circumstances ‘tlmgr’ will not install packages that
have been forcibly removed by the user; that is, removed with
- 'remove --force', or whose installation was prohibited by
- '--no-auto-install' during an earlier update.
+ ‘remove --force’, or whose installation was prohibited by
+ ‘--no-auto-install’ during an earlier update.
- This option makes 'tlmgr' ignore the forcible removals and
+ This option makes ‘tlmgr’ ignore the forcible removals and
re-install all such packages. This can be used to completely
- synchronize an installation with the server's idea of what is
+ synchronize an installation with the server’s idea of what is
available:
tlmgr update --reinstall-forcibly-removed --all
-*-backup*
+*–backup*
-*-backupdir* _directory_
+*–backupdir* _directory_
These two options control the creation of backups of packages
_before_ updating; that is, backing up packages as currently
installed. If neither option is given, no backup will made. If
- '--backupdir' is given and specifies a writable directory then a
- backup will be made in that location. If only '--backup' is given,
+ ‘--backupdir’ is given and specifies a writable directory then a
+ backup will be made in that location. If only ‘--backup’ is given,
then a backup will be made to the directory previously set via the
*note option: tlmgr option. action (see below). If both are given
then a backup will be made to the specified _directory_.
@@ -4535,9 +4536,9 @@
to automatically make backups for all packages, and/or keep only a
certain number of backups.
- 'tlmgr' always makes a temporary backup when updating packages, in
+ ‘tlmgr’ always makes a temporary backup when updating packages, in
case of download or other failure during an update. In contrast,
- the purpose of this '--backup' option is to save a persistent
+ the purpose of this ‘--backup’ option is to save a persistent
backup in case the actual _content_ of the update causes problems,
e.g., introduces an TeX incompatibility.
@@ -4544,38 +4545,38 @@
The *note restore: tlmgr restore. action explains how to restore
from a backup.
-*-no-depends*
+*–no-depends*
If you call for updating a package normally all depending packages
will also be checked for updates and updated if necessary. This
switch suppresses this behavior.
-*-no-depends-at-all*
+*–no-depends-at-all*
- See above under *note install: tlmgr install [_option_...] _pkg_...
- (and beware).
+ See above under *note install: tlmgr install [_option_...]
+ _pkg_.... (and beware).
-*-force*
+*–force*
- Force update of normal packages, without updating 'tlmgr' itself
- (unless the '--self' option is also given). Not recommended.
+ Force update of normal packages, without updating ‘tlmgr’ itself
+ (unless the ‘--self’ option is also given). Not recommended.
- Also, 'update --list' is still performed regardless of this option.
+ Also, ‘update --list’ is still performed regardless of this option.
If the package on the server is older than the package already
-installed (e.g., if the selected mirror is out of date), 'tlmgr' does
+installed (e.g., if the selected mirror is out of date), ‘tlmgr’ does
not downgrade. Also, packages for uninstalled platforms are not
installed.
- 'tlmgr' saves one copy of the main 'texlive.tlpdb' file used for an
+ ‘tlmgr’ saves one copy of the main ‘texlive.tlpdb’ file used for an
update with a suffix representing the repository url, as in
-'tlpkg/texlive.tlpdb.main.'_long-hash-string_. Thus, even when many
-mirrors are used, only one main 'tlpdb' backup is kept. For non-main
+‘tlpkg/texlive.tlpdb.main.’_long-hash-string_. Thus, even when many
+mirrors are used, only one main ‘tlpdb’ backup is kept. For non-main
repositories, which do not generally have (m)any mirrors, no pruning of
backups is done.
This action does not automatically add or remove new symlinks in
-system directories; you need to run 'tlmgr' *note path: tlmgr path.
+system directories; you need to run ‘tlmgr’ *note path: tlmgr path.
yourself if you are using this feature and want new symlinks added.
@@ -4584,11 +4585,11 @@
B.7 CONFIGURATION FILE FOR TLMGR
================================
-'tlmgr' reads two configuration files: one is system-wide, in
-'TEXMFSYSCONFIG/tlmgr/config', and the other is user-specific, in
-'TEXMFCONFIG/tlmgr/config'. The user-specific one is the default for
-the 'conf tlmgr' action. (Run 'kpsewhich -var-value=TEXMFSYSCONFIG' or
-'... TEXMFCONFIG ...' to see the actual directory names.)
+‘tlmgr’ reads two configuration files: one is system-wide, in
+‘TEXMFSYSCONFIG/tlmgr/config’, and the other is user-specific, in
+‘TEXMFCONFIG/tlmgr/config’. The user-specific one is the default for
+the ‘conf tlmgr’ action. (Run ‘kpsewhich -var-value=TEXMFSYSCONFIG’ or
+‘... TEXMFCONFIG ...’ to see the actual directory names.)
A few defaults corresponding to command-line options can be set in
these configuration files. In addition, the system-wide file can
@@ -4599,43 +4600,43 @@
key = value
- where the spaces are optional but the '=' is required.
+ where the spaces are optional but the ‘=’ is required.
The allowed keys are:
-'auto-remove =' 0 or 1 (default 1), same as command-line option.
+‘auto-remove =’ 0 or 1 (default 1), same as command-line option.
-'gui-expertmode =' 0 or 1 (default 1). This switches between the full GUI and a simplified GUI with only the most common settings.
+‘gui-expertmode =’ 0 or 1 (default 1). This switches between the full GUI and a simplified GUI with only the most common settings.
-'gui-lang =' _llcode_, with a language code value as with the command-line option.
+‘gui-lang =’ _llcode_, with a language code value as with the command-line option.
-'no-checksums =' 0 or 1 (default 0, see below).
+‘no-checksums =’ 0 or 1 (default 0, see below).
-'persistent-downloads =' 0 or 1 (default 1), same as command-line option.
+‘persistent-downloads =’ 0 or 1 (default 1), same as command-line option.
-'require-verification =' 0 or 1 (default 0), same as command-line option.
+‘require-verification =’ 0 or 1 (default 0), same as command-line option.
-'tkfontscale =' _floating-point number_ (default 1.0); scaling factor for fonts in the Tk-based frontends.
+‘tkfontscale =’ _floating-point number_ (default 1.0); scaling factor for fonts in the Tk-based frontends.
-'update-exclude =' _comma-separated list of packages_ (no spaces allowed). Same as the command line option '--exclude' for the 'update' action.
+‘update-exclude =’ _comma-separated list of packages_ (no spaces allowed). Same as the command line option ‘--exclude’ for the ‘update’ action.
-'verify-downloads =' 0 or 1 (default 1), same as command-line option.
+‘verify-downloads =’ 0 or 1 (default 1), same as command-line option.
The system-wide config file can contain one additional key:
-'allowed-actions =' _action1_[,_action2_,...] The value is a comma-separated list (no spaces) of 'tlmgr' actions which are allowed to be executed when 'tlmgr' is invoked in system mode (that is, without '--usermode'). This allows distributors to include 'tlmgr' in their packaging, but allow only a restricted set of actions that do not interfere with their distro package manager. For native TeX Live installations, it doesn't make sense to set this.
+‘allowed-actions =’ _action1_[,_action2_,...] The value is a comma-separated list (no spaces) of ‘tlmgr’ actions which are allowed to be executed when ‘tlmgr’ is invoked in system mode (that is, without ‘--usermode’). This allows distributors to include ‘tlmgr’ in their packaging, but allow only a restricted set of actions that do not interfere with their distro package manager. For native TeX Live installations, it doesn’t make sense to set this.
- Finally, the 'no-checksums' key needs more explanation. By default,
+ Finally, the ‘no-checksums’ key needs more explanation. By default,
package checksums computed and stored on the server (in the TLPDB) are
compared to checksums computed locally after downloading.
-'no-checksums' disables this process. The checksum algorithm is
+‘no-checksums’ disables this process. The checksum algorithm is
SHA-512. Your system must have one of (looked for in this order) the
-Perl 'Digest::SHA' module, the 'openssl' program
-(<https://openssl.org>), the 'sha512sum' program (from GNU Coreutils,
-<https://www.gnu.org/software/coreutils>), or finally the 'shasum'
+Perl ‘Digest::SHA’ module, the ‘openssl’ program
+(<https://openssl.org>), the ‘sha512sum’ program (from GNU Coreutils,
+<https://www.gnu.org/software/coreutils>), or finally the ‘shasum’
program (just to support old Macs). If none of these are available, a
-warning is issued and 'tlmgr' proceeds without checking checksums.
-'no-checksums' avoids the warning. (Incidentally, other SHA
+warning is issued and ‘tlmgr’ proceeds without checking checksums.
+‘no-checksums’ avoids the warning. (Incidentally, other SHA
implementations, such as the pure Perl and pure Lua modules, are much
too slow to be usable in our context.)
@@ -4645,41 +4646,41 @@
B.8 CRYPTOGRAPHIC VERIFICATION
==============================
-'tlmgr' and 'install-tl' perform cryptographic verification if possible.
+‘tlmgr’ and ‘install-tl’ perform cryptographic verification if possible.
If verification is performed and successful, the programs report
-'(verified)' after loading the TLPDB; otherwise, they report '(not
-verified)'. But either way, by default the installation and/or updates
+‘(verified)’ after loading the TLPDB; otherwise, they report ‘(not
+verified)’. But either way, by default the installation and/or updates
proceed normally.
- If a program named 'gpg' is available (that is, found in 'PATH'), by
+ If a program named ‘gpg’ is available (that is, found in ‘PATH’), by
default cryptographic signatures will be checked: we require the main
-repository be signed, but not any additional repositories. If 'gpg' is
+repository be signed, but not any additional repositories. If ‘gpg’ is
not available, by default signatures are not checked and no verification
-is carried out, but 'tlmgr' still proceeds normally.
+is carried out, but ‘tlmgr’ still proceeds normally.
The behavior of the verification can be controlled by the command
-line and config file option 'verify-repo' which takes one of the
-following values: 'none', 'main', or 'all'. With 'none', no
-verification whatsoever is attempted. With 'main' (the default)
-verification is required only for the main repository, and only if 'gpg'
+line and config file option ‘verify-repo’ which takes one of the
+following values: ‘none’, ‘main’, or ‘all’. With ‘none’, no
+verification whatsoever is attempted. With ‘main’ (the default)
+verification is required only for the main repository, and only if ‘gpg’
is available; though attempted for all, missing signatures of subsidiary
repositories will not result in an error. Finally, in the case of
-'all', 'gpg' must be available and all repositories need to be signed.
+‘all’, ‘gpg’ must be available and all repositories need to be signed.
In all cases, if a signature is checked and fails to verify, an error
is raised.
Cryptographic verification requires checksum checking (described just
-above) to succeed, and a working GnuPG ('gpg') program (see below for
+above) to succeed, and a working GnuPG (‘gpg’) program (see below for
search method). Then, unless cryptographic verification has been
-disabled, a signature file ('texlive.tlpdb.*.asc') of the checksum file
+disabled, a signature file (‘texlive.tlpdb.*.asc’) of the checksum file
is downloaded and the signature verified. The signature is created by
the TeX Live Distribution GPG key 0x0D5E5D9106BAB6BC, which in turn is
-signed by Karl Berry's key 0x0716748A30D155AD and Norbert Preining's key
+signed by Karl Berry’s key 0x0716748A30D155AD and Norbert Preining’s key
0x6CACA448860CDC13. All of these keys are obtainable from the standard
key servers.
- Additional trusted keys can be added using the 'key' action.
+ Additional trusted keys can be added using the ‘key’ action.
* Menu:
@@ -4692,13 +4693,13 @@
---------------------------------------
The executable used for GnuPG is searched as follows: If the environment
-variable 'TL_GNUPG' is set, it is tested and used; otherwise 'gpg' is
-checked; finally 'gpg2' is checked.
+variable ‘TL_GNUPG’ is set, it is tested and used; otherwise ‘gpg’ is
+checked; finally ‘gpg2’ is checked.
- Further adaptation of the 'gpg' invocation can be made using the two
-environment variables 'TL_GNUPGHOME', which is passed to 'gpg' as the
-value for '--homedir', and 'TL_GNUPGARGS', which replaces the default
-options '--no-secmem-warning --no-permission-warning'.
+ Further adaptation of the ‘gpg’ invocation can be made using the two
+environment variables ‘TL_GNUPGHOME’, which is passed to ‘gpg’ as the
+value for ‘--homedir’, and ‘TL_GNUPGARGS’, which replaces the default
+options ‘--no-secmem-warning --no-permission-warning’.
File: tlbuild.info, Node: tlmgr USER MODE, Next: tlmgr MULTIPLE REPOSITORIES, Prev: tlmgr CRYPTOGRAPHIC VERIFICATION, Up: tlmgr
@@ -4706,52 +4707,52 @@
B.9 USER MODE
=============
-'tlmgr' provides a restricted way, called "user mode", to manage
+‘tlmgr’ provides a restricted way, called “user mode”, to manage
arbitrary texmf trees in the same way as the main installation. For
example, this allows people without write permissions on the
installation location to update/install packages into a tree of their
own.
- 'tlmgr' is switched into user mode with the command line option
-'--usermode'. It does not switch automatically, nor is there any
+ ‘tlmgr’ is switched into user mode with the command line option
+‘--usermode’. It does not switch automatically, nor is there any
configuration file setting for it. Thus, this option has to be
explicitly given every time user mode is to be activated.
- This mode of 'tlmgr' works on a user tree, by default the value of
-the 'TEXMFHOME' variable. This can be overridden with the command line
-option '--usertree'. In the following when we speak of the user tree we
-mean either 'TEXMFHOME' or the one given on the command line.
+ This mode of ‘tlmgr’ works on a user tree, by default the value of
+the ‘TEXMFHOME’ variable. This can be overridden with the command line
+option ‘--usertree’. In the following when we speak of the user tree we
+mean either ‘TEXMFHOME’ or the one given on the command line.
- Not all actions are allowed in user mode; 'tlmgr' will warn you and
+ Not all actions are allowed in user mode; ‘tlmgr’ will warn you and
not carry out any problematic actions. Currently not supported (and
-probably will never be) is the 'platform' action. The 'gui' action is
+probably will never be) is the ‘platform’ action. The ‘gui’ action is
currently not supported, but may be in a future release.
- Some 'tlmgr' actions don't need any write permissions and thus work
-the same in user mode and normal mode. Currently these are: 'check',
-'help', 'list', 'print-platform', 'print-platform-info', 'search',
-'show', 'version'.
+ Some ‘tlmgr’ actions don’t need any write permissions and thus work
+the same in user mode and normal mode. Currently these are: ‘check’,
+‘help’, ‘list’, ‘print-platform’, ‘print-platform-info’, ‘search’,
+‘show’, ‘version’.
On the other hand, most of the actions dealing with package
management do need write permissions, and thus behave differently in
-user mode, as described below: 'install', 'update', 'remove', 'option',
-'paper', 'generate', 'backup', 'restore', 'uninstall', 'symlinks'.
+user mode, as described below: ‘install’, ‘update’, ‘remove’, ‘option’,
+‘paper’, ‘generate’, ‘backup’, ‘restore’, ‘uninstall’, ‘symlinks’.
- Before using 'tlmgr' in user mode, you have to set up the user tree
-with the 'init-usertree' action. This creates _usertree_'/web2c' and
-_usertree_'/tlpkg/tlpobj', and a minimal
-_usertree_'/tlpkg/texlive.tlpdb'. At that point, you can tell 'tlmgr'
-to do the (supported) actions by adding the '--usermode' command line
+ Before using ‘tlmgr’ in user mode, you have to set up the user tree
+with the ‘init-usertree’ action. This creates _usertree_‘/web2c’ and
+_usertree_‘/tlpkg/tlpobj’, and a minimal
+_usertree_‘/tlpkg/texlive.tlpdb’. At that point, you can tell ‘tlmgr’
+to do the (supported) actions by adding the ‘--usermode’ command line
option.
- In user mode the file _usertree_'/tlpkg/texlive.tlpdb' contains only
-the packages that have been installed into the user tree using 'tlmgr',
-plus additional options from the "virtual" package
-'00texlive.installation' (similar to the main installation's
-'texlive.tlpdb').
+ In user mode the file _usertree_‘/tlpkg/texlive.tlpdb’ contains only
+the packages that have been installed into the user tree using ‘tlmgr’,
+plus additional options from the “virtual” package
+‘00texlive.installation’ (similar to the main installation’s
+‘texlive.tlpdb’).
All actions on packages in user mode can only be carried out on
-packages that are known as 'relocatable'. This excludes all packages
+packages that are known as ‘relocatable’. This excludes all packages
containing executables and a few other core packages. Of the 2500 or so
packages currently in TeX Live the vast majority are relocatable and can
be installed into a user tree.
@@ -4765,31 +4766,31 @@
* tlmgr User mode generate, option, paper::
-File: tlbuild.info, Node: tlmgr User mode install, Next: tlmgr User mode backup, restore, remove, update, Up: tlmgr USER MODE
+File: tlbuild.info, Node: tlmgr User mode install, Next: tlmgr User mode backup, restore, remove, update, Up: tlmgr USER MODE
B.9.1 User mode install
-----------------------
-In user mode, the 'install' action checks that the package and all
+In user mode, the ‘install’ action checks that the package and all
dependencies are all either relocated or already installed in the system
installation. If this is the case, it unpacks all containers to be
-installed into the user tree (to repeat, that's either 'TEXMFHOME' or
-the value of '--usertree') and add the respective packages to the user
-tree's 'texlive.tlpdb' (creating it if need be).
+installed into the user tree (to repeat, that’s either ‘TEXMFHOME’ or
+the value of ‘--usertree’) and add the respective packages to the user
+tree’s ‘texlive.tlpdb’ (creating it if need be).
Currently installing a collection in user mode installs all dependent
packages, but in contrast to normal mode, does _not_ install dependent
-collections. For example, in normal mode 'tlmgr install
-collection-context' would install 'collection-basic' and other
+collections. For example, in normal mode ‘tlmgr install
+collection-context’ would install ‘collection-basic’ and other
collections, while in user mode, _only_ the packages mentioned in
-'collection-context' are installed.
+‘collection-context’ are installed.
If a package shipping map files is installed in user mode, a backup
-of the user's 'updmap.cfg' in 'USERTREE/web2c/' is made, and then this
+of the user’s ‘updmap.cfg’ in ‘USERTREE/web2c/’ is made, and then this
file regenerated from the list of installed packages.
-File: tlbuild.info, Node: tlmgr User mode backup, restore, remove, update, Next: tlmgr User mode generate, option, paper, Prev: tlmgr User mode install, Up: tlmgr USER MODE
+File: tlbuild.info, Node: tlmgr User mode backup, restore, remove, update, Next: tlmgr User mode generate, option, paper, Prev: tlmgr User mode install, Up: tlmgr USER MODE
B.9.2 User mode backup, restore, remove, update
-----------------------------------------------
@@ -4799,13 +4800,13 @@
just as in normal mode.
-File: tlbuild.info, Node: tlmgr User mode generate, option, paper, Prev: tlmgr User mode backup, restore, remove, update, Up: tlmgr USER MODE
+File: tlbuild.info, Node: tlmgr User mode generate, option, paper, Prev: tlmgr User mode backup, restore, remove, update, Up: tlmgr USER MODE
B.9.3 User mode generate, option, paper
---------------------------------------
-In user mode, these actions operate only on the user tree's
-configuration files and/or 'texlive.tlpdb'.
+In user mode, these actions operate only on the user tree’s
+configuration files and/or ‘texlive.tlpdb’.
File: tlbuild.info, Node: tlmgr MULTIPLE REPOSITORIES, Next: tlmgr GUI FOR TLMGR, Prev: tlmgr USER MODE, Up: tlmgr
@@ -4820,13 +4821,13 @@
or should not be included in TeX Live, for whatever reason.
The simplest and most reliable method is to temporarily set the
-installation source to any repository (with the '-repository' or 'option
-repository' command line options), and perform your operations.
+installation source to any repository (with the ‘-repository’ or ‘option
+repository’ command line options), and perform your operations.
When you are using multiple repositories over a sustained length of
time, however, explicitly switching between them becomes inconvenient.
-Thus, it's possible to tell 'tlmgr' about additional repositories you
-want to use. The basic command is 'tlmgr repository add'. The rest of
+Thus, it’s possible to tell ‘tlmgr’ about additional repositories you
+want to use. The basic command is ‘tlmgr repository add’. The rest of
this section explains further.
When using multiple repositories, one of them has to be set as the
@@ -4839,7 +4840,7 @@
are _still_ _only_ installed from the main repository. Thus, simply
adding a second repository does not actually enable installation of
anything from there. You also have to specify which packages should be
-taken from the new repository, by specifying so-called "pinning" rules,
+taken from the new repository, by specifying so-called “pinning” rules,
described next.
* Menu:
@@ -4852,12 +4853,12 @@
B.10.1 Pinning
--------------
-When a package 'foo' is pinned to a repository, a package 'foo' in any
+When a package ‘foo’ is pinned to a repository, a package ‘foo’ in any
other repository, even if it has a higher revision number, will not be
considered an installable candidate.
As mentioned above, by default everything is pinned to the main
-repository. Let's now go through an example of setting up a second
+repository. Let’s now go through an example of setting up a second
repository and enabling updates of a package from it.
First, check that we have support for multiple repositories, and have
@@ -4867,8 +4868,8 @@
List of repositories (with tags if set):
/var/www/norbert/tlnet
- Ok. Let's add the 'tlcontrib' repository (this is a real repository
-hosted at <http://contrib.texlive.info>) with the tag 'tlcontrib':
+ Ok. Let’s add the ‘tlcontrib’ repository (this is a real repository
+hosted at <http://contrib.texlive.info>) with the tag ‘tlcontrib’:
$ tlmgr repository add http://contrib.texlive.info/current tlcontrib
@@ -4879,12 +4880,12 @@
http://contrib.texlive.info/current (tlcontrib)
/var/www/norbert/tlnet (main)
- Now we specify a pinning entry to get the package 'classico' from
-'tlcontrib':
+ Now we specify a pinning entry to get the package ‘classico’ from
+‘tlcontrib’:
$ tlmgr pinning add tlcontrib classico
- Check that we can find 'classico':
+ Check that we can find ‘classico’:
$ tlmgr show classico
package: classico
@@ -4892,7 +4893,7 @@
shortdesc: URW Classico fonts
...
- - install 'classico':
+ - install ‘classico’:
$ tlmgr install classico
tlmgr: package repositories:
@@ -4899,16 +4900,16 @@
...
[1/1, ??:??/??:??] install: classico @tlcontrib [737k]
- In the output here you can see that the 'classico' package has been
-installed from the 'tlcontrib' repository ('@tlcontrib').
+ In the output here you can see that the ‘classico’ package has been
+installed from the ‘tlcontrib’ repository (‘@tlcontrib’).
- Finally, 'tlmgr pinning' also supports removing certain or all
+ Finally, ‘tlmgr pinning’ also supports removing certain or all
packages from a given repository:
$ tlmgr pinning remove tlcontrib classico # remove just classico
$ tlmgr pinning remove tlcontrib --all # take nothing from tlcontrib
- A summary of 'tlmgr pinning' actions is given above.
+ A summary of ‘tlmgr pinning’ actions is given above.
File: tlbuild.info, Node: tlmgr GUI FOR TLMGR, Next: tlmgr MACHINE-READABLE OUTPUT, Prev: tlmgr MULTIPLE REPOSITORIES, Up: tlmgr
@@ -4916,12 +4917,12 @@
B.11 GUI FOR TLMGR
==================
-The graphical user interface for 'tlmgr' requires Perl/Tk
+The graphical user interface for ‘tlmgr’ requires Perl/Tk
<https://search.cpan.org/search?query=perl%2Ftk>. For Unix-based
systems Perl/Tk (as well as Perl of course) has to be installed outside
of TL. <https://tug.org/texlive/distro.html#perltk> has a list of
invocations for some distros. For Windows the necessary modules are no
-longer shipped within TeX Live, so you'll have to have an external Perl
+longer shipped within TeX Live, so you’ll have to have an external Perl
available that includes them.
We are talking here about the GUI built into tlmgr itself, not about
@@ -4929,17 +4930,17 @@
(Java-based) and, only on Macs, TeX Live Utility. These are invoked as
separate programs.
- The GUI mode of tlmgr is started with the invocation 'tlmgr gui';
+ The GUI mode of tlmgr is started with the invocation ‘tlmgr gui’;
assuming Tk is loadable, the graphical user interface will be shown.
The main window contains a menu bar, the main display, and a status area
where messages normally shown on the console are displayed.
- Within the main display there are three main parts: the 'Display
-configuration' area, the list of packages, and the action buttons.
+ Within the main display there are three main parts: the ‘Display
+configuration’ area, the list of packages, and the action buttons.
Also, at the top right the currently loaded repository is shown; this
also acts as a button and when clicked will try to load the default
-repository. To load a different repository, see the 'tlmgr' menu item.
+repository. To load a different repository, see the ‘tlmgr’ menu item.
Finally, the status area at the bottom of the window gives additional
information about what is going on.
@@ -4993,7 +4994,7 @@
Selection
Select packages to those selected, those not selected, or all.
- Here, "selected" means that the checkbox in the beginning of the
+ Here, “selected” means that the checkbox in the beginning of the
line of a package is ticked.
Display configuration buttons
@@ -5055,7 +5056,7 @@
Update all installed
- This calls 'tlmgr update --all', i.e., tries to update all
+ This calls ‘tlmgr update --all’, i.e., tries to update all
available packages. Below this button is a toggle to allow
reinstallation of previously removed packages as part of this
action.
@@ -5070,20 +5071,20 @@
Install
- Install the selected packages; acts like 'tlmgr install', i.e.,
+ Install the selected packages; acts like ‘tlmgr install’, i.e.,
also installs dependencies. Thus, installing a collection installs
all its constituent packages.
Remove
- Removes the selected packages; acts like 'tlmgr remove', i.e., it
+ Removes the selected packages; acts like ‘tlmgr remove’, i.e., it
will also remove dependencies of collections (but not dependencies
of normal packages).
Backup
- Makes a backup of the selected packages; acts like 'tlmgr backup'.
- This action needs the option 'backupdir' set (see 'Options -'
+ Makes a backup of the selected packages; acts like ‘tlmgr backup’.
+ This action needs the option ‘backupdir’ set (see ‘Options -’
General>).
@@ -5094,41 +5095,41 @@
The following entries can be found in the menu bar:
-'tlmgr' menu
+‘tlmgr’ menu
The items here load various repositories: the default as specified
in the TeX Live database, the default network repository, the
repository specified on the command line (if any), and an
- arbitrarily manually-entered one. Also has the so-necessary 'quit'
+ arbitrarily manually-entered one. Also has the so-necessary ‘quit’
operation.
-'Options menu'
+‘Options menu’
- Provides access to several groups of options: 'Paper'
- (configuration of default paper sizes), 'Platforms' (only on Unix,
- configuration of the supported/installed platforms), 'GUI Language'
- (select language used in the GUI interface), and 'General'
+ Provides access to several groups of options: ‘Paper’
+ (configuration of default paper sizes), ‘Platforms’ (only on Unix,
+ configuration of the supported/installed platforms), ‘GUI Language’
+ (select language used in the GUI interface), and ‘General’
(everything else).
- Several toggles are also here. The first is 'Expert options',
+ Several toggles are also here. The first is ‘Expert options’,
which is set by default. If you turn this off, the next time you
start the GUI a simplified screen will be shown that display only
the most important functionality. This setting is saved in the
- configuration file of 'tlmgr'; see *note CONFIGURATION FILE FOR
+ configuration file of ‘tlmgr’; see *note CONFIGURATION FILE FOR
TLMGR: tlmgr CONFIGURATION FILE FOR TLMGR. for details.
The other toggles are all off by default: for debugging output, to
disable the automatic installation of new packages, and to disable
the automatic removal of packages deleted from the server. Playing
- with the choices of what is or isn't installed may lead to an
+ with the choices of what is or isn’t installed may lead to an
inconsistent TeX Live installation; e.g., when a package is
renamed.
-'Actions menu'
+‘Actions menu’
Provides access to several actions: update the filename database
- (aka 'ls-R', 'mktexlsr', 'texhash'), rebuild all formats
- ('fmtutil-sys --all'), update the font map database ('updmap-sys'),
+ (aka ‘ls-R’, ‘mktexlsr’, ‘texhash’), rebuild all formats
+ (‘fmtutil-sys --all’), update the font map database (‘updmap-sys’),
restore from a backup of a package, and use of symbolic links in
system directories (not on Windows).
@@ -5135,10 +5136,10 @@
The final action is to remove the entire TeX Live installation
(also not on Windows).
-'Help menu'
+‘Help menu’
Provides access to the TeX Live manual (also on the web at
- <https://tug.org/texlive/doc.html>) and the usual "About" box.
+ <https://tug.org/texlive/doc.html>) and the usual “About” box.
File: tlbuild.info, Node: tlmgr GUI options, Prev: tlmgr Menu bar, Up: tlmgr GUI FOR TLMGR
@@ -5146,29 +5147,29 @@
B.11.3 GUI options
------------------
-Some generic Perl/Tk options can be specified with 'tlmgr gui' to
+Some generic Perl/Tk options can be specified with ‘tlmgr gui’ to
control the display:
-'-background' _color_
+‘-background’ _color_
Set background color.
-'-font "' _fontname_ _fontsize_ '"'
+‘-font "’ _fontname_ _fontsize_ ‘"’
- Set font, e.g., 'tlmgr gui -font "helvetica 18"'. The argument to
- '-font' must be quoted, i.e., passed as a single string.
+ Set font, e.g., ‘tlmgr gui -font "helvetica 18"’. The argument to
+ ‘-font’ must be quoted, i.e., passed as a single string.
-'-foreground' _color_
+‘-foreground’ _color_
Set foreground color.
-'-geometry' _geomspec_
+‘-geometry’ _geomspec_
- Set the X geometry, e.g., 'tlmgr gui -geometry 1024x512-0+0'
+ Set the X geometry, e.g., ‘tlmgr gui -geometry 1024x512-0+0’
creates the window of (approximately) the given size in the
upper-right corner of the display.
-'-xrm' _xresource_
+‘-xrm’ _xresource_
Pass the arbitrary X resource string _xresource_.
@@ -5182,25 +5183,25 @@
B.12 MACHINE-READABLE OUTPUT
============================
-With the '--machine-readable' option, 'tlmgr' writes to stdout in the
+With the ‘--machine-readable’ option, ‘tlmgr’ writes to stdout in the
fixed line-oriented format described here, and the usual informational
messages for human consumption are written to stderr (normally they are
written to stdout). The idea is that a program can get all the
information it needs by reading stdout.
- Currently this option only applies to the *note update: tlmgr update
-[_option_...] [_pkg_...], *note install: tlmgr install [_option_...]
-_pkg_..., and *note option: tlmgr option. actions.
+ Currently this option only applies to the *note update: tlmgr update
+[_option_...] [_pkg_...], *note install: tlmgr install [_option_...]
+_pkg_..., and *note option: tlmgr option. actions.
* Menu:
-* tlmgr Machine-readable 'update' and 'install' output::
-* tlmgr Machine-readable 'option' output::
+* tlmgr Machine-readable update and install output::
+* tlmgr Machine-readable option output::
-File: tlbuild.info, Node: tlmgr Machine-readable 'update' and 'install' output, Next: tlmgr Machine-readable 'option' output, Up: tlmgr MACHINE-READABLE OUTPUT
+File: tlbuild.info, Node: tlmgr Machine-readable update and install output, Next: tlmgr Machine-readable option output, Up: tlmgr MACHINE-READABLE OUTPUT
-B.12.1 Machine-readable 'update' and 'install' output
+B.12.1 Machine-readable ‘update’ and ‘install’ output
-----------------------------------------------------
The output format is as follows:
@@ -5213,8 +5214,8 @@
"end-of-updates"
other output from post actions, not in machine readable form
- The header section currently has two fields: 'location-url' (the
-repository source from which updates are being drawn), and 'total-bytes'
+ The header section currently has two fields: ‘location-url’ (the
+repository source from which updates are being drawn), and ‘total-bytes’
(the total number of bytes to be downloaded).
The _localrev_ and _serverrev_ fields for each package are the
@@ -5228,21 +5229,21 @@
Line endings may be either LF or CRLF depending on the current
platform.
-'location-url' _location_
+‘location-url’ _location_
- The _location_ may be a url (including 'file:///foo/bar/...'), or a
- directory name ('/foo/bar'). It is the package repository from
+ The _location_ may be a url (including ‘file:///foo/bar/...’), or a
+ directory name (‘/foo/bar’). It is the package repository from
which the new package information was drawn.
-'total-bytes' _count_
+‘total-bytes’ _count_
The _count_ is simply a decimal number, the sum of the sizes of all
the packages that need updating or installing (which are listed
subsequently).
- Then comes a line with only the literal string 'end-of-header'.
+ Then comes a line with only the literal string ‘end-of-header’.
- Each following line until a line with literal string 'end-of-updates'
+ Each following line until a line with literal string ‘end-of-updates’
reports on one package. The fields on each line are separated by a tab.
Here are the fields.
@@ -5249,7 +5250,7 @@
_pkgname_
The TeX Live package identifier, with a possible platform suffix
- for executables. For instance, 'pdftex' and 'pdftex.i386-linux'
+ for executables. For instance, ‘pdftex’ and ‘pdftex.i386-linux’
are given as two separate packages, one on each line.
_status_
@@ -5256,37 +5257,37 @@
The status of the package update. One character, as follows:
- 'd'
+ ‘d’
The package was removed on the server.
- 'f'
+ ‘f’
The package was removed in the local installation, even though
- a collection depended on it. (E.g., the user ran 'tlmgr
- remove --force'.)
+ a collection depended on it. (E.g., the user ran ‘tlmgr
+ remove --force’.)
- 'u'
+ ‘u’
Normal update is needed.
- 'r'
+ ‘r’
Reversed non-update: the locally-installed version is newer
than the version on the server.
- 'a'
+ ‘a’
Automatically-determined need for installation, the package is
new on the server and is (most probably) part of an installed
collection.
- 'i'
+ ‘i’
- Package will be installed and isn't present in the local
+ Package will be installed and isn’t present in the local
installation (action install).
- 'I'
+ ‘I’
Package is already present but will be reinstalled (action
install).
@@ -5293,18 +5294,18 @@
_localrev_
- The revision number of the installed package, or '-' if it is not
+ The revision number of the installed package, or ‘-’ if it is not
present locally.
_serverrev_
- The revision number of the package on the server, or '-' if it is
+ The revision number of the package on the server, or ‘-’ if it is
not present on the server.
_size_
The size in bytes of the package on the server. The sum of all the
- package sizes is given in the 'total-bytes' header field mentioned
+ package sizes is given in the ‘total-bytes’ header field mentioned
above.
_runtime_
@@ -5316,9 +5317,9 @@
The estimated total time.
-File: tlbuild.info, Node: tlmgr Machine-readable 'option' output, Prev: tlmgr Machine-readable 'update' and 'install' output, Up: tlmgr MACHINE-READABLE OUTPUT
+File: tlbuild.info, Node: tlmgr Machine-readable option output, Prev: tlmgr Machine-readable update and install output, Up: tlmgr MACHINE-READABLE OUTPUT
-B.12.2 Machine-readable 'option' output
+B.12.2 Machine-readable ‘option’ output
---------------------------------------
The output format is as follows:
@@ -5325,7 +5326,7 @@
key "\t" value
- If a value is not saved in the database the string '(not set)' is
+ If a value is not saved in the database the string ‘(not set)’ is
shown.
If you are developing a program that uses this output, and find that
@@ -5337,22 +5338,22 @@
B.13 ENVIRONMENT VARIABLES
==========================
-'tlmgr' uses many of the standard TeX environment variables, as reported
-by, e.g., 'tlmgr conf' (*note conf: tlmgr conf.).
+‘tlmgr’ uses many of the standard TeX environment variables, as reported
+by, e.g., ‘tlmgr conf’ (*note conf: tlmgr conf.).
- In addition, for ease in scripting and debugging, 'tlmgr' looks for
+ In addition, for ease in scripting and debugging, ‘tlmgr’ looks for
the following environment variables. These are not of interest for
normal user installations.
-'TEXLIVE_COMPRESSOR'
+‘TEXLIVE_COMPRESSOR’
This variable allows selecting a different compressor program for
backups and intermediate rollback containers. The order of
selection is:
- 1. If the environment variable 'TEXLIVE_COMPRESSOR' is defined,
- use it; abort if it doesn't work. Possible values: 'lz4',
- 'gzip', 'xz'. The necessary options are added internally.
+ 1. If the environment variable ‘TEXLIVE_COMPRESSOR’ is defined,
+ use it; abort if it doesn’t work. Possible values: ‘lz4’,
+ ‘gzip’, ‘xz’. The necessary options are added internally.
2. If lz4 is available (either from the system or TL) and
working, use that.
@@ -5362,28 +5363,28 @@
4. If xz is available (either from the system or TL) and working,
use that.
- lz4 and gzip are faster in creating tlmgr's local backups, hence
+ lz4 and gzip are faster in creating tlmgr’s local backups, hence
they are preferred. The unconditional use of xz for the tlnet
containers is unaffected, to minimize download sizes.
-'TEXLIVE_DOWNLOADER'
+‘TEXLIVE_DOWNLOADER’
-'TL_DOWNLOAD_PROGRAM'
+‘TL_DOWNLOAD_PROGRAM’
-'TL_DOWNLOAD_ARGS'
+‘TL_DOWNLOAD_ARGS’
These options allow selecting different download programs then the
ones automatically selected by the installer. The order of
selection is:
- 1. If the environment variable 'TEXLIVE_DOWNLOADER' is defined,
- use it; abort if the specified program doesn't work. Possible
- values: 'lwp', 'curl', 'wget'. The necessary options are
+ 1. If the environment variable ‘TEXLIVE_DOWNLOADER’ is defined,
+ use it; abort if the specified program doesn’t work. Possible
+ values: ‘lwp’, ‘curl’, ‘wget’. The necessary options are
added internally.
- 2. If the environment variable 'TL_DOWNLOAD_PROGRAM' is defined
- (can be any value), use it together with 'TL_DOWNLOAD_ARGS';
- abort if it doesn't work.
+ 2. If the environment variable ‘TL_DOWNLOAD_PROGRAM’ is defined
+ (can be any value), use it together with ‘TL_DOWNLOAD_ARGS’;
+ abort if it doesn’t work.
3. If LWP is available and working, use that (by far the most
efficient method, as it supports persistent downloads).
@@ -5393,27 +5394,27 @@
5. If wget is available (either from the system or TL) and
working, use that.
- TL provides 'wget' binaries for platforms where necessary, so some
+ TL provides ‘wget’ binaries for platforms where necessary, so some
download method should always be available.
-'TEXLIVE_PREFER_OWN'
+‘TEXLIVE_PREFER_OWN’
By default, compression and download programs provided by the
- system, i.e., found along 'PATH' are preferred over those shipped
+ system, i.e., found along ‘PATH’ are preferred over those shipped
with TeX Live.
This can create problems with systems that are too old, and so can
be overridden by setting the environment variable
- 'TEXLIVE_PREFER_OWN' to 1. In this case, executables shipped with
+ ‘TEXLIVE_PREFER_OWN’ to 1. In this case, executables shipped with
TL will be preferred.
Extra compression/download programs not provided by TL, such as
gzip, lwp, and curl, are still checked for on the system and used
- if available, per the above. 'TEXLIVE_PREFER_OWN' only applies
+ if available, per the above. ‘TEXLIVE_PREFER_OWN’ only applies
when the program being checked for is shipped with TL, namely the
lz4 and xz compressors and wget downloader.
- Exception: on Windows, the 'tar.exe' shipped with TL is always
+ Exception: on Windows, the ‘tar.exe’ shipped with TL is always
used, regardless of any setting.
@@ -5437,116 +5438,114 @@
[index ]
* Menu:
-* '$@' target in normal 'make' rules: Prerequisites. (line 13)
-* --bindir configure option: '--prefix' '--bindir' ....
+* $@ target in normal make rules: Prerequisites. (line 13)
+* --bindir configure option: --prefix --bindir ....
(line 6)
-* --bindir configure option <1>: '--enable-multiplatform'.
+* --bindir configure option <1>: --enable-multiplatform.
(line 6)
* --build=HOST: Cross configuring. (line 6)
* --disable-all-packages: Build one package. (line 6)
-* --disable-all-pkgs: '--disable-all-pkgs'.
- (line 6)
-* --disable-bibtex8: Configure options for 'texk/bibtex-x'.
+* --disable-all-pkgs: --disable-all-pkgs. (line 6)
+* --disable-bibtex8: Configure options for texk/bibtex-x.
(line 9)
-* --disable-bibtexu: Configure options for 'texk/bibtex-x'.
+* --disable-bibtexu: Configure options for texk/bibtex-x.
(line 12)
-* --disable-dump-share: Configure options for 'texk/web2c'.
+* --disable-dump-share: Configure options for texk/web2c.
(line 27)
-* --disable-dvipdfmx: Configure options for 'texk/dvipdfm-x'.
+* --disable-dvipdfmx: Configure options for texk/dvipdfm-x.
(line 12)
-* --disable-etex-synctex: Configure options for 'texk/web2c'.
+* --disable-etex-synctex: Configure options for texk/web2c.
(line 59)
-* --disable-ipc: Configure options for 'texk/web2c'.
+* --disable-ipc: Configure options for texk/web2c.
(line 31)
-* --disable-largefile: '--disable-largefile'.
+* --disable-largefile: --disable-largefile. (line 6)
+* --disable-linked-scripts: Configure options for texk/texlive.
(line 6)
-* --disable-linked-scripts: Configure options for 'texk/texlive'.
- (line 6)
-* --disable-mf-nowin: Configure options for 'texk/web2c'.
+* --disable-mf-nowin: Configure options for texk/web2c.
(line 34)
-* --disable-missing: '--disable-missing'. (line 6)
-* --disable-native-texlive-build: '--disable-native-texlive-build'.
+* --disable-missing: --disable-missing. (line 6)
+* --disable-native-texlive-build: --disable-native-texlive-build.
(line 6)
-* --disable-PROG: '--enable-PROG' '--disable-PROG'.
+* --disable-PROG: --enable-PROG --disable-PROG.
(line 6)
-* --disable-synctex: Configure options for 'texk/web2c'.
+* --disable-synctex: Configure options for texk/web2c.
(line 64)
-* --disable-tex: Configure options for 'texk/web2c'.
+* --disable-tex: Configure options for texk/web2c.
(line 37)
-* --disable-web-progs: Configure options for 'texk/web2c'.
+* --disable-web-progs: Configure options for texk/web2c.
(line 41)
-* --disable-xdvipdfmx: Configure options for 'texk/dvipdfm-x'.
+* --disable-xdvipdfmx: Configure options for texk/dvipdfm-x.
(line 15)
-* --enable-*win for Metafont window support: Configure options for 'texk/web2c'.
+* --enable-*win for Metafont window support: Configure options for texk/web2c.
(line 55)
-* --enable-auto-core: Configure options for 'texk/web2c'.
+* --enable-auto-core: Configure options for texk/web2c.
(line 45)
-* --enable-compiler-warnings=LEVEL: '--enable-compiler-warnings='LEVEL.
+* --enable-compiler-warnings=LEVEL: --enable-compiler-warnings=LEVEL.
(line 6)
* --enable-cxx-runtime-hack: Macros for compilers.
(line 29)
-* --enable-etex: Configure options for 'texk/web2c'.
+* --enable-etex: Configure options for texk/web2c.
(line 37)
-* --enable-libtool-hack: Configure options for 'texk/web2c'.
+* --enable-libtool-hack: Configure options for texk/web2c.
(line 50)
* --enable-maintainer-mode: Build system tools. (line 28)
-* --enable-maintainer-mode <1>: '--enable-maintainer-mode'.
+* --enable-maintainer-mode <1>: --enable-maintainer-mode.
(line 6)
* --enable-missing to ignore dependencies: Build one package. (line 94)
-* --enable-mktextfm-default: 'kpathsea' library. (line 18)
-* --enable-multiplatform: '--enable-multiplatform'.
+* --enable-mktextfm-default: kpathsea library. (line 18)
+* --enable-multiplatform: --enable-multiplatform.
(line 6)
-* --enable-PROG: '--enable-PROG' '--disable-PROG'.
+* --enable-PROG: --enable-PROG --disable-PROG.
(line 6)
-* --enable-shared: '--enable-shared'. (line 6)
-* --enable-silent-rules: '--enable-silent-rules'.
+* --enable-shared: --enable-shared. (line 6)
+* --enable-silent-rules: --enable-silent-rules.
(line 6)
-* --enable-tex-synctex: Configure options for 'texk/web2c'.
+* --enable-tex-synctex: Configure options for texk/web2c.
(line 59)
-* --enable-texlive-build: '--disable-native-texlive-build'.
+* --enable-texlive-build: --disable-native-texlive-build.
(line 15)
-* --enable-xi2-scrolling: Configure options for 'texk/xdvik'.
+* --enable-xi2-scrolling: Configure options for texk/xdvik.
(line 13)
-* --enable-xindy-docs: Configure options for 'utils/xindy'.
+* --enable-xindy-docs: Configure options for utils/xindy.
(line 10)
-* --enable-xindy-rules: Configure options for 'utils/xindy'.
+* --enable-xindy-rules: Configure options for utils/xindy.
(line 6)
* --host=HOST: Cross configuring. (line 6)
-* --libdir configure option: '--enable-multiplatform'.
+* --libdir configure option: --enable-multiplatform.
(line 6)
* --no-print-directory GNU make option: Build one engine. (line 56)
-* --prefix configure option: '--prefix' '--bindir' ....
+* --prefix configure option: --prefix --bindir ....
(line 6)
-* --with-banner-add=STR: Configure options for 'texk/web2c'.
+* --with-banner-add=STR: Configure options for texk/web2c.
(line 6)
-* --with-clisp-runtime=FILENAME: Configure options for 'utils/xindy'.
+* --with-clisp-runtime=FILENAME: Configure options for utils/xindy.
(line 14)
-* --with-editor=CMD: Configure options for 'texk/web2c'.
+* --with-editor=CMD: Configure options for texk/web2c.
(line 11)
-* --with-fontconfig-includes=DIR: Configure options for 'texk/web2c'.
+* --with-fontconfig-includes=DIR: Configure options for texk/web2c.
(line 16)
-* --with-fontconfig-libdir=DIR: Configure options for 'texk/web2c'.
+* --with-fontconfig-libdir=DIR: Configure options for texk/web2c.
(line 16)
-* --with-gs=FILENAME: Configure options for 'texk/xdvik'.
+* --with-gs=FILENAME: Configure options for texk/xdvik.
(line 6)
* --with-LIB-includes=DIR, -libdir: Library-specific configure options.
(line 16)
-* --with-libgs-includes, -libdir: Configure options for 'texk/dvisvgm'.
+* --with-libgs-includes, -libdir: Configure options for texk/dvisvgm.
(line 17)
-* --with-system-kpathsea: 'kpathsea' library. (line 13)
+* --with-system-kpathsea: kpathsea library. (line 13)
* --with-system-LIB: Adding a new generic library module.
(line 34)
* --with-system-LIB <1>: Library-specific configure options.
(line 9)
-* --with-system-libgs: Configure options for 'texk/dvisvgm'.
+* --with-system-libgs: Configure options for texk/dvisvgm.
(line 6)
-* --with-xdvi-x-toolkit: 'xdvik' package. (line 21)
-* --with-xdvi-x-toolkit=KIT: Configure options for 'texk/xdvik'.
+* --with-xdvi-x-toolkit: xdvik package. (line 21)
+* --with-xdvi-x-toolkit=KIT: Configure options for texk/xdvik.
(line 9)
-* --without-libgs: Configure options for 'texk/dvisvgm'.
+* --without-libgs: Configure options for texk/dvisvgm.
(line 12)
-* --without-ln-s: '--without-ln-s'. (line 6)
-* --without-x: '--without-x'. (line 6)
+* --without-ln-s: --without-ln-s. (line 6)
+* --without-x: --without-x. (line 6)
* -C configure option: Build in parallel. (line 11)
* -j make option: Build in parallel. (line 6)
* ac/withenable.ac: Adding a new program module.
@@ -5560,14 +5559,14 @@
* adding a new TeX-specific library: Adding a new TeX-specific library module.
(line 6)
* adding to TeX Live: Extending TeX Live. (line 6)
-* 'am/' top-level directory: Top-level directories.
+* am/ top-level directory: Top-level directories.
(line 14)
* ANSI C: Declarations and definitions.
(line 6)
-* 'ApplicationServices' Mac framework, required by 'xetex': Prerequisites.
+* ApplicationServices Mac framework, required by xetex: Prerequisites.
(line 40)
* asymptote: Linked scripts. (line 23)
-* asymptote <1>: 'asymptote'. (line 6)
+* asymptote <1>: asymptote. (line 6)
* Autoconf: Overview of build system.
(line 6)
* autoconf macros: Autoconf macros. (line 6)
@@ -5576,11 +5575,11 @@
* autoreconf, for new program: Adding a new program module.
(line 76)
* biber: Linked scripts. (line 23)
-* bibtex-x: Configure options for 'texk/bibtex-x'.
+* bibtex-x: Configure options for texk/bibtex-x.
(line 6)
-* bibtex8: Configure options for 'texk/bibtex-x'.
+* bibtex8: Configure options for texk/bibtex-x.
(line 6)
-* bibtexu: Configure options for 'texk/bibtex-x'.
+* bibtexu: Configure options for texk/bibtex-x.
(line 6)
* BSD distro: Distro builds. (line 6)
* build directory, required: Building. (line 17)
@@ -5591,7 +5590,7 @@
* Build script: Building. (line 6)
* build system, design of: Overview of build system.
(line 6)
-* 'build-aux/' top-level directory: Top-level directories.
+* build-aux/ top-level directory: Top-level directories.
(line 30)
* BUILDCC, BUILDCFLAGS, ...: Cross configuring. (line 42)
* building: Building. (line 6)
@@ -5603,8 +5602,8 @@
(line 6)
* C99, avoided: Declarations and definitions.
(line 6)
-* cache file, for 'configure': Build in parallel. (line 11)
-* cache for 'configure': Build in parallel. (line 6)
+* cache file, for configure: Build in parallel. (line 11)
+* cache for configure: Build in parallel. (line 6)
* callexe.c: Macros for Windows. (line 32)
* CC: Variables for configure.
(line 10)
@@ -5618,45 +5617,45 @@
(line 18)
* CLISP: Variables for configure.
(line 17)
-* CLISP <1>: Configure options for 'utils/xindy'.
+* CLISP <1>: Configure options for utils/xindy.
(line 14)
-* 'clisp', required by 'xindy': Prerequisites. (line 44)
-* 'Cocoa' Mac framework, required by 'xetex': Prerequisites. (line 40)
+* clisp, required by xindy: Prerequisites. (line 44)
+* Cocoa Mac framework, required by xetex: Prerequisites. (line 40)
* coding conventions: Coding conventions. (line 6)
* compilers, C and C++11: Prerequisites. (line 6)
* config.guess, config.sub, ...: Top-level directories.
(line 30)
-* 'configure' options: Configure options. (line 6)
-* 'configure' options, for 'bibtex-x': Configure options for 'texk/bibtex-x'.
+* configure options: Configure options. (line 6)
+* configure options, for bibtex-x: Configure options for texk/bibtex-x.
(line 6)
-* 'configure' options, for 'dvipdfm-x': Configure options for 'texk/dvipdfm-x'.
+* configure options, for dvipdfm-x: Configure options for texk/dvipdfm-x.
(line 6)
-* 'configure' options, for 'dvisvgm': Configure options for 'texk/dvisvgm'.
+* configure options, for dvisvgm: Configure options for texk/dvisvgm.
(line 6)
-* 'configure' options, for 'kpathsea': Configure options for 'kpathsea'.
+* configure options, for kpathsea: Configure options for kpathsea.
(line 6)
-* 'configure' options, for 'texk/texlive': Configure options for 'texk/texlive'.
+* configure options, for texk/texlive: Configure options for texk/texlive.
(line 6)
-* 'configure' options, for 'web2c': Configure options for 'texk/web2c'.
+* configure options, for web2c: Configure options for texk/web2c.
(line 6)
-* 'configure' options, for 'xdvik': Configure options for 'texk/xdvik'.
+* configure options, for xdvik: Configure options for texk/xdvik.
(line 6)
-* 'configure' options, for 'xindy': Configure options for 'utils/xindy'.
+* configure options, for xindy: Configure options for utils/xindy.
(line 6)
-* 'configure' options, global: Global configure options.
+* configure options, global: Global configure options.
(line 6)
-* 'configure' options, library-specific: Library-specific configure options.
+* configure options, library-specific: Library-specific configure options.
(line 6)
-* 'configure' options, program-specific: Program-specific configure options.
+* configure options, program-specific: Program-specific configure options.
(line 6)
-* 'configure' problems, work around by removing: Build one package.
+* configure problems, work around by removing: Build one package.
(line 106)
-* 'configure' variables: Variables for configure.
+* configure variables: Variables for configure.
(line 6)
* configure.ac: Adding a new program module.
(line 45)
* configuring, for cross compilation: Cross configuring. (line 6)
-* 'const': Const. (line 6)
+* const: Const. (line 6)
* continuous integration: Continuous integration.
(line 6)
* conventions, coding: Coding conventions. (line 6)
@@ -5665,7 +5664,7 @@
* cross compilation: Cross compilation. (line 6)
* cross compilation configuring: Cross configuring. (line 6)
* cross compilation problems: Cross problems. (line 6)
-* cross compilation, with host binary: 'xdvik' package. (line 14)
+* cross compilation, with host binary: xdvik package. (line 14)
* ctangle: Cross problems. (line 26)
* CXX: Variables for configure.
(line 11)
@@ -5675,7 +5674,7 @@
* declarations before statements, avoiding: Declarations and definitions.
(line 6)
* dependencies, with several output files: Build in parallel. (line 6)
-* DESTDIR: '--prefix' '--bindir' ....
+* DESTDIR: --prefix --bindir ....
(line 9)
* directories, for installation: Installation directories.
(line 6)
@@ -5682,32 +5681,31 @@
* directories, top-level: Top-level directories.
(line 6)
* discards qualifiers warning: Const. (line 30)
-* 'dist' and 'distcheck' targets for 'make': Build distribution.
- (line 6)
+* dist and distcheck targets for make: Build distribution. (line 6)
* distribution tarball, making: Build distribution. (line 6)
* distro, building for: Distro builds. (line 6)
-* dvipdfm-x: Configure options for 'texk/dvipdfm-x'.
+* dvipdfm-x: Configure options for texk/dvipdfm-x.
(line 6)
-* dvipdfmx: Configure options for 'texk/dvipdfm-x'.
+* dvipdfmx: Configure options for texk/dvipdfm-x.
(line 6)
-* dvisvgm: Configure options for 'texk/dvisvgm'.
+* dvisvgm: Configure options for texk/dvisvgm.
(line 6)
-* 'dvisvgm', requires C++11: Prerequisites. (line 17)
+* dvisvgm, requires C++11: Prerequisites. (line 17)
* engine, adding new: Adding a new engine. (line 6)
* engine, building one: Build one engine. (line 6)
-* environment variables, for 'configure': Configure options. (line 16)
-* exec_prefix: '--enable-multiplatform'.
+* environment variables, for configure: Configure options. (line 16)
+* exec_prefix: --enable-multiplatform.
(line 6)
* extending TeX Live: Extending TeX Live. (line 6)
-* 'extern' functions: Declarations and definitions.
+* extern functions: Declarations and definitions.
(line 41)
* flags, macros for library and header: Macros for library and header flags.
(line 6)
-* 'fontconfig' library, required by 'xetex': Prerequisites. (line 40)
-* 'freetype' cross compiling: Cross problems. (line 13)
-* freetype library: 'freetype' library. (line 6)
-* FreeType, requires 'gmake': Prerequisites. (line 13)
-* freetype-config: 'freetype' library. (line 13)
+* fontconfig library, required by xetex: Prerequisites. (line 40)
+* freetype cross compiling: Cross problems. (line 13)
+* freetype library: freetype library. (line 6)
+* FreeType, requires gmake: Prerequisites. (line 13)
+* freetype-config: freetype library. (line 13)
* freetype-config <1>: Variables for configure.
(line 24)
* FT2_CONFIG: Variables for configure.
@@ -5717,14 +5715,14 @@
(line 6)
* generic library module, adding: Adding a new generic library module.
(line 6)
-* Ghostscript location for Xdvik: Configure options for 'texk/xdvik'.
+* Ghostscript location for Xdvik: Configure options for texk/xdvik.
(line 6)
* git-svn: Transfer from Subversion to Github.
(line 6)
-* global 'configure' options: Global configure options.
+* global configure options: Global configure options.
(line 6)
-* 'gmake', required: Prerequisites. (line 13)
-* GNU 'make', required: Prerequisites. (line 13)
+* gmake, required: Prerequisites. (line 13)
+* GNU make, required: Prerequisites. (line 13)
* GNU tools, needed for building: Build system tools. (line 6)
* GNU/Linux distro: Distro builds. (line 6)
* Gnulib, used for common files: Top-level directories.
@@ -5739,23 +5737,23 @@
* ICU_CONFIG: Variables for configure.
(line 22)
* infrastructure, tools needed for: Build system tools. (line 6)
-* 'inst/' top-level directory: Top-level directories.
+* inst/ top-level directory: Top-level directories.
(line 39)
* install-tl, TeX Live installer: Installing. (line 8)
* installation directories: Installation directories.
(line 6)
* installing: Installing. (line 6)
-* interprocess communication: Configure options for 'texk/web2c'.
+* interprocess communication: Configure options for texk/web2c.
(line 31)
* introduction: Introduction. (line 6)
-* iteration through sources, by 'configure' and 'make': Build iteration.
+* iteration through sources, by configure and make: Build iteration.
(line 6)
-* kpathsea library: 'kpathsea' library. (line 6)
-* kpathsea.ac: 'kpathsea' library. (line 18)
-* kpse-libpng-flags.m4: 'png' library. (line 46)
+* kpathsea library: kpathsea library. (line 6)
+* kpathsea.ac: kpathsea library. (line 18)
+* kpse-libpng-flags.m4: png library. (line 45)
* kpse-pkgs.m4: Overview of build system.
(line 30)
-* kpse-zlib-flags.m4: 'zlib' library. (line 6)
+* kpse-zlib-flags.m4: zlib library. (line 6)
* kpsewhich: Variables for configure.
(line 30)
* KPSEWHICH: Variables for configure.
@@ -5794,7 +5792,7 @@
(line 8)
* KPSE_LIBPNG_FLAGS: Macros for library and header flags.
(line 10)
-* KPSE_LIBPNG_FLAGS <1>: 'png' library. (line 46)
+* KPSE_LIBPNG_FLAGS <1>: png library. (line 45)
* kpse_libs_pkgs: Adding a new generic library module.
(line 6)
* KPSE_LIB_FLAGS: Macros for library and header flags.
@@ -5810,10 +5808,10 @@
(line 6)
* kpse_texlibs_pkgs: Adding a new TeX-specific library module.
(line 11)
-* KPSE_TRY_LIB: 'png' library. (line 18)
+* KPSE_TRY_LIB: png library. (line 17)
* KPSE_TRY_LIB <1>: Adding a new generic library module.
(line 20)
-* KPSE_TRY_LIBXX: 'png' library. (line 31)
+* KPSE_TRY_LIBXX: png library. (line 30)
* KPSE_TRY_LIBXX <1>: Adding a new generic library module.
(line 20)
* kpse_utils_pkgs: Adding a new program module.
@@ -5823,46 +5821,44 @@
(line 11)
* KPSE_WITH_TEXLIB: Adding a new TeX-specific library module.
(line 14)
-* large file support: '--disable-largefile'.
- (line 6)
+* large file support: --disable-largefile. (line 6)
* LATEX: Variables for configure.
(line 40)
* layout of sources: Layout and infrastructure.
(line 6)
-* LFS (large file support): '--disable-largefile'.
- (line 6)
-* libexpat, dependency of 'libfontconfig': Configure options for 'texk/web2c'.
+* LFS (large file support): --disable-largefile. (line 6)
+* libexpat, dependency of libfontconfig: Configure options for texk/web2c.
(line 50)
-* libfontconfig, hack for avoiding linking dependencies: Configure options for 'texk/web2c'.
+* libfontconfig, hack for avoiding linking dependencies: Configure options for texk/web2c.
(line 50)
* libfreetype: Variables for configure.
(line 24)
-* 'libfreetype', and 'const': Const. (line 21)
-* libpng library: 'png' library. (line 6)
+* libfreetype, and const: Const. (line 21)
+* libpng library: png library. (line 6)
* library module, generic, adding: Adding a new generic library module.
(line 6)
* library module, TeX-specific, adding: Adding a new TeX-specific library module.
(line 6)
* library modules: Library modules. (line 6)
-* library-specific 'configure' options: Library-specific configure options.
+* library-specific configure options: Library-specific configure options.
(line 6)
-* 'libsigsegv', required by 'xindy': Prerequisites. (line 44)
+* libsigsegv, required by xindy: Prerequisites. (line 44)
* libstc++, statically linking: Macros for compilers.
(line 29)
* Libtool: Overview of build system.
(line 6)
-* libtool, hack for avoiding excessive linking: Configure options for 'texk/web2c'.
+* libtool, hack for avoiding excessive linking: Configure options for texk/web2c.
(line 50)
-* libXt: Configure options for 'texk/web2c'.
+* libXt: Configure options for texk/web2c.
(line 22)
* linked scripts: Linked scripts. (line 6)
* linking C++ libraries statically: Macros for compilers.
(line 29)
-* lisp.run, lisp.exe: Configure options for 'utils/xindy'.
+* lisp.run, lisp.exe: Configure options for utils/xindy.
(line 14)
-* LittleEndian architectures: Configure options for 'texk/web2c'.
+* LittleEndian architectures: Configure options for texk/web2c.
(line 27)
-* 'm4/' top-level directory: Top-level directories.
+* m4/ top-level directory: Top-level directories.
(line 14)
* macros, for compilers: Macros for compilers.
(line 6)
@@ -5877,19 +5873,19 @@
* MAKE: Variables for configure.
(line 33)
* make -t: Build system tools. (line 43)
-* 'make' rules, verbose vs. silent: '--enable-silent-rules'.
+* make rules, verbose vs. silent: --enable-silent-rules.
(line 6)
* Makefile.am: Adding a new program module.
(line 46)
-* mf-nowin: Configure options for 'texk/web2c'.
+* mf-nowin: Configure options for texk/web2c.
(line 34)
-* 'mingw32': Cross configuring. (line 27)
+* mingw32: Cross configuring. (line 27)
* MINGW32, Automake conditional: Macros for Windows. (line 20)
-* mktex.ac: 'kpathsea' library. (line 18)
-* mktextfm: 'kpathsea' library. (line 18)
+* mktex.ac: kpathsea library. (line 18)
+* mktextfm: kpathsea library. (line 18)
* modules, for libraries: Library modules. (line 6)
* modules, for programs: Program modules. (line 6)
-* motif: Configure options for 'texk/xdvik'.
+* motif: Configure options for texk/xdvik.
(line 9)
* native cross compilation: Cross compilation. (line 10)
* NEWPROG-SRC, original source subdirectory: Adding a new program module.
@@ -5897,7 +5893,7 @@
* OBJCXX=OBJC-COMPILER: Build one package. (line 77)
* one engine, building: Build one engine. (line 6)
* one package, building: Build one package. (line 6)
-* OpenGL, required for Asymptote: 'asymptote'. (line 6)
+* OpenGL, required for Asymptote: asymptote. (line 6)
* operating system distribution, building for: Distro builds. (line 6)
* otangle: Cross problems. (line 26)
* overall build process: Building. (line 6)
@@ -5904,29 +5900,27 @@
* parallel build: Build in parallel. (line 6)
* paths, for installation: Installation directories.
(line 6)
-* PDF files, size of: '--disable-largefile'.
- (line 11)
+* PDF files, size of: --disable-largefile. (line 11)
* PDFLATEX: Variables for configure.
(line 41)
* PERL: Variables for configure.
(line 39)
-* 'perl', required by 'web2c', etc.: Prerequisites. (line 29)
+* perl, required by web2c, etc.: Prerequisites. (line 29)
* PKG_CONFIG: Variables for configure.
(line 23)
* plain.tex, not in source tree: Installing. (line 8)
-* png library: 'png' library. (line 6)
-* PostScript files, size of: '--disable-largefile'.
- (line 11)
+* png library: png library. (line 6)
+* PostScript files, size of: --disable-largefile. (line 11)
* Preining, Norbert: Distro builds. (line 54)
-* preloaded binaries: Configure options for 'texk/web2c'.
+* preloaded binaries: Configure options for texk/web2c.
(line 45)
* prerequisites for building: Prerequisites. (line 6)
* program module, adding: Adding a new program module.
(line 6)
* program modules: Program modules. (line 6)
-* program-specific 'configure' options: Program-specific configure options.
+* program-specific configure options: Program-specific configure options.
(line 6)
-* proxy build system: 'png' library. (line 36)
+* proxy build system: png library. (line 35)
* Python, required by ICU: Prerequisites. (line 23)
* reautoconf: Build system tools. (line 28)
* reautoconf, for new program: Adding a new program module.
@@ -5935,7 +5929,7 @@
* requirements for building: Prerequisites. (line 6)
* runscript.exe: Macros for Windows. (line 25)
* scripts, linked and not maintained: Linked scripts. (line 6)
-* scrolling, smooth: Configure options for 'texk/xdvik'.
+* scrolling, smooth: Configure options for texk/xdvik.
(line 13)
* SED: Variables for configure.
(line 34)
@@ -5942,8 +5936,7 @@
* setup macros, general: General setup macros.
(line 6)
* shared libraries, using vs. avoiding: Distro builds. (line 11)
-* size of PDF and PS files: '--disable-largefile'.
- (line 11)
+* size of PDF and PS files: --disable-largefile. (line 11)
* size of source tree: Build one package. (line 63)
* source code declarations: Declarations and definitions.
(line 6)
@@ -5951,8 +5944,8 @@
* source tree: Layout and infrastructure.
(line 6)
* squeeze: Cross problems. (line 13)
-* squeeze/configure.ac: 'xdvik' package. (line 14)
-* 'static' functions: Declarations and definitions.
+* squeeze/configure.ac: xdvik package. (line 14)
+* static functions: Declarations and definitions.
(line 35)
* static linking for C++: Macros for compilers.
(line 29)
@@ -5961,12 +5954,12 @@
* Subversion repository: Build system tools. (line 38)
* support files, separate from build: Installing. (line 8)
* symlinks, used for scripts: Linked scripts. (line 6)
-* synctex: Configure options for 'texk/web2c'.
+* synctex: Configure options for texk/web2c.
(line 59)
-* synctex <1>: Configure options for 'texk/web2c'.
+* synctex <1>: Configure options for texk/web2c.
(line 64)
* system distribution, building for: Distro builds. (line 6)
-* t1utils package: 't1utils' package. (line 6)
+* t1utils package: t1utils package. (line 6)
* tangle: Cross problems. (line 26)
* tests, running: Overview of build system.
(line 6)
@@ -5993,13 +5986,13 @@
* use-commit-times, Subversion: Build system tools. (line 38)
* variable declarations, in source code: Declarations and definitions.
(line 52)
-* variables for 'configure': Variables for configure.
+* variables for configure: Variables for configure.
(line 6)
* warning, discards qualifiers: Const. (line 30)
* WARNING_C[XX]FLAGS: Macros for compilers.
(line 9)
* web2c program: Cross problems. (line 13)
-* web2c.ac: Configure options for 'texk/web2c'.
+* web2c.ac: Configure options for texk/web2c.
(line 37)
* wget: Linked scripts. (line 23)
* WIN32, Automake conditional: Macros for Windows. (line 16)
@@ -6008,433 +6001,438 @@
* Windows, macros for: Macros for Windows. (line 6)
* withenable.ac, for new modules: Adding a new program module.
(line 14)
-* 'Work/' top-level directory: Top-level directories.
+* Work/ top-level directory: Top-level directories.
(line 39)
* wrapper binary for scripts on Windows: Linked scripts. (line 6)
-* wrapper build system: 'freetype' library. (line 6)
-* X toolkit: Configure options for 'texk/web2c'.
+* wrapper build system: freetype library. (line 6)
+* X toolkit: Configure options for texk/web2c.
(line 22)
* X11 development, required by X clients: Prerequisites. (line 36)
-* X11 headers, and 'const': Const. (line 21)
-* xasy: 'asymptote'. (line 6)
-* xaw: Configure options for 'texk/xdvik'.
+* X11 headers, and const: Const. (line 21)
+* xasy: asymptote. (line 6)
+* xaw: Configure options for texk/xdvik.
(line 9)
-* xdvik: 'xdvik' package. (line 6)
-* xdvik <1>: Configure options for 'texk/xdvik'.
+* xdvik: xdvik package. (line 6)
+* xdvik <1>: Configure options for texk/xdvik.
(line 6)
-* xdvipdfmx: Configure options for 'texk/dvipdfm-x'.
+* xdvipdfmx: Configure options for texk/dvipdfm-x.
(line 6)
* xindy: Linked scripts. (line 23)
-* xindy <1>: 'xindy' package. (line 6)
-* xindy <2>: Configure options for 'utils/xindy'.
+* xindy <1>: xindy package. (line 6)
+* xindy <2>: Configure options for utils/xindy.
(line 6)
-* 'xindy' cross compiling requires 'clisp': Cross problems. (line 33)
-* XInput: Configure options for 'texk/xdvik'.
+* xindy cross compiling requires clisp: Cross problems. (line 33)
+* XInput: Configure options for texk/xdvik.
(line 13)
-* Xlib: Configure options for 'texk/web2c'.
+* Xlib: Configure options for texk/web2c.
(line 22)
* xz: Linked scripts. (line 23)
-* zlib library: 'zlib' library. (line 6)
+* zlib library: zlib library. (line 6)
Tag Table:
-Node: Top1208
-Node: Introduction2118
-Node: Overview of build system3941
-Node: Prerequisites5992
-Ref: Prerequisites-Footnote-18991
-Node: Building9294
-Node: Build iteration10636
-Node: Build in parallel11680
-Node: Build distribution12285
-Node: Build one package12933
-Node: Build one engine17648
-Node: Cross compilation20073
-Node: Cross configuring21352
-Node: Cross problems23029
-Node: Installing24691
-Node: Installation directories25711
-Node: Linked scripts27529
-Node: Distro builds29020
-Node: Layout and infrastructure31396
-Node: Build system tools32227
-Node: Top-level directories34444
-Node: Autoconf macros36680
-Node: General setup macros37442
-Node: Macros for programs38317
-Node: Macros for compilers39118
-Node: Macros for libraries40526
-Node: Macros for library and header flags40952
-Node: Macros for Windows42863
-Node: Library modules44450
-Node: 'png' library44947
-Node: 'zlib' library47299
-Node: 'freetype' library47820
-Node: 'kpathsea' library48522
-Node: Program modules49905
-Node: 't1utils' package50341
-Node: 'xindy' package50890
-Node: 'xdvik' package52012
-Node: 'asymptote'53077
-Node: Extending TeX Live53585
-Node: Adding a new program module54392
-Node: Adding a new engine59155
-Node: Adding a new generic library module60940
-Node: Adding a new TeX-specific library module63161
-Node: Configure options63859
-Node: Global configure options65240
-Node: '--disable-native-texlive-build'65808
-Node: '--prefix' '--bindir' ...66776
-Node: '--disable-largefile'67324
-Node: '--disable-missing'67874
-Node: '--enable-compiler-warnings='LEVEL68281
-Node: '--enable-cxx-runtime-hack'68943
-Node: '--enable-maintainer-mode'69369
-Node: '--enable-multiplatform'69904
-Node: '--enable-shared'70483
-Node: '--enable-silent-rules'70860
-Node: '--without-ln-s'71318
-Node: '--without-x'71671
-Node: Program-specific configure options71863
-Node: '--enable-PROG' '--disable-PROG'72526
-Node: '--disable-all-pkgs'72805
-Node: Configure options for 'texk/web2c'73596
-Node: Configure options for 'texk/bibtex-x'76140
-Node: Configure options for 'texk/dvipdfm-x'76689
-Node: Configure options for 'texk/dvisvgm'77471
-Node: Configure options for 'texk/texlive'78358
-Node: Configure options for 'texk/xdvik'78785
-Node: Configure options for 'utils/xindy'79412
-Node: Library-specific configure options80306
-Node: Configure options for 'kpathsea'81269
-Node: Variables for configure81977
-Node: Coding conventions83403
-Node: Declarations and definitions84118
-Node: Const86292
-Node: Continuous integration88156
-Node: Transfer from Subversion to Github88820
-Node: Automatic update of the Git mirror90982
-Node: CI testing on Travis-CI91564
-Node: Releases on Github92273
-Node: install-tl92713
-Node: install-tl NAME93082
-Node: install-tl SYNOPSIS93240
-Node: install-tl DESCRIPTION93456
-Node: install-tl REFERENCES94516
-Node: install-tl OPTIONS95040
-Ref: install-tl *-gui* [[=]_module_]95381
-Ref: install-tl 'text'95589
-Ref: install-tl 'tcl' (or "perltk" or "wizard" or "expert" or nothing)95774
-Ref: install-tl *-no-gui*96406
-Ref: install-tl *-lang* _llcode_96496
-Ref: install-tl *-repository* _url|path_97120
-Ref: install-tl *-select-repository*98009
-Ref: install-tl *-all-options*98427
-Ref: install-tl *-custom-bin* _path_98682
-Ref: install-tl *-debug-fakenet*99512
-Ref: install-tl *-debug-translation*99688
-Ref: install-tl *-force-platform* _platform_99964
-Ref: install-tl *-help*, *--help*, *-?*100208
-Ref: install-tl *-in-place*100621
-Ref: install-tl *-init-from-profile* _profile_file_101166
-Ref: install-tl *-logfile* _file_101435
-Ref: install-tl *-no-cls*101786
-Ref: install-tl *-no-persistent-downloads*101934
-Ref: install-tl *-persistent-downloads*101959
-Ref: install-tl *-no-verify-downloads*102577
-Ref: install-tl *-non-admin*102940
-Ref: install-tl *-portable*103033
-Ref: install-tl *-print-platform*103172
-Ref: install-tl *-profile* _profile_file_103370
-Ref: install-tl *-q*103591
-Ref: install-tl *-scheme* _scheme_103653
-Ref: install-tl *-v*104127
-Ref: install-tl *-version*, *--version*104282
-Node: install-tl PROFILES104416
-Ref: install-tl 'instopt_adjustpath' (default 0 on Unix, 1 on Windows)107282
-Ref: install-tl 'instopt_adjustrepo' (default 1)107358
-Ref: install-tl 'instopt_letter' (default 0)107495
-Ref: install-tl 'instopt_portable' (default 0)107586
-Ref: install-tl 'instopt_write18_restricted' (default 1)107682
-Node: install-tl ENVIRONMENT VARIABLES109021
-Ref: install-tl 'TEXLIVE_DOWNLOADER'109399
-Ref: install-tl 'TL_DOWNLOAD_PROGRAM'109422
-Ref: install-tl 'TL_DOWNLOAD_ARGS'109442
-Ref: install-tl 'TEXLIVE_INSTALL_ENV_NOCHECK'109646
-Ref: install-tl 'TEXLIVE_INSTALL_NO_CONTEXT_CACHE'109848
-Ref: install-tl 'TEXLIVE_INSTALL_NO_RESUME'109957
-Ref: install-tl 'TEXLIVE_INSTALL_NO_WELCOME'110109
-Ref: install-tl 'TEXLIVE_INSTALL_PAPER'110230
-Ref: install-tl 'TEXLIVE_INSTALL_PREFIX'110376
-Ref: install-tl 'TEXLIVE_INSTALL_TEXMFCONFIG'110407
-Ref: install-tl 'TEXLIVE_INSTALL_TEXMFVAR'110435
-Ref: install-tl 'TEXLIVE_INSTALL_TEXMFHOME'110464
-Ref: install-tl 'TEXLIVE_INSTALL_TEXMFLOCAL'110494
-Ref: install-tl 'TEXLIVE_INSTALL_TEXMFSYSCONFIG'110528
-Ref: install-tl 'TEXLIVE_INSTALL_TEXMFSYSVAR'110559
-Ref: install-tl 'NOPERLDOC'110974
-Node: install-tl AUTHORS AND COPYRIGHT111038
-Node: tlmgr111451
-Node: tlmgr NAME111936
-Node: tlmgr SYNOPSIS112068
-Node: tlmgr DESCRIPTION112258
-Node: tlmgr EXAMPLES113357
-Ref: tlmgr 'tlmgr option repository ctan'113608
-Ref: tlmgr 'tlmgr option repository https://mirror.ctan.org/systems/texlive/tlnet'113681
-Ref: tlmgr 'tlmgr update --list'114286
-Ref: tlmgr 'tlmgr update --all'114379
-Ref: tlmgr 'tlmgr info' _what_114536
-Node: tlmgr OPTIONS114798
-Ref: tlmgr *--repository* _url|path_115318
-Ref: tlmgr '/some/local/dir'116504
-Ref: tlmgr 'file:/some/local/dir'116533
-Ref: tlmgr 'ctan'116606
-Ref: tlmgr 'https://mirror.ctan.org/systems/texlive/tlnet'116660
-Ref: tlmgr 'http://server/path/to/tlnet'117001
-Ref: tlmgr 'https://server/path/to/tlnet'117382
-Ref: tlmgr 'ftp://server/path/to/tlnet'117850
-Ref: tlmgr 'user at machine:/path/to/tlnet'117982
-Ref: tlmgr 'scp://user@machine/path/to/tlnet'118023
-Ref: tlmgr 'ssh://user@machine/path/to/tlnet'118064
-Ref: tlmgr *--gui* [_action_]118457
-Ref: tlmgr *--gui-lang* _llcode_119270
-Ref: tlmgr *--command-logfile* _file_120011
-Ref: tlmgr *--debug-translation*120277
-Ref: tlmgr *--machine-readable*120480
-Ref: tlmgr *--no-execute-actions*120748
-Ref: tlmgr *--package-logfile* _file_120941
-Ref: tlmgr *--pause*121195
-Ref: tlmgr *--persistent-downloads*121350
-Ref: tlmgr *--no-persistent-downloads*121378
-Ref: tlmgr *--pin-file*121872
-Ref: tlmgr *--usermode*122090
-Ref: tlmgr *--usertree* _dir_122210
-Ref: tlmgr *--verify-repo=[none|main|all]*122336
-Node: tlmgr ACTIONS123235
-Node: tlmgr help124096
-Node: tlmgr version124573
-Node: tlmgr backup124836
-Ref: tlmgr *backup [_option_...] --all*125007
-Ref: tlmgr *backup [_option_...] _pkg_...*125040
-Ref: tlmgr *--backupdir* _directory_126106
-Ref: tlmgr *--all*126323
-Ref: tlmgr *--clean*[=_N_]126575
-Ref: tlmgr *--dry-run*126902
-Node: tlmgr candidates _pkg_127032
-Node: tlmgr check [_option_...] [depends|executes|files|runfiles|texmfdbs|all]127387
-Ref: tlmgr *depends*127901
-Ref: tlmgr *executes*128243
-Ref: tlmgr *files*128358
-Ref: tlmgr *runfiles*128494
-Ref: tlmgr *texmfdbs*128631
-Ref: tlmgr - all items in 'TEXMFDBS' have the '!!' prefix.128861
-Ref: tlmgr - all items in 'TEXMFBDS' have an 'ls-R' file (if they exist at all).128937
-Ref: tlmgr - all items in 'TEXMF' with '!!' are listed in 'TEXMFDBS'.129002
-Ref: tlmgr - all items in 'TEXMF' with an 'ls-R' file are listed in 'TEXMFDBS'.129077
-Ref: tlmgr *--use-svn*129102
-Node: tlmgr conf129243
-Ref: tlmgr *conf [texmf|tlmgr|updmap [--conffile _file_] [--delete] [_key_ [_value_]]]*129531
-Ref: tlmgr *conf auxtrees [--conffile _file_] [show|add|remove] [_value_]*129595
-Node: tlmgr dump-tlpdb [_option_...] [--json]132010
-Ref: tlmgr *--local*132443
-Ref: tlmgr *--remote*132482
-Ref: tlmgr *--json*132520
-Node: tlmgr generate133091
-Ref: tlmgr *generate [_option_...] language*133287
-Ref: tlmgr *generate [_option_...] language.dat*133326
-Ref: tlmgr *generate [_option_...] language.def*133365
-Ref: tlmgr *generate [_option_...] language.dat.lua*133408
-Ref: tlmgr *--dest* _output_file_135735
-Ref: tlmgr *--localcfg* _local_conf_file_136311
-Ref: tlmgr *--rebuild-sys*136434
-Node: tlmgr gui137249
-Node: tlmgr info137427
-Ref: tlmgr *info [_option_...] _pkg_...*137589
-Ref: tlmgr *info [_option_...] collections*137623
-Ref: tlmgr *info [_option_...] schemes*137653
-Ref: tlmgr *--list*139183
-Ref: tlmgr *--only-installed*139497
-Ref: tlmgr *--only-remote*139685
-Ref: tlmgr *--data 'item1,item2,...'*139989
-Ref: tlmgr *--json* 1141361
-Node: tlmgr init-usertree141744
-Node: tlmgr install [_option_...] _pkg_...142125
-Ref: tlmgr *--dry-run* 1142633
-Ref: tlmgr *--file*142750
-Ref: tlmgr *--force*142972
-Ref: tlmgr *--no-depends*143192
-Ref: tlmgr *--no-depends-at-all*143351
-Ref: tlmgr *--reinstall*143751
-Ref: tlmgr *--with-doc*144129
-Ref: tlmgr *--with-src*144142
-Node: tlmgr key144870
-Ref: tlmgr *key list*145028
-Ref: tlmgr *key add _file_*145046
-Ref: tlmgr *key remove _keyid_*145068
-Node: tlmgr list145662
-Node: tlmgr option145824
-Ref: tlmgr *option [--json] [show]*145979
-Ref: tlmgr *option [--json] showall|help*146010
-Ref: tlmgr *option _key_ [_value_]*146036
-Node: tlmgr paper150615
-Ref: tlmgr *paper [a4|letter]*150764
-Ref: tlmgr *<[xdvi|pdftex|dvips|dvipdfmx|context|psutils] paper [_papersize_|--list]*>150840
-Ref: tlmgr *paper --json*150855
-Node: tlmgr path152070
-Ref: tlmgr *path [--w32mode=user|admin] add*152231
-Ref: tlmgr *path [--w32mode=user|admin] remove*152268
-Node: tlmgr pinning153753
-Ref: tlmgr 'pinning show'153994
-Ref: tlmgr 'pinning add' _repo_ _pkgglob_...154067
-Ref: tlmgr 'pinning remove' _repo_ _pkgglob_...154186
-Ref: tlmgr 'pinning remove _repo_ --all'154339
-Node: tlmgr platform154393
-Ref: tlmgr *platform list|add|remove _platform_...*154579
-Ref: tlmgr *platform set _platform_*154606
-Ref: tlmgr *platform set auto*154627
-Ref: tlmgr *--dry-run* 2155504
-Node: tlmgr postaction155623
-Ref: tlmgr *postaction [_option_...] install [shortcut|fileassoc|script] [_pkg_...]*155853
-Ref: tlmgr *postaction [_option_...] remove [shortcut|fileassoc|script] [_pkg_...]*155927
-Ref: tlmgr *--w32mode=[user|admin]*156242
-Ref: tlmgr *--fileassocmode=[1|2]*156658
-Ref: tlmgr *--all* 1156943
-Node: tlmgr print-platform156998
-Node: tlmgr print-platform-info157329
-Node: tlmgr remove [_option_...] _pkg_...157629
-Ref: tlmgr *--all* 2158113
-Ref: tlmgr *--backup*158223
-Ref: tlmgr *--backupdir* _directory_ 1158249
-Ref: tlmgr *--no-depends* 1158654
-Ref: tlmgr *--no-depends-at-all* 1158716
-Ref: tlmgr *--force* 1158819
-Ref: tlmgr *--dry-run* 3159292
-Node: tlmgr repository159669
-Ref: tlmgr *repository list*159857
-Ref: tlmgr *repository list _path|url|tag_*159891
-Ref: tlmgr *repository add _path_ [_tag_]*159924
-Ref: tlmgr *repository remove _path|tag_*159956
-Ref: tlmgr *repository set _path_[#_tag_] [_path_[#_tag_] ...]*160010
-Ref: tlmgr *repository status*160031
-Ref: tlmgr The tag (which can be the same as the url);161258
-Node: tlmgr restore161736
-Ref: tlmgr *restore [_option_...] _pkg_ [_rev_]*161915
-Ref: tlmgr *restore [_option_...] --all*161945
-Ref: tlmgr *--all* 3162645
-Ref: tlmgr *--backupdir* _directory_ 2162859
-Ref: tlmgr *--dry-run* 4163040
-Ref: tlmgr *--force* 2163172
-Ref: tlmgr *--json* 2163218
-Node: tlmgr search163545
-Ref: tlmgr *search [_option_...] _what_*163709
-Ref: tlmgr *search [_option_...] --file _what_*163746
-Ref: tlmgr *search [_option_...] --all _what_*163782
-Ref: tlmgr *--file* 1164002
-Ref: tlmgr *--all* 4164064
-Ref: tlmgr *--global*164153
-Ref: tlmgr *--word*164280
-Node: tlmgr shell164595
-Ref: tlmgr protocol165330
-Ref: tlmgr help 1165394
-Ref: tlmgr version 1165447
-Ref: tlmgr quit, end, bye, byebye, EOF165515
-Ref: tlmgr restart165536
-Ref: tlmgr load [local|remote]165659
-Ref: tlmgr save165729
-Ref: tlmgr get [_var_] =item set [_var_ [_val_]]165852
-Node: tlmgr show166453
-Node: tlmgr uninstall166620
-Node: tlmgr update [_option_...] [_pkg_...]166850
-Ref: tlmgr *--all* 5167221
-Ref: tlmgr *--self*169400
-Ref: tlmgr *--dry-run* 5170164
-Ref: tlmgr *--list* [_pkg_]170341
-Ref: tlmgr *--exclude* _pkg_171030
-Ref: tlmgr *--no-auto-remove* [_pkg_...]171830
-Ref: tlmgr *--no-auto-install* [_pkg_...]172314
-Ref: tlmgr *--reinstall-forcibly-removed*173076
-Ref: tlmgr *--backup* 1173611
-Ref: tlmgr *--backupdir* _directory_ 3173637
-Ref: tlmgr *--no-depends* 2174803
-Ref: tlmgr *--no-depends-at-all* 2175006
-Ref: tlmgr *--force* 3175109
-Node: tlmgr CONFIGURATION FILE FOR TLMGR176100
-Ref: tlmgr 'auto-remove =' 0 or 1 (default 1), same as command-line option.177102
-Ref: tlmgr 'gui-expertmode =' 0 or 1 (default 1). This switches between the full GUI and a simplified GUI with only the most common settings.177234
-Ref: tlmgr 'gui-lang =' _llcode_, with a language code value as with the command-line option.177318
-Ref: tlmgr 'no-checksums =' 0 or 1 (default 0, see below).177367
-Ref: tlmgr 'persistent-downloads =' 0 or 1 (default 1), same as command-line option.177442
-Ref: tlmgr 'require-verification =' 0 or 1 (default 0), same as command-line option.177517
-Ref: tlmgr 'tkfontscale =' _floating-point number_ (default 1.0); scaling factor for fonts in the Tk-based frontends.177625
-Ref: tlmgr 'update-exclude =' _comma-separated list of packages_ (no spaces allowed). Same as the command line option '--exclude' for the 'update' action.177770
-Ref: tlmgr 'verify-downloads =' 0 or 1 (default 1), same as command-line option.177841
-Ref: tlmgr 'allowed-actions =' _action1_[,_action2_,...] The value is a comma-separated list (no spaces) of 'tlmgr' actions which are allowed to be executed when 'tlmgr' is invoked in system mode (that is, without '--usermode'). This allows distributors to include 'tlmgr' in their packaging, but allow only a restricted set of actions that do not interfere with their distro package manager. For native TeX Live installations, it doesn't make sense to set this.178358
-Node: tlmgr CRYPTOGRAPHIC VERIFICATION179190
-Node: tlmgr Configuration of GnuPG invocation181363
-Node: tlmgr USER MODE182001
-Node: tlmgr User mode install184847
-Node: tlmgr User mode backup, restore, remove, update185991
-Node: tlmgr User mode generate, option, paper186433
-Node: tlmgr MULTIPLE REPOSITORIES186767
-Node: tlmgr Pinning188496
-Node: tlmgr GUI FOR TLMGR190419
-Node: tlmgr Main display192068
-Node: tlmgr Display configuration area192320
-Ref: tlmgr Status192681
-Ref: tlmgr Category192845
-Ref: tlmgr Match193031
-Ref: tlmgr Selection193212
-Ref: tlmgr Display configuration buttons193416
-Node: tlmgr Package list area193599
-Ref: tlmgr a checkbox194183
-Ref: tlmgr package name194319
-Ref: tlmgr local revision (and version)194418
-Ref: tlmgr remote revision (and version)194793
-Ref: tlmgr short description195090
-Node: tlmgr Main display action buttons195135
-Ref: tlmgr Update all installed195401
-Ref: tlmgr Update195773
-Ref: tlmgr Install195823
-Ref: tlmgr Remove196009
-Ref: tlmgr Backup196187
-Node: tlmgr Menu bar196344
-Ref: tlmgr 'tlmgr' menu196567
-Ref: tlmgr 'Options menu'196875
-Ref: tlmgr 'Actions menu'197958
-Ref: tlmgr 'Help menu'198386
-Node: tlmgr GUI options198520
-Ref: tlmgr '-background' _color_198766
-Ref: tlmgr '-font "' _fontname_ _fontsize_ '"'198831
-Ref: tlmgr '-foreground' _color_198989
-Ref: tlmgr '-geometry' _geomspec_199041
-Ref: tlmgr '-xrm' _xresource_199233
-Node: tlmgr MACHINE-READABLE OUTPUT199502
-Node: tlmgr Machine-readable 'update' and 'install' output200318
-Ref: tlmgr 'location-url' _location_201600
-Ref: tlmgr 'total-bytes' _count_201816
-Ref: tlmgr _pkgname_202226
-Ref: tlmgr _status_202436
-Ref: tlmgr 'd'202514
-Ref: tlmgr 'f'202574
-Ref: tlmgr 'u'202753
-Ref: tlmgr 'r'202799
-Ref: tlmgr 'a'202922
-Ref: tlmgr 'i'203100
-Ref: tlmgr 'I'203219
-Ref: tlmgr _localrev_203321
-Ref: tlmgr _serverrev_203428
-Ref: tlmgr _size_203540
-Ref: tlmgr _runtime_203709
-Ref: tlmgr _esttot_203779
-Node: tlmgr Machine-readable 'option' output203812
-Node: tlmgr ENVIRONMENT VARIABLES204330
-Ref: tlmgr 'TEXLIVE_COMPRESSOR'204841
-Ref: tlmgr 'TEXLIVE_DOWNLOADER'205689
-Ref: tlmgr 'TL_DOWNLOAD_PROGRAM'205712
-Ref: tlmgr 'TL_DOWNLOAD_ARGS'205732
-Ref: tlmgr 'TEXLIVE_PREFER_OWN'206758
-Node: tlmgr AUTHORS AND COPYRIGHT207582
-Node: Index207984
+Node: Top1212
+Node: Introduction2122
+Node: Overview of build system3996
+Node: Prerequisites6102
+Ref: Prerequisites-Footnote-19272
+Node: Building9593
+Node: Build iteration10988
+Node: Build in parallel12104
+Node: Build distribution12741
+Node: Build one package13401
+Node: Build one engine18256
+Node: Cross compilation20751
+Node: Cross configuring22070
+Node: Cross problems23791
+Node: Installing25529
+Node: Installation directories26577
+Node: Linked scripts28507
+Node: Distro builds30046
+Node: Layout and infrastructure32502
+Node: Build system tools33345
+Node: Top-level directories35668
+Node: Autoconf macros38015
+Node: General setup macros38786
+Node: Macros for programs39693
+Node: Macros for compilers40574
+Node: Macros for libraries42034
+Node: Macros for library and header flags42476
+Node: Macros for Windows44511
+Node: Library modules46202
+Node: png library46707
+Node: zlib library49207
+Node: freetype library49754
+Node: kpathsea library50482
+Node: Program modules51925
+Node: t1utils package52369
+Node: xindy package52946
+Node: xdvik package54150
+Node: asymptote55273
+Node: Extending TeX Live55789
+Node: Adding a new program module56624
+Node: Adding a new engine61657
+Node: Adding a new generic library module63526
+Node: Adding a new TeX-specific library module65877
+Node: Configure options66603
+Node: Global configure options68020
+Node: --disable-native-texlive-build68562
+Node: --prefix --bindir ...69556
+Node: --disable-largefile70112
+Node: --disable-missing70674
+Node: --enable-compiler-warnings=LEVEL71079
+Node: --enable-cxx-runtime-hack71759
+Node: --enable-maintainer-mode72191
+Node: --enable-multiplatform72736
+Node: --enable-shared73341
+Node: --enable-silent-rules73724
+Node: --without-ln-s74200
+Node: --without-x74559
+Node: Program-specific configure options74751
+Node: --enable-PROG --disable-PROG75398
+Node: --disable-all-pkgs75683
+Node: Configure options for texk/web2c76489
+Node: Configure options for texk/bibtex-x79213
+Node: Configure options for texk/dvipdfm-x79796
+Node: Configure options for texk/dvisvgm80616
+Node: Configure options for texk/texlive81533
+Node: Configure options for texk/xdvik81970
+Node: Configure options for utils/xindy82635
+Node: Library-specific configure options83577
+Node: Configure options for kpathsea84566
+Node: Variables for configure85310
+Node: Coding conventions86856
+Node: Declarations and definitions87579
+Node: Const89802
+Node: Continuous integration91746
+Node: Transfer from Subversion to Github92410
+Node: Automatic update of the Git mirror94644
+Node: CI testing on Travis-CI95246
+Node: Releases on Github95975
+Node: install-tl96423
+Node: install-tl NAME96792
+Node: install-tl SYNOPSIS96950
+Node: install-tl DESCRIPTION97166
+Node: install-tl REFERENCES98234
+Node: install-tl OPTIONS98758
+Ref: install-tl *-gui* [[=]_module_]99111
+Ref: install-tl text99323
+Ref: install-tl tcl (or "perltk" or "wizard" or "expert" or nothing)99516
+Ref: install-tl *-no-gui*100156
+Ref: install-tl *-lang* _llcode_100246
+Ref: install-tl *-repository* _url|path_100870
+Ref: install-tl *-select-repository*101767
+Ref: install-tl *-all-options*102195
+Ref: install-tl *-custom-bin* _path_102450
+Ref: install-tl *-debug-fakenet*103292
+Ref: install-tl *-debug-translation*103470
+Ref: install-tl *-force-platform* _platform_103746
+Ref: install-tl *-help*, *--help*, *-?*103996
+Ref: install-tl *-in-place*104427
+Ref: install-tl *-init-from-profile* _profile_file_104976
+Ref: install-tl *-logfile* _file_105245
+Ref: install-tl *-no-cls*105600
+Ref: install-tl *-no-persistent-downloads*105748
+Ref: install-tl *-persistent-downloads*105773
+Ref: install-tl *-no-verify-downloads*106403
+Ref: install-tl *-non-admin*106774
+Ref: install-tl *-portable*106867
+Ref: install-tl *-print-platform*107006
+Ref: install-tl *-profile* _profile_file_107208
+Ref: install-tl *-q*107429
+Ref: install-tl *-scheme* _scheme_107491
+Ref: install-tl *-v*107973
+Ref: install-tl *-version*, *--version*108134
+Node: install-tl PROFILES108272
+Ref: install-tl instopt_adjustpath (default 0 on Unix, 1 on Windows)111206
+Ref: install-tl instopt_adjustrepo (default 1)111290
+Ref: install-tl instopt_letter (default 0)111435
+Ref: install-tl instopt_portable (default 0)111530
+Ref: install-tl instopt_write18_restricted (default 1)111630
+Node: install-tl ENVIRONMENT VARIABLES113009
+Ref: install-tl TEXLIVE_DOWNLOADER113395
+Ref: install-tl TL_DOWNLOAD_PROGRAM113422
+Ref: install-tl TL_DOWNLOAD_ARGS113446
+Ref: install-tl TEXLIVE_INSTALL_ENV_NOCHECK113658
+Ref: install-tl TEXLIVE_INSTALL_NO_CONTEXT_CACHE113868
+Ref: install-tl TEXLIVE_INSTALL_NO_RESUME113981
+Ref: install-tl TEXLIVE_INSTALL_NO_WELCOME114137
+Ref: install-tl TEXLIVE_INSTALL_PAPER114262
+Ref: install-tl TEXLIVE_INSTALL_PREFIX114424
+Ref: install-tl TEXLIVE_INSTALL_TEXMFCONFIG114459
+Ref: install-tl TEXLIVE_INSTALL_TEXMFVAR114491
+Ref: install-tl TEXLIVE_INSTALL_TEXMFHOME114524
+Ref: install-tl TEXLIVE_INSTALL_TEXMFLOCAL114558
+Ref: install-tl TEXLIVE_INSTALL_TEXMFSYSCONFIG114596
+Ref: install-tl TEXLIVE_INSTALL_TEXMFSYSVAR114631
+Ref: install-tl NOPERLDOC115070
+Node: install-tl AUTHORS AND COPYRIGHT115144
+Node: tlmgr115557
+Node: tlmgr NAME116042
+Node: tlmgr SYNOPSIS116174
+Node: tlmgr DESCRIPTION116364
+Node: tlmgr EXAMPLES117467
+Ref: tlmgr tlmgr option repository ctan117726
+Ref: tlmgr tlmgr option repository https://mirror.ctan.org/systems/texlive/tlnet117803
+Ref: tlmgr tlmgr update --list118424
+Ref: tlmgr tlmgr update --all118521
+Ref: tlmgr tlmgr info _what_118682
+Node: tlmgr OPTIONS118948
+Ref: tlmgr *--repository* _url|path_119486
+Ref: tlmgr /some/local/dir120700
+Ref: tlmgr file:/some/local/dir120733
+Ref: tlmgr ctan120810
+Ref: tlmgr https://mirror.ctan.org/systems/texlive/tlnet120868
+Ref: tlmgr http://server/path/to/tlnet121217
+Ref: tlmgr https://server/path/to/tlnet121614
+Ref: tlmgr ftp://server/path/to/tlnet122098
+Ref: tlmgr user at machine:/path/to/tlnet122234
+Ref: tlmgr scp://user@machine/path/to/tlnet122279
+Ref: tlmgr ssh://user@machine/path/to/tlnet122324
+Ref: tlmgr *--gui* [_action_]122739
+Ref: tlmgr *--gui-lang* _llcode_123584
+Ref: tlmgr *--command-logfile* _file_124331
+Ref: tlmgr *--debug-translation*124607
+Ref: tlmgr *--machine-readable*124816
+Ref: tlmgr *--no-execute-actions*125086
+Ref: tlmgr *--package-logfile* _file_125281
+Ref: tlmgr *--pause*125545
+Ref: tlmgr *--persistent-downloads*125706
+Ref: tlmgr *--no-persistent-downloads*125736
+Ref: tlmgr *--pin-file*126252
+Ref: tlmgr *--usermode*126476
+Ref: tlmgr *--usertree* _dir_126602
+Ref: tlmgr *--verify-repo=[none|main|all]*126730
+Node: tlmgr ACTIONS127677
+Node: tlmgr help128538
+Node: tlmgr version129037
+Node: tlmgr backup129308
+Ref: tlmgr *backup [_option_...] --all*129481
+Ref: tlmgr *backup [_option_...] _pkg_...*129514
+Ref: tlmgr *--backupdir* _directory_130626
+Ref: tlmgr *--all*130849
+Ref: tlmgr *--clean*[=_N_]131111
+Ref: tlmgr *--dry-run*131448
+Node: tlmgr candidates _pkg_131578
+Node: tlmgr check [_option_...] [depends|executes|files|runfiles|texmfdbs|all]131933
+Ref: tlmgr *depends*132451
+Ref: tlmgr *executes*132801
+Ref: tlmgr *files*132920
+Ref: tlmgr *runfiles*133060
+Ref: tlmgr *texmfdbs*133197
+Ref: tlmgr - all items in TEXMFDBS have the !! prefix.133449
+Ref: tlmgr - all items in TEXMFBDS have an ls-R file (if they exist at all).133533
+Ref: tlmgr - all items in TEXMF with !! are listed in TEXMFDBS.133610
+Ref: tlmgr - all items in TEXMF with an ls-R file are listed in TEXMFDBS.133697
+Ref: tlmgr *--use-svn*133724
+Node: tlmgr conf133869
+Ref: tlmgr *conf [texmf|tlmgr|updmap [--conffile _file_] [--delete] [_key_ [_value_]]]*134161
+Ref: tlmgr *conf auxtrees [--conffile _file_] [show|add|remove] [_value_]*134227
+Node: tlmgr dump-tlpdb [_option_...] [--json]136738
+Ref: tlmgr *--local*137179
+Ref: tlmgr *--remote*137220
+Ref: tlmgr *--json*137260
+Node: tlmgr generate137851
+Ref: tlmgr *generate [_option_...] language*138047
+Ref: tlmgr *generate [_option_...] language.dat*138086
+Ref: tlmgr *generate [_option_...] language.def*138125
+Ref: tlmgr *generate [_option_...] language.dat.lua*138168
+Ref: tlmgr *--dest* _output_file_140625
+Ref: tlmgr *--localcfg* _local_conf_file_141243
+Ref: tlmgr *--rebuild-sys*141372
+Node: tlmgr gui142215
+Node: tlmgr info142393
+Ref: tlmgr *info [_option_...] _pkg_...*142555
+Ref: tlmgr *info [_option_...] collections*142589
+Ref: tlmgr *info [_option_...] schemes*142619
+Ref: tlmgr *--list*144175
+Ref: tlmgr *--only-installed*144499
+Ref: tlmgr *--only-remote*144689
+Ref: tlmgr *--data item1,item2,...*145011
+Ref: tlmgr *--json* 1146515
+Node: tlmgr init-usertree146926
+Node: tlmgr install [_option_...] _pkg_...147315
+Ref: tlmgr *--dry-run* 1147829
+Ref: tlmgr *--file*147948
+Ref: tlmgr *--force*148172
+Ref: tlmgr *--no-depends*148402
+Ref: tlmgr *--no-depends-at-all*148563
+Ref: tlmgr *--reinstall*148983
+Ref: tlmgr *--with-doc*149363
+Ref: tlmgr *--with-src*149378
+Node: tlmgr key150122
+Ref: tlmgr *key list*150280
+Ref: tlmgr *key add _file_*150298
+Ref: tlmgr *key remove _keyid_*150320
+Node: tlmgr list150946
+Node: tlmgr option151108
+Ref: tlmgr *option [--json] [show]*151265
+Ref: tlmgr *option [--json] showall|help*151298
+Ref: tlmgr *option _key_ [_value_]*151324
+Node: tlmgr paper156091
+Ref: tlmgr *paper [a4|letter]*156240
+Ref: tlmgr *<[xdvi|pdftex|dvips|dvipdfmx|context|psutils] paper [_papersize_|--list]*>156318
+Ref: tlmgr *paper --json*156335
+Node: tlmgr path157602
+Ref: tlmgr *path [--w32mode=user|admin] add*157765
+Ref: tlmgr *path [--w32mode=user|admin] remove*157804
+Node: tlmgr pinning159313
+Ref: tlmgr pinning show159562
+Ref: tlmgr pinning add _repo_ _pkgglob_...159639
+Ref: tlmgr pinning remove _repo_ _pkgglob_...159762
+Ref: tlmgr pinning remove _repo_ --all159919
+Node: tlmgr platform159973
+Ref: tlmgr *platform list|add|remove _platform_...*160159
+Ref: tlmgr *platform set _platform_*160186
+Ref: tlmgr *platform set auto*160207
+Ref: tlmgr *--dry-run* 2161126
+Node: tlmgr postaction161245
+Ref: tlmgr *postaction [_option_...] install [shortcut|fileassoc|script] [_pkg_...]*161475
+Ref: tlmgr *postaction [_option_...] remove [shortcut|fileassoc|script] [_pkg_...]*161549
+Ref: tlmgr *--w32mode=[user|admin]*161882
+Ref: tlmgr *--fileassocmode=[1|2]*162316
+Ref: tlmgr *--all* 1162611
+Node: tlmgr print-platform162666
+Node: tlmgr print-platform-info163001
+Node: tlmgr remove [_option_...] _pkg_...163301
+Ref: tlmgr *--all* 2163791
+Ref: tlmgr *--backup*163907
+Ref: tlmgr *--backupdir* _directory_ 1163935
+Ref: tlmgr *--no-depends* 1164344
+Ref: tlmgr *--no-depends-at-all* 1164408
+Ref: tlmgr *--force* 1164516
+Ref: tlmgr *--dry-run* 3165003
+Node: tlmgr repository165392
+Ref: tlmgr *repository list*165580
+Ref: tlmgr *repository list _path|url|tag_*165614
+Ref: tlmgr *repository add _path_ [_tag_]*165647
+Ref: tlmgr *repository remove _path|tag_*165679
+Ref: tlmgr *repository set _path_[#_tag_] [_path_[#_tag_] ...]*165733
+Ref: tlmgr *repository status*165754
+Ref: tlmgr The tag (which can be the same as the url);167009
+Node: tlmgr restore167491
+Ref: tlmgr *restore [_option_...] _pkg_ [_rev_]*167670
+Ref: tlmgr *restore [_option_...] --all*167702
+Ref: tlmgr *--all* 3168412
+Ref: tlmgr *--backupdir* _directory_ 2168628
+Ref: tlmgr *--dry-run* 4168811
+Ref: tlmgr *--force* 2168945
+Ref: tlmgr *--json* 2168995
+Node: tlmgr search169358
+Ref: tlmgr *search [_option_...] _what_*169522
+Ref: tlmgr *search [_option_...] --file _what_*169561
+Ref: tlmgr *search [_option_...] --all _what_*169599
+Ref: tlmgr *--file* 1169821
+Ref: tlmgr *--all* 4169885
+Ref: tlmgr *--global*169976
+Ref: tlmgr *--word*170105
+Node: tlmgr shell170432
+Ref: tlmgr protocol171175
+Ref: tlmgr help 1171243
+Ref: tlmgr version 1171296
+Ref: tlmgr quit, end, bye, byebye, EOF171364
+Ref: tlmgr restart171385
+Ref: tlmgr load [local|remote]171516
+Ref: tlmgr save171586
+Ref: tlmgr get [_var_] =item set [_var_ [_val_]]171709
+Node: tlmgr show172354
+Node: tlmgr uninstall172521
+Node: tlmgr update [_option_...] [_pkg_...]172753
+Ref: tlmgr *--all* 5173130
+Ref: tlmgr *--self*175383
+Ref: tlmgr *--dry-run* 5176161
+Ref: tlmgr *--list* [_pkg_]176344
+Ref: tlmgr *--exclude* _pkg_177075
+Ref: tlmgr *--no-auto-remove* [_pkg_...]177897
+Ref: tlmgr *--no-auto-install* [_pkg_...]178395
+Ref: tlmgr *--reinstall-forcibly-removed*179179
+Ref: tlmgr *--backup* 1179734
+Ref: tlmgr *--backupdir* _directory_ 3179762
+Ref: tlmgr *--no-depends* 2180946
+Ref: tlmgr *--no-depends-at-all* 2181151
+Ref: tlmgr *--force* 3181259
+Node: tlmgr CONFIGURATION FILE FOR TLMGR182286
+Ref: tlmgr auto-remove = 0 or 1 (default 1), same as command-line option.183320
+Ref: tlmgr gui-expertmode = 0 or 1 (default 1). This switches between the full GUI and a simplified GUI with only the most common settings.183456
+Ref: tlmgr gui-lang = _llcode_, with a language code value as with the command-line option.183544
+Ref: tlmgr no-checksums = 0 or 1 (default 0, see below).183597
+Ref: tlmgr persistent-downloads = 0 or 1 (default 1), same as command-line option.183676
+Ref: tlmgr require-verification = 0 or 1 (default 0), same as command-line option.183755
+Ref: tlmgr tkfontscale = _floating-point number_ (default 1.0); scaling factor for fonts in the Tk-based frontends.183867
+Ref: tlmgr update-exclude = _comma-separated list of packages_ (no spaces allowed). Same as the command line option --exclude for the update action.184024
+Ref: tlmgr verify-downloads = 0 or 1 (default 1), same as command-line option.184099
+Ref: tlmgr allowed-actions = _action1_[,_action2_,...] The value is a comma-separated list (no spaces) of tlmgr actions which are allowed to be executed when tlmgr is invoked in system mode (that is, without --usermode). This allows distributors to include tlmgr in their packaging, but allow only a restricted set of actions that do not interfere with their distro package manager. For native TeX Live installations, it doesn't make sense to set this.184638
+Node: tlmgr CRYPTOGRAPHIC VERIFICATION185502
+Node: tlmgr Configuration of GnuPG invocation187759
+Node: tlmgr USER MODE188433
+Node: tlmgr User mode install191455
+Node: tlmgr User mode backup, restore, remove, update192643
+Node: tlmgr User mode generate, option, paper193089
+Node: tlmgr MULTIPLE REPOSITORIES193433
+Node: tlmgr Pinning195184
+Node: tlmgr GUI FOR TLMGR197163
+Node: tlmgr Main display198830
+Node: tlmgr Display configuration area199082
+Ref: tlmgr Status199443
+Ref: tlmgr Category199607
+Ref: tlmgr Match199793
+Ref: tlmgr Selection199974
+Ref: tlmgr Display configuration buttons200182
+Node: tlmgr Package list area200365
+Ref: tlmgr a checkbox200949
+Ref: tlmgr package name201085
+Ref: tlmgr local revision (and version)201184
+Ref: tlmgr remote revision (and version)201559
+Ref: tlmgr short description201856
+Node: tlmgr Main display action buttons201901
+Ref: tlmgr Update all installed202167
+Ref: tlmgr Update202543
+Ref: tlmgr Install202593
+Ref: tlmgr Remove202783
+Ref: tlmgr Backup202965
+Node: tlmgr Menu bar203134
+Ref: tlmgr tlmgr menu203361
+Ref: tlmgr Options menu203677
+Ref: tlmgr Actions menu204790
+Ref: tlmgr Help menu205242
+Node: tlmgr GUI options205380
+Ref: tlmgr -background _color_205634
+Ref: tlmgr -font " _fontname_ _fontsize_ "205707
+Ref: tlmgr -foreground _color_205877
+Ref: tlmgr -geometry _geomspec_205933
+Ref: tlmgr -xrm _xresource_206133
+Node: tlmgr MACHINE-READABLE OUTPUT206402
+Node: tlmgr Machine-readable update and install output207224
+Ref: tlmgr location-url _location_208520
+Ref: tlmgr total-bytes _count_208748
+Ref: tlmgr _pkgname_209166
+Ref: tlmgr _status_209384
+Ref: tlmgr d209466
+Ref: tlmgr f209530
+Ref: tlmgr u209717
+Ref: tlmgr r209767
+Ref: tlmgr a209894
+Ref: tlmgr i210076
+Ref: tlmgr I210201
+Ref: tlmgr _localrev_210303
+Ref: tlmgr _serverrev_210414
+Ref: tlmgr _size_210530
+Ref: tlmgr _runtime_210703
+Ref: tlmgr _esttot_210773
+Node: tlmgr Machine-readable option output210806
+Node: tlmgr ENVIRONMENT VARIABLES211326
+Ref: tlmgr TEXLIVE_COMPRESSOR211853
+Ref: tlmgr TEXLIVE_DOWNLOADER212725
+Ref: tlmgr TL_DOWNLOAD_PROGRAM212752
+Ref: tlmgr TL_DOWNLOAD_ARGS212776
+Ref: tlmgr TEXLIVE_PREFER_OWN213838
+Node: tlmgr AUTHORS AND COPYRIGHT214678
+Node: Index215080
End Tag Table
+
+
+Local Variables:
+coding: utf-8
+End:
Modified: branches/stable/source/src/doc/tlbuild.texi
===================================================================
--- branches/stable/source/src/doc/tlbuild.texi 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/doc/tlbuild.texi 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,8 +1,8 @@
\input texinfo
@setfilename tlbuild.info
- at set version 2022
- at set month-year May 2022
+ at set version 2023
+ at set month-year February 2023
@set mytitle Building @TeX{} Live (@value{version})
@settitle @value{mytitle}
@@ -15,7 +15,7 @@
This file documents the @TL{} build system and more.
@noindent
-Copyright @copyright{} 2016--2022 Karl Berry.@*
+Copyright @copyright{} 2016--2023 Karl Berry.@*
Copyright @copyright{} 2013--2015 Karl Berry & Peter Breitenlohner.
Permission is granted to make and distribute verbatim copies of this
Modified: branches/stable/source/src/libs/README
===================================================================
--- branches/stable/source/src/libs/README 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/README 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,4 +1,4 @@
-$Id: README 65526 2023-01-12 04:40:09Z kakuto $
+$Id: README 65992 2023-02-20 23:13:30Z kakuto $
Public domain. Originally created by Karl Berry, 2005.
Libraries we compile for TeX Live.
@@ -12,7 +12,7 @@
cairo 1.16.0 - checked 20oct18
http://cairographics.org/releases/
-freetype2 2.12.1 - checked 07may22
+freetype2 2.13.0 - checked 11feb23
http://download.savannah.gnu.org/releases/freetype/
gd 2.3.3 - checked 13sep21
@@ -25,8 +25,8 @@
http://sourceforge.net/projects/silgraphite/files/graphite2/
(requires C++11)
-harfbuzz 6.0.0 - checked 18dec22
- https://github.com/harfbuzz/harfbuzz/releases/tag/6.0.0
+harfbuzz 7.0.1 - checked 21feb23
+ https://github.com/harfbuzz/harfbuzz/releases/tag/7.0.1
icu 70.1 - checked 16jan22
https://github.com/unicode-org/icu/releases/
Modified: branches/stable/source/src/libs/configure
===================================================================
--- branches/stable/source/src/libs/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for TeX Live libs 2023/dev.
+# Generated by GNU Autoconf 2.71 for TeX Live libs 2023.
#
# Report bugs to <tex-k at tug.org>.
#
@@ -610,8 +610,8 @@
# Identity of this package.
PACKAGE_NAME='TeX Live libs'
PACKAGE_TARNAME='tex-live-libs'
-PACKAGE_VERSION='2023/dev'
-PACKAGE_STRING='TeX Live libs 2023/dev'
+PACKAGE_VERSION='2023'
+PACKAGE_STRING='TeX Live libs 2023'
PACKAGE_BUGREPORT='tex-k at tug.org'
PACKAGE_URL=''
@@ -1441,7 +1441,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures TeX Live libs 2023/dev to adapt to many kinds of systems.
+\`configure' configures TeX Live libs 2023 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1512,7 +1512,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of TeX Live libs 2023/dev:";;
+ short | recursive ) echo "Configuration of TeX Live libs 2023:";;
esac
cat <<\_ACEOF
@@ -1555,11 +1555,11 @@
--enable-tex-synctex build TeX with SyncTeX support
--enable-etex compile and install e-TeX
--disable-etex-synctex build e-TeX without SyncTeX support
- --disable-ptex do not compile and install pTeX
+ --enable-ptex compile and install pTeX
--disable-ptex-synctex build pTeX without SyncTeX support
--disable-eptex do not compile and install e-pTeX
--disable-eptex-synctex build e-pTeX without SyncTeX support
- --disable-uptex do not compile and install upTeX
+ --enable-uptex compile and install upTeX
--disable-uptex-synctex build upTeX without SyncTeX support
--disable-euptex do not compile and install e-upTeX
--disable-euptex-synctex build e-upTeX without SyncTeX support
@@ -1804,7 +1804,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-TeX Live libs configure 2023/dev
+TeX Live libs configure 2023
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -1927,7 +1927,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by TeX Live libs $as_me 2023/dev, which was
+It was created by TeX Live libs $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -4480,7 +4480,7 @@
yes | no) :
;; #(
*) :
- enable_ptex=yes ;;
+ enable_ptex=no ;;
esac
# Check whether --enable-ptex-synctex was given.
@@ -4524,7 +4524,7 @@
yes | no) :
;; #(
*) :
- enable_uptex=yes ;;
+ enable_uptex=no ;;
esac
# Check whether --enable-uptex-synctex was given.
@@ -7016,7 +7016,7 @@
# Define the identity of the package.
PACKAGE='tex-live-libs'
- VERSION='2023/dev'
+ VERSION='2023'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -8051,7 +8051,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by TeX Live libs $as_me 2023/dev, which was
+This file was extended by TeX Live libs $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -8110,7 +8110,7 @@
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-TeX Live libs config.status 2023/dev
+TeX Live libs config.status 2023
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
Modified: branches/stable/source/src/libs/libpng/ChangeLog
===================================================================
--- branches/stable/source/src/libs/libpng/ChangeLog 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/libpng/ChangeLog 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,3 +1,12 @@
+2023-01-22 Karl Berry <karl at freefriends.org>
+
+ * configure.ac (KPSE_CANONICAL_HOST): call this,
+ since we use $host_cpu in the optimization checks.
+ Else could be determined wrong. Report from Dick Koch,
+ karl mail 22 Jan 2023 00:43:11.
+ (PNG_ARM_NEON, PNG_POWERPC_VSX): report results;
+ also sync comments with upstream (trivial typos).
+
2022-11-21 Akira Kakuto <kakuto at jcom.zaq.ne.jp>
Import libpng-1.6.39.
Modified: branches/stable/source/src/libs/libpng/Makefile.in
===================================================================
--- branches/stable/source/src/libs/libpng/Makefile.in 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/libpng/Makefile.in 2023-02-21 22:38:24 UTC (rev 903)
@@ -86,6 +86,8 @@
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
+build_triplet = @build@
+host_triplet = @host@
@PNG_ARM_NEON_TRUE at am__append_1 = @LIBPNG_TREE@/arm/arm_init.c\
@PNG_ARM_NEON_TRUE@ @LIBPNG_TREE@/arm/filter_neon.S @LIBPNG_TREE@/arm/filter_neon_intrinsics.c \
@PNG_ARM_NEON_TRUE@ @LIBPNG_TREE@/arm/palette_neon_intrinsics.c
@@ -454,6 +456,8 @@
$(srcdir)/../../am/rebuild.am $(srcdir)/../../am/reconfig.am \
$(srcdir)/Makefile.in $(srcdir)/config.h.in \
$(top_srcdir)/../../build-aux/compile \
+ $(top_srcdir)/../../build-aux/config.guess \
+ $(top_srcdir)/../../build-aux/config.sub \
$(top_srcdir)/../../build-aux/depcomp \
$(top_srcdir)/../../build-aux/install-sh \
$(top_srcdir)/../../build-aux/missing \
@@ -580,7 +584,11 @@
am__tar = @am__tar@
am__untar = @am__untar@
bindir = @bindir@
+build = @build@
build_alias = @build_alias@
+build_cpu = @build_cpu@
+build_os = @build_os@
+build_vendor = @build_vendor@
builddir = @builddir@
datadir = @datadir@
datarootdir = @datarootdir@
@@ -587,7 +595,11 @@
docdir = @docdir@
dvidir = @dvidir@
exec_prefix = @exec_prefix@
+host = @host@
host_alias = @host_alias@
+host_cpu = @host_cpu@
+host_os = @host_os@
+host_vendor = @host_vendor@
htmldir = @htmldir@
includedir = @includedir@
infodir = @infodir@
Modified: branches/stable/source/src/libs/libpng/aclocal.m4
===================================================================
--- branches/stable/source/src/libs/libpng/aclocal.m4 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/libpng/aclocal.m4 2023-02-21 22:38:24 UTC (rev 903)
@@ -128,6 +128,43 @@
am_aux_dir=`cd "$ac_aux_dir" && pwd`
])
+# AM_COND_IF -*- Autoconf -*-
+
+# Copyright (C) 2008-2021 Free Software Foundation, Inc.
+#
+# This file is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# _AM_COND_IF
+# _AM_COND_ELSE
+# _AM_COND_ENDIF
+# --------------
+# These macros are only used for tracing.
+m4_define([_AM_COND_IF])
+m4_define([_AM_COND_ELSE])
+m4_define([_AM_COND_ENDIF])
+
+# AM_COND_IF(COND, [IF-TRUE], [IF-FALSE])
+# ---------------------------------------
+# If the shell condition COND is true, execute IF-TRUE, otherwise execute
+# IF-FALSE. Allow automake to learn about conditional instantiating macros
+# (the AC_CONFIG_FOOS).
+AC_DEFUN([AM_COND_IF],
+[m4_ifndef([_AM_COND_VALUE_$1],
+ [m4_fatal([$0: no such condition "$1"])])dnl
+_AM_COND_IF([$1])dnl
+if test -z "$$1_TRUE"; then :
+ m4_n([$2])[]dnl
+m4_ifval([$3],
+[_AM_COND_ELSE([$1])dnl
+else
+ $3
+])dnl
+_AM_COND_ENDIF([$1])dnl
+fi[]dnl
+])
+
# AM_CONDITIONAL -*- Autoconf -*-
# Copyright (C) 1997-2021 Free Software Foundation, Inc.
Modified: branches/stable/source/src/libs/libpng/configure
===================================================================
--- branches/stable/source/src/libs/libpng/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/libpng/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -676,6 +676,14 @@
CCASDEPMODE
CCASFLAGS
CCAS
+host_os
+host_vendor
+host_cpu
+host
+build_os
+build_vendor
+build_cpu
+build
WARNING_CFLAGS
am__fastdepCC_FALSE
am__fastdepCC_TRUE
@@ -1400,6 +1408,10 @@
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names
+
+System types:
+ --build=BUILD configure for building on BUILD [guessed]
+ --host=HOST cross-compile to build programs to run on HOST [BUILD]
_ACEOF
fi
@@ -2433,7 +2445,7 @@
as_fn_append ac_header_c_list " unistd.h unistd_h HAVE_UNISTD_H"
# Auxiliary files required by this configure script.
-ac_aux_files="compile missing install-sh"
+ac_aux_files="config.guess config.sub compile missing install-sh"
# Locations in which to look for auxiliary files.
ac_aux_dir_candidates="${srcdir}/../../build-aux"
@@ -4601,6 +4613,89 @@
+# Because we use $host_cpu below.
+
+
+ # Make sure we can run config.sub.
+$SHELL "${ac_aux_dir}config.sub" sun4 >/dev/null 2>&1 ||
+ as_fn_error $? "cannot run $SHELL ${ac_aux_dir}config.sub" "$LINENO" 5
+
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking build system type" >&5
+printf %s "checking build system type... " >&6; }
+if test ${ac_cv_build+y}
+then :
+ printf %s "(cached) " >&6
+else $as_nop
+ ac_build_alias=$build_alias
+test "x$ac_build_alias" = x &&
+ ac_build_alias=`$SHELL "${ac_aux_dir}config.guess"`
+test "x$ac_build_alias" = x &&
+ as_fn_error $? "cannot guess build type; you must specify one" "$LINENO" 5
+ac_cv_build=`$SHELL "${ac_aux_dir}config.sub" $ac_build_alias` ||
+ as_fn_error $? "$SHELL ${ac_aux_dir}config.sub $ac_build_alias failed" "$LINENO" 5
+
+fi
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_build" >&5
+printf "%s\n" "$ac_cv_build" >&6; }
+case $ac_cv_build in
+*-*-*) ;;
+*) as_fn_error $? "invalid value of canonical build" "$LINENO" 5;;
+esac
+build=$ac_cv_build
+ac_save_IFS=$IFS; IFS='-'
+set x $ac_cv_build
+shift
+build_cpu=$1
+build_vendor=$2
+shift; shift
+# Remember, the first character of IFS is used to create $*,
+# except with old shells:
+build_os=$*
+IFS=$ac_save_IFS
+case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac
+
+
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking host system type" >&5
+printf %s "checking host system type... " >&6; }
+if test ${ac_cv_host+y}
+then :
+ printf %s "(cached) " >&6
+else $as_nop
+ if test "x$host_alias" = x; then
+ ac_cv_host=$ac_cv_build
+else
+ ac_cv_host=`$SHELL "${ac_aux_dir}config.sub" $host_alias` ||
+ as_fn_error $? "$SHELL ${ac_aux_dir}config.sub $host_alias failed" "$LINENO" 5
+fi
+
+fi
+{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_host" >&5
+printf "%s\n" "$ac_cv_host" >&6; }
+case $ac_cv_host in
+*-*-*) ;;
+*) as_fn_error $? "invalid value of canonical host" "$LINENO" 5;;
+esac
+host=$ac_cv_host
+ac_save_IFS=$IFS; IFS='-'
+set x $ac_cv_host
+shift
+host_cpu=$1
+host_vendor=$2
+shift; shift
+# Remember, the first character of IFS is used to create $*,
+# except with old shells:
+host_os=$*
+IFS=$ac_save_IFS
+case $host_os in *\ *) host_os=`echo "$host_os" | sed 's/ /-/g'`;; esac
+
+
+if test "x$host_alias" != x && test "x$build_alias" = x
+then :
+ as_fn_error $? "when cross-compiling you must specify both --host and --build." "$LINENO" 5
+fi
+eval kpse_build_alias=\${build_alias-$build}
+
+
ac_config_headers="$ac_config_headers config.h"
@@ -6582,7 +6677,7 @@
printf "%s\n" "#define PNG_ARM_NEON_OPT 0" >>confdefs.h
# Prevent inclusion of the assembler files below:
- enable_arm_neon=no;;
+ enable_arm_neon=no ;;
check)
printf "%s\n" "#define PNG_ARM_NEON_CHECK_SUPPORTED /**/" >>confdefs.h
@@ -6607,14 +6702,14 @@
fi
-# Add ARM specific files to all builds where the host_cpu is arm ('arm*') or
-# where ARM optimizations were explicitly requested (this allows a fallback if a
-# future host CPU does not match 'arm*')
+# Add ARM-specific files to all builds where the host_cpu is arm ('arm*') or
+# where ARM optimizations were explicitly requested (this allows a fallback
+# if a future host CPU does not match 'arm*')
if test "$enable_arm_neon" != 'no' &&
case "$host_cpu" in
- arm*|aarch64*) :;;
- *) test "$enable_arm_neon" != '';;
+ arm*|aarch64*) : ;;
+ *) test "$enable_arm_neon" != '' ;;
esac; then
PNG_ARM_NEON_TRUE=
PNG_ARM_NEON_FALSE='#'
@@ -6624,6 +6719,14 @@
fi
+if test -z "$PNG_ARM_NEON_TRUE"; then :
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: arm_neon opts on (host_cpu=$host_cpu)" >&5
+printf "%s\n" "$as_me: arm_neon opts on (host_cpu=$host_cpu)" >&6;}
+else
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: arm_neon opts off (host_cpu=$host_cpu)" >&5
+printf "%s\n" "$as_me: arm_neon opts off (host_cpu=$host_cpu)" >&6;}
+fi
+
# emacs-page
# PowerPC
# ===
@@ -6639,8 +6742,8 @@
printf "%s\n" "#define PNG_POWERPC_VSX_OPT 0" >>confdefs.h
- # Prevent inclusion of the platform specific files below:
- enable_powerpc_vsx=no;;
+ # Prevent inclusion of the platform-specific files below:
+ enable_powerpc_vsx=no ;;
check)
printf "%s\n" "#define PNG_POWERPC_VSX_CHECK_SUPPORTED /**/" >>confdefs.h
@@ -6659,10 +6762,10 @@
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: --enable-powerpc-vsx: please specify 'check' or 'api', if
you want the optimizations unconditionally pass '-maltivec -mvsx'
- or '-mcpu=power8'to the compiler." >&5
+ or '-mcpu=power8' to the compiler." >&5
printf "%s\n" "$as_me: WARNING: --enable-powerpc-vsx: please specify 'check' or 'api', if
you want the optimizations unconditionally pass '-maltivec -mvsx'
- or '-mcpu=power8'to the compiler." >&2;};;
+ or '-mcpu=power8' to the compiler." >&2;};;
*)
as_fn_error $? "--enable-powerpc-vsx=${enable_powerpc_vsx}: invalid value" "$LINENO" 5
esac
@@ -6669,13 +6772,13 @@
fi
-# Add PowerPC specific files to all builds where the host_cpu is powerpc('powerpc*') or
-# where POWERPC optimizations were explicitly requested (this allows a fallback if a
-# future host CPU does not match 'powerpc*')
+# Add PowerPC-specific files to all builds where $host_cpu is powerpc('powerpc*')
+# or where PowerPC optimizations were explicitly requested (this allows a fallback
+# if a future host CPU does not match 'powerpc*')
if test "$enable_powerpc_vsx" != 'no' &&
case "$host_cpu" in
- powerpc*|ppc64*) :;;
+ powerpc*|ppc64*) : ;;
esac; then
PNG_POWERPC_VSX_TRUE=
PNG_POWERPC_VSX_FALSE='#'
@@ -6684,8 +6787,13 @@
PNG_POWERPC_VSX_FALSE=
fi
-
-
+if test -z "$PNG_POWERPC_VSX_TRUE"; then :
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: powerpc_vsx opts on (host_cpu=$host_cpu)" >&5
+printf "%s\n" "$as_me: powerpc_vsx opts on (host_cpu=$host_cpu)" >&6;}
+else
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: powerpc_vsx opts off (host_cpu=$host_cpu)" >&5
+printf "%s\n" "$as_me: powerpc_vsx opts off (host_cpu=$host_cpu)" >&6;}
+fi
ac_config_files="$ac_config_files Makefile include/Makefile"
Modified: branches/stable/source/src/libs/libpng/configure.ac
===================================================================
--- branches/stable/source/src/libs/libpng/configure.ac 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/libpng/configure.ac 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,7 +1,7 @@
-dnl $Id: configure.ac 54291 2020-03-14 16:03:19Z karl $
+dnl $Id: configure.ac 65609 2023-01-23 02:20:55Z karl $
dnl Process this file with autoconf to produce a configure script.
dnl
-dnl Copyright 2016-2020 Karl Berry <tex-live at tug.org>
+dnl Copyright 2016-2023 Karl Berry <tex-live at tug.org>
dnl Copyright 2009-2015 Peter Breitenlohner <tex-live at tug.org>
dnl
dnl This file is free software; the copyright holder
@@ -17,6 +17,9 @@
KPSE_BASIC([libpng])
+# Because we use $host_cpu below.
+KPSE_CANONICAL_HOST
+
AC_CONFIG_HEADERS([config.h])
AC_PROG_CC
@@ -96,7 +99,7 @@
AC_DEFINE([PNG_ARM_NEON_OPT], [0],
[Disable ARM Neon optimizations])
# Prevent inclusion of the assembler files below:
- enable_arm_neon=no;;
+ enable_arm_neon=no ;;
check)
AC_DEFINE([PNG_ARM_NEON_CHECK_SUPPORTED], [],
[Check for ARM Neon support at run-time]);;
@@ -113,17 +116,22 @@
AC_MSG_ERROR([--enable-arm-neon=${enable_arm_neon}: invalid value])
esac])
-# Add ARM specific files to all builds where the host_cpu is arm ('arm*') or
-# where ARM optimizations were explicitly requested (this allows a fallback if a
-# future host CPU does not match 'arm*')
+# Add ARM-specific files to all builds where the host_cpu is arm ('arm*') or
+# where ARM optimizations were explicitly requested (this allows a fallback
+# if a future host CPU does not match 'arm*')
AM_CONDITIONAL([PNG_ARM_NEON],
[test "$enable_arm_neon" != 'no' &&
case "$host_cpu" in
- arm*|aarch64*) :;;
- *) test "$enable_arm_neon" != '';;
+ arm*|aarch64*) : ;;
+ *) test "$enable_arm_neon" != '' ;;
esac])
+AM_COND_IF([PNG_ARM_NEON],
+ AC_MSG_NOTICE([[arm_neon opts on (host_cpu=$host_cpu)]]),
+ AC_MSG_NOTICE([[arm_neon opts off (host_cpu=$host_cpu)]]),
+)
+
# emacs-page
# PowerPC
# ===
@@ -142,8 +150,8 @@
# disable the default enabling on __ppc64__ systems:
AC_DEFINE([PNG_POWERPC_VSX_OPT], [0],
[Disable POWERPC VSX optimizations])
- # Prevent inclusion of the platform specific files below:
- enable_powerpc_vsx=no;;
+ # Prevent inclusion of the platform-specific files below:
+ enable_powerpc_vsx=no ;;
check)
AC_DEFINE([PNG_POWERPC_VSX_CHECK_SUPPORTED], [],
[Check for POWERPC VSX support at run-time])
@@ -157,22 +165,24 @@
[Enable POWERPC VSX optimizations])
AC_MSG_WARN([--enable-powerpc-vsx: please specify 'check' or 'api', if]
[you want the optimizations unconditionally pass '-maltivec -mvsx']
- [or '-mcpu=power8'to the compiler.]);;
+ [or '-mcpu=power8' to the compiler.]);;
*)
AC_MSG_ERROR([--enable-powerpc-vsx=${enable_powerpc_vsx}: invalid value])
esac])
-# Add PowerPC specific files to all builds where the host_cpu is powerpc('powerpc*') or
-# where POWERPC optimizations were explicitly requested (this allows a fallback if a
-# future host CPU does not match 'powerpc*')
+# Add PowerPC-specific files to all builds where $host_cpu is powerpc('powerpc*')
+# or where PowerPC optimizations were explicitly requested (this allows a fallback
+# if a future host CPU does not match 'powerpc*')
AM_CONDITIONAL([PNG_POWERPC_VSX],
[test "$enable_powerpc_vsx" != 'no' &&
case "$host_cpu" in
- powerpc*|ppc64*) :;;
+ powerpc*|ppc64*) : ;;
esac])
-
-
+AM_COND_IF([PNG_POWERPC_VSX],
+ AC_MSG_NOTICE([[powerpc_vsx opts on (host_cpu=$host_cpu)]]),
+ AC_MSG_NOTICE([[powerpc_vsx opts off (host_cpu=$host_cpu)]]),
+)
AC_CONFIG_FILES([Makefile include/Makefile])
AC_OUTPUT
Modified: branches/stable/source/src/libs/libpng/include/Makefile.in
===================================================================
--- branches/stable/source/src/libs/libpng/include/Makefile.in 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/libs/libpng/include/Makefile.in 2023-02-21 22:38:24 UTC (rev 903)
@@ -85,6 +85,8 @@
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
+build_triplet = @build@
+host_triplet = @host@
subdir = include
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/../../m4/kpse-common.m4 \
@@ -194,7 +196,11 @@
am__tar = @am__tar@
am__untar = @am__untar@
bindir = @bindir@
+build = @build@
build_alias = @build_alias@
+build_cpu = @build_cpu@
+build_os = @build_os@
+build_vendor = @build_vendor@
builddir = @builddir@
datadir = @datadir@
datarootdir = @datarootdir@
@@ -201,7 +207,11 @@
docdir = @docdir@
dvidir = @dvidir@
exec_prefix = @exec_prefix@
+host = @host@
host_alias = @host_alias@
+host_cpu = @host_cpu@
+host_os = @host_os@
+host_vendor = @host_vendor@
htmldir = @htmldir@
includedir = @includedir@
infodir = @infodir@
Modified: branches/stable/source/src/texk/README
===================================================================
--- branches/stable/source/src/texk/README 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/README 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,4 +1,4 @@
-$Id: README 65276 2022-12-15 12:41:31Z hironobu $
+$Id: README 65770 2023-02-09 21:26:50Z karl $
Copyright 2006-2023 TeX Users Group.
You may freely use, modify and/or distribute this file.
@@ -63,7 +63,7 @@
dvipsk - maintained here, by us
-dvisvgm 3.0.1 - checked 19jan23
+dvisvgm 3.0.2 - checked 1feb23
https://dvisvgm.de/Downloads/
https://github.com/mgieseki/dvisvgm
https://ctan.org/pkg/dvisvgm
Modified: branches/stable/source/src/texk/configure
===================================================================
--- branches/stable/source/src/texk/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for TeX Live texk 2023/dev.
+# Generated by GNU Autoconf 2.71 for TeX Live texk 2023.
#
# Report bugs to <tex-live at tug.org>.
#
@@ -610,8 +610,8 @@
# Identity of this package.
PACKAGE_NAME='TeX Live texk'
PACKAGE_TARNAME='tex-live-texk'
-PACKAGE_VERSION='2023/dev'
-PACKAGE_STRING='TeX Live texk 2023/dev'
+PACKAGE_VERSION='2023'
+PACKAGE_STRING='TeX Live texk 2023'
PACKAGE_BUGREPORT='tex-live at tug.org'
PACKAGE_URL=''
@@ -1441,7 +1441,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures TeX Live texk 2023/dev to adapt to many kinds of systems.
+\`configure' configures TeX Live texk 2023 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1512,7 +1512,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of TeX Live texk 2023/dev:";;
+ short | recursive ) echo "Configuration of TeX Live texk 2023:";;
esac
cat <<\_ACEOF
@@ -1555,11 +1555,11 @@
--enable-tex-synctex build TeX with SyncTeX support
--enable-etex compile and install e-TeX
--disable-etex-synctex build e-TeX without SyncTeX support
- --disable-ptex do not compile and install pTeX
+ --enable-ptex compile and install pTeX
--disable-ptex-synctex build pTeX without SyncTeX support
--disable-eptex do not compile and install e-pTeX
--disable-eptex-synctex build e-pTeX without SyncTeX support
- --disable-uptex do not compile and install upTeX
+ --enable-uptex compile and install upTeX
--disable-uptex-synctex build upTeX without SyncTeX support
--disable-euptex do not compile and install e-upTeX
--disable-euptex-synctex build e-upTeX without SyncTeX support
@@ -1804,7 +1804,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-TeX Live texk configure 2023/dev
+TeX Live texk configure 2023
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -1927,7 +1927,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by TeX Live texk $as_me 2023/dev, which was
+It was created by TeX Live texk $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -4480,7 +4480,7 @@
yes | no) :
;; #(
*) :
- enable_ptex=yes ;;
+ enable_ptex=no ;;
esac
# Check whether --enable-ptex-synctex was given.
@@ -4524,7 +4524,7 @@
yes | no) :
;; #(
*) :
- enable_uptex=yes ;;
+ enable_uptex=no ;;
esac
# Check whether --enable-uptex-synctex was given.
@@ -7016,7 +7016,7 @@
# Define the identity of the package.
PACKAGE='tex-live-texk'
- VERSION='2023/dev'
+ VERSION='2023'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -8129,7 +8129,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by TeX Live texk $as_me 2023/dev, which was
+This file was extended by TeX Live texk $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -8188,7 +8188,7 @@
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-TeX Live texk config.status 2023/dev
+TeX Live texk config.status 2023
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
Modified: branches/stable/source/src/texk/kpathsea/ChangeLog
===================================================================
--- branches/stable/source/src/texk/kpathsea/ChangeLog 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/ChangeLog 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,3 +1,21 @@
+2023-02-19 TANAKA Takuji <ttk at t-lab.opal.ne.jp>
+
+ * texmf.cnf (BIBINPUTS.bibtexu, BSTINPUTS.bibtexu):
+ New definition for BibTeXu which can import Japanese inputs
+ for pBibTeX in UTF-8.
+
+2023-02-18 Karl Berry <karl at tug.org>
+
+ * texmf.cnf (TEXMFVAR, TEXMFCONFIG, doc): 2023.
+
+2023-02-09 Karl Berry <karl at freefriends.org>
+
+ * version.ac (kpse_dev): no more /dev.
+ * NEWS,
+ * doc/kpathsea.texi,
+ * kpsewhich.c,
+ * texmf.cnf: copyright 2023.
+
2022-12-20 Karl Berry <karl at freefriends.org>
* doc/kpathsea.texi (Supported file formats): add .lua (LUAINPUTS).
Modified: branches/stable/source/src/texk/kpathsea/NEWS
===================================================================
--- branches/stable/source/src/texk/kpathsea/NEWS 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/NEWS 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,10 @@
-$Id: NEWS 61654 2022-01-18 22:17:46Z karl $
+$Id: NEWS 65770 2023-02-09 21:26:50Z karl $
This file records noteworthy changes. (Public domain.)
+6.3.5 (for TeX Live 2023)
+* Support guessing input file encodings for Unix-ish platforms, as on
+ Windows; enabled for (e)p(la)tex, pbibtex, mendex.
+
6.3.4 (for TeX Live 2022)
* First return path from kpsewhich -all is now the same as non-all.
(Internally, str_list_uniqify retains ordering.)
Modified: branches/stable/source/src/texk/kpathsea/c-auto.in
===================================================================
--- branches/stable/source/src/texk/kpathsea/c-auto.in 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/c-auto.in 2023-02-21 22:38:24 UTC (rev 903)
@@ -23,7 +23,7 @@
#define KPATHSEA_C_AUTO_H
/* kpathsea: the version string. */
-#define KPSEVERSION "kpathsea version 6.3.5/dev"
+#define KPSEVERSION "kpathsea version 6.3.5"
/* Define to 1 if the `closedir' function returns void instead of int. */
#undef CLOSEDIR_VOID
Modified: branches/stable/source/src/texk/kpathsea/configure
===================================================================
--- branches/stable/source/src/texk/kpathsea/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for Kpathsea 6.3.5/dev.
+# Generated by GNU Autoconf 2.71 for Kpathsea 6.3.5.
#
# Report bugs to <tex-k at tug.org>.
#
@@ -621,8 +621,8 @@
# Identity of this package.
PACKAGE_NAME='Kpathsea'
PACKAGE_TARNAME='kpathsea'
-PACKAGE_VERSION='6.3.5/dev'
-PACKAGE_STRING='Kpathsea 6.3.5/dev'
+PACKAGE_VERSION='6.3.5'
+PACKAGE_STRING='Kpathsea 6.3.5'
PACKAGE_BUGREPORT='tex-k at tug.org'
PACKAGE_URL=''
@@ -1376,7 +1376,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures Kpathsea 6.3.5/dev to adapt to many kinds of systems.
+\`configure' configures Kpathsea 6.3.5 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1447,7 +1447,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of Kpathsea 6.3.5/dev:";;
+ short | recursive ) echo "Configuration of Kpathsea 6.3.5:";;
esac
cat <<\_ACEOF
@@ -1575,7 +1575,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-Kpathsea configure 6.3.5/dev
+Kpathsea configure 6.3.5
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -2331,7 +2331,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by Kpathsea $as_me 6.3.5/dev, which was
+It was created by Kpathsea $as_me 6.3.5, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -3091,7 +3091,7 @@
-KPSEVERSION=6.3.5/dev
+KPSEVERSION=6.3.5
KPSE_LT_VERSINFO=9:5:3
@@ -3098,7 +3098,7 @@
- WEB2CVERSION=" (TeX Live 2023/dev)"
+ WEB2CVERSION=" (TeX Live 2023)"
am__api_version='1.16'
@@ -8663,7 +8663,7 @@
# Define the identity of the package.
PACKAGE='kpathsea'
- VERSION='6.3.5/dev'
+ VERSION='6.3.5'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -15416,7 +15416,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by Kpathsea $as_me 6.3.5/dev, which was
+This file was extended by Kpathsea $as_me 6.3.5, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -15484,7 +15484,7 @@
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-Kpathsea config.status 6.3.5/dev
+Kpathsea config.status 6.3.5
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
Modified: branches/stable/source/src/texk/kpathsea/doc/kpathsea.info
===================================================================
--- branches/stable/source/src/texk/kpathsea/doc/kpathsea.info 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/doc/kpathsea.info 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,9 +1,9 @@
-This is kpathsea.info, produced by makeinfo version 7.0.1 from
+This is kpathsea.info, produced by makeinfo version 6.5 from
kpathsea.texi.
This file documents the Kpathsea library for path searching.
- Copyright © 1996–2022 Karl Berry & Olaf Weber.
+ Copyright (C) 1996-2023 Karl Berry & Olaf Weber.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
@@ -37,7 +37,7 @@
****************
This manual documents the Kpathsea library for path searching. It
-corresponds to version 6.3.4, released in December 2022.
+corresponds to version 6.3.5, released in February 2023.
* Menu:
@@ -61,10 +61,10 @@
1 Introduction
**************
-This manual corresponds to version 6.3.4 of the Kpathsea library,
-released in December 2022.
+This manual corresponds to version 6.3.5 of the Kpathsea library,
+released in February 2023.
- The library’s fundamental purpose is to return a filename from a list
+ The library's fundamental purpose is to return a filename from a list
of directories specified by the user, similar to what shells do when
looking up program names to execute.
@@ -71,11 +71,11 @@
The following software, all of which is maintained in parallel, uses
this library:
- • Dviljk (see the ‘dvilj’ man page)
- • Dvipsk (*note (dvips)::)
- • GNU font utilities (*note (fontu)::)
- • Web2c (*note (web2c)::)
- • Xdvik (see the ‘xdvi’ man page)
+ * Dviljk (see the 'dvilj' man page)
+ * Dvipsk (*note (dvips)::)
+ * GNU font utilities (*note (fontu)::)
+ * Web2c (*note (web2c)::)
+ * Xdvik (see the 'xdvi' man page)
Other software that we do not maintain also uses it.
@@ -98,8 +98,8 @@
<https://gnu.org/licenses>.
If you know enough about TeX to be reading this manual, then you (or
-your institution) should consider joining the TeX Users Group (if you’re
-already a member, thanks!). TUG produces the periodical ‘TUGboat’,
+your institution) should consider joining the TeX Users Group (if you're
+already a member, thanks!). TUG produces the periodical 'TUGboat',
sponsors an annual meeting and publishes the proceedings, and arranges
courses on TeX for all levels of users throughout the world. See
<https://tug.org> for information.
@@ -116,8 +116,8 @@
This section is for those people who are curious about how the library
came about. If you like to read historical accounts of software, we
-urge you to seek out the GNU Autoconf manual and the “Errors of TeX”
-paper by Don Knuth, published in his book ‘Digital Typography’, among
+urge you to seek out the GNU Autoconf manual and the "Errors of TeX"
+paper by Don Knuth, published in his book 'Digital Typography', among
other places.
[Karl writes.] My first ChangeLog entry for Web2c seems to be
@@ -125,32 +125,32 @@
Tim Morgan and I were jointly maintaining it for a time. (I should
mention here that Tim had made Web2c into a real distribution long
before I had ever used it or even heard of it, and Tom Rokicki did the
-original implementation. When I started, I was using ‘pxp’ and ‘pc’ on
-VAX 11/750’s and the hot new Sun 2 machines.)
+original implementation. When I started, I was using 'pxp' and 'pc' on
+VAX 11/750's and the hot new Sun 2 machines.)
It must have been later in 1990 and 1991 that I started working on
-‘TeX for the Impatient’. Dvips, Xdvi, Web2c, and the GNU fontutils
+'TeX for the Impatient'. Dvips, Xdvi, Web2c, and the GNU fontutils
(which I was also writing at the time) all used different environment
variables, and, more importantly, had different bugs in their path
searching. This became extremely painful, as I was stressing everything
to the limit working on the book. I also desperately wanted to
-implement subdirectory searching, since I couldn’t stand putting
-everything in one big directory, and also couldn’t stand having to
-explicitly specify ‘cm’, ‘pandora’, ... in a path.
+implement subdirectory searching, since I couldn't stand putting
+everything in one big directory, and also couldn't stand having to
+explicitly specify 'cm', 'pandora', ... in a path.
In the first incarnation, I just hacked separately on each
-program—that was the original subdirectory searching code in both Xdvi
+program--that was the original subdirectory searching code in both Xdvi
and Dvips. That is, I tried to go with the flow in each program, rather
-than changing the program’s calling sequences to conform to new
+than changing the program's calling sequences to conform to new
routines.
Then, as bugs inevitably appeared, I found I was fixing the same
thing three times (Web2c and fontutils were already sharing code, since
-I maintained both of those—there was no Dvipsk or Xdvik or Dviljk at
+I maintained both of those--there was no Dvipsk or Xdvik or Dviljk at
this point). After a while, I finally started sharing source files.
-They weren’t yet a library, though. I just kept things up to date with
+They weren't yet a library, though. I just kept things up to date with
shell scripts. (I was developing on a 386 running ISC 2.2 at the time,
-and so didn’t have symbolic links. An awful experience.)
+and so didn't have symbolic links. An awful experience.)
The ChangeLogs for Xdvik and Dvipsk record initial releases of those
distributions in May and June 1992. I think it was because I was tired
@@ -159,7 +159,7 @@
MacKenzie and others, and I was adapting it to TeX and friends.
I started to make a separate library that other programs could link
-with on my birthday in April 1993, according to the ChangeLog. I don’t
+with on my birthday in April 1993, according to the ChangeLog. I don't
remember exactly why I finally took the time to make it a separate
library; a conversation with david zuhn initiated it. Just seemed like
it was time.
@@ -166,7 +166,7 @@
Dviljk got started in March 1994 after I bought a Laserjet 4.
(Kpathsea work got suspended while Norm Walsh and I, with Gustaf
-Neumann’s help, implemented a way for TeX to get at all those neat
+Neumann's help, implemented a way for TeX to get at all those neat
builtin LJ4 fonts ... such a treat to have something to typeset in
besides Palatino!)
@@ -175,11 +175,11 @@
initial goals by Thomas Esser and others. I then started to integrate
Web2c with Kpathsea. After the release of a stable Web2c, I hope to be
able to stop development, and turn most of my attention back to making
-fonts for GNU. (Always assuming Micros**t hasn’t completely obliterated
-Unix by then, or that software patents haven’t stopped software
+fonts for GNU. (Always assuming Micros**t hasn't completely obliterated
+Unix by then, or that software patents haven't stopped software
development by anybody smaller than a company with a
million-dollar-a-year legal budget. Which is actually what I think is
-likely to happen, but that’s another story...)
+likely to happen, but that's another story...)
[Olaf writes.] At the end of 1997, Unix is still alive and kicking,
individuals still develop software, and Web2c development still
@@ -186,7 +186,7 @@
continues. Karl had been looking for some time for someone to take up
part of the burden, and I volunteered.
- [Karl writes again.] Indeed, time goes on. As of 2006 or so, Olaf’s
+ [Karl writes again.] Indeed, time goes on. As of 2006 or so, Olaf's
available time for Kpathsea was reduced, and I started taking overall
care of it again, although I did not do any significant new development.
In 2009, Taco Hoekwater implemented a major rearrangement to make the
@@ -198,7 +198,7 @@
File: kpathsea.info, Node: unixtex.ftp, Next: Security, Prev: Introduction, Up: Top
-2 ‘unixtex.ftp’: Obtaining TeX
+2 'unixtex.ftp': Obtaining TeX
******************************
This is <ftp://tug.org/tex/unixtex.ftp>, a.k.a.
@@ -216,13 +216,13 @@
part of TeX Live.
The host ftp.cs.stanford.edu is the original source for the files for
-which Donald Knuth is directly responsible: ‘tex.web’, ‘plain.tex’, etc.
+which Donald Knuth is directly responsible: 'tex.web', 'plain.tex', etc.
However, unless you want to undertake the project of building your TeX
system from scratch, it is more reliable and less work to retrieve these
files as part of a larger package.
In any case, the Stanford ftp site is not the canonical source for
-anything except what was created as part of Knuth’s original TeX, so do
+anything except what was created as part of Knuth's original TeX, so do
not rely on any other files available there being up-to-date. The best
place to check for up-to-date files is CTAN (the Comprehensive TeX
Archive Network), <https://ctan.org>.
@@ -234,25 +234,25 @@
**********
None of the programs in the TeX system require any special system
-privileges, so there’s no first-level security concern of people gaining
+privileges, so there's no first-level security concern of people gaining
illegitimate root access.
A TeX document, however, can write to arbitrary files, e.g.,
-‘~/.rhosts’, and thus an unwitting user who runs TeX on a random
+'~/.rhosts', and thus an unwitting user who runs TeX on a random
document is vulnerable to a trojan horse attack. This loophole is
closed by default, but you can be permissive if you so desire in
-‘texmf.cnf’. *Note (web2c)tex invocation::. MetaPost has the same
+'texmf.cnf'. *Note (web2c)tex invocation::. MetaPost has the same
issue.
Dvips, Xdvi, and TeX can also execute shell commands under some
-circumstances. To disable this, see the ‘-R’ option in *note
+circumstances. To disable this, see the '-R' option in *note
(dvips)Option details::, the xdvi man page, and *note (web2c)tex
invocation::, respectively.
- Another security issue arises because it’s very useful—almost
-necessary—to make arbitrary fonts on user demand with ‘mktexpk’ and
-friends. Where do these files get installed? By default, the ‘mktexpk’
-distributed with Kpathsea assumes a world-writable ‘/var/tmp’ directory;
+ Another security issue arises because it's very useful--almost
+necessary--to make arbitrary fonts on user demand with 'mktexpk' and
+friends. Where do these files get installed? By default, the 'mktexpk'
+distributed with Kpathsea assumes a world-writable '/var/tmp' directory;
this is a simple and convenient approach, but it may not suit your
situation because it means that a local cache of fonts is created on
every machine.
@@ -259,27 +259,27 @@
To avoid this duplication, many people consider a shared, globally
writable font tree desirable, in spite of the potential security
-problems. To do this you should change the value of ‘VARTEXFONTS’ in
-‘texmf.cnf’ to refer to some globally known directory. *Note mktex
+problems. To do this you should change the value of 'VARTEXFONTS' in
+'texmf.cnf' to refer to some globally known directory. *Note mktex
configuration::.
The first restriction you can apply is to make newly-created
-directories under ‘texmf’ be append-only with an option in ‘mktex.cnf’.
+directories under 'texmf' be append-only with an option in 'mktex.cnf'.
*Note mktex configuration::.
Another approach is to establish a group (or user) for TeX files,
-make the ‘texmf’ tree writable only to that group (or user), and make
-‘mktexpk’ et al. setgid to that group (or setuid to that user). Then
-users must invoke the scripts to install things. (If you’re worried
+make the 'texmf' tree writable only to that group (or user), and make
+'mktexpk' et al. setgid to that group (or setuid to that user). Then
+users must invoke the scripts to install things. (If you're worried
about the inevitable security holes in scripts, then you could write a C
wrapper to exec the script.)
- The ‘mktex...’ scripts install files with the same read and write
+ The 'mktex...' scripts install files with the same read and write
permissions as the directory they are installed in. The executable,
sgid, suid, and sticky bits are always cleared.
- Any directories created by the ‘mktex...’ scripts have the same
-permissions as their parent directory, unless the ‘appendonlydir’
+ Any directories created by the 'mktex...' scripts have the same
+permissions as their parent directory, unless the 'appendonlydir'
feature is used, in which case the sticky bit is always set.
@@ -298,53 +298,53 @@
In short, here is a skeleton of the default directory structure,
extracted from the TDS document:
- PREFIX/ installation root (‘/usr/local’ by default)
+ PREFIX/ installation root ('/usr/local' by default)
bin/ executables
man/ man pages
include/ C header files
info/ GNU info files
- lib/ libraries (‘libkpathsea.*’)
+ lib/ libraries ('libkpathsea.*')
share/ architecture-independent files
texmf/ TDS root
bibtex/ BibTeX input files
bib/ BibTeX databases
- base/ base distribution (e.g., ‘xampl.bib’)
+ base/ base distribution (e.g., 'xampl.bib')
misc/ single-file databases
PKG/ name of a package
bst/ BibTeX style files
- base/ base distribution (e.g., ‘plain.bst’, ‘acm.bst’)
+ base/ base distribution (e.g., 'plain.bst', 'acm.bst')
misc/ single-file styles
PKG/ name of a package
doc/ additional documentation
- dvips/ ‘.pro’, ‘.ps’, ‘psfonts.map’
+ dvips/ '.pro', '.ps', 'psfonts.map'
fonts/ font-related files
- TYPE/ file type (e.g., ‘tfm’, ‘pk’)
- MODE/ type of output device (types ‘pk’ and ‘gf’ only)
- SUPPLIER/ name of a font supplier (e.g., ‘public’)
- TYPEFACE/ name of a typeface (e.g., ‘cm’)
- dpiNNN/ font resolution (types ‘pk’ and ‘gf’ only)
+ TYPE/ file type (e.g., 'tfm', 'pk')
+ MODE/ type of output device (types 'pk' and 'gf' only)
+ SUPPLIER/ name of a font supplier (e.g., 'public')
+ TYPEFACE/ name of a typeface (e.g., 'cm')
+ dpiNNN/ font resolution (types 'pk' and 'gf' only)
metafont/ Metafont (non-font) input files
- base/ base distribution (e.g., ‘plain.mf’)
- misc/ single-file packages (e.g., ‘modes.mf’)
- PKG/ name of a package (e.g., ‘mfpic’)
+ base/ base distribution (e.g., 'plain.mf')
+ misc/ single-file packages (e.g., 'modes.mf')
+ PKG/ name of a package (e.g., 'mfpic')
metapost/ MetaPost input files
- base/ base distribution (e.g., ‘plain.mp’)
+ base/ base distribution (e.g., 'plain.mp')
misc/ single-file packages
PKG/ name of a package
- support/ support files for MetaPost-related utilities (e.g., ‘trfonts.map’)
- mft/ ‘MFT’ inputs (e.g., ‘plain.mft’)
+ support/ support files for MetaPost-related utilities (e.g., 'trfonts.map')
+ mft/ 'MFT' inputs (e.g., 'plain.mft')
tex/ TeX input files
- FORMAT/ name of a format (e.g., ‘plain’)
- base/ base distribution for FORMAT (e.g., ‘plain.tex’)
- misc/ single-file packages (e.g., ‘webmac.tex’)
+ FORMAT/ name of a format (e.g., 'plain')
+ base/ base distribution for FORMAT (e.g., 'plain.tex')
+ misc/ single-file packages (e.g., 'webmac.tex')
local/ local additions to or local configuration files for FORMAT
- PKG/ name of a package (e.g., ‘graphics’, ‘mfnfss’)
+ PKG/ name of a package (e.g., 'graphics', 'mfnfss')
generic/ format-independent packages
- hyphen/ hyphenation patterns (e.g., ‘hyphen.tex’)
+ hyphen/ hyphenation patterns (e.g., 'hyphen.tex')
images/ image input files (e.g., Encapsulated PostScript)
- misc/ single-file format-independent packages (e.g., ‘null.tex’).
- PKG/ name of a package (e.g., ‘babel’)
- web2c/ implementation-dependent files (‘.pool’, ‘.fmt’, ‘texmf.cnf’, etc.)
+ misc/ single-file format-independent packages (e.g., 'null.tex').
+ PKG/ name of a package (e.g., 'babel')
+ web2c/ implementation-dependent files ('.pool', '.fmt', 'texmf.cnf', etc.)
Some concrete examples for most file types:
@@ -395,16 +395,16 @@
5.1 Searching overview
======================
-A “search path” is a colon-separated list of “path elements”, which are
+A "search path" is a colon-separated list of "path elements", which are
directory names with a few extra frills. A search path can come from (a
-combination of) many sources; see below. To look up a file ‘foo’ along
-a path ‘.:/dir’, Kpathsea checks each element of the path in turn: first
-‘./foo’, then ‘/dir/foo’, returning the first match (or possibly all
+combination of) many sources; see below. To look up a file 'foo' along
+a path '.:/dir', Kpathsea checks each element of the path in turn: first
+'./foo', then '/dir/foo', returning the first match (or possibly all
matches).
- The “colon” and “slash” mentioned here aren’t necessarily ‘:’ and ‘/’
+ The "colon" and "slash" mentioned here aren't necessarily ':' and '/'
on non-Unix systems. Kpathsea tries to adapt to other operating
-systems’ conventions.
+systems' conventions.
To check a particular path element E, Kpathsea first sees if a
prebuilt database (*note Filename database::) applies to E, i.e., if the
@@ -413,7 +413,7 @@
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 the specification with ‘!!’ and if the file being
+not forbidden by the specification 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 searched for. (To help speed future lookups of files in the
@@ -420,10 +420,10 @@
same directory, the directory in which a file is found is floated to the
top of the directory list.)
- The “file must exist” condition comes into play with VF files and
-input files read by the TeX ‘\openin’ command. These files might very
-well not exist (consider ‘cmr10.vf’), and so it would be wrong to search
-the disk for them. Therefore, if you fail to update ‘ls-R’ when you
+ The "file must exist" condition comes into play with VF files and
+input files read by the TeX '\openin' command. These files might very
+well not exist (consider '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 not be found.
Each path element is checked in turn: first the database, then the
@@ -435,20 +435,20 @@
On Unix-like systems, if no match is found by any of the above, and
the path element allows checking the filesystem (per the above), a final
check is made for a case-insensitive match. Thus, looking for a name
-like ‘./FooBar.TeX’ will match a file ‘./foobar.tex’, and vice versa.
+like './FooBar.TeX' will match a file './foobar.tex', and vice versa.
This is not done on Windows. *Note Casefolding search::.
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’
+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 transforming all the
+that Kpathsea "expands" a path element, meaning transforming all the
magic specifications into the basic directory name or names. This
process is described in the sections below. It happens in the same
order as the sections.
Exception to all of the above: If the filename being searched for is
-absolute or explicitly relative, i.e., starts with ‘/’ or ‘./’ or ‘../’,
+absolute or explicitly relative, i.e., starts with '/' or './' or '../',
Kpathsea simply checks if that file exists, with a fallback to a
casefolding match if needed and enabled, as described above.
@@ -455,12 +455,12 @@
Ordinarily, if Kpathsea tries to access a file or directory that
cannot be read, it gives a warning. This is so you will be alerted to
directories or files that accidentally lack any read permission (for
-example, a ‘lost+found’ directory). If you prefer not to see these
-warnings, include the value ‘readable’ in the ‘TEX_HUSH’ environment
+example, a 'lost+found' directory). If you prefer not to see these
+warnings, include the value 'readable' in the 'TEX_HUSH' environment
variable or config file value.
This generic path searching algorithm is implemented in
-‘kpathsea/pathsearch.c’. It is employed by a higher-level algorithm
+'kpathsea/pathsearch.c'. It is employed by a higher-level algorithm
when searching for a file of a particular type (*note File lookup::, and
*note Glyph lookup::).
@@ -473,21 +473,21 @@
A search path or other configuration value can come from many sources.
In the order in which Kpathsea looks for them:
- 1. A command-line option such as ‘--cnf-line’, available in
- ‘kpsewhich’ and most TeX engines. *Note Path searching options::.
+ 1. A command-line option such as '--cnf-line', available in
+ 'kpsewhich' and most TeX engines. *Note Path searching options::.
- A user-set environment variable, e.g., ‘TEXINPUTS’. Environment
+ A user-set environment variable, e.g., 'TEXINPUTS'. Environment
variables with an underscore and the program name appended
- override; for example, ‘TEXINPUTS_latex’ overrides ‘TEXINPUTS’ if
- the program being run is named ‘latex’.
+ override; for example, 'TEXINPUTS_latex' overrides 'TEXINPUTS' if
+ the program being run is named 'latex'.
- 2. A program-specific configuration file, e.g., an ‘S /a:/b’ line in
- Dvips’ ‘config.ps’ (*note (dvips)Config files::).
+ 2. A program-specific configuration file, e.g., an 'S /a:/b' line in
+ Dvips' 'config.ps' (*note (dvips)Config files::).
- 3. A line in a Kpathsea configuration file ‘texmf.cnf’, e.g.,
- ‘TEXINPUTS=/c:/d’ (see below).
+ 3. A line in a Kpathsea configuration file 'texmf.cnf', e.g.,
+ 'TEXINPUTS=/c:/d' (see below).
- 4. The compile-time default (specified in ‘kpathsea/paths.h’).
+ 4. The compile-time default (specified in 'kpathsea/paths.h').
You can see each of these values for a given search path by using the
debugging options (*note Debugging::).
@@ -497,7 +497,7 @@
* Menu:
-* Config files:: Kpathsea’s runtime config files (texmf.cnf).
+* Config files:: Kpathsea's runtime config files (texmf.cnf).
File: kpathsea.info, Node: Config files, Up: Path sources
@@ -505,73 +505,73 @@
5.2.1 Config files
------------------
-As mentioned above, Kpathsea reads “runtime configuration files” named
-‘texmf.cnf’ for search path and other definitions. The search path used
-to look for these configuration files is named ‘TEXMFCNF’, and is
+As mentioned above, Kpathsea reads "runtime configuration files" named
+'texmf.cnf' for search path and other definitions. The search path used
+to look for these configuration files is named 'TEXMFCNF', and is
constructed in the usual way, as described above, except that
configuration files cannot be used to define the path, naturally; also,
-an ‘ls-R’ database is not used to search for them.
+an 'ls-R' database is not used to search for them.
- Kpathsea reads _all_ ‘texmf.cnf’ files in the search path, not just
+ Kpathsea reads _all_ 'texmf.cnf' files in the search path, not just
the first one found; definitions in earlier files override those in
-later files. Thus, if the search path is ‘.:$TEXMF’, values from
-‘./texmf.cnf’ override those from ‘$TEXMF/texmf.cnf’.
+later files. Thus, if the search path is '.:$TEXMF', values from
+'./texmf.cnf' override those from '$TEXMF/texmf.cnf'.
- If Kpathsea cannot find any ‘texmf.cnf’ file, it reports a warning
-including all the directories it checked. If you don’t want to see this
-warning, set the environment variable ‘KPATHSEA_WARNING’ to the single
-character ‘0’ (zero, not oh).
+ If Kpathsea cannot find any 'texmf.cnf' file, it reports a warning
+including all the directories it checked. If you don't want to see this
+warning, set the environment variable 'KPATHSEA_WARNING' to the single
+character '0' (zero, not oh).
While (or instead of) reading this description, you may find it
-helpful to look at the distributed ‘texmf.cnf’, which uses or at least
-mentions most features. The format of ‘texmf.cnf’ files follows:
+helpful to look at the distributed 'texmf.cnf', which uses or at least
+mentions most features. The format of 'texmf.cnf' files follows:
- • Comments start with ‘%’ or ‘#’, either at the beginning of a line
+ * Comments start with '%' or '#', either at the beginning of a line
or preceded by whitespace, and continue to the end of the line.
That is, similar to most shells, a comment character in the
- “middle” of a value does not start a comment. Examples:
+ "middle" of a value does not start a comment. Examples:
% this is a comment
var = a%b % but the value of var will be "a%b"
- • Blank lines are ignored.
+ * Blank lines are ignored.
- • A ‘\’ at the end of a line acts as a continuation character, i.e.,
+ * 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 will look like:
+ * Each remaining line will look like:
VARIABLE [. PROGNAME] [=] VALUE
- where the ‘=’ and surrounding whitespace is optional.
+ where the '=' and surrounding whitespace is optional.
- • The VARIABLE name may contain any character other than whitespace,
- ‘=’, or ‘.’, but sticking to ‘A-Za-z_’ is safest.
+ * The VARIABLE name may contain any character other than whitespace,
+ '=', or '.', but sticking to 'A-Za-z_' is safest.
- • If ‘.PROGNAME’ is present (preceding spaces are ignored), the
+ * If '.PROGNAME' is present (preceding spaces are ignored), the
definition only applies if the program that is running is named
- (i.e., the last component of ‘argv[0]’ is) PROGNAME or
- ‘PROGNAME.{exe,bat,cmd,...}’. Most notably, this allows different
+ (i.e., the last component of 'argv[0]' is) PROGNAME or
+ 'PROGNAME.{exe,bat,cmd,...}'. Most notably, this allows different
flavors of TeX to have different search paths. The PROGNAME value
is used literally, without variable or other expansions.
- • Considered as strings, VALUE may contain any character. However,
- in practice most ‘texmf.cnf’ values are related to path expansion,
+ * Considered as strings, VALUE may contain any character. However,
+ in practice most 'texmf.cnf' values are related to path expansion,
and since various special characters are used in expansion, such as
braces and commas, they cannot be used in directory names.
- The ‘$VAR.PROG’ feature is not available on the right-hand side;
+ The '$VAR.PROG' feature is not available on the right-hand side;
instead, you must use an additional variable (see below for
example).
- A ‘;’ in VALUE is translated to ‘:’ if running under Unix, in order
- to have a single ‘texmf.cnf’ that can support both Unix and Windows
+ A ';' in VALUE is translated to ':' if running under Unix, in order
+ to have a single 'texmf.cnf' that can support both Unix and Windows
systems. This translation happens with any value, not just search
- paths, but fortunately in practice ‘;’ is not needed in other
+ paths, but fortunately in practice ';' is not needed in other
values.
- • All definitions are read before anything is expanded, so you can
+ * All definitions are read before anything is expanded, so you can
use variables before they are defined (like Make, unlike most other
programs).
@@ -585,26 +585,26 @@
TEXINPUTS.latex2e = $latex2e_inputs
TEXINPUTS.latex = $latex2e_inputs
- The combination of spaces being ignored before the ‘.’ of a program
-name qualifer and the optional ‘=’ for the assignment has an unexpected
-consequence: if the value begins with a literal ‘.’ and the ‘=’ is
+ The combination of spaces being ignored before the '.' of a program
+name qualifer and the optional '=' for the assignment has an unexpected
+consequence: if the value begins with a literal '.' and the '=' is
omitted, the intended value is interpreted as a program name. For
-example, a line ‘var .;/some/path’ is taken as an empty value for ‘var’
-running under the program named ‘;/some/path’. To diagnose this,
+example, a line 'var .;/some/path' is taken as an empty value for 'var'
+running under the program named ';/some/path'. To diagnose this,
Kpathsea warns if the program name contains a path separator or other
special character. The simplest way to avoid the problem is to use the
-‘=’.
+'='.
Exactly when a character will be considered special or act as itself
depends on the context in which it is used. The rules are inherent in
the multiple levels of interpretation of the configuration (parsing,
expansion, search, ...) and so cannot be concisely stated,
-unfortunately. There is no general escape mechanism; in particular, ‘\’
-is not an “escape character” in ‘texmf.cnf’ files. When it comes
+unfortunately. There is no general escape mechanism; in particular, '\'
+is not an "escape character" in 'texmf.cnf' files. When it comes
choosing directory names for installation, it is safest to avoid them
all.
- The implementation of all this is in ‘kpathsea/cnf.c’.
+ The implementation of all this is in 'kpathsea/cnf.c'.
File: kpathsea.info, Node: Path expansion, Next: Casefolding search, Prev: Path sources, Up: Path searching
@@ -614,9 +614,9 @@
Kpathsea recognizes certain special characters and constructions in
search paths, similar to that in shells. As a general example:
-‘~$USER/{foo,bar}//baz’ expands to all subdirectories under directories
-‘foo’ and ‘bar’ in $USER’s home directory that contain a directory or
-file ‘baz’.
+'~$USER/{foo,bar}//baz' expands to all subdirectories under directories
+'foo' and 'bar' in $USER's home directory that contain a directory or
+file 'baz'.
These expansions are explained in the sections below.
@@ -636,7 +636,7 @@
-----------------------
If the highest-priority search path (*note Path sources::) contains an
-“extra colon” (i.e., leading, trailing, or doubled), Kpathsea inserts at
+"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. (An extra colon in the compile-time default value has
@@ -646,7 +646,7 @@
setenv TEXINPUTS /home/karl:
-and a ‘TEXINPUTS’ value from ‘texmf.cnf’ of
+and a 'TEXINPUTS' value from 'texmf.cnf' of
.:$TEXMF//tex
@@ -654,9 +654,9 @@
/home/karl:.:$TEXMF//tex
- Put another way, default expansion works on “formats” (search paths),
+ Put another way, default expansion works on "formats" (search paths),
and not directly on environment variables. Example, showing the
-trailing ‘:’ ignored in the first case and expanded in the second:
+trailing ':' ignored in the first case and expanded in the second:
$ env TTFONTS=/tmp: kpsewhich --expand-path '$TTFONTS'
/tmp
@@ -664,21 +664,21 @@
/tmp:.:/home/olaf/texmf/fonts/truetype//:...
Since Kpathsea looks for multiple configuration files, it would be
-natural to expect that (for example) an extra colon in ‘./texmf.cnf’
-would expand to the path in ‘$TEXMF/texmf.cnf’. Or, with Dvips’
-configuration files, that an extra colon in ‘config.$PRINTER’ would
-expand to the path in ‘config.ps’. This doesn’t happen. It’s not clear
+natural to expect that (for example) an extra colon in './texmf.cnf'
+would expand to the path in '$TEXMF/texmf.cnf'. Or, with Dvips'
+configuration files, that an extra colon in 'config.$PRINTER' would
+expand to the path in 'config.ps'. This doesn't happen. It's not clear
this would be desirable in all cases, and trying to devise a way to
specify the path to which the extra colon should expand seemed truly
baroque.
Technicality: Since it would be useless to insert the default value
-in more than one place, Kpathsea changes only one extra ‘:’ and leaves
+in more than one place, Kpathsea changes only one extra ':' and leaves
any others in place (they will eventually be ignored). Kpathsea checks
-first for a leading ‘:’, then a trailing ‘:’, then a doubled ‘:’.
+first for a leading ':', then a trailing ':', then a doubled ':'.
- You can trace this by debugging “paths” (*note Debugging::). Default
-expansion is implemented in the source file ‘kpathsea/kdefault.c’.
+ You can trace this by debugging "paths" (*note Debugging::). Default
+expansion is implemented in the source file 'kpathsea/kdefault.c'.
File: kpathsea.info, Node: Variable expansion, Next: Tilde expansion, Prev: Default expansion, Up: Path expansion
@@ -686,34 +686,34 @@
5.3.2 Variable expansion
------------------------
-‘$foo’ or ‘${foo}’ in a path element is replaced by (1) the value of an
-environment variable ‘foo’ (if defined); (2) the value of ‘foo’ from
-‘texmf.cnf’ (if defined); (3) the empty string.
+'$foo' or '${foo}' in a path element is replaced by (1) the value of an
+environment variable 'foo' (if defined); (2) the value of 'foo' from
+'texmf.cnf' (if defined); (3) the empty string.
- If the character after the ‘$’ is alphanumeric or ‘_’, the variable
+ If the character after the '$' is alphanumeric or '_', the variable
name consists of all consecutive such characters. If the character
-after the ‘$’ is a ‘{’, the variable name consists of everything up to
-the next ‘}’ (braces may not be nested around variable names).
-Otherwise, Kpathsea gives a warning and ignores the ‘$’ and its
+after the '$' is a '{', the variable name consists of everything up to
+the next '}' (braces may not be nested around variable names).
+Otherwise, Kpathsea gives a warning and ignores the '$' and its
following character.
- You must quote the $’s and braces as necessary for your shell.
+ You must quote the $'s and braces as necessary for your shell.
_Shell_ variable values cannot be seen by Kpathsea, i.e., ones defined
-by ‘set’ in C shells and without ‘export’ in Bourne shells.
+by 'set' in C shells and without 'export' in Bourne shells.
For example, given
setenv tex /home/texmf
setenv TEXINPUTS .:$tex:${tex}prev
-the final ‘TEXINPUTS’ path is the three directories:
+the final 'TEXINPUTS' path is the three directories:
.:/home/texmf:/home/texmfprev
- The ‘.PROGNAME’ suffix on variables and ‘_PROGNAME’ on environment
+ The '.PROGNAME' suffix on variables and '_PROGNAME' on environment
variable names are not implemented for general variable expansions.
These are only recognized when search paths are initialized (*note Path
sources::).
Variable expansion is implemented in the source file
-‘kpathsea/variable.c’.
+'kpathsea/variable.c'.
File: kpathsea.info, Node: Tilde expansion, Next: Brace expansion, Prev: Variable expansion, Up: Path expansion
@@ -721,26 +721,26 @@
5.3.3 Tilde expansion
---------------------
-A leading ‘~’ in a path element is replaced by the value of the
-environment variable ‘HOME’, or ‘.’ if ‘HOME’ is not set. On Windows,
-the environment variable ‘USERPROFILE’ is checked instead of ‘HOME’.
+A leading '~' in a path element is replaced by the value of the
+environment variable 'HOME', or '.' if 'HOME' is not set. On Windows,
+the environment variable 'USERPROFILE' is checked instead of 'HOME'.
- A leading ‘~USER’ in a path element is replaced by USER’s home
-directory from the system ‘passwd’ database.
+ A leading '~USER' in a path element is replaced by USER's home
+directory from the system 'passwd' database.
For example,
setenv TEXINPUTS ~/mymacros:
-will prepend a directory ‘mymacros’ in your home directory to the
+will prepend a directory 'mymacros' in your home directory to the
default path.
- As a special case, if a home directory ends in ‘/’, the trailing
-slash is dropped, to avoid inadvertently creating a ‘//’ construct in
-the path. For example, if the home directory of the user ‘root’ is ‘/’,
-the path element ‘~root/mymacros’ expands to just ‘/mymacros’, not
-‘//mymacros’.
+ As a special case, if a home directory ends in '/', the trailing
+slash is dropped, to avoid inadvertently creating a '//' construct in
+the path. For example, if the home directory of the user 'root' is '/',
+the path element '~root/mymacros' expands to just '/mymacros', not
+'//mymacros'.
- Tilde expansion is implemented in the source file ‘kpathsea/tilde.c’.
+ Tilde expansion is implemented in the source file 'kpathsea/tilde.c'.
File: kpathsea.info, Node: Brace expansion, Next: KPSE_DOT expansion, Prev: Tilde expansion, Up: Path expansion
@@ -748,38 +748,38 @@
5.3.4 Brace expansion
---------------------
-‘x{A,B}y’ expands to ‘xAy:xBy’. For example:
+'x{A,B}y' expands to 'xAy:xBy'. For example:
foo/{1,2}/baz
-expands to ‘foo/1/baz:foo/2/baz’. ‘:’ is the path separator on the
-current system; e.g., on a Windows system, it’s ‘;’.
+expands to 'foo/1/baz:foo/2/baz'. ':' is the path separator on the
+current system; e.g., on a Windows system, it's ';'.
- Braces can be nested; for example, ‘x{A,B{1,2}}y’ expands to
-‘xAy:xB1y:xB2y’.
+ Braces can be nested; for example, 'x{A,B{1,2}}y' expands to
+'xAy:xB1y:xB2y'.
Multiple non-nested braces are expanded from right to left; for
-example, ‘x{A,B}{1,2}y’ expands to ‘x{A,B}1y:x{A,B}2y’, which expands to
-‘xA1y:xB1y:xA2y:xB2y’.
+example, 'x{A,B}{1,2}y' expands to 'x{A,B}1y:x{A,B}2y', which expands to
+'xA1y:xB1y:xA2y:xB2y'.
This feature can be used to implement multiple TeX hierarchies, by
-assigning a brace list to ‘$TEXMF’, as mentioned in ‘texmf.in’.
+assigning a brace list to '$TEXMF', as mentioned in 'texmf.in'.
You can also use the path separator instead of the comma. The last
-example could have been written ‘x{A:B}{1:2}y’ (on Unix).
+example could have been written 'x{A:B}{1:2}y' (on Unix).
Brace expansion is implemented in the source file
-‘kpathsea/expand.c’.
+'kpathsea/expand.c'.
File: kpathsea.info, Node: KPSE_DOT expansion, Next: Subdirectory expansion, Prev: Brace expansion, Up: Path expansion
-5.3.5 ‘KPSE_DOT’ expansion
+5.3.5 'KPSE_DOT' expansion
--------------------------
-When ‘KPSE_DOT’ is defined in the environment, it names a directory that
+When 'KPSE_DOT' is defined in the environment, it names a directory that
should be considered the current directory for the purpose of looking up
-files in the search paths. This feature is needed by the ‘mktex...’
+files in the search paths. This feature is needed by the 'mktex...'
scripts *note mktex scripts::, because these change the working
directory. You should not ever define it yourself.
@@ -793,16 +793,16 @@
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. (It’s “directory order”, and definitely not alphabetical.)
+unspecified. (It's "directory order", and definitely not alphabetical.)
- If you specify any filename components after the ‘//’, only
+ If you specify any filename components after the '//', only
subdirectories which match those components are included. For example,
-‘/a//b’ would expand into directories ‘/a/1/b’, ‘/a/2/b’, ‘/a/1/1/b’,
-and so on, but not ‘/a/b/c’ or ‘/a/1’.
+'/a//b' would expand into directories '/a/1/b', '/a/2/b', '/a/1/1/b',
+and so on, but not '/a/b/c' or '/a/1'.
- You can include multiple ‘//’ constructs in the path.
+ You can include multiple '//' constructs in the path.
- ‘//’ at the beginning of a path is ignored; you didn’t really want to
+ '//' at the beginning of a path is ignored; you didn't really want to
search every directory on the system, did you?
I should mention one related implementation trick, which I took from
@@ -811,28 +811,28 @@
The trick is that in every real Unix implementation (as opposed to
the POSIX specification), a directory which contains no subdirectories
-will have exactly two links (namely, one for ‘.’ and one for ‘..’).
-That is to say, the ‘st_nlink’ field in the ‘stat’ structure will be
-two. Thus, we don’t have to stat everything in the bottom-level (leaf)
-directories—we can just check ‘st_nlink’, notice it’s two, and do no
+will have exactly two links (namely, one for '.' and one for '..').
+That is to say, the 'st_nlink' field in the 'stat' structure will be
+two. Thus, we don't have to stat everything in the bottom-level (leaf)
+directories--we can just check 'st_nlink', notice it's two, and do no
more work.
But if you have a directory that contains a single subdirectory and
-500 regular files, ‘st_nlink’ will be 3, and Kpathsea has to stat every
+500 regular files, 'st_nlink' will be 3, and Kpathsea has to stat every
one of those 501 entries. Therein lies slowness.
- You can disable the trick by undefining ‘ST_NLINK_TRICK’ in
-‘kpathsea/config.h’. (It is undefined by default except under Unix.)
+ You can disable the trick by undefining 'ST_NLINK_TRICK' in
+'kpathsea/config.h'. (It is undefined by default except under Unix.)
- Unfortunately, in some cases files in leaf directories are ‘stat’’d:
-if the path specification is, say, ‘$TEXMF/fonts//pk//’, then files in a
-subdirectory ‘.../pk’, even if it is a leaf, are checked. The reason
+ Unfortunately, in some cases files in leaf directories are 'stat''d:
+if the path specification is, say, '$TEXMF/fonts//pk//', then files in a
+subdirectory '.../pk', even if it is a leaf, are checked. The reason
cannot be explained without reference to the implementation, so read
-‘kpathsea/elt-dirs.c’ (search for ‘may descend’) if you are curious.
+'kpathsea/elt-dirs.c' (search for 'may descend') if you are curious.
And if you find a way to solve the problem, please let me know.
Subdirectory expansion is implemented in the source file
-‘kpathsea/elt-dirs.c’.
+'kpathsea/elt-dirs.c'.
File: kpathsea.info, Node: Casefolding search, Next: Filename database, Prev: Path expansion, Up: Path searching
@@ -847,8 +847,8 @@
for a case-insensitive match.
This is enabled at compile-time on Unix systems, and enabled at
-runtime by setting the configuration variable ‘texmf_casefold_search’,
-to a true value, e.g., ‘1’; this is done by default in TeX Live.
+runtime by setting the configuration variable 'texmf_casefold_search',
+to a true value, e.g., '1'; this is done by default in TeX Live.
* Menu:
@@ -866,9 +866,9 @@
ones. In particular, Apple decided to make the default filesystem on
Macs be case-insensitive some years ago, and this has exacerbated a
problem of people creating documents that use, say, an image under the
-name ‘foo.jpg’, while the actual file is named ‘foo.JPG’ or ‘Foo.jpg’.
+name 'foo.jpg', while the actual file is named 'foo.JPG' or 'Foo.jpg'.
It works on the Mac but if the document is transferred and run on a
-standard case-sensitive Unix (file)system, the file can’t be found, due
+standard case-sensitive Unix (file)system, the file can't be found, due
only to differences in case.
This same problematic scenario has always existed on Windows, but for
@@ -880,7 +880,7 @@
Windows, where (for practical purposes) all file names are
case-insensitive at the kernel level, and so the normal search will
already have definitively matched or not. Therefore, search results in
-unusual cases can be different on Windows and Unix—but this has always
+unusual cases can be different on Windows and Unix--but this has always
been true.
@@ -900,60 +900,60 @@
to case thus even more rare, the hope is that it will not cause
difficulties in practice.
- If it’s desirable in a given situation to have the exact same search
+ If it's desirable in a given situation to have the exact same search
behavior as previously, that can be accomplished by setting the
-configuration variable ‘texmf_casefold_search’ to ‘0’ (*note Path
+configuration variable 'texmf_casefold_search' to '0' (*note Path
sources::).
Some examples to illustrate the new behavior follow.
- Example #1: suppose the file ‘./foobar.tex’ exists. Now, searching
-for ‘./FooBar.TeX’ (or any other case variation) will succeed, returning
-‘./foobar.tex’—the name as stored on disk. In previous releases, or if
-‘texmf_casefold_search’ is false, the search would fail.
+ Example #1: suppose the file './foobar.tex' exists. Now, searching
+for './FooBar.TeX' (or any other case variation) will succeed, returning
+'./foobar.tex'--the name as stored on disk. In previous releases, or if
+'texmf_casefold_search' is false, the search would fail.
Example #2: suppose we are using a case-sensitive (file)system, and
-the search path is ‘.:/somedir’, and the files ‘./foobar.tex’ and
-‘/somedir/FooBar.TeX’ both exist. Both now and previously, searching
-for ‘foobar.tex’ returns ‘./foobar.tex’. However, searching for
-‘FooBar.TeX’ now returns ‘./foobar.tex’ instead of
-‘/somedir/FooBar.TeX’; this is the incompatibility mentioned above.
-Also (as expected), searching for ‘FOOBAR.TEX’ (or whatever variation)
-will now return ‘./foobar.tex’, whereas before it would fail. Searching
-for all (‘kpsewhich --all’) ‘foobar.tex’ will return both matches.
+the search path is '.:/somedir', and the files './foobar.tex' and
+'/somedir/FooBar.TeX' both exist. Both now and previously, searching
+for 'foobar.tex' returns './foobar.tex'. However, searching for
+'FooBar.TeX' now returns './foobar.tex' instead of
+'/somedir/FooBar.TeX'; this is the incompatibility mentioned above.
+Also (as expected), searching for 'FOOBAR.TEX' (or whatever variation)
+will now return './foobar.tex', whereas before it would fail. Searching
+for all ('kpsewhich --all') 'foobar.tex' will return both matches.
Example #3: same as example #2, but on a case-insensitive
-(file)system: both now and previously, searching for ‘FooBar.TeX’
-returns ‘./foobar.tex’, since the system considers that a match. The
+(file)system: both now and previously, searching for 'FooBar.TeX'
+returns './foobar.tex', since the system considers that a match. The
Kpathsea casefolding never comes into play.
Example #4: if we have (on a case-sensitive system) both
-‘./foobar.tex’ and ‘./FOOBAR.TEX’, searching with the exact case returns
-that exact match, now and previously. Searching for ‘FooBar.tex’ will
+'./foobar.tex' and './FOOBAR.TEX', searching with the exact case returns
+that exact match, now and previously. Searching for 'FooBar.tex' will
now return one or the other (chosen arbitrarily), rather than failing.
-Perhaps unexpectedly, searching for all ‘foobar.tex’ or ‘FooBar.tex’
+Perhaps unexpectedly, searching for all 'foobar.tex' or 'FooBar.tex'
will also return only one or the other, not both (see more below).
- Example #5: the font file ‘STIX-Regular.otf’ is included in TeX Live
-in the system directory ‘texmf-dist/fonts/opentype/public/stix’.
+ Example #5: the font file 'STIX-Regular.otf' is included in TeX Live
+in the system directory 'texmf-dist/fonts/opentype/public/stix'.
Because Kpathsea never searches the disk in the big system directory,
-the casefolding is not done, and a search for ‘stix-regular.otf’ will
+the casefolding is not done, and a search for 'stix-regular.otf' will
fail (on case-sensitive systems), as it always has.
The caveat about not searching the disk amounts to saying that
-casefolding does not happen in the trees specified with ‘!!’ (*note
-ls-R::), that is, where only database (‘ls-R’) searching is done. In
-TeX Live, that is the ‘texmf-local’ and ‘texmf-dist’ trees (also
-‘$TEXMFSYSCONFIG’ and ‘$TEXMFSYSVAR’, but those are rarely noticed).
+casefolding does not happen in the trees specified with '!!' (*note
+ls-R::), that is, where only database ('ls-R') searching is done. In
+TeX Live, that is the 'texmf-local' and 'texmf-dist' trees (also
+'$TEXMFSYSCONFIG' and '$TEXMFSYSVAR', but those are rarely noticed).
The rationale for this is that in practice, case mangling happens with
user-created files, not with packages distributed as part of the TeX
system.
- One more caveat: the purpose of ‘kpsewhich’ is to exercise the path
+ One more caveat: the purpose of 'kpsewhich' is to exercise the path
searching in Kpathsea as it is actually done. Therefore, as shown
-above, ‘kpsewhich --all’ will not return all matches regardless of case
+above, 'kpsewhich --all' will not return all matches regardless of case
within a given path element. If you want to find all matches in all
-directories, ‘find’ is the best tool, although the setup takes a couple
+directories, 'find' is the best tool, although the setup takes a couple
steps:
kpsewhich -show-path=tex >/tmp/texpath # search path specification
@@ -961,23 +961,23 @@
tr ':' '\n' </tmp/texdirs >/tmp/texdirlist # colons to newlines
find `cat /tmp/texdirlist` -iname somefile.tex -print </tmp/texdirlist
- Sorry that it’s annoyingly lengthy, but implementing this inside
+ Sorry that it's annoyingly lengthy, but implementing this inside
Kpathsea would be a lot of error-prone trouble for something that is
-only useful for debugging. If your ‘find’ does not support ‘-iname’,
+only useful for debugging. If your 'find' does not support '-iname',
you can get GNU Find from <https://gnu.org/software/findutils>.
The casefolding search is implemented in the source file
-‘kpathsea/pathsearch.c’. Two implementation points:
+'kpathsea/pathsearch.c'. Two implementation points:
- • Kpathsea never tries to check if a given directory resides on a
+ * Kpathsea never tries to check if a given directory resides on a
case-insensitive filesystem, because there is no efficient and
portable way to do so. All it does is try to see if a potential
- file name is a readable normal file (with, usually, the ‘access’
+ file name is a readable normal file (with, usually, the 'access'
system call).
- • Kpathsea does not do any case-insensitive matching of the
- directories along the path. It’s not going to find
- ‘/Some/Random/file.tex’ when looking for ‘/some/random/file.tex’.
+ * Kpathsea does not do any case-insensitive matching of the
+ directories along the path. It's not going to find
+ '/Some/Random/file.tex' when looking for '/some/random/file.tex'.
The casefolding only happens with the elements of the leaf
directory.
@@ -984,7 +984,7 @@
File: kpathsea.info, Node: Filename database, Next: Invoking kpsewhich, Prev: Casefolding search, Up: Path searching
-5.5 Filename database (‘ls-R’)
+5.5 Filename database ('ls-R')
==============================
Kpathsea goes to some lengths to minimize disk accesses for searches
@@ -992,15 +992,15 @@
every possible directory in typical TeX installations takes an
excessively long time.
- Therefore, Kpathsea can use an externally-built “filename database”
-file named ‘ls-R’ that maps files to directories, thus avoiding the need
+ Therefore, Kpathsea can use an externally-built "filename database"
+file named 'ls-R' that maps files to directories, thus avoiding the need
to exhaustively search the disk.
- A second database file ‘aliases’ allows you to give additional names
-to the files listed in ‘ls-R’.
+ A second database file 'aliases' allows you to give additional names
+to the files listed in 'ls-R'.
- The ‘ls-R’ and ‘aliases’ features are implemented in the source file
-‘kpathsea/db.c’.
+ The 'ls-R' and 'aliases' features are implemented in the source file
+'kpathsea/db.c'.
* Menu:
@@ -1011,77 +1011,77 @@
File: kpathsea.info, Node: ls-R, Next: Filename aliases, Up: Filename database
-5.5.1 ‘ls-R’
+5.5.1 'ls-R'
------------
-As mentioned above, you must name the main filename database ‘ls-R’.
+As mentioned above, you must name the main filename database 'ls-R'.
You can put one at the root of each TeX installation hierarchy you wish
-to search (‘$TEXMF’ by default, which expands to a braced list of
+to search ('$TEXMF' by default, which expands to a braced list of
several hierarchies in TeX Live).
- Kpathsea looks for ‘ls-R’ files along the ‘TEXMFDBS’ path. It is
-best for this to contain all and only those hierarchies from ‘$TEXMF’
-which are specified with ‘!!’—and also to specify them with ‘!!’ in
-‘TEXMFDBS’. (See the end of this section for more on ‘!!’.)
+ Kpathsea looks for 'ls-R' files along the 'TEXMFDBS' path. It is
+best for this to contain all and only those hierarchies from '$TEXMF'
+which are specified with '!!'--and also to specify them with '!!' in
+'TEXMFDBS'. (See the end of this section for more on '!!'.)
- The recommended way to create and maintain ‘ls-R’ is to run the
-‘mktexlsr’ script, which is installed in ‘$(bindir)’ (‘/usr/local/bin’
+ The recommended way to create and maintain 'ls-R' is to run the
+'mktexlsr' script, which is installed in '$(bindir)' ('/usr/local/bin'
by default). That script goes to some trouble to follow symbolic links
-as necessary, etc. It’s also invoked by the distributed ‘mktex...’
+as necessary, etc. It's also invoked by the distributed 'mktex...'
scripts.
- At its simplest, though, you can build ‘ls-R’ with the command
+ At its simplest, though, you can build 'ls-R' with the command
cd /YOUR/TEXMF/ROOT && ls -LAR ./ >ls-R
-presuming your ‘ls’ produces the right output format (see the section
-below). GNU ‘ls’, for example, outputs in this format. Also presuming
-your ‘ls’ hasn’t been aliased in a system file (e.g., ‘/etc/profile’) to
-something problematic, e.g., ‘ls --color=tty’. In that case, you will
-have to disable the alias before generating ‘ls-R’. For the precise
+presuming your 'ls' produces the right output format (see the section
+below). GNU 'ls', for example, outputs in this format. Also presuming
+your 'ls' hasn't been aliased in a system file (e.g., '/etc/profile') to
+something problematic, e.g., 'ls --color=tty'. In that case, you will
+have to disable the alias before generating 'ls-R'. For the precise
definition of the file format, see *note Database format::.
Regardless of whether you use the supplied script or your own, you
-will almost certainly want to invoke it via ‘cron’, so when you make
+will almost certainly want to invoke it via 'cron', so when you make
changes in the installed files (say if you install a new LaTeX package),
-‘ls-R’ will be automatically updated. However, for those using TeX Live
-or system distributions, the package managers should run ‘mktexlsr’ as
+'ls-R' will be automatically updated. However, for those using TeX Live
+or system distributions, the package managers should run 'mktexlsr' as
needed.
- The ‘-A’ option to ‘ls’ includes files beginning with ‘.’ (except for
-‘.’ and ‘..’), such as the file ‘.tex’ included with the LaTeX tools
-package. (On the other hand, _directories_ whose names begin with ‘.’
+ The '-A' option to 'ls' includes files beginning with '.' (except for
+'.' and '..'), such as the file '.tex' included with the LaTeX tools
+package. (On the other hand, _directories_ whose names begin with '.'
are always ignored.)
- If your system does not support symbolic links, omit the ‘-L’.
+ If your system does not support symbolic links, omit the '-L'.
- ‘ls -LAR /YOUR/TEXMF/ROOT’ will also work. But using ‘./’ avoids
+ 'ls -LAR /YOUR/TEXMF/ROOT' will also work. But using './' avoids
embedding absolute pathnames, so the hierarchy can be easily
transported. It also avoids possible trouble with automounters or other
network filesystem conventions.
- Kpathsea warns you if it finds an ‘ls-R’ file, but the file does not
-contain any usable entries. The usual culprit is running plain ‘ls -R’
-instead of ‘ls -LR ./’ or ‘ls -R /YOUR/TEXMF/ROOT’. Another possibility
-is some system directory name starting with a ‘.’ (perhaps if you are
+ Kpathsea warns you if it finds an 'ls-R' file, but the file does not
+contain any usable entries. The usual culprit is running plain 'ls -R'
+instead of 'ls -LR ./' or 'ls -R /YOUR/TEXMF/ROOT'. Another possibility
+is some system directory name starting with a '.' (perhaps if you are
using AFS); Kpathsea ignores everything under such directories.
- If a particular path element begins with ‘!!’, _only_ the database
+ If a particular path element begins with '!!', _only_ the database
will be searched for that element, never the disk; and if the database
does not exist, nothing at all will be searched. In TeX Live, most of
-the trees are specified with ‘!!’.
+the trees are specified with '!!'.
- For path elements that do not begin with ‘!!’, if the database
+ For path elements that do not begin with '!!', if the database
exists, it will be used, and the disk will not be searched. However, in
this case, if the database does not exist, the disk will be searched.
-In TeX Live, the most notable case of this is the ‘TEXMFHOME’ tree, to
+In TeX Live, the most notable case of this is the 'TEXMFHOME' tree, to
allow users to add and remove files from their own tree without having
-to worry about ‘ls-R’.
+to worry about 'ls-R'.
- (Aside: there are uncommon cases where a ‘!!’ tree will be searched
-on disk even if the ‘ls-R’ file exists; they are too obscure to try to
-explain here. See ‘pathsearch.c’ in the source if you need to know.)
+ (Aside: there are uncommon cases where a '!!' tree will be searched
+on disk even if the 'ls-R' file exists; they are too obscure to try to
+explain here. See 'pathsearch.c' in the source if you need to know.)
- To sum up: do not create an ‘ls-R’ file unless you also take care to
+ To sum up: do not create an 'ls-R' file unless you also take care to
keep it up to date. Otherwise newly-installed files will not be found.
@@ -1092,24 +1092,24 @@
In some circumstances, you may wish to find a file under several names.
For example, suppose a TeX document was created using a DOS system and
-tries to read ‘longtabl.sty’. But now it’s being run on a Unix system,
-and the file has its original name, ‘longtable.sty’. The file won’t be
-found. You need to give the actual file ‘longtable.sty’ an alias
-‘longtabl.sty’.
+tries to read 'longtabl.sty'. But now it's being run on a Unix system,
+and the file has its original name, 'longtable.sty'. The file won't be
+found. You need to give the actual file 'longtable.sty' an alias
+'longtabl.sty'.
- You can handle this by creating a file ‘aliases’ as a companion to
-the ‘ls-R’ for the hierarchy containing the file in question. (You must
-have an ‘ls-R’ for the alias feature to work.)
+ You can handle this by creating a file 'aliases' as a companion to
+the 'ls-R' for the hierarchy containing the file in question. (You must
+have an 'ls-R' for the alias feature to work.)
- The format of ‘aliases’ is simple: two whitespace-separated words per
-line; the first is the real name ‘longtable.sty’, and second is the
-alias (‘longtabl.sty’). These must be base filenames, with no directory
-components. ‘longtable.sty’ must be in the sibling ‘ls-R’.
+ The format of 'aliases' is simple: two whitespace-separated words per
+line; the first is the real name 'longtable.sty', and second is the
+alias ('longtabl.sty'). These must be base filenames, with no directory
+components. 'longtable.sty' must be in the sibling 'ls-R'.
- Also, blank lines and lines starting with ‘%’ or ‘#’ are ignored in
-‘aliases’, to allow for comments.
+ Also, blank lines and lines starting with '%' or '#' are ignored in
+'aliases', to allow for comments.
- If a real file ‘longtabl.sty’ exists, it is used regardless of any
+ If a real file 'longtabl.sty' exists, it is used regardless of any
aliases.
@@ -1118,22 +1118,22 @@
5.5.3 Database format
---------------------
-The “database” read by Kpathsea is a line-oriented file of plain text.
-The format is that generated by GNU (and most other) ‘ls’ programs given
-the ‘-R’ option, as follows.
+The "database" read by Kpathsea is a line-oriented file of plain text.
+The format is that generated by GNU (and most other) 'ls' programs given
+the '-R' option, as follows.
- • Blank lines are ignored.
+ * Blank lines are ignored.
- • If a line begins with ‘/’ or ‘./’ or ‘../’ and ends with a colon,
- it’s the name of a directory. (‘../’ lines aren’t useful, however,
+ * If a line begins with '/' or './' or '../' and ends with a colon,
+ it's the name of a directory. ('../' lines aren't useful, however,
and should not be generated.)
- • All other lines define entries in the most recently seen directory.
- /’s in such lines will produce possibly-strange results.
+ * All other lines define entries in the most recently seen directory.
+ /'s in such lines will produce possibly-strange results.
- • Files with no preceding directory line are ignored.
+ * Files with no preceding directory line are ignored.
- For example, here’s the first few lines of ‘ls-R’ (which totals about
+ For example, here's the first few lines of 'ls-R' (which totals about
30K bytes) on my system:
bibtex
@@ -1158,14 +1158,14 @@
File: kpathsea.info, Node: Invoking kpsewhich, Prev: Filename database, Up: Path searching
-5.6 ‘kpsewhich’: Standalone path searching
+5.6 'kpsewhich': Standalone path searching
==========================================
The Kpsewhich program exercises the path searching functionality
independent of any particular application. This can also be useful as a
-sort of ‘find’ program to locate files in your TeX hierarchies, perhaps
+sort of 'find' program to locate files in your TeX hierarchies, perhaps
in administrative scripts. It is used heavily in the distributed
-‘mktex...’ scripts.
+'mktex...' scripts.
Synopsis:
@@ -1172,7 +1172,7 @@
kpsewhich OPTION... FILENAME...
The options and filename(s) to look up can be intermixed. Options
-can start with either ‘-’ or ‘--’, and any unambiguous abbreviation is
+can start with either '-' or '--', and any unambiguous abbreviation is
accepted.
* Menu:
@@ -1180,7 +1180,7 @@
* Path searching options:: Changing the mode, resolution, etc.
* Specially-recognized files:: Default formats for texmf.cnf, etc.
* Auxiliary tasks:: Path and variable expansion, etc.
-* Standard options:: ‘--help’ and ‘--version’.
+* Standard options:: '--help' and '--version'.
File: kpathsea.info, Node: Path searching options, Next: Specially-recognized files, Up: Invoking kpsewhich
@@ -1193,80 +1193,80 @@
Various options alter the path searching behavior:
-‘--all’
+'--all'
Report all matches found, one per line. By default, if there is
more than one match, just one will be reported (chosen effectively
- at random). Exception: with the glyph formats (‘pk’, ‘gf’), this
+ at random). Exception: with the glyph formats ('pk', 'gf'), this
option has no effect and only the first match is returned.
-‘--casefold-search’
-‘--no-casefold-search’
+'--casefold-search'
+'--no-casefold-search'
Explicitly enable or disable the fallback to a case-insensitive
search on Unix platforms (*note Casefolding search::); no effect on
- Windows. The default is enabled, set in ‘texmf.cnf’. Disabling
- (‘--no-casefold-search’) does not mean that searches magically
+ Windows. The default is enabled, set in 'texmf.cnf'. Disabling
+ ('--no-casefold-search') does not mean that searches magically
become case-sensitive when the underlying (file)system is
case-insensitive, it merely means that Kpathsea does not do any
casefolding itself.
-‘--cnf-line=STR’
- Parse STR as if it were a line in the ‘texmf.cnf’ configuration
+'--cnf-line=STR'
+ Parse STR as if it were a line in the 'texmf.cnf' configuration
file (*note Config files::), overriding settings in the actual
configuration files, and also in the environment (*note Path
sources::). This is implemented by making any settings from STR in
the environment, overwriting any value already there. Thus, an
- extra colon in a ‘--cnf-line’ value will refer to the value from a
+ extra colon in a '--cnf-line' value will refer to the value from a
configuration file, not a user-set environment variable.
Furthermore, any variable set from STR will also be set with the
- program name suffix. For example, ‘pdftex
- --cnf-line=TEXINPUTS=/foo:’ will set both ‘TEXINPUTS’ and
- ‘TEXINPUTS_pdftex’ in the environment (and the value will be ‘/foo’
- followed by the setting from ‘texmf.cnf’, ignoring any user-set
- ‘TEXINPUTS’).
+ program name suffix. For example, 'pdftex
+ --cnf-line=TEXINPUTS=/foo:' will set both 'TEXINPUTS' and
+ 'TEXINPUTS_pdftex' in the environment (and the value will be '/foo'
+ followed by the setting from 'texmf.cnf', ignoring any user-set
+ 'TEXINPUTS').
This behavior is desirable because, in practice, many variables in
- the distributed ‘texmf.cnf’ are program-specific, and the intuitive
- behavior is for values set on the command line with ‘--cnf-line’ to
+ the distributed 'texmf.cnf' are program-specific, and the intuitive
+ behavior is for values set on the command line with '--cnf-line' to
override them.
-‘--dpi=NUM’
- Set the resolution to NUM; this only affects ‘gf’ and ‘pk’ lookups.
- ‘-D’ is a synonym, for compatibility with Dvips. Default is 600.
+'--dpi=NUM'
+ Set the resolution to NUM; this only affects 'gf' and 'pk' lookups.
+ '-D' is a synonym, for compatibility with Dvips. Default is 600.
-‘--engine=NAME’
+'--engine=NAME'
Set the engine name to NAME. By default it is not set. The engine
name is used in some search paths to allow files with the same name
but used by different engines to coexist.
- In particular, since the memory dump files (‘.fmt’/‘.base’/‘.mem’)
- are now stored in subdirectories named for the engine (‘tex’,
- ‘pdftex’, ‘xetex’, etc.), you must specify an engine name in order
- to find them. For example, ‘cont-en.fmt’ typically exists for both
- ‘pdftex’ and ‘xetex’. With the default path settings, you can use
- ‘--engine=/’ to look for any dump file, regardless of engine; if a
- dump file exists for more than one engine, it’s indeterminate which
- one is returned. (The ‘/’ ends up specifying a normal recursive
+ In particular, since the memory dump files ('.fmt'/'.base'/'.mem')
+ are now stored in subdirectories named for the engine ('tex',
+ 'pdftex', 'xetex', etc.), you must specify an engine name in order
+ to find them. For example, 'cont-en.fmt' typically exists for both
+ 'pdftex' and 'xetex'. With the default path settings, you can use
+ '--engine=/' to look for any dump file, regardless of engine; if a
+ dump file exists for more than one engine, it's indeterminate which
+ one is returned. (The '/' ends up specifying a normal recursive
search along the path where the dumps are stored, namely
- ‘$TEXMF/web2c{/$engine,}’.)
+ '$TEXMF/web2c{/$engine,}'.)
-‘--format=NAME’
+'--format=NAME'
Set the format for lookup to NAME. By default, the format is
- guessed from the filename, with ‘tex’ being used if nothing else
+ guessed from the filename, with 'tex' being used if nothing else
fits. The recognized filename extensions (including any leading
- ‘.’) are also allowable NAMEs.
+ '.') are also allowable NAMEs.
All formats also have a name, which is the only way to specify
formats with no associated suffix. For example, for Dvips
- configuration files you can use ‘--format="dvips config"’. (The
+ configuration files you can use '--format="dvips config"'. (The
quotes are for the sake of the shell.)
- Here’s the current list of recognized names and the associated
+ Here's the current list of recognized names and the associated
suffixes. *Note Supported file formats::, for more information on
each of these.
The strings in parentheses are abbreviations recognized only by
- ‘kpsewhich’ (not the underlying library calls). They are provided
+ 'kpsewhich' (not the underlying library calls). They are provided
when it would otherwise require an argument containing a space to
specify the format, to simplify quoting of calls from shells.
@@ -1330,43 +1330,43 @@
ris: .ris
bltxml: .bltxml
- This option and ‘--path’ are mutually exclusive.
+ This option and '--path' are mutually exclusive.
-‘--interactive’
+'--interactive'
After processing the command line, read additional filenames to
look up from standard input.
-‘--mktex=FILETYPE’
-‘--no-mktex=FILETYPE’
- Turn on or off the ‘mktex’ script associated with FILETYPE. Usual
- values for FILETYPE are ‘pk’, ‘mf’, ‘tex’, and ‘tfm’. By default,
+'--mktex=FILETYPE'
+'--no-mktex=FILETYPE'
+ Turn on or off the 'mktex' script associated with FILETYPE. Usual
+ values for FILETYPE are 'pk', 'mf', 'tex', and 'tfm'. By default,
all are off in Kpsewhich, even if they are enabled for TeX. This
- option implies setting ‘--must-exist’. *Note mktex scripts::.
+ option implies setting '--must-exist'. *Note mktex scripts::.
-‘--mode=STRING’
- Set the mode name to STRING; this also only affects ‘gf’ and ‘pk’
+'--mode=STRING'
+ Set the mode name to STRING; this also only affects 'gf' and 'pk'
lookups. No default: any mode will be found. *Note mktex script
arguments::.
-‘--must-exist’
+'--must-exist'
Do everything possible to find the files, notably including
- searching the disk and running the ‘mktex’ scripts. By default,
- only the ‘ls-R’ database is checked, in the interest of efficiency.
+ searching the disk and running the 'mktex' scripts. By default,
+ only the 'ls-R' database is checked, in the interest of efficiency.
-‘--path=STRING’
+'--path=STRING'
Search along the path STRING (colon-separated as usual), instead of
- guessing the search path from the filename. ‘//’ and all the usual
+ guessing the search path from the filename. '//' and all the usual
expansions are supported (*note Path expansion::). This option and
- ‘--format’ are mutually exclusive. To output the complete
+ '--format' are mutually exclusive. To output the complete
directory expansion of a path, instead of doing a one-shot lookup,
- see ‘--expand-path’ and ‘--show-path’ in the following section.
+ see '--expand-path' and '--show-path' in the following section.
-‘--progname=NAME’
- Set the program name to NAME; default is ‘kpsewhich’. This can
- affect the search paths via the ‘.PROGNAM’ feature in configuration
+'--progname=NAME'
+ Set the program name to NAME; default is 'kpsewhich'. This can
+ affect the search paths via the '.PROGNAM' feature in configuration
files (*note Config files::).
-‘--subdir=STRING’
+'--subdir=STRING'
Report only those matches whose directory part _ends_ with STRING
(compared literally, except case is ignored on a case-insensitive
operating system). For example, suppose there are two matches for
@@ -1373,108 +1373,108 @@
a given name:
kpsewhich foo.sty
- ⇒ /some/where/foo.sty
+ => /some/where/foo.sty
/another/place/foo.sty
Then we can narrow the result to what we are interested in with
- ‘--subdir’:
+ '--subdir':
kpsewhich --subdir=where foo.sty
- ⇒ /some/where/foo.sty
+ => /some/where/foo.sty
kpsewhich --subdir=place foo.sty
- ⇒ /another/place/foo.sty
+ => /another/place/foo.sty
The string to match must be at the end of the directory part of the
match, and it is taken literally, with no pattern matching:
kpsewhich --subdir=another foo.sty
- ⇒
+ =>
The string to match may cross directory components:
kpsewhich --subdir=some/where foo.sty
- ⇒ /some/where/foo.sty
+ => /some/where/foo.sty
- ‘--subdir’ implies ‘--all’; if there is more than one match, they
- will all be reported (in our example, both ‘where’ and ‘place’ end
- in ‘e’):
+ '--subdir' implies '--all'; if there is more than one match, they
+ will all be reported (in our example, both 'where' and 'place' end
+ in 'e'):
kpsewhich --subdir=e
- ⇒ /some/where/foo.sty
+ => /some/where/foo.sty
/another/place/foo.sty
- Because of the above rules, the presence of a leading ‘/’ is
- important, since it “anchors” the match to a full component name:
+ Because of the above rules, the presence of a leading '/' is
+ important, since it "anchors" the match to a full component name:
kpsewhich --subdir=/lace foo.sty
- ⇒
+ =>
- However, a trailing ‘/’ is immaterial (and ignored), since the
+ However, a trailing '/' is immaterial (and ignored), since the
match always takes place at the end of the directory part:
kpsewhich --subdir=lace/ foo.sty
- ⇒ /another/place/foo.sty
+ => /another/place/foo.sty
The purpose of these rules is to make it convenient to find results
only within a particular area of the tree. For instance, a given
- script named ‘foo.lua’ might exist within both
- ‘texmf-dist/scripts/pkg1/’ and ‘texmf-dist/scripts/pkg2/’. By
- specifying, say, ‘--subdir=/pkg1’, you can be sure of getting the
+ script named 'foo.lua' might exist within both
+ 'texmf-dist/scripts/pkg1/' and 'texmf-dist/scripts/pkg2/'. By
+ specifying, say, '--subdir=/pkg1', you can be sure of getting the
one you are interested in.
We only match at the end because a site might happen to install TeX
- in ‘/some/coincidental/pkg1/path/’, and we wouldn’t want to match
- ‘texmf-dist/scripts/pkg2/’ that when searching for ‘/pkg1’.
+ in '/some/coincidental/pkg1/path/', and we wouldn't want to match
+ 'texmf-dist/scripts/pkg2/' that when searching for '/pkg1'.
File: kpathsea.info, Node: Specially-recognized files, Next: Auxiliary tasks, Prev: Path searching options, Up: Invoking kpsewhich
-5.6.2 Specially-recognized files for ‘kpsewhich’
+5.6.2 Specially-recognized files for 'kpsewhich'
------------------------------------------------
-‘kpsewhich’ recognizes a few special filenames on the command line and
-defaults to using the ‘known’ file formats for them, merely to save the
+'kpsewhich' recognizes a few special filenames on the command line and
+defaults to using the 'known' file formats for them, merely to save the
time and trouble of specifying the format. This is only a feature of
-‘kpsewhich’; when using the Kpathsea library itself, none of these
-special filenames are recognized, and it’s still up to the caller to
+'kpsewhich'; when using the Kpathsea library itself, none of these
+special filenames are recognized, and it's still up to the caller to
specify the desired format.
- Here is the list of special filenames to ‘kpsewhich’, along with
+ Here is the list of special filenames to 'kpsewhich', along with
their corresponding format:
-‘config.ps’
- ‘dvips config’
+'config.ps'
+ 'dvips config'
-‘dvipdfmx.cfg’
- ‘other text files’
+'dvipdfmx.cfg'
+ 'other text files'
-‘fmtutil.cnf’
- ‘web2c files’
+'fmtutil.cnf'
+ 'web2c files'
-‘glyphlist.txt’
- ‘map’
+'glyphlist.txt'
+ 'map'
-‘mktex.cnf’
- ‘web2c files’
+'mktex.cnf'
+ 'web2c files'
-‘pdfglyphlist.txt’
- ‘map’
+'pdfglyphlist.txt'
+ 'map'
-‘pdftex.cfg’
- ‘pdftex config’ (although ‘pdftex.cfg’ is not used any more; look
- for the file ‘pdftexconfig.tex’ instead.)
+'pdftex.cfg'
+ 'pdftex config' (although 'pdftex.cfg' is not used any more; look
+ for the file 'pdftexconfig.tex' instead.)
-‘texmf.cnf’
- ‘cnf’
+'texmf.cnf'
+ 'cnf'
-‘XDvi’
- ‘other text files’
+'XDvi'
+ 'other text files'
A user-specified format will override the above defaults.
- Another useful configuration file in this regard is ‘tcfmgr.map’,
-found in ‘texmf/texconfig/tcfmgr.map’, which records various information
+ Another useful configuration file in this regard is 'tcfmgr.map',
+found in 'texmf/texconfig/tcfmgr.map', which records various information
about the above configuration files (among others).
@@ -1485,84 +1485,84 @@
Kpsewhich provides some features in addition to path lookup as such:
-‘--debug=NUM’
+'--debug=NUM'
Set debugging options to NUM. *Note Debugging::.
-‘--expand-braces=STRING’
+'--expand-braces=STRING'
Output variable, tilde, and brace expansion of STRING, which is
assumed to be a single path element. *Note Path expansion::.
-‘--expand-path=STRING’
+'--expand-path=STRING'
Output the complete expansion of STRING, with each element
- separated by the usual path separator on the current system (‘;’ on
- Windows, ‘:’ otherwise). This may be useful to construct a custom
+ separated by the usual path separator on the current system (';' on
+ Windows, ':' otherwise). This may be useful to construct a custom
search path for a format not otherwise supported. To retrieve the
search path for a format that is already supported, see
- ‘--show-path’.
+ '--show-path'.
Nonexistent directories are culled from the output:
$ kpsewhich --expand-path '/tmp'
- ⇒ /tmp
+ => /tmp
$ kpsewhich --expand-path '/nonesuch'
- ⇒
+ =>
For one-shot uses of an arbitrary (not built in to Kpathsea) path,
- see ‘--path’ (*note Path searching options::).
+ see '--path' (*note Path searching options::).
-‘--expand-var=STRING’
+'--expand-var=STRING'
Output the variable and tilde expansion of STRING. For example,
- with the usual ‘texmf.cnf’, ‘kpsewhich --expand-var='$TEXMF'’
+ with the usual 'texmf.cnf', 'kpsewhich --expand-var='$TEXMF''
returns the TeX system hierarchy root(s). *Note Path expansion::.
The specified STRING can contain anything, though, not just
- variable references. This calls ‘kpse_var_expand’ (*note
+ variable references. This calls 'kpse_var_expand' (*note
Programming with config files::).
-‘--help-formats’
+'--help-formats'
Output information about each supported format (*note Supported
file formats::), including the names and abbreviations, variables
looked for, and the original path.
-‘--safe-in-name=NAME’
-‘--safe-out-name=NAME’
+'--safe-in-name=NAME'
+'--safe-out-name=NAME'
Exit successfully if NAME is safe to open for reading or writing,
respectively, else unsuccessfully. No output is written. These
tests take account of the related Kpathsea configuration settings
(*note Calling sequence::).
-‘--show-path=NAME’
+'--show-path=NAME'
Show the path that would be used for file lookups of file type
- NAME. Either a filename extension (‘pk’, ‘.vf’, etc.) or an
- integer can be used, just as with ‘--format’, described in the
+ NAME. Either a filename extension ('pk', '.vf', etc.) or an
+ integer can be used, just as with '--format', described in the
previous section.
-‘--var-brace-value=VARIABLE’
- Like ‘--var-value’ (next), but also expands ‘{...}’ constructs.
+'--var-brace-value=VARIABLE'
+ Like '--var-value' (next), but also expands '{...}' constructs.
(*note Brace expansion::). Thus, the value is assumed to possibly
- be several path elements, and ‘~’ is expanded at the beginning of
+ be several path elements, and '~' is expanded at the beginning of
each. The path separator is changed to that of the current system
in the expansion.
- Example: ‘FOO='.;~' kpsewhich --var-brace-value=FOO’ outputs (on a
- Unix-ish system) ‘.:/home/karl’, supposing the latter is the
- current user’s home directory. Note that the ‘;’ in the source
- value, as commonly used in ‘texmf.cnf’, has changed to a ‘:’, as
+ Example: 'FOO='.;~' kpsewhich --var-brace-value=FOO' outputs (on a
+ Unix-ish system) '.:/home/karl', supposing the latter is the
+ current user's home directory. Note that the ';' in the source
+ value, as commonly used in 'texmf.cnf', has changed to a ':', as
the normal path separator on the current system. On a Windows-ish
- system, the ‘;’ would remain.
+ system, the ';' would remain.
-‘--var-value=VARIABLE’
+'--var-value=VARIABLE'
Outputs the value of VARIABLE (a simple identifier like
- ‘TEXMFDIST’, with no ‘$’ or other constructs), expanding ‘$’ (*note
- Variable expansion::) and ‘~’ (*note Tilde expansion::) constructs
- in the value. ‘~’ expansion happens at the beginning of the
+ 'TEXMFDIST', with no '$' or other constructs), expanding '$' (*note
+ Variable expansion::) and '~' (*note Tilde expansion::) constructs
+ in the value. '~' expansion happens at the beginning of the
overall value and at the beginning of a variable expansion, but not
arbitrarily within the string. Braces are not expanded.
- Example: ‘--var-value=texmf_casefold_search’ outputs (if the
- default is not changed) ‘1’.
+ Example: '--var-value=texmf_casefold_search' outputs (if the
+ default is not changed) '1'.
- Example to contrast with ‘--var-brace-value’: ‘FOO='.;~' kpsewhich
- --var-value=FOO’ outputs ‘.;~’, i.e., the same as the input value,
+ Example to contrast with '--var-brace-value': 'FOO='.;~' kpsewhich
+ --var-value=FOO' outputs '.;~', i.e., the same as the input value,
on all systems.
@@ -1573,10 +1573,10 @@
Kpsewhich accepts the standard GNU options:
- • ‘--help’ prints a help message on standard output and exits
+ * '--help' prints a help message on standard output and exits
successfully.
- • ‘--version’ prints the Kpathsea version number and exits
+ * '--version' prints the Kpathsea version number and exits
successfully.
@@ -1599,8 +1599,8 @@
Kpathsea provides a standard way to search for files of any of the
supported file types; glyph fonts are a bit different than all the rest.
-Searches are based solely on names of files, not their contents—if a GF
-file is (mis)named ‘cmr10.600pk’, it will be found as a PK file.
+Searches are based solely on names of files, not their contents--if a GF
+file is (mis)named 'cmr10.600pk', it will be found as a PK file.
* Menu:
@@ -1623,253 +1623,253 @@
suffixes, and/or a program to be run to create missing files on the fly.
Since environment variables containing periods, such as
-‘TEXINPUTS.latex’, are not allowed on some systems, Kpathsea looks for
-environment variables with an underscore, e.g., ‘TEXINPUTS_latex’ (*note
+'TEXINPUTS.latex', are not allowed on some systems, Kpathsea looks for
+environment variables with an underscore, e.g., 'TEXINPUTS_latex' (*note
Config files::).
The following table lists the above information. You can also get
-the list by giving the ‘--help-formats’ option to ‘kpsewhich’ (*note
+the list by giving the '--help-formats' option to 'kpsewhich' (*note
Auxiliary tasks::).
-‘afm’
- (Adobe font metrics, *note (dvips)Metric files::) ‘AFMFONTS’;
- suffix ‘.afm’.
+'afm'
+ (Adobe font metrics, *note (dvips)Metric files::) 'AFMFONTS';
+ suffix '.afm'.
-‘base’
- (Metafont memory dump, *note (web2c)Memory dumps::) ‘MFBASES’,
- ‘TEXMFINI’; suffix ‘.base’.
+'base'
+ (Metafont memory dump, *note (web2c)Memory dumps::) 'MFBASES',
+ 'TEXMFINI'; suffix '.base'.
-‘bib’
+'bib'
(BibTeX bibliography source, *note (web2c)bibtex invocation::)
- ‘BIBINPUTS’, ‘TEXBIB’; suffix ‘.bib’.
+ 'BIBINPUTS', 'TEXBIB'; suffix '.bib'.
-‘bltxml’
+'bltxml'
(BibLaTeXML bibliography files for Biber,
- <https://ctan.org/pkg/biber>) ‘BLTXMLINPUTS’ suffix ‘.bltxml’.
+ <https://ctan.org/pkg/biber>) 'BLTXMLINPUTS' suffix '.bltxml'.
-‘bst’
+'bst'
(BibTeX style, *note Basic BibTeX style files: (web2c)Basic BibTeX
- style files.) ‘BSTINPUTS’; suffix ‘.bst’.
+ style files.) 'BSTINPUTS'; suffix '.bst'.
-‘clua’
+'clua'
(dynamic libraries for Lua, <https://ctan.org/pkg/luatex>)
- ‘CLUAINPUTS’ suffixes ‘.dll’ and ‘.so’.
+ 'CLUAINPUTS' suffixes '.dll' and '.so'.
-‘cmap’
- (character map files) ‘CMAPFONTS’; suffix ‘.cmap’.
+'cmap'
+ (character map files) 'CMAPFONTS'; suffix '.cmap'.
-‘cnf’
- (Runtime configuration files, *note Config files::) ‘TEXMFCNF’;
- suffix ‘.cnf’.
+'cnf'
+ (Runtime configuration files, *note Config files::) 'TEXMFCNF';
+ suffix '.cnf'.
-‘cweb’
- (CWEB input files) ‘CWEBINPUTS’; suffixes ‘.w’, ‘.web’; additional
- suffix ‘.ch’.
+'cweb'
+ (CWEB input files) 'CWEBINPUTS'; suffixes '.w', '.web'; additional
+ suffix '.ch'.
-‘dvips config’
- (Dvips ‘config.*’ files, such as ‘config.ps’, *note (dvips)Config
- files::) ‘TEXCONFIG’.
+'dvips config'
+ (Dvips 'config.*' files, such as 'config.ps', *note (dvips)Config
+ files::) 'TEXCONFIG'.
-‘enc files’
- (encoding vectors) ‘ENCFONTS’; suffix ‘.enc’.
+'enc files'
+ (encoding vectors) 'ENCFONTS'; suffix '.enc'.
-‘fmt’
- (TeX memory dump, *note (web2c)Memory dumps::) ‘TEXFORMATS’,
- ‘TEXMFINI’; suffix ‘.fmt’.
+'fmt'
+ (TeX memory dump, *note (web2c)Memory dumps::) 'TEXFORMATS',
+ 'TEXMFINI'; suffix '.fmt'.
-‘font cid map’
- (CJK mapping) ‘FONTCIDMAPS’ suffix ‘.cid’.
+'font cid map'
+ (CJK mapping) 'FONTCIDMAPS' suffix '.cid'.
-‘font feature files’
- (primarily for OpenType font features) ‘FONTFEATURES’ suffix
- ‘.fea’.
+'font feature files'
+ (primarily for OpenType font features) 'FONTFEATURES' suffix
+ '.fea'.
-‘gf’
- (generic font bitmap, *note (dvips)Glyph files::) ‘PROGRAMFONTS’,
- ‘GFFONTS’, ‘GLYPHFONTS’, ‘TEXFONTS’; suffix ‘gf’.
+'gf'
+ (generic font bitmap, *note (dvips)Glyph files::) 'PROGRAMFONTS',
+ 'GFFONTS', 'GLYPHFONTS', 'TEXFONTS'; suffix 'gf'.
-‘graphic/figure’
+'graphic/figure'
(Encapsulated PostScript figures, *note (dvips)PostScript
- figures::) ‘TEXPICTS’, ‘TEXINPUTS’; additional suffixes: ‘.eps’,
- ‘.epsi’.
+ figures::) 'TEXPICTS', 'TEXINPUTS'; additional suffixes: '.eps',
+ '.epsi'.
-‘ist’
- (makeindex style files) ‘TEXINDEXSTYLE’, ‘INDEXSTYLE’; suffix
- ‘.ist’.
+'ist'
+ (makeindex style files) 'TEXINDEXSTYLE', 'INDEXSTYLE'; suffix
+ '.ist'.
-‘lig files’
- (ligature definition files) ‘LIGFONTS’; suffix ‘.lig’.
+'lig files'
+ (ligature definition files) 'LIGFONTS'; suffix '.lig'.
-‘ls-R’
- (Filename databases, *note Filename database::) ‘TEXMFDBS’.
+'ls-R'
+ (Filename databases, *note Filename database::) 'TEXMFDBS'.
-‘lua’
- (Lua scripts, <https://ctan.org/pkg/luatex>) ‘LUAINPUTS’ suffixes
- ‘.lua’, ‘.luatex’, ‘.luc’, ‘.luctex’, ‘.texlua’, ‘.texluc’, ‘.tlu’.
+'lua'
+ (Lua scripts, <https://ctan.org/pkg/luatex>) 'LUAINPUTS' suffixes
+ '.lua', '.luatex', '.luc', '.luctex', '.texlua', '.texluc', '.tlu'.
-‘map’
- (Fontmaps, *note Fontmap::) ‘TEXFONTMAPS’; suffix ‘.map’.
+'map'
+ (Fontmaps, *note Fontmap::) 'TEXFONTMAPS'; suffix '.map'.
-‘mem’
- (MetaPost memory dump, *note (web2c)Memory dumps::) ‘MPMEMS’,
- ‘TEXMFINI’; suffix ‘.mem’.
+'mem'
+ (MetaPost memory dump, *note (web2c)Memory dumps::) 'MPMEMS',
+ 'TEXMFINI'; suffix '.mem'.
-‘MetaPost support’
+'MetaPost support'
(MetaPost support files, used by DMP; *note (web2c)dmp
- invocation::) ‘MPSUPPORT’.
+ invocation::) 'MPSUPPORT'.
-‘mf’
- (Metafont source, *note (web2c)mf invocation::) ‘MFINPUTS’; suffix
- ‘.mf’; dynamic creation program: ‘mktexmf’.
+'mf'
+ (Metafont source, *note (web2c)mf invocation::) 'MFINPUTS'; suffix
+ '.mf'; dynamic creation program: 'mktexmf'.
-‘mfpool’
+'mfpool'
(Metafont program strings, *note (web2c)pooltype invocation::)
- ‘MFPOOL’, ‘TEXMFINI’; suffix ‘.pool’.
+ 'MFPOOL', 'TEXMFINI'; suffix '.pool'.
-‘mft’
- (‘MFT’ style file, *note (web2c)mft invocation::) ‘MFTINPUTS’;
- suffix ‘.mft’.
+'mft'
+ ('MFT' style file, *note (web2c)mft invocation::) 'MFTINPUTS';
+ suffix '.mft'.
-‘misc fonts’
- (font-related files that don’t fit the other categories)
- ‘MISCFONTS’
+'misc fonts'
+ (font-related files that don't fit the other categories)
+ 'MISCFONTS'
-‘mlbib’
- (MlBibTeX bibliography source) ‘MLBIBINPUTS’, ‘BIBINPUTS’,
- ‘TEXBIB’; suffixes ‘.mlbib’, ‘.mlbib’.
+'mlbib'
+ (MlBibTeX bibliography source) 'MLBIBINPUTS', 'BIBINPUTS',
+ 'TEXBIB'; suffixes '.mlbib', '.mlbib'.
-‘mlbst’
- (MlBibTeX style) ‘MLBSTINPUTS’, ‘BSTINPUTS’; suffixes ‘.mlbst’,
- ‘.bst’.
+'mlbst'
+ (MlBibTeX style) 'MLBSTINPUTS', 'BSTINPUTS'; suffixes '.mlbst',
+ '.bst'.
-‘mp’
- (MetaPost source, *note (web2c)mpost invocation::) ‘MPINPUTS’;
- suffix ‘.mp’.
+'mp'
+ (MetaPost source, *note (web2c)mpost invocation::) 'MPINPUTS';
+ suffix '.mp'.
-‘mppool’
+'mppool'
(MetaPost program strings, *note (web2c)pooltype invocation::)
- ‘MPPOOL’, ‘TEXMFINI’; suffix ‘.pool’.
+ 'MPPOOL', 'TEXMFINI'; suffix '.pool'.
-‘ocp’
- (Omega compiled process files) ‘OCPINPUTS’;
- suffix ‘.ocp’; dynamic creation program: ‘MakeOmegaOCP’.
+'ocp'
+ (Omega compiled process files) 'OCPINPUTS';
+ suffix '.ocp'; dynamic creation program: 'MakeOmegaOCP'.
-‘ofm’
- (Omega font metrics) ‘OFMFONTS’, ‘TEXFONTS’;
- suffixes ‘.ofm’, ‘.tfm’; dynamic creation program: ‘MakeOmegaOFM’.
+'ofm'
+ (Omega font metrics) 'OFMFONTS', 'TEXFONTS';
+ suffixes '.ofm', '.tfm'; dynamic creation program: 'MakeOmegaOFM'.
-‘opentype fonts’
- (OpenType fonts) ‘OPENTYPEFONTS’.
+'opentype fonts'
+ (OpenType fonts) 'OPENTYPEFONTS'.
-‘opl’
- (Omega property lists) ‘OPLFONTS’, ‘TEXFONTS’; suffix ‘.opl’.
+'opl'
+ (Omega property lists) 'OPLFONTS', 'TEXFONTS'; suffix '.opl'.
-‘otp’
- (Omega translation process files) ‘OTPINPUTS’; suffix ‘.otp’.
+'otp'
+ (Omega translation process files) 'OTPINPUTS'; suffix '.otp'.
-‘ovf’
- (Omega virtual fonts) ‘OVFFONTS’, ‘TEXFONTS’; suffix ‘.ovf’.
+'ovf'
+ (Omega virtual fonts) 'OVFFONTS', 'TEXFONTS'; suffix '.ovf'.
-‘ovp’
- (Omega virtual property lists) ‘OVPFONTS’, ‘TEXFONTS’; suffix
- ‘.ovp’.
+'ovp'
+ (Omega virtual property lists) 'OVPFONTS', 'TEXFONTS'; suffix
+ '.ovp'.
-‘pdftex config’
- (PDFTeX-specific configuration files) ‘PDFTEXCONFIG’.
+'pdftex config'
+ (PDFTeX-specific configuration files) 'PDFTEXCONFIG'.
-‘pk’
- (packed bitmap fonts, *note (dvips)Glyph files::) ‘PROGRAMFONTS’
- (PROGRAM being ‘XDVI’, etc.), ‘PKFONTS’, ‘TEXPKS’, ‘GLYPHFONTS’,
- ‘TEXFONTS’; suffix ‘pk’; dynamic creation program: ‘mktexpk’.
+'pk'
+ (packed bitmap fonts, *note (dvips)Glyph files::) 'PROGRAMFONTS'
+ (PROGRAM being 'XDVI', etc.), 'PKFONTS', 'TEXPKS', 'GLYPHFONTS',
+ 'TEXFONTS'; suffix 'pk'; dynamic creation program: 'mktexpk'.
-‘PostScript header’
+'PostScript header'
(downloadable PostScript, *note (dvips)Header files::)
- ‘TEXPSHEADERS’, ‘PSHEADERS’; additional suffix ‘.pro’.
+ 'TEXPSHEADERS', 'PSHEADERS'; additional suffix '.pro'.
-‘ris’
+'ris'
(RIS bibliography files, primarily for Biber,
- <https://ctan.org/pkg/biber>) ‘RISINPUTS’ suffix ‘.ris’.
+ <https://ctan.org/pkg/biber>) 'RISINPUTS' suffix '.ris'.
-‘subfont definition files’
- (subfont definition files) ‘SFDFONTS’ suffix ‘.sfd’.
+'subfont definition files'
+ (subfont definition files) 'SFDFONTS' suffix '.sfd'.
-‘tex’
- (TeX source, *note (web2c)tex invocation::) ‘TEXINPUTS’; suffix
- ‘.tex’; additional suffixes: none, because such a list cannot be
- complete; dynamic creation program: ‘mktextex’.
+'tex'
+ (TeX source, *note (web2c)tex invocation::) 'TEXINPUTS'; suffix
+ '.tex'; additional suffixes: none, because such a list cannot be
+ complete; dynamic creation program: 'mktextex'.
-‘TeX system documentation’
- (Documentation files for the TeX system) ‘TEXDOCS’.
+'TeX system documentation'
+ (Documentation files for the TeX system) 'TEXDOCS'.
-‘TeX system sources’
- (Source files for the TeX system) ‘TEXSOURCES’.
+'TeX system sources'
+ (Source files for the TeX system) 'TEXSOURCES'.
-‘texmfscripts’
+'texmfscripts'
(Architecture-independent executables distributed in the texmf
- trees) ‘TEXMFSCRIPTS’.
+ trees) 'TEXMFSCRIPTS'.
-‘texpool’
+'texpool'
(TeX program strings, *note (web2c)pooltype invocation::)
- ‘TEXPOOL’, ‘TEXMFINI’; suffix ‘.pool’.
+ 'TEXPOOL', 'TEXMFINI'; suffix '.pool'.
-‘tfm’
- (TeX font metrics, *note (dvips)Metric files::) ‘TFMFONTS’,
- ‘TEXFONTS’; suffix ‘.tfm’; dynamic creation program: ‘mktextfm’.
+'tfm'
+ (TeX font metrics, *note (dvips)Metric files::) 'TFMFONTS',
+ 'TEXFONTS'; suffix '.tfm'; dynamic creation program: 'mktextfm'.
-‘Troff fonts’
+'Troff fonts'
(Troff fonts, used by DMP; *note (web2c)DMP invocation::)
- ‘TRFONTS’.
+ 'TRFONTS'.
-‘truetype fonts’
- (TrueType outline fonts) ‘TTFONTS’; suffixes ‘.ttf’ and ‘.TTF’,
- ‘.ttc’ and ‘.TTC’, ‘.dfont’.
+'truetype fonts'
+ (TrueType outline fonts) 'TTFONTS'; suffixes '.ttf' and '.TTF',
+ '.ttc' and '.TTC', '.dfont'.
-‘type1 fonts’
+'type1 fonts'
(Type 1 PostScript outline fonts, *note (dvips)Glyph files::)
- ‘T1FONTS’, ‘T1INPUTS’, ‘TEXPSHEADERS’, ‘DVIPSHEADERS’; suffixes
- ‘.pfa’, ‘.pfb’.
+ 'T1FONTS', 'T1INPUTS', 'TEXPSHEADERS', 'DVIPSHEADERS'; suffixes
+ '.pfa', '.pfb'.
-‘type42 fonts’
- (Type 42 PostScript outline fonts) ‘T42FONTS’.
+'type42 fonts'
+ (Type 42 PostScript outline fonts) 'T42FONTS'.
-‘vf’
- (virtual fonts, *note (dvips)Virtual fonts::) ‘VFFONTS’,
- ‘TEXFONTS’; suffix ‘.vf’.
+'vf'
+ (virtual fonts, *note (dvips)Virtual fonts::) 'VFFONTS',
+ 'TEXFONTS'; suffix '.vf'.
-‘web’
- (WEB input files) ‘WEBINPUTS’; suffix ‘.web’; additional suffix
- ‘.ch’.
+'web'
+ (WEB input files) 'WEBINPUTS'; suffix '.web'; additional suffix
+ '.ch'.
-‘web2c files’
- (files specific to the web2c implementation) ‘WEB2C’.
+'web2c files'
+ (files specific to the web2c implementation) 'WEB2C'.
There are two special cases, because the paths and environment
variables always depend on the name of the program: the variable name is
constructed by converting the program name to upper case, and then
-appending ‘INPUTS’. Assuming the program is called ‘foo’, this gives us
+appending 'INPUTS'. Assuming the program is called 'foo', this gives us
the following table.
-‘other text files’
- (text files used by ‘foo’) ‘FOOINPUTS’.
+'other text files'
+ (text files used by 'foo') 'FOOINPUTS'.
-‘other binary files’
- (binary files used by ‘foo’) ‘FOOINPUTS’.
+'other binary files'
+ (binary files used by 'foo') 'FOOINPUTS'.
If an environment variable by these names are set, the corresponding
-‘texmf.cnf’ definition won’t be looked at (unless, as usual, the
-environment variable value has an extra ‘:’). *Note Default
+'texmf.cnf' definition won't be looked at (unless, as usual, the
+environment variable value has an extra ':'). *Note Default
expansion::.
For the font variables, the intent is that:
- • ‘TEXFONTS’ is the default for everything.
+ * 'TEXFONTS' is the default for everything.
- • ‘GLYPHFONTS’ is the default for bitmap (or, more precisely,
+ * 'GLYPHFONTS' is the default for bitmap (or, more precisely,
non-metric) files.
- • Each font format has a variable of its own.
+ * Each font format has a variable of its own.
- • Each program has its own font override path as well; e.g.,
- ‘DVIPSFONTS’ for Dvipsk. Again, this is for bitmaps, not metrics.
+ * Each program has its own font override path as well; e.g.,
+ 'DVIPSFONTS' for Dvipsk. Again, this is for bitmaps, not metrics.
File: kpathsea.info, Node: File lookup, Next: Glyph lookup, Prev: Supported file formats, Up: TeX support
@@ -1885,31 +1885,31 @@
1. If the file format defines default suffixes, and the suffix of NAME
name is not already a known suffix for that format, try the name
with each default appended, and use alternative names found in the
- fontmaps if necessary. Example: given ‘foo.bar’, look for
- ‘foo.bar.tex’.
+ fontmaps if necessary. Example: given 'foo.bar', look for
+ 'foo.bar.tex'.
2. Search for NAME, and if necessary for alternative names found in
- the fontmaps. Example: given ‘foo.bar’, we also look for
- ‘foo.bar’.
+ the fontmaps. Example: given 'foo.bar', we also look for
+ 'foo.bar'.
3. If the file format defines a program to invoke to create missing
files, run it (*note mktex scripts::).
- The order in which we search for “suffixed” name (item 1) or the
-“as-is” name (item 2) is controlled by the ‘try_std_extension_first’
-configuration value. The default set in ‘texmf.cnf’ is true, since
-common suffixes are already recognized: ‘babel.sty’ will only look for
-‘babel.sty’, not ‘babel.sty.tex’, regardless of this setting.
+ The order in which we search for "suffixed" name (item 1) or the
+"as-is" name (item 2) is controlled by the 'try_std_extension_first'
+configuration value. The default set in 'texmf.cnf' is true, since
+common suffixes are already recognized: 'babel.sty' will only look for
+'babel.sty', not 'babel.sty.tex', regardless of this setting.
- When the suffix is unknown (e.g., ‘foo.bar’), both names are always
+ When the suffix is unknown (e.g., 'foo.bar'), both names are always
tried; the difference is the order in which they are tried.
- ‘try_std_extension_first’ only affects names being looked up which
-*already* have an extension. A name without an extension (e.g., ‘tex
-story’) will always have an extension added first.
+ 'try_std_extension_first' only affects names being looked up which
+*already* have an extension. A name without an extension (e.g., 'tex
+story') will always have an extension added first.
- This algorithm is implemented in the function ‘kpathsea_find_file’ in
-the source file ‘kpathsea/tex-file.c’. You can watch it in action with
+ This algorithm is implemented in the function 'kpathsea_find_file' in
+the source file 'kpathsea/tex-file.c'. You can watch it in action with
the debugging options (*note Debugging::).
@@ -1919,7 +1919,7 @@
================
This section describes how Kpathsea searches for a bitmap font in GF or
-PK format (or either) given a font name (e.g., ‘cmr10’) and a resolution
+PK format (or either) given a font name (e.g., 'cmr10') and a resolution
(e.g., 600).
Here is an outline of the search strategy (details in the sections
@@ -1930,16 +1930,16 @@
format(s).
2. If NAME is an alias for a file F in the fontmap file
- ‘texfonts.map’, look for F.DPI.
+ 'texfonts.map', look for F.DPI.
- 3. Run an external program (typically named ‘mktexpk’) to generate the
+ 3. Run an external program (typically named 'mktexpk') to generate the
font (*note mktex scripts::)
4. Look for FALLBACK.DPI, where FALLBACK is some last-resort font
- (typically ‘cmr10’).
+ (typically 'cmr10').
- This is implemented in ‘kpathsea_find_glyph’ in
-‘kpathsea/tex-glyph.c’.
+ This is implemented in 'kpathsea_find_glyph' in
+'kpathsea/tex-glyph.c'.
* Menu:
@@ -1955,16 +1955,16 @@
When Kpathsea looks for a bitmap font NAME at resolution DPI in a format
FORMAT, it first checks each directory in the search path for a file
-‘NAME.DPIFORMAT’; for example, ‘cmr10.600pk’. Kpathsea looks for a PK
+'NAME.DPIFORMAT'; for example, 'cmr10.600pk'. Kpathsea looks for a PK
file first, then a GF file.
- If that fails, Kpathsea looks for ‘dpiDPI/NAME.FORMAT’; for example,
-‘dpi600/cmr10.pk’. This is how fonts are typically stored on
+ If that fails, Kpathsea looks for 'dpiDPI/NAME.FORMAT'; for example,
+'dpi600/cmr10.pk'. This is how fonts are typically stored on
filesystems (such as DOS) that permit only three-character extensions.
If that fails, Kpathsea looks for a font with a close-enough DPI.
-“Close enough” is defined by the macro ‘KPSE_BITMAP_TOLERANCE’ in
-‘kpathsea/tex-glyph.h’ to be ‘DPI / 500 + 1’. This is slightly more
+"Close enough" is defined by the macro 'KPSE_BITMAP_TOLERANCE' in
+'kpathsea/tex-glyph.h' to be 'DPI / 500 + 1'. This is slightly more
than the 0.2% minimum allowed by the DVI standard
(<CTAN:/dviware/driv-standard/level-0>).
@@ -1975,51 +1975,51 @@
-------------
If a bitmap font or metric file is not found with the original name (see
-the previous section), Kpathsea looks through any “fontmap” files for an
-“alias” for the original font name. These files are named
-‘texfonts.map’ and searched for along the ‘TEXFONTMAPS’
-environment/config file variable. All ‘texfonts.map’ files that are
+the previous section), Kpathsea looks through any "fontmap" files for an
+"alias" for the original font name. These files are named
+'texfonts.map' and searched for along the 'TEXFONTMAPS'
+environment/config file variable. All 'texfonts.map' files that are
found are read; earlier definitions override later ones.
This feature is intended to help in two respects:
1. An alias name is limited in length only by available memory, not by
- your filesystem. Therefore, if you want to ask for ‘Times-Roman’
- instead of ‘ptmr’, you can (you get ‘ptmr8r’).
+ your filesystem. Therefore, if you want to ask for 'Times-Roman'
+ instead of 'ptmr', you can (you get 'ptmr8r').
2. A few fonts have historically had multiple names: specifically,
- LaTeX’s “circle font” has variously been known as ‘circle10’,
- ‘lcircle10’, and ‘lcirc10’. Aliases can make all the names
+ LaTeX's "circle font" has variously been known as 'circle10',
+ 'lcircle10', and 'lcirc10'. Aliases can make all the names
equivalent, so that it no longer matters what the name of the
installed file is; TeX documents will find their favorite name.
The format of fontmap files:
- • Comments start with the last ‘%’ on a line and continue to the end
+ * Comments start with the last '%' on a line and continue to the end
of the line. (This provides for names that include a %,
ill-advised as that may be.)
- • Blank lines are ignored.
+ * Blank lines are ignored.
- • Each nonblank line is broken up into a series of “words”: a
+ * Each nonblank line is broken up into a series of "words": a
sequence of non-whitespace characters.
- • If the first word is ‘include’, the second word is used as a
+ * If the first word is 'include', the second word is used as a
filename, and it is searched for and read.
- • Otherwise, the first word on each line is the true filename;
+ * Otherwise, the first word on each line is the true filename;
- • the second word is the alias;
+ * the second word is the alias;
- • subsequent words are ignored.
+ * subsequent words are ignored.
If an alias has an extension, it matches only those files with that
extension; otherwise, it matches anything with the same root, regardless
-of extension. For example, an alias ‘foo.tfm’ matches only when
-‘foo.tfm’ is being searched for; but an alias ‘foo’ matches ‘foo.vf’,
-‘foo.600pk’, etc.
+of extension. For example, an alias 'foo.tfm' matches only when
+'foo.tfm' is being searched for; but an alias 'foo' matches 'foo.vf',
+'foo.600pk', etc.
- As an example, here is an excerpt from the ‘texfonts.map’ in the
+ As an example, here is an excerpt from the 'texfonts.map' in the
Web2c distribution. It makes the old and new names of the LaTeX circle
fonts equivalent.
@@ -2031,7 +2031,7 @@
lcirc10 lcircle10
...
- Fontmaps are implemented in the file ‘kpathsea/fontmap.c’. The
+ Fontmaps are implemented in the file 'kpathsea/fontmap.c'. The
Fontname distribution has much more information on font naming (*note
(fontname)::).
@@ -2042,17 +2042,17 @@
-------------------
If a bitmap font cannot be found or created at the requested size,
-Kpathsea looks for the font at a set of “fallback resolutions”. You
+Kpathsea looks for the font at a set of "fallback resolutions". You
specify these resolutions as a colon-separated list (like search paths).
Kpathsea looks first for a program-specific environment variable (e.g.,
-‘DVIPSSIZES’ for Dvipsk), then the environment variable ‘TEXSIZES’, then
+'DVIPSSIZES' for Dvipsk), then the environment variable 'TEXSIZES', then
a default specified at compilation time (the Make variable
-‘default_texsizes’). You can set this list to be empty if you prefer to
+'default_texsizes'). You can set this list to be empty if you prefer to
find fonts at their stated size or not at all.
Finally, if the font cannot be found even at the fallback
-resolutions, Kpathsea looks for a fallback font, typically ‘cmr10’.
-Programs must enable this feature by calling ‘kpathsea_init_prog’ (*note
+resolutions, Kpathsea looks for a fallback font, typically 'cmr10'.
+Programs must enable this feature by calling 'kpathsea_init_prog' (*note
Calling sequence::); the default is no fallback font.
@@ -2065,52 +2065,52 @@
this is useful at large sites where most users are not administrators,
and thus the warnings are merely a source of confusion, not a help. To
do this, you set the environment variable or configuration file value
-‘TEX_HUSH’ to a colon-separated list of values. Here are the
+'TEX_HUSH' to a colon-separated list of values. Here are the
possibilities:
-‘all’
+'all'
Suppress everything possible.
-‘checksum’
+'checksum'
Suppress mismatched font checksum warnings.
-‘lostchar’
+'lostchar'
Suppress warnings when a character is missing from a font that a
DVI or VF file tries to typeset.
-‘none’
- Don’t suppress any warnings.
+'none'
+ Don't suppress any warnings.
-‘readable’
+'readable'
Suppress warnings about attempts to access a file whose permissions
render it unreadable.
-‘special’
- Suppresses warnings about an unimplemented or unparsable ‘\special’
+'special'
+ Suppresses warnings about an unimplemented or unparsable '\special'
command.
-‘tex-hush.c’ defines the function that checks the variable value. Each
+'tex-hush.c' defines the function that checks the variable value. Each
driver implements its own checks where appropriate.
File: kpathsea.info, Node: mktex scripts, Prev: Suppressing warnings, Up: TeX support
-6.5 ‘mktex’ scripts
+6.5 'mktex' scripts
===================
If Kpathsea cannot otherwise find a file, for some file types it is
configured by default to invoke an external program to create it
dynamically (*note mktex configuration::). These are collectively known
-as “‘mktex’ scripts”, since most of them are named ‘mktex...’.
+as "'mktex' scripts", since most of them are named 'mktex...'.
- For example, this is useful for fonts (bitmaps, TFM’s, and
+ For example, this is useful for fonts (bitmaps, TFM's, and
arbitrarily-sizable Metafont sources such as the Sauter and EC fonts),
since any given document can use fonts never before referenced.
Building all fonts in advance is therefore impractical, if not
impossible.
- It is also useful for the TeX ‘.fmt’ (and Metafont ‘.base’ and
-Metapost ‘.mem’ files, *note (Web2c)Memory dumps::), where
+ It is also useful for the TeX '.fmt' (and Metafont '.base' and
+Metapost '.mem' files, *note (Web2c)Memory dumps::), where
pre-generating every format consumes a lot of both time and space.
The script is passed the name of the file to create and possibly
@@ -2127,13 +2127,13 @@
File: kpathsea.info, Node: mktex configuration, Next: mktex script names, Up: mktex scripts
-6.5.1 ‘mktex’ configuration
+6.5.1 'mktex' configuration
---------------------------
The list of file types and program names that can run an external
program to create missing files is listed in the next section. In the
-absence of ‘configure’ options specifying otherwise, everything but
-‘mktextex’ will be enabled by default. The ‘configure’ options to
+absence of 'configure' options specifying otherwise, everything but
+'mktextex' will be enabled by default. The 'configure' options to
change the defaults are:
--without-mktexfmt-default
@@ -2144,186 +2144,186 @@
--without-mktextfm-default
--with-mktextex-default
- The ‘configure’ setting is overridden if the environment variable or
-configuration file value named for the script is set; e.g., ‘MKTEXPK’
+ The 'configure' setting is overridden if the environment variable or
+configuration file value named for the script is set; e.g., 'MKTEXPK'
(*note mktex script arguments::).
- ‘mktexfmt’ reads a file ‘fmtutil.cnf’, typically located in
-‘texmf/web2c/’ to glean its configuration information. The rest of the
+ 'mktexfmt' reads a file 'fmtutil.cnf', typically located in
+'texmf/web2c/' to glean its configuration information. The rest of the
files and features in this section are primarily intended for the font
generation scripts.
- As distributed, all the scripts source a file ‘texmf/web2c/mktex.cnf’
-if it exists, so you can override various defaults. See ‘mktex.opt’,
+ As distributed, all the scripts source a file 'texmf/web2c/mktex.cnf'
+if it exists, so you can override various defaults. See 'mktex.opt',
for instance, which defines the default mode, resolution, some special
directory names, etc. If you prefer not to change the distributed
-scripts, you can simply create ‘mktex.cnf’ with the appropriate
+scripts, you can simply create 'mktex.cnf' with the appropriate
definitions (you do not need to create it if you have nothing to put in
-it). ‘mktex.cnf’ has no special syntax; it’s an arbitrary Bourne shell
-script. The distribution contains a sample ‘mktex.cnf’ for you to copy
+it). 'mktex.cnf' has no special syntax; it's an arbitrary Bourne shell
+script. The distribution contains a sample 'mktex.cnf' for you to copy
and modify as you please (it is not installed anywhere).
In addition, you can configure a number of features with the
-‘MT_FEATURES’ variable, which you can define:
+'MT_FEATURES' variable, which you can define:
- • in ‘mktex.opt’, as just mentioned;
+ * in 'mktex.opt', as just mentioned;
- • by editing the file ‘mktex.opt’, either before ‘make install’ (in
+ * by editing the file 'mktex.opt', either before 'make install' (in
the source hierarchy) or after (in the installed hierarchy);
- • or in the environment.
+ * or in the environment.
- If none of the options below are enabled, ‘mktexpk’, ‘mktextfm’, and
-‘mktexmf’ follow the following procedure to decide where fonts should be
-installed. Find the tree where the font’s sources are, and test the
-permissions of the ‘fonts’ directory of that tree to determine whether
+ If none of the options below are enabled, 'mktexpk', 'mktextfm', and
+'mktexmf' follow the following procedure to decide where fonts should be
+installed. Find the tree where the font's sources are, and test the
+permissions of the 'fonts' directory of that tree to determine whether
it is writable. If it is, put the files in the tree in appropriate
-locations. If it isn’t writable, see whether the tree is a system tree
-(named in ‘SYSTEXMF’). If so, the ‘VARTEXFONTS’ tree is used. In all
+locations. If it isn't writable, see whether the tree is a system tree
+(named in 'SYSTEXMF'). If so, the 'VARTEXFONTS' tree is used. In all
other cases the working directory is used.
- The ‘appendonlydir’ option is enabled by default.
+ The 'appendonlydir' option is enabled by default.
-‘appendonlydir’
- Tell ‘mktexdir’ to create directories append-only, i.e., set their
+'appendonlydir'
+ Tell 'mktexdir' to create directories append-only, i.e., set their
sticky bit (*note (coreutils)Mode Structure::). This feature is
silently ignored on non-Unix platforms (e.g. Windows/NT and
- MS-DOS) which don’t support similar functionality. This feature is
+ MS-DOS) which don't support similar functionality. This feature is
enabled by default.
-‘dosnames’
- Use 8.3 names; e.g., ‘dpi600/cmr10.pk’ instead of ‘cmr10.600pk’.
+'dosnames'
+ Use 8.3 names; e.g., 'dpi600/cmr10.pk' instead of 'cmr10.600pk'.
Note that this feature only affects filenames that would otherwise
- clash with other TeX-related filenames; ‘mktex’ scripts do nothing
+ clash with other TeX-related filenames; 'mktex' scripts do nothing
about filenames which exceed the 8+3 MS-DOS limits but remain
unique when truncated (by the OS) to these limits, and nether do
- the scripts care about possible clashes with files which aren’t
- related with TeX. For example, ‘cmr10.600pk’ would clash with
- ‘cmr10.600gf’ and is therefore changed when ‘dosnames’ is in
- effect, but ‘mf.pool’ and ‘mp.base’ don’t clash with any
+ the scripts care about possible clashes with files which aren't
+ related with TeX. For example, 'cmr10.600pk' would clash with
+ 'cmr10.600gf' and is therefore changed when 'dosnames' is in
+ effect, but 'mf.pool' and 'mp.base' don't clash with any
TeX-related files and are therefore unchanged.
This feature is turned on by default on MS-DOS. If you do not wish
- ‘dosnames’ to be set on an MS-DOS platform, you need to set the
- ‘MT_FEATURES’ environment variable to a value that doesn’t include
- ‘dosnames’. You can also change the default setting by editing
- ‘mktex.opt’, but only if you use the ‘mktex’ shell scripts; the
- emulation programs don’t consult ‘mktex.opt’.
+ 'dosnames' to be set on an MS-DOS platform, you need to set the
+ 'MT_FEATURES' environment variable to a value that doesn't include
+ 'dosnames'. You can also change the default setting by editing
+ 'mktex.opt', but only if you use the 'mktex' shell scripts; the
+ emulation programs don't consult 'mktex.opt'.
-‘fontmaps’
+'fontmaps'
Instead of deriving the location of a font in the destination tree
from the location of the sources, the aliases and directory names
from the Fontname distribution are used. (*note Introduction:
(fontname)Top.).
-‘nomfdrivers’
+'nomfdrivers'
Let mktexpk and mktextfm create metafont driver files in a
temporary directory. These will be used for just one metafont run
and not installed permanently.
-‘nomode’
+'nomode'
Omit the directory level for the mode name; this is fine as long as
you generate fonts for only one mode.
-‘stripsupplier’
+'stripsupplier'
Omit the font supplier name directory level.
-‘striptypeface’
+'striptypeface'
Omit the font typeface name directory level.
-‘strip’
+'strip'
Omit the font supplier and typeface name directory levels. This
- feature is deprecated in favour of ‘stripsupplier’ and
- ‘striptypeface’.
+ feature is deprecated in favour of 'stripsupplier' and
+ 'striptypeface'.
-‘varfonts’
+'varfonts'
When this option is enabled, fonts that would otherwise be written
- in system texmf tree go to the ‘VARTEXFONTS’ tree instead. The
- default value in ‘kpathsea/Makefile.in’ is ‘/var/tmp/texfonts’.
- The ‘Linux File System Standard’ recommends ‘/var/tex/fonts’.
+ in system texmf tree go to the 'VARTEXFONTS' tree instead. The
+ default value in 'kpathsea/Makefile.in' is '/var/tmp/texfonts'.
+ The 'Linux File System Standard' recommends '/var/tex/fonts'.
- The ‘varfonts’ setting in ‘MT_FEATURES’ is overridden by the
- ‘USE_VARTEXFONTS’ environment variable: if set to ‘1’, the feature
- is enabled, and if set to ‘0’, the feature is disabled.
+ The 'varfonts' setting in 'MT_FEATURES' is overridden by the
+ 'USE_VARTEXFONTS' environment variable: if set to '1', the feature
+ is enabled, and if set to '0', the feature is disabled.
-‘texmfvar’
+'texmfvar'
Force generated files that would go into a system tree (as defined
- by ‘SYSTEXMF’) into ‘TEXMFVAR’. Starting with teTeX-3.0, the
- variable ‘TEXMFVAR’ is always set. The ‘varfonts’ feature takes
+ by 'SYSTEXMF') into 'TEXMFVAR'. Starting with teTeX-3.0, the
+ variable 'TEXMFVAR' is always set. The 'varfonts' feature takes
precedence if also set.
- The ‘texmfvar’ setting in ‘MT_FEATURES’ is overridden by the
- ‘USE_TEXMFVAR’ environment variable: if set to ‘1’, the feature is
- enabled, and if set to ‘0’, the feature is disabled.
+ The 'texmfvar' setting in 'MT_FEATURES' is overridden by the
+ 'USE_TEXMFVAR' environment variable: if set to '1', the feature is
+ enabled, and if set to '0', the feature is disabled.
File: kpathsea.info, Node: mktex script names, Next: mktex script arguments, Prev: mktex configuration, Up: mktex scripts
-6.5.2 ‘mktex’ script names
+6.5.2 'mktex' script names
--------------------------
The following table shows the default name of the script for each of the
file types which support runtime generation.
-‘mktexfmt’
- (‘.fmt’, ‘.base’, ‘.mem’) TeX/Metafont/MetaPost formats. This
- script is also named ‘fmtutil’, and reads ‘fmtutil.cnf’ for
+'mktexfmt'
+ ('.fmt', '.base', '.mem') TeX/Metafont/MetaPost formats. This
+ script is also named 'fmtutil', and reads 'fmtutil.cnf' for
configuration information.
-‘mktexmf’
- (‘.mf’) Metafont input files.
+'mktexmf'
+ ('.mf') Metafont input files.
-‘mkocp’
- (‘.ocp’) Omega compiled process files.
+'mkocp'
+ ('.ocp') Omega compiled process files.
-‘mkofm’
- (‘.ofm’) Omega font metric files.
+'mkofm'
+ ('.ofm') Omega font metric files.
-‘mktexpk’
- (‘pk’) Glyph fonts.
+'mktexpk'
+ ('pk') Glyph fonts.
-‘mktextex’
- (‘.tex’) TeX input files (disabled by default).
+'mktextex'
+ ('.tex') TeX input files (disabled by default).
-‘mktextfm’
- (‘.tfm’) TFM files.
+'mktextfm'
+ ('.tfm') TFM files.
These names can be overridden by an environment variable specific to the
-program—for example, ‘DVIPSMAKEPK’ for Dvipsk.
+program--for example, 'DVIPSMAKEPK' for Dvipsk.
- If a ‘mktex...’ script fails, the invocation is appended to a file
-‘missfont.log’ (by default) in the current directory. You can then
+ If a 'mktex...' script fails, the invocation is appended to a file
+'missfont.log' (by default) in the current directory. You can then
execute the log file to create the missing files after fixing the
problem.
If the current directory is not writable and the environment variable
-or configuration file value ‘TEXMFOUTPUT’ is set, its value is used.
-Otherwise, nothing is written. The name ‘missfont.log’ is overridden by
-the ‘MISSFONT_LOG’ environment variable or configuration file value.
+or configuration file value 'TEXMFOUTPUT' is set, its value is used.
+Otherwise, nothing is written. The name 'missfont.log' is overridden by
+the 'MISSFONT_LOG' environment variable or configuration file value.
File: kpathsea.info, Node: mktex script arguments, Prev: mktex script names, Up: mktex scripts
-6.5.3 ‘mktex’ script arguments
+6.5.3 'mktex' script arguments
------------------------------
-The first argument to a ‘mktex’ script is always the name of the file to
+The first argument to a 'mktex' script is always the name of the file to
be created.
- In the default ‘mktexpk’ implementation, additional arguments may
+ In the default 'mktexpk' implementation, additional arguments may
also be passed:
-‘--dpi NUM’
+'--dpi NUM'
Sets the resolution of the generated font to NUM.
-‘--mfmode NAME’
+'--mfmode NAME'
Sets the Metafont mode to NAME.
-‘--bdpi NUM’
- Sets the “base dpi” for the font. This must match the mode being
+'--bdpi NUM'
+ Sets the "base dpi" for the font. This must match the mode being
used.
-‘--mag STRING’
- A “magstep” string suitable for the Metafont ‘mag’ variable. This
+'--mag STRING'
+ A "magstep" string suitable for the Metafont 'mag' variable. This
must match the combination of BDPI and DPI being used.
-‘--destdir STRING’
+'--destdir STRING'
A directory name. If the directory is absolute, it is used as-is.
Otherwise, it is appended to the root destination directory set in
the script.
@@ -2364,7 +2364,7 @@
When looking at these program sources, you should know that previous
versions of the library had a different programming interface; the
current interface supports re-entrancy. Historically, the library
-function names were prefixed with ‘kpse_’ instead of ‘kpathsea_’, and
+function names were prefixed with 'kpse_' instead of 'kpathsea_', and
they did not need an instance variable as first argument. This change
was made in 2009. The old functions will never disappear, and can
reliably continue to be used when they suffice, as they do for the
@@ -2371,27 +2371,27 @@
programs above. The main application using the re-entrant API is the
MetaPost library used by MetaPost and LuaTeX.
- Beyond these examples, the ‘.h’ files in the Kpathsea source describe
-the interfaces and functionality (and of course the ‘.c’ files define
+ Beyond these examples, the '.h' files in the Kpathsea source describe
+the interfaces and functionality (and of course the '.c' files define
the actual routines, which are the ultimate documentation).
-‘pathsearch.h’ declares the basic searching routine. ‘tex-file.h’ and
-‘tex-glyph.h’ define the interfaces for looking up particular kinds of
+'pathsearch.h' declares the basic searching routine. 'tex-file.h' and
+'tex-glyph.h' define the interfaces for looking up particular kinds of
files. In view of the way the headers depend on each other, it is
-recommended to use ‘#include <kpathsea/kpathsea.h>’, which includes
+recommended to use '#include <kpathsea/kpathsea.h>', which includes
every Kpathsea header.
If you want to include only specific headers, you should still
-consider including ‘kpathsea/config.h’ before including any other
+consider including 'kpathsea/config.h' before including any other
Kpathsea header, as it provides symbols used in the other headers. Note
-that ‘kpathsea/config.h’ includes ‘kpathsea/c-auto.h’, which is
+that 'kpathsea/config.h' includes 'kpathsea/c-auto.h', which is
generated by Autoconf.
The library provides no way for an external program to register new
-file types: ‘tex-file.[ch]’ must be modified to do this. For example,
+file types: 'tex-file.[ch]' must be modified to do this. For example,
Kpathsea has support for looking up Dvips config files, even though no
program other than Dvips will likely ever want to do so. I felt this
was acceptable, since along with new file types should also come new
-defaults in ‘texmf.cnf’ (and its descendant ‘paths.h’), since it’s
+defaults in 'texmf.cnf' (and its descendant 'paths.h'), since it's
simplest for users if they can modify one configuration file for all
kinds of paths.
@@ -2409,51 +2409,51 @@
The typical way to use Kpathsea in your program goes something like
this:
- 1. Call ‘kpathsea_new’ to create a new library instance. This
+ 1. Call 'kpathsea_new' to create a new library instance. This
variable must be passed as the first argument to all the following
- library functions. The rest of this manual will be using ‘kpse’ as
+ library functions. The rest of this manual will be using 'kpse' as
a placeholder for the name of this variable.
- 2. Call ‘kpathsea_set_program_name’ with ‘argv[0]’ as the second
- argument; the third argument is a string or ‘NULL’. The third
- argument is used by Kpathsea as the program name for the ‘.PROGRAM’
+ 2. Call 'kpathsea_set_program_name' with 'argv[0]' as the second
+ argument; the third argument is a string or 'NULL'. The third
+ argument is used by Kpathsea as the program name for the '.PROGRAM'
feature of config files (*note Config files::). If the third
- argument is ‘NULL’, the value of the second argument is used. This
+ argument is 'NULL', the value of the second argument is used. This
function must be called before any other use of the Kpathsea
library.
- ‘kpathsea_set_program_name’ always sets the variables
- ‘kpse->invocation_name’ and ‘kpse->invocation_short_name’. These
+ 'kpathsea_set_program_name' always sets the variables
+ 'kpse->invocation_name' and 'kpse->invocation_short_name'. These
variables are used in the error message macros defined in
- ‘kpathsea/lib.h’. It sets the variable ‘kpse->program_name’ to the
+ 'kpathsea/lib.h'. It sets the variable 'kpse->program_name' to the
program name it uses.
It also initializes debugging options based on the environment
- variable ‘KPATHSEA_DEBUG’ (if that is set).
+ variable 'KPATHSEA_DEBUG' (if that is set).
- Finally, it sets the environment variables ‘SELFAUTOLOC’,
- ‘SELFAUTODIR’ and ‘SELFAUTOPARENT’ to the location, parent and
- grandparent directory of the executable, removing ‘.’ and ‘..’ path
+ Finally, it sets the environment variables 'SELFAUTOLOC',
+ 'SELFAUTODIR' and 'SELFAUTOPARENT' to the location, parent and
+ grandparent directory of the executable, removing '.' and '..' path
elements and resolving symbolic links. These are used in the
default configuration file to allow people to invoke TeX from
- anywhere. You can use ‘kpsewhich --expand-var=\$SELFAUTOLOC’,
+ anywhere. You can use 'kpsewhich --expand-var=\$SELFAUTOLOC',
etc., to see the values.
- 3. Set debugging options. *Note Debugging::. If your program doesn’t
+ 3. Set debugging options. *Note Debugging::. If your program doesn't
have a debugging option already, you can define one and set
- ‘kpse->debug’ to the number that the user supplies (as in Dviljk
+ 'kpse->debug' to the number that the user supplies (as in Dviljk
and Web2c), or you can just omit this altogether (people can always
- set ‘KPATHSEA_DEBUG’). If you do have runtime debugging already,
- you need to merge Kpathsea’s options with yours (as in Dvipsk and
+ set 'KPATHSEA_DEBUG'). If you do have runtime debugging already,
+ you need to merge Kpathsea's options with yours (as in Dvipsk and
Xdvik).
4. If your program has its own configuration files that can define
- search paths, you should assign those paths to the ‘client_path’
- member in the appropriate element of the ‘kpse->format_info’ array.
- (This array is indexed by file type; see ‘tex-file.h’.) See
- ‘resident.c’ in Dvipsk for an example.
+ search paths, you should assign those paths to the 'client_path'
+ member in the appropriate element of the 'kpse->format_info' array.
+ (This array is indexed by file type; see 'tex-file.h'.) See
+ 'resident.c' in Dvipsk for an example.
- 5. Call ‘kpathsea_init_prog’ (see ‘proginit.c’). It’s useful for the
+ 5. Call 'kpathsea_init_prog' (see 'proginit.c'). It's useful for the
DVI drivers, at least, but for other programs it may be simpler to
extract the parts of it that actually apply. This does not
initialize any paths, it just looks for (and sets) certain
@@ -2463,61 +2463,61 @@
BibTeX search paths in a DVI driver.)
6. The routine to actually find a file of type FORMAT is
- ‘kpathsea_find_file’. You can call ‘kpathsea_find_file’ after
+ 'kpathsea_find_file'. You can call 'kpathsea_find_file' after
doing only the first and second of the initialization steps
- above—Kpathsea automatically reads the ‘texmf.cnf’ generic config
+ above--Kpathsea automatically reads the 'texmf.cnf' generic config
files, looks for environment variables, and does expansions at the
first lookup.
7. To find PK and/or GF bitmap fonts, the routine is
- ‘kpathsea_find_glyph’, defined in ‘tex-glyph.h’. This returns a
+ 'kpathsea_find_glyph', defined in 'tex-glyph.h'. This returns a
structure in addition to the resultant filename, because fonts can
be found in so many ways. See the documentation in the source.
8. To actually open a file, not just return a filename, call
- ‘kpathsea_open_file’. This function takes the name to look up and
- a Kpathsea file format as arguments, and returns the usual ‘FILE
- *’. It always assumes the file must exist, and thus will search
- the disk if necessary (unless the search path specified ‘!!’,
+ 'kpathsea_open_file'. This function takes the name to look up and
+ a Kpathsea file format as arguments, and returns the usual 'FILE
+ *'. It always assumes the file must exist, and thus will search
+ the disk if necessary (unless the search path specified '!!',
etc.). In other words, if you are looking up a VF or some other
- file that need not exist, don’t use this.
+ file that need not exist, don't use this.
- 9. TeX can write output files, via the ‘\openout’ primitive; this
+ 9. TeX can write output files, via the '\openout' primitive; this
opens a security hole vulnerable to Trojan horse attack: an
unwitting user could run a TeX program that overwrites, say,
- ‘~/.rhosts’. Analogous security holes exist for many other
+ '~/.rhosts'. Analogous security holes exist for many other
programs. To alleviate this, there is a configuration variable
- ‘openout_any’, which selects one of three levels of security. When
- it is set to ‘a’ (for “any”), no restrictions are imposed. When it
- is set to ‘r’ (for “restricted”), filenames beginning with ‘.’ are
- disallowed (except ‘.tex’ because LaTeX needs it). When it is set
- to ‘p’ (for “paranoid”) additional restrictions are imposed: an
+ 'openout_any', which selects one of three levels of security. When
+ it is set to 'a' (for "any"), no restrictions are imposed. When it
+ is set to 'r' (for "restricted"), filenames beginning with '.' are
+ disallowed (except '.tex' because LaTeX needs it). When it is set
+ to 'p' (for "paranoid") additional restrictions are imposed: an
absolute filename must refer to a file in (a subdirectory) of
- ‘TEXMFOUTPUT’, and any attempt to go up a directory level is
- forbidden (that is, paths may not contain a ‘..’ component). The
- paranoid setting is the default. (For backwards compatibility, ‘y’
- and ‘1’ are synonyms of ‘a’, while ‘n’ and ‘0’ are synonyms for
- ‘r’.) The function ‘kpathsea_out_name_ok’, with a filename as
- second argument, returns ‘true’ if that filename is acceptable to
- be opend for output or ‘false’ otherwise.
+ 'TEXMFOUTPUT', and any attempt to go up a directory level is
+ forbidden (that is, paths may not contain a '..' component). The
+ paranoid setting is the default. (For backwards compatibility, 'y'
+ and '1' are synonyms of 'a', while 'n' and '0' are synonyms for
+ 'r'.) The function 'kpathsea_out_name_ok', with a filename as
+ second argument, returns 'true' if that filename is acceptable to
+ be opend for output or 'false' otherwise.
- 10. Similarly, the function ‘kpathsea_in_name_ok’, with a filename as
- second argument, returns ‘true’ if that filename is acceptable to
- be opend for input or ‘false’ otherwise, depending on the value of
- the configuration variable ‘openin_any’ (with ‘a’ as default).
+ 10. Similarly, the function 'kpathsea_in_name_ok', with a filename as
+ second argument, returns 'true' if that filename is acceptable to
+ be opend for input or 'false' otherwise, depending on the value of
+ the configuration variable 'openin_any' (with 'a' as default).
11. To close the kpathsea library instance you are using, call
- ‘kpathsea_finish’. This function closes any open log files and
+ 'kpathsea_finish'. This function closes any open log files and
frees the memory used by the instance.
Kpathsea also provides many utility routines. Some are generic: hash
tables, memory allocation, string concatenation and copying, string
lists, reading input lines of arbitrary length, etc. Others are
-filename-related: default path, tilde, and variable expansion, ‘stat’
-calls, etc. (Perhaps someday I’ll move the former to a separate
+filename-related: default path, tilde, and variable expansion, 'stat'
+calls, etc. (Perhaps someday I'll move the former to a separate
library.)
- The ‘c-*.h’ header files can also help your program adapt to many
+ The 'c-*.h' header files can also help your program adapt to many
different systems. You will almost certainly want to use Autoconf and
probably Automake for configuring and building your software if you use
Kpathsea; I strongly recommend using Autoconf and Automake regardless.
@@ -2533,17 +2533,17 @@
contains some support to make it easy to place them in their own
directories. The Standard TeX directory structure (*note Introduction:
(tds)Top.), specifies that such files should go into a subdirectory
-named after the program, like ‘texmf/ttf2pk’.
+named after the program, like 'texmf/ttf2pk'.
- Two formats, ‘kpse_program_text_format’ and
-‘kpse_program_binary_format’, use ‘.:$TEXMF/PROGRAM//’ as their
+ Two formats, 'kpse_program_text_format' and
+'kpse_program_binary_format', use '.:$TEXMF/PROGRAM//' as their
compiled-in search path. To override this default, you can use the
-variable ‘PROGRAMINPUTS’ in the environment and/or ‘texmf.cnf’. That is
+variable 'PROGRAMINPUTS' in the environment and/or 'texmf.cnf'. That is
to say, the name of the variable is constructed by converting the name
-of the program to upper case, and appending ‘INPUTS’.
+of the program to upper case, and appending 'INPUTS'.
The only difference between these two formats is whether
-‘kpathsea_open_file’ will open the files it finds in text or binary
+'kpathsea_open_file' will open the files it finds in text or binary
mode.
@@ -2552,30 +2552,30 @@
7.4 Programming with config files
=================================
-You can (and probably should) use the same ‘texmf.cnf’ configuration
+You can (and probably should) use the same 'texmf.cnf' configuration
file that Kpathsea uses for your program. This helps installers by
keeping all configuration in one place.
To retrieve a value for a configuration variable VAR, the best way is
-to call ‘kpathsea_var_value’ on the string ‘VAR’. This will look first
+to call 'kpathsea_var_value' on the string 'VAR'. This will look first
for an environment variable VAR, then a config file value. The result
-will be the value found or ‘NULL’. This function is declared in
-‘kpathsea/variable.h’. For an example, see the ‘shell_escape’ code in
-‘web2c/lib/texmfmp.c’.
+will be the value found or 'NULL'. This function is declared in
+'kpathsea/variable.h'. For an example, see the 'shell_escape' code in
+'web2c/lib/texmfmp.c'.
The routine to do full variable and tilde expansion of an arbitrary
string in the context of a search path (as opposed to simply retrieving
-a value) is ‘kpathsea_var_expand’, also declared in
-‘kpathsea/variable.h’. However, it’s generally only necessary to set
+a value) is 'kpathsea_var_expand', also declared in
+'kpathsea/variable.h'. However, it's generally only necessary to set
the search path structure components as explained in the previous
section instead of using this directly. Because of its usage with any
-input string, undefined ‘$FOO’ constructs in the argument to
-‘kpathsea_var_expand’ are returned literally (‘"$FOO"’), while undefined
-‘${FOO}’ constructs are expanded to the empty string.
+input string, undefined '$FOO' constructs in the argument to
+'kpathsea_var_expand' are returned literally ('"$FOO"'), while undefined
+'${FOO}' constructs are expanded to the empty string.
If for some reason you want to retrieve a value _only_ from a config
file, not automatically looking for a corresponding environment
-variable, call ‘kpathsea_cnf_get’ (declared in ‘kpathsea/cnf.h’) with
+variable, call 'kpathsea_cnf_get' (declared in 'kpathsea/cnf.h') with
the string VAR.
No initialization calls are needed.
@@ -2607,7 +2607,7 @@
8.1 Bug checklist
=================
-Before reporting a bug, please check below to be sure it isn’t already
+Before reporting a bug, please check below to be sure it isn't already
known (*note Common problems::).
Bug reports should be sent via electronic mail to <tex-k at tug.org>.
@@ -2616,53 +2616,53 @@
information necessary for reproduction. Therefore, to enable
investigation, your report should include the following:
- • The version number(s) of the program(s) involved, and of Kpathsea
- itself. You can get the former by giving a sole option ‘--version’
- to the program, and the latter by running ‘kpsewhich --version’.
- The ‘NEWS’ and ‘ChangeLog’ files also contain the version number.
+ * The version number(s) of the program(s) involved, and of Kpathsea
+ itself. You can get the former by giving a sole option '--version'
+ to the program, and the latter by running 'kpsewhich --version'.
+ The 'NEWS' and 'ChangeLog' files also contain the version number.
- • The hardware, operating system (including version), compiler, and
- ‘make’ program you are using (the output of ‘uname -a’ is a start
+ * The hardware, operating system (including version), compiler, and
+ 'make' program you are using (the output of 'uname -a' is a start
on the first two, though incomplete).
- • Any options you gave to ‘configure’. This is recorded in the
- ‘config.status’ files.
+ * Any options you gave to 'configure'. This is recorded in the
+ 'config.status' files.
- If you are reporting a bug in ‘configure’ itself, it’s probably
+ If you are reporting a bug in 'configure' itself, it's probably
system-dependent, and it will be unlikely the maintainers can do
anything useful if you merely report that thus-and-such is broken.
Therefore, you need to do some additional work: for some bugs, you
- can look in the file ‘config.log’ where the test that failed should
+ can look in the file 'config.log' where the test that failed should
appear, along with the compiler invocation and source program in
question. You can then compile it yourself by hand, and discover
- why the test failed. Other ‘configure’ bugs do not involve the
+ why the test failed. Other 'configure' bugs do not involve the
compiler; in that case, the only recourse is to inspect the
- ‘configure’ shell script itself, or the Autoconf macros that
- generated ‘configure’.
+ 'configure' shell script itself, or the Autoconf macros that
+ generated 'configure'.
- • The log of all debugging output, if the bug is in path searching.
+ * The log of all debugging output, if the bug is in path searching.
You can get this by setting the environment variable
- ‘KPATHSEA_DEBUG’ to ‘-1’ before running the program. Please look
+ 'KPATHSEA_DEBUG' to '-1' before running the program. Please look
at the log yourself to make sure the behavior is really a bug
- before reporting it; perhaps “old” environment variable settings
+ before reporting it; perhaps "old" environment variable settings
are causing files not to be found, for example.
- • The contents of any input files necessary to reproduce the bug.
+ * The contents of any input files necessary to reproduce the bug.
For bugs in DVI-reading programs, for example, this generally means
- a DVI file (and any EPS or other files it uses)—TeX source files
- are helpful, but the DVI file is required, because that’s the
+ a DVI file (and any EPS or other files it uses)--TeX source files
+ are helpful, but the DVI file is required, because that's the
actual program input.
- • If you are sending a patch (do so if you can!), please do so in the
- form of a context diff (‘diff -c’) against the original
+ * If you are sending a patch (do so if you can!), please do so in the
+ form of a context diff ('diff -c') against the original
distribution source. Any other form of diff is either not as
complete or harder for me to understand. Please also include a
- ‘ChangeLog’ entry.
+ 'ChangeLog' entry.
- • If the bug involved is an actual crash (i.e., core dump), it is
+ * If the bug involved is an actual crash (i.e., core dump), it is
easy and useful to include a stack trace from a debugger (I
recommend the GNU debugger GDB (<https://gnu.org/software/gdb>).
- If the cause is apparent (a ‘NULL’ value being dereferenced, for
+ If the cause is apparent (a 'NULL' value being dereferenced, for
example), please send the details along. If the program involved
is TeX or Metafont, and the crash is happening at apparently-sound
code, however, the bug may well be in the compiler, rather than in
@@ -2669,7 +2669,7 @@
the program or the library (*note TeX or Metafont failing: TeX or
Metafont failing.).
- • Any additional information that will be helpful in reproducing,
+ * Any additional information that will be helpful in reproducing,
diagnosing, or fixing the bug.
@@ -2699,22 +2699,22 @@
Kpathsea provides a number of runtime debugging options, detailed below
by their names and corresponding numeric values. When the files you
-expect aren’t being found, the thing to do is enable these options and
+expect aren't being found, the thing to do is enable these options and
examine the output.
- You can set these with some runtime argument (e.g., ‘-d’) to the
+ You can set these with some runtime argument (e.g., '-d') to the
program; in that case, you should use the numeric values described in
-the program’s documentation (which, for Dvipsk and Xdvik, are different
-than those below). It’s best to give the ‘-d’ (or whatever) option
+the program's documentation (which, for Dvipsk and Xdvik, are different
+than those below). It's best to give the '-d' (or whatever) option
first, for maximal output. Dvipsk and Xdvik have additional
program-specific debugging options as well.
- You can also set the environment variable ‘KPATHSEA_DEBUG’; in this
+ You can also set the environment variable 'KPATHSEA_DEBUG'; in this
case, you should use the numbers below. If you run the program under a
-debugger and set the instance variable ‘kpse->debug’, also use the
+debugger and set the instance variable 'kpse->debug', also use the
numbers below.
- In any case, by far the simplest value to use is ‘-1’, which will
+ In any case, by far the simplest value to use is '-1', which will
turn on all debugging output. This is usually better than guessing
which particular values will yield the output you need.
@@ -2726,81 +2726,81 @@
(*note Invoking kpsewhich::), instead of the original program.
In any case, you cannot use the names below; you must always use
-somebody’s numbers. (Sorry.) To set more than one option, just sum the
+somebody's numbers. (Sorry.) To set more than one option, just sum the
corresponding numbers.
-‘KPSE_DEBUG_STAT (1)’
- Report ‘stat’(2) calls. This is useful for verifying that your
+'KPSE_DEBUG_STAT (1)'
+ Report 'stat'(2) calls. This is useful for verifying that your
directory structure is not forcing Kpathsea to do many additional
file tests (*note Slow path searching::, and *note Subdirectory
- expansion::). If you are using an up-to-date ‘ls-R’ database
+ expansion::). If you are using an up-to-date 'ls-R' database
(*note Filename database::), this should produce no output unless a
nonexistent file that must exist is searched for.
-‘KPSE_DEBUG_HASH (2)’
- Report lookups in all hash tables: ‘ls-R’ and ‘aliases’ (*note
+'KPSE_DEBUG_HASH (2)'
+ Report lookups in all hash tables: 'ls-R' and 'aliases' (*note
Filename database::); font aliases (*note Fontmap::); and config
file values (*note Config files::). Useful when expected values
are not being found, e.g.., file searches are looking at the disk
- instead of using ‘ls-R’.
+ instead of using 'ls-R'.
-‘KPSE_DEBUG_FOPEN (4)’
+'KPSE_DEBUG_FOPEN (4)'
Report file openings and closings. Especially useful when your
- system’s file table is full, for seeing which files have been
+ system's file table is full, for seeing which files have been
opened but never closed. In case you want to set breakpoints in a
- debugger: this works by redefining ‘fopen’ (‘fclose’) to be
- ‘kpse_fopen_trace’ (‘kpse_fclose_trace’).
+ debugger: this works by redefining 'fopen' ('fclose') to be
+ 'kpse_fopen_trace' ('kpse_fclose_trace').
-‘KPSE_DEBUG_PATHS (8)’
+'KPSE_DEBUG_PATHS (8)'
Report general path information for each file type Kpathsea is
asked to search. This is useful when you are trying to track down
- how a particular path got defined—from ‘texmf.cnf’, ‘config.ps’, an
- environment variable, the compile-time default, etc. This is the
- contents of the ‘kpse_format_info_type’ structure defined in
- ‘tex-file.h’.
+ how a particular path got defined--from 'texmf.cnf', 'config.ps',
+ an environment variable, the compile-time default, etc. This is
+ the contents of the 'kpse_format_info_type' structure defined in
+ 'tex-file.h'.
-‘KPSE_DEBUG_EXPAND (16)’
+'KPSE_DEBUG_EXPAND (16)'
Report the directory list corresponding to each path element
Kpathsea searches. This is only relevant when Kpathsea searches
- the disk, since ‘ls-R’ searches don’t look through directory lists
+ the disk, since 'ls-R' searches don't look through directory lists
in this way.
-‘KPSE_DEBUG_SEARCH (32)’
+'KPSE_DEBUG_SEARCH (32)'
Report on each file search: the name of the file searched for, the
path searched in, whether or not the file must exist (when drivers
- search for ‘cmr10.vf’, it need not exist), and whether or not we
+ search for 'cmr10.vf', it need not exist), and whether or not we
are collecting all occurrences of the file in the path (as with,
- e.g., ‘texmf.cnf’ and ‘texfonts.map’), or just the first (as with
+ e.g., 'texmf.cnf' and 'texfonts.map'), or just the first (as with
most lookups). This can help you correlate what Kpathsea is doing
with what is in your input file.
-‘KPSE_DEBUG_VARS (64)’
+'KPSE_DEBUG_VARS (64)'
Report the value of each variable Kpathsea looks up. This is
useful for verifying that variables do indeed obtain their correct
values.
-‘GSFTOPK_DEBUG (128)’
- Activates debugging printout specific to ‘gsftopk’ program.
+'GSFTOPK_DEBUG (128)'
+ Activates debugging printout specific to 'gsftopk' program.
-‘MAKETEX_DEBUG (512)’
- If you use the optional ‘mktex’ programs instead of the traditional
+'MAKETEX_DEBUG (512)'
+ If you use the optional 'mktex' programs instead of the traditional
shell scripts, this will report the name of the site file
- (‘mktex.cnf’ by default) which is read, directories created by
- ‘mktexdir’, the full path of the ‘ls-R’ database built by
- ‘mktexlsr’, font map searches, ‘MT_FEATURES’ in effect, parameters
- from ‘mktexnam’, filenames added by ‘mktexupd’, and some subsidiary
+ ('mktex.cnf' by default) which is read, directories created by
+ 'mktexdir', the full path of the 'ls-R' database built by
+ 'mktexlsr', font map searches, 'MT_FEATURES' in effect, parameters
+ from 'mktexnam', filenames added by 'mktexupd', and some subsidiary
commands run by the programs.
-‘MAKETEX_FINE_DEBUG (1024)’
- When the optional ‘mktex’ programs are used, this will print
+'MAKETEX_FINE_DEBUG (1024)'
+ When the optional 'mktex' programs are used, this will print
additional debugging info from functions internal to these
programs.
Debugging output from Kpathsea is always written to standard error,
-and begins with the string ‘kdebug:’. (Except for hash table buckets,
+and begins with the string 'kdebug:'. (Except for hash table buckets,
which just start with the number, but you can only get that output
-running under a debugger. See comments at the ‘hash_summary_only’
-variable in ‘kpathsea/db.c’.)
+running under a debugger. See comments at the 'hash_summary_only'
+variable in 'kpathsea/db.c'.)
File: kpathsea.info, Node: Logging, Next: Common problems, Prev: Debugging, Up: Reporting bugs
@@ -2813,18 +2813,18 @@
your filesystem is full, or in discovering usage patterns at your site.
To do this, define the environment or config file variable
-‘TEXMFLOG’. The value is the name of the file to append the information
-to. The file is created if it doesn’t exist, and appended to if it
+'TEXMFLOG'. The value is the name of the file to append the information
+to. The file is created if it doesn't exist, and appended to if it
does.
Each successful search turns into one line in the log file: two words
separated by a space. The first word is the time of the search, as the
-integer number of seconds since “the epoch”, i.e., UTC midnight 1
-January 1970 (more precisely, the result of the ‘time’ system call).
+integer number of seconds since "the epoch", i.e., UTC midnight 1
+January 1970 (more precisely, the result of the 'time' system call).
The second word is the filename.
- For example, after ‘setenv TEXMFLOG /tmp/log’, running Dvips on
-‘story.dvi’ appends the following lines:
+ For example, after 'setenv TEXMFLOG /tmp/log', running Dvips on
+'story.dvi' appends the following lines:
774455887 /usr/local/share/texmf/dvips/config.ps
774455887 /usr/local/share/texmf/dvips/psfonts.map
@@ -2837,13 +2837,13 @@
Only filenames that are absolute are recorded, to preserve some
semblance of privacy.
- In addition to this Kpathsea-specific logging, ‘pdftex’ provides an
-option ‘-recorder’ to write the names of all files accessed during a run
-to the file ‘BASEFILE.fls’.
+ In addition to this Kpathsea-specific logging, 'pdftex' provides an
+option '-recorder' to write the names of all files accessed during a run
+to the file 'BASEFILE.fls'.
Finally, most systems provide a general tool to output each system
call, thus including opening and closing files. It might be named
-‘strace’, ‘truss’, ‘struss’, or something else.
+'strace', 'truss', 'struss', or something else.
File: kpathsea.info, Node: Common problems, Prev: Logging, Up: Reporting bugs
@@ -2856,7 +2856,7 @@
* Menu:
-* Unable to find files:: If your program can’t find fonts (or whatever).
+* Unable to find files:: If your program can't find fonts (or whatever).
* Slow path searching:: If it takes forever to find anything.
* Unable to generate fonts:: If mktexpk fails.
* TeX or Metafont failing:: Likely compiler bugs.
@@ -2871,21 +2871,21 @@
of several things might be wrong. In any case, you may find the
debugging options helpful. *Note Debugging::.
- • Perhaps you simply haven’t installed all the necessary files; the
+ * Perhaps you simply haven't installed all the necessary files; the
basic fonts and input files are distributed separately from the
programs. *Note unixtex.ftp::.
- • You have (perhaps unknowingly) told Kpathsea to use search paths
- that don’t reflect where the files actually are. One common cause
+ * You have (perhaps unknowingly) told Kpathsea to use search paths
+ that don't reflect where the files actually are. One common cause
is having environment variables set from a previous installation,
- thus overriding what you carefully set in ‘texmf.cnf’ (*note
- Supported file formats::). System ‘/etc/profile’ or other files
+ thus overriding what you carefully set in 'texmf.cnf' (*note
+ Supported file formats::). System '/etc/profile' or other files
such may be the culprit.
- • Your files reside in a directory that is only pointed to via a
- symbolic link, in a leaf directory and is not listed in ‘ls-R’.
+ * Your files reside in a directory that is only pointed to via a
+ symbolic link, in a leaf directory and is not listed in 'ls-R'.
- Unfortunately, Kpathsea’s subdirectory searching has an
+ Unfortunately, Kpathsea's subdirectory searching has an
irremediable deficiency: If a directory D being searched for
subdirectories contains plain files and symbolic links to other
directories, but no true subdirectories, D will be considered a
@@ -2896,21 +2896,21 @@
subdirectory in D. Then D will no longer be a leaf, and the
symlinks will be followed.
- The directory immediately followed by the ‘//’ in the path
+ The directory immediately followed by the '//' in the path
specification, however, is always searched for subdirectories, even
if it is a leaf. Presumably you would not have asked for the
- directory to be searched for subdirectories if you didn’t want it
+ directory to be searched for subdirectories if you didn't want it
to be.
- • If the fonts (or whatever) don’t already exist, ‘mktexpk’ (or
- ‘mktexmf’ or ‘mktextfm’) will try to create them. If these rather
- complicated shell scripts fail, you’ll eventually get an error
- message saying something like ‘Can't find font FONTNAME’. The best
- solution is to fix (or at least report) the bug in ‘mktexpk’; the
+ * If the fonts (or whatever) don't already exist, 'mktexpk' (or
+ 'mktexmf' or 'mktextfm') will try to create them. If these rather
+ complicated shell scripts fail, you'll eventually get an error
+ message saying something like 'Can't find font FONTNAME'. The best
+ solution is to fix (or at least report) the bug in 'mktexpk'; the
workaround is to generate the necessary fonts by hand with
Metafont, or to grab them from a CTAN site (*note unixtex.ftp::).
- • There is a bug in the library. *Note Reporting bugs::.
+ * There is a bug in the library. *Note Reporting bugs::.
File: kpathsea.info, Node: Slow path searching, Next: Unable to generate fonts, Prev: Unable to find files, Up: Common problems
@@ -2922,20 +2922,20 @@
input files, but does eventually succeed, here are some possible
culprits:
- • Most likely, you just have a lot of directories to search, and that
+ * Most likely, you just have a lot of directories to search, and that
takes a noticeable time. The solution is to create and maintain a
- separate ‘ls-R’ file that lists all the files in your main TeX
- hierarchy. *Note Filename database::. Kpathsea always uses ‘ls-R’
- if it’s present; there’s no need to recompile or reconfigure any of
+ separate 'ls-R' file that lists all the files in your main TeX
+ hierarchy. *Note Filename database::. Kpathsea always uses 'ls-R'
+ if it's present; there's no need to recompile or reconfigure any of
the programs.
- • Your recursively-searched directories (e.g.,
- ‘/usr/local/share/texmf/fonts//’), contain a mixture of files and
+ * Your recursively-searched directories (e.g.,
+ '/usr/local/share/texmf/fonts//'), contain a mixture of files and
directories. This prevents Kpathsea from using a useful
optimization (*note Subdirectory expansion::).
- It is best to have only directories (and perhaps a ‘README’) in the
- upper levels of the directory structure, and it’s very important to
+ It is best to have only directories (and perhaps a 'README') in the
+ upper levels of the directory structure, and it's very important to
have _only_ files, and no subdirectories, in the leaf directories
where the dozens of TFM, PK, or whatever files reside.
@@ -2955,17 +2955,17 @@
generate these on the fly when they are needed, but this generation may
fail in several cases.
- If ‘mktexpk’ runs, but fails with this error:
+ If 'mktexpk' runs, but fails with this error:
mktexpk: Can't guess mode for NNN dpi devices.
mktexpk: Use a config file to specify the mode, or update me.
you need to ensure the resolution and mode match; just specifying the
-resolution, as in ‘-D 360’, is not enough.
+resolution, as in '-D 360', is not enough.
- You can specify the mode name with the ‘-mode’ option on the Dvips
+ You can specify the mode name with the '-mode' option on the Dvips
command line, or in a Dvips configuration file (*note (dvips)Config
-files::), such as ‘config.ps’ in your document directory, ‘~/.dvipsrc’
+files::), such as 'config.ps' in your document directory, '~/.dvipsrc'
in your home directory, or in a system directory (again named
-‘config.ps’). (Other drivers use other files, naturally.)
+'config.ps'). (Other drivers use other files, naturally.)
For example, if you need 360dpi fonts, you could include this in a
configuration file:
@@ -2973,7 +2973,7 @@
M lqmed
If Metafont runs, but generates fonts at the wrong resolution or for
-the wrong device, most likely ‘mktexpk’’s built-in guess for the mode is
+the wrong device, most likely 'mktexpk''s built-in guess for the mode is
wrong, and you should override it as above.
See <https://ctan.org/pkg/modes> for a list of resolutions and mode
@@ -2982,19 +2982,19 @@
If Metafont runs but generates fonts at a resolution of 2602dpi (and
prints out the name of each character as well as just a character
number, and maybe tries to display the characters), then your Metafont
-base file probably hasn’t been made properly. (It’s using the default
-‘proof’ mode, instead of an actual device mode.) To make a proper
-‘plain.base’, assuming the local mode definitions are contained in a
-file ‘modes.mf’, run the following command (assuming Unix):
+base file probably hasn't been made properly. (It's using the default
+'proof' mode, instead of an actual device mode.) To make a proper
+'plain.base', assuming the local mode definitions are contained in a
+file 'modes.mf', run the following command (assuming Unix):
inimf "plain; input modes; dump"
-Then copy the ‘plain.base’ file from the current directory to where the
-base files are stored on your system (‘/usr/local/share/texmf/web2c’ by
-default), and make a link (either hard or soft) from ‘plain.base’ to
-‘mf.base’ in that directory. *Note (web2c)inimf invocation::.
+Then copy the 'plain.base' file from the current directory to where the
+base files are stored on your system ('/usr/local/share/texmf/web2c' by
+default), and make a link (either hard or soft) from 'plain.base' to
+'mf.base' in that directory. *Note (web2c)inimf invocation::.
- If ‘mf’ is a command not found at all by ‘mktexpk’, then you need to
+ If 'mf' is a command not found at all by 'mktexpk', then you need to
install Metafont (*note unixtex.ftp::).
@@ -3009,9 +3009,9 @@
passed, problems may lurk. Optimization occasionally causes trouble in
programs other than TeX and Metafont themselves, too.
- For a workaround, if you enabled any optimization flags, it’s best to
+ For a workaround, if you enabled any optimization flags, it's best to
omit optimization entirely. In any case, the way to find the facts is
-to run the program under the debugger and see where it’s failing.
+to run the program under the debugger and see where it's failing.
Also, if you have trouble with a system C compiler, I advise trying
the GNU C compiler. And vice versa, unfortunately; but in that case I
@@ -3021,7 +3021,7 @@
To report compiler bugs effectively requires perseverance and
perspicacity: you must find the miscompiled line, and that usually
involves delving backwards in time from the point of error, checking
-through TeX’s (or whatever program’s) data structures. Good luck.
+through TeX's (or whatever program's) data structures. Good luck.
File: kpathsea.info, Node: Index, Prev: Reporting bugs, Up: Top
@@ -3508,7 +3508,7 @@
(line 27)
* KPATHSEA_DEBUG: Calling sequence. (line 28)
* KPATHSEA_DEBUG <1>: Debugging. (line 18)
-* kpathsea_find_file: File lookup. (line 37)
+* kpathsea_find_file: File lookup. (line 38)
* kpathsea_find_file <1>: Calling sequence. (line 62)
* kpathsea_find_glyph: Glyph lookup. (line 26)
* kpathsea_finish: Calling sequence. (line 106)
@@ -3614,7 +3614,7 @@
* mktexfmt: mktex script names. (line 10)
* mktexmf: mktex script names. (line 15)
* mktexpk: mktex script names. (line 24)
-* mktexpk can’t guess mode: Unable to generate fonts.
+* mktexpk can't guess mode: Unable to generate fonts.
(line 12)
* mktextex: mktex script names. (line 27)
* mktextfm: mktex script names. (line 30)
@@ -3809,8 +3809,8 @@
* TeX file lookup: File lookup. (line 6)
* TeX glyph lookup: Glyph lookup. (line 6)
* TeX support: TeX support. (line 6)
-* TeX Users Group: Introduction. (line 42)
-* tex-file.c: File lookup. (line 37)
+* TeX Users Group: Introduction. (line 43)
+* tex-file.c: File lookup. (line 38)
* tex-file.h: Programming overview.
(line 26)
* tex-glyph.c: Glyph lookup. (line 26)
@@ -3966,67 +3966,62 @@
Tag Table:
-Node: Top1483
-Node: Introduction2266
-Node: History4362
-Node: unixtex.ftp9012
-Node: Security10496
-Node: TeX directory structure13068
-Node: Path searching17243
-Node: Searching overview18201
-Node: Path sources22126
-Node: Config files23400
-Node: Path expansion28458
-Node: Default expansion29429
-Node: Variable expansion31565
-Node: Tilde expansion33036
-Node: Brace expansion34086
-Node: KPSE_DOT expansion35083
-Node: Subdirectory expansion35608
-Node: Casefolding search38063
-Node: Casefolding rationale38840
-Node: Casefolding examples40201
-Node: Filename database45430
-Node: ls-R46444
-Node: Filename aliases50321
-Node: Database format51567
-Node: Invoking kpsewhich52628
-Node: Path searching options53611
-Node: Specially-recognized files63552
-Node: Auxiliary tasks65017
-Node: Standard options68902
-Node: TeX support69270
-Node: Supported file formats70629
-Node: File lookup79384
-Node: Glyph lookup81197
-Node: Basic glyph lookup82345
-Node: Fontmap83257
-Node: Fallback font85871
-Node: Suppressing warnings86807
-Node: mktex scripts87972
-Node: mktex configuration89217
-Node: mktex script names95326
-Node: mktex script arguments96813
-Node: Programming97736
-Node: Programming overview98309
-Node: Calling sequence101228
-Node: Program-specific files108028
-Node: Programming with config files109083
-Node: Reporting bugs110732
-Node: Bug checklist111410
-Node: Mailing lists114978
-Node: Debugging115655
-Node: Logging120925
-Node: Common problems122838
-Node: Unable to find files123317
-Node: Slow path searching125785
-Node: Unable to generate fonts127186
-Node: TeX or Metafont failing129728
-Node: Index130938
+Node: Top1480
+Node: Introduction2263
+Node: History4333
+Node: unixtex.ftp8929
+Node: Security10399
+Node: TeX directory structure12903
+Node: Path searching16942
+Node: Searching overview17900
+Node: Path sources21719
+Node: Config files22945
+Node: Path expansion27817
+Node: Default expansion28770
+Node: Variable expansion30840
+Node: Tilde expansion32241
+Node: Brace expansion33221
+Node: KPSE_DOT expansion34160
+Node: Subdirectory expansion34673
+Node: Casefolding search37021
+Node: Casefolding rationale37790
+Node: Casefolding examples39136
+Node: Filename database44182
+Node: ls-R45164
+Node: Filename aliases48840
+Node: Database format50018
+Node: Invoking kpsewhich51031
+Node: Path searching options51986
+Node: Specially-recognized files61589
+Node: Auxiliary tasks62944
+Node: Standard options66669
+Node: TeX support67025
+Node: Supported file formats68379
+Node: File lookup76198
+Node: Glyph lookup77947
+Node: Basic glyph lookup79071
+Node: Fontmap79951
+Node: Fallback font82461
+Node: Suppressing warnings83373
+Node: mktex scripts84500
+Node: mktex configuration85715
+Node: mktex script names91518
+Node: mktex script arguments92904
+Node: Programming93783
+Node: Programming overview94356
+Node: Calling sequence97217
+Node: Program-specific files103746
+Node: Programming with config files104769
+Node: Reporting bugs106356
+Node: Bug checklist107034
+Node: Mailing lists110503
+Node: Debugging111180
+Node: Logging116257
+Node: Common problems118124
+Node: Unable to find files118601
+Node: Slow path searching121011
+Node: Unable to generate fonts122386
+Node: TeX or Metafont failing124858
+Node: Index126060
End Tag Table
-
-
-Local Variables:
-coding: utf-8
-End:
Modified: branches/stable/source/src/texk/kpathsea/doc/kpathsea.texi
===================================================================
--- branches/stable/source/src/texk/kpathsea/doc/kpathsea.texi 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/doc/kpathsea.texi 2023-02-21 22:38:24 UTC (rev 903)
@@ -2,13 +2,13 @@
@setfilename kpathsea.info
@settitle Kpathsea: A library for path searching
- at set version 6.3.4
- at set month-year December 2022
+ at set version 6.3.5
+ at set month-year February 2023
@copying
This file documents the Kpathsea library for path searching.
-Copyright @copyright{} 1996--2022 Karl Berry & Olaf Weber.
+Copyright @copyright{} 1996--2023 Karl Berry & Olaf Weber.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
Modified: branches/stable/source/src/texk/kpathsea/kpsewhich.c
===================================================================
--- branches/stable/source/src/texk/kpathsea/kpsewhich.c 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/kpsewhich.c 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,7 +1,7 @@
/* kpsewhich -- standalone path lookup and variable expansion for Kpathsea.
Ideas from Thomas Esser, Pierre MacKay, and many others.
- Copyright 1995-2022 Karl Berry & Olaf Weber.
+ Copyright 1995-2023 Karl Berry & Olaf Weber.
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
@@ -736,7 +736,7 @@
} else if (ARGUMENT_IS ("version")) {
puts (kpathsea_version_string);
- puts ("Copyright 2022 Karl Berry & Olaf Weber.\n\
+ puts ("Copyright 2023 Karl Berry & Olaf Weber.\n\
License LGPLv2.1+: GNU Lesser GPL version 2.1 or later <https://gnu.org/licenses/lgpl.html>\n\
This is free software: you are free to change and redistribute it.\n\
There is NO WARRANTY, to the extent permitted by law.\n");
Modified: branches/stable/source/src/texk/kpathsea/texmf.cnf
===================================================================
--- branches/stable/source/src/texk/kpathsea/texmf.cnf 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/texmf.cnf 2023-02-21 22:38:24 UTC (rev 903)
@@ -4,8 +4,8 @@
% If you modify this original file, YOUR CHANGES WILL BE LOST when it is
% updated. Instead, put your changes -- and only your changes, not an
% entire copy! -- in ../../texmf.cnf. That is, if this file is
-% installed in /some/path/to/texlive/2022/texmf-dist/web2c/texmf.cnf,
-% put your custom settings in /some/path/to/texlive/2022/texmf.cnf.
+% installed in /some/path/to/texlive/2023/texmf-dist/web2c/texmf.cnf,
+% put your custom settings in /some/path/to/texlive/2023/texmf.cnf.
% (Below, we use YYYY in place of the specific year.)
%
% What follows is a super-summary of what this .cnf file can
@@ -84,10 +84,10 @@
TEXMFHOME = ~/texmf
% TEXMFVAR, where texconfig/updmap/fmtutil store cached runtime data.
-TEXMFVAR = ~/.texlive2022/texmf-var
+TEXMFVAR = ~/.texlive2023/texmf-var
% TEXMFCONFIG, where texconfig/updmap/fmtutil store configuration data.
-TEXMFCONFIG = ~/.texlive2022/texmf-config
+TEXMFCONFIG = ~/.texlive2023/texmf-config
% This is the value manipulated by tlmgr's auxtrees subcommand in the
% root texmf.cnf. Kpathsea warns about a literally empty string for a
@@ -372,6 +372,10 @@
BIBINPUTS.upbibtex = $TEXMFDOTDIR;$TEXMF/{upbibtex,pbibtex,bibtex}/bib//
BSTINPUTS.upbibtex = $TEXMFDOTDIR;$TEXMF/{upbibtex,pbibtex,bibtex}/bst//
+% BibTeXu bibliographies and style files.
+BIBINPUTS.bibtexu = $TEXMFDOTDIR;$TEXMF/{bibtexu,pbibtex,bibtex}/bib//
+BSTINPUTS.bibtexu = $TEXMFDOTDIR;$TEXMF/{bibtexu,pbibtex,bibtex}/bst//
+
% .ris and .bltxml bibliography formats.
RISINPUTS = $TEXMFDOTDIR;$TEXMF/biber/ris//
BLTXMLINPUTS = $TEXMFDOTDIR;$TEXMF/biber/bltxml//
Modified: branches/stable/source/src/texk/kpathsea/version.ac
===================================================================
--- branches/stable/source/src/texk/kpathsea/version.ac 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/kpathsea/version.ac 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
-dnl $Id: version.ac 62887 2022-04-03 17:27:53Z karl $
-dnl Copyright 2016-2022 Karl Berry <tex-live at tug.org>
+dnl $Id: version.ac 65770 2023-02-09 21:26:50Z karl $
+dnl Copyright 2016-2023 Karl Berry <tex-live at tug.org>
dnl Copyright 2011-2015 Peter Breitenlohner <tex-live at tug.org>
dnl
dnl This file is free software; the copyright holder
@@ -20,4 +20,4 @@
dnl --------------------------------------------------------
dnl
dnl This file is m4-included from configure.ac.
-m4_define([kpse_version], [6.3.5/dev])
+m4_define([kpse_version], [6.3.5])
Modified: branches/stable/source/src/texk/tests/TeXLive/TLConfig.pm
===================================================================
--- branches/stable/source/src/texk/tests/TeXLive/TLConfig.pm 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/tests/TeXLive/TLConfig.pm 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
# TeXLive::TLConfig.pm - module exporting configuration values
-# Copyright 2007-2022 Norbert Preining
+# Copyright 2007-2023 Norbert Preining
# This file is licensed under the GNU General Public License version 2
# or any later version.
@@ -6,7 +6,7 @@
use strict; use warnings;
package TeXLive::TLConfig;
-my $svnrev = '$Revision: 63068 $';
+my $svnrev = '$Revision: 65950 $';
my $_modulerevision = ($svnrev =~ m/: ([0-9]+) /) ? $1 : "unknown";
sub module_revision { return $_modulerevision; }
@@ -61,7 +61,7 @@
# the year of our release, will be used in the location of the
# network packages, and in menu names, and other places.
-our $ReleaseYear = 2022;
+our $ReleaseYear = 2023;
# users can upgrade from this year to the current year; might be the
# same as the release year, or any number of releases earlier.
@@ -118,8 +118,8 @@
our @CriticalPackagesList = qw/texlive.infra/;
our $CriticalPackagesRegexp = '^(texlive\.infra)';
if ($^O =~ /^MSWin/i) {
- push (@CriticalPackagesList, "tlperl.win32");
- $CriticalPackagesRegexp = '^(texlive\.infra|tlperl\.win32$)';
+ push (@CriticalPackagesList, "tlperl.windows");
+ $CriticalPackagesRegexp = '^(texlive\.infra|tlperl\.windows$)';
}
@@ -366,7 +366,7 @@
=item C<@TeXLive::TLConfig::CriticalPackagesRegexp>
A list of all those packages which we do not update regularly since they
-are too central, currently texlive.infra and (for Windows) tlperl.win32.
+are too central, currently texlive.infra and (for Windows) tlperl.windows.
=item C<@TeXLive::TLConfig::InstallExtraRequiredPackages>
Modified: branches/stable/source/src/texk/tests/TeXLive/TLUtils.pm
===================================================================
--- branches/stable/source/src/texk/tests/TeXLive/TLUtils.pm 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/tests/TeXLive/TLUtils.pm 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
# TeXLive::TLUtils.pm - the inevitable utilities for TeX Live.
-# Copyright 2007-2022 Norbert Preining, Reinhard Kotucha
+# Copyright 2007-2023 Norbert Preining, Reinhard Kotucha
# This file is licensed under the GNU General Public License version 2
# or any later version.
@@ -7,7 +7,7 @@
package TeXLive::TLUtils;
-my $svnrev = '$Revision: 64503 $';
+my $svnrev = '$Revision: 65994 $';
my $_modulerevision = ($svnrev =~ m/: ([0-9]+) /) ? $1 : "unknown";
sub module_revision { return $_modulerevision; }
@@ -26,7 +26,7 @@
TeXLive::TLUtils::platform();
TeXLive::TLUtils::platform_name($canonical_host);
TeXLive::TLUtils::platform_desc($platform);
- TeXLive::TLUtils::win32();
+ TeXLive::TLUtils::wndws();
TeXLive::TLUtils::unix();
=head2 System tools
@@ -264,7 +264,7 @@
@EXPORT = qw(setup_programs download_file process_logging_options
tldie tlwarn info log debug ddebug dddebug debug
debug_hash_str debug_hash
- win32 xchdir xsystem run_cmd system_pipe sort_archs);
+ wndws xchdir xsystem run_cmd system_pipe sort_archs);
}
use Cwd;
@@ -284,7 +284,7 @@
=item C<platform>
If C<$^O =~ /MSWin/i> is true we know that we're on
-Windows and we set the global variable C<$::_platform_> to C<win32>.
+Windows and we set the global variable C<$::_platform_> to C<windows>.
Otherwise we call C<platform_name> with the output of C<config.guess>
as argument.
@@ -296,13 +296,16 @@
systems, such as Solaris, we have to look for a shell. We use the value
of the C<CONFIG_SHELL> environment variable if it is set, else
C</bin/ksh> if it exists, else C</bin/bash> if it exists, else give up.
+Happily, C<config.guess> later reverted this change, but we keep our
+shell-finding code anyway to defend against future mistakes of the same ilk.
=cut
sub platform {
- unless (defined $::_platform_) {
+ if (! defined $::_platform_) {
if ($^O =~ /^MSWin/i) {
- $::_platform_ = "win32";
+ print STDERR "\$^O is $^O\n";
+ $::_platform_ = "windows";
} else {
my $config_guess = "$::installerdir/tlpkg/installer/config.guess";
@@ -527,7 +530,8 @@
'sparc-linux' => 'GNU/Linux on Sparc',
'sparc-solaris' => 'Solaris on Sparc',
'universal-darwin' => 'MacOSX current (10.14-) on ARM/x86_64',
- 'win32' => 'Windows',
+ 'win32' => 'Windows (32-bit)',
+ 'windows' => 'Windows (64-bit)',
'x86_64-cygwin' => 'Cygwin on x86_64',
'x86_64-darwinlegacy' => 'MacOSX legacy (10.6-) on x86_64',
'x86_64-dragonfly' => 'DragonFlyBSD on x86_64',
@@ -550,7 +554,7 @@
}
-=item C<win32>
+=item C<wndws>
Return C<1> if platform is Windows and C<0> otherwise. The test is
currently based on the value of Perl's C<$^O> variable.
@@ -557,7 +561,7 @@
=cut
-sub win32 {
+sub wndws {
if ($^O =~ /^MSWin/i) {
return 1;
} else {
@@ -564,7 +568,7 @@
return 0;
}
# the following needs config.guess, which is quite bad ...
- # return (&platform eq "win32")? 1:0;
+ # return (&platform eq "windows")? 1:0;
}
@@ -575,7 +579,7 @@
=cut
sub unix {
- return (&platform eq "win32")? 0:1;
+ return (&platform eq "windows")? 0:1;
}
@@ -599,7 +603,7 @@
my $envvar=shift;
my $var=$ENV{"$envvar"};
return 0 unless (defined $var);
- if (&win32) {
+ if (&wndws) {
$var=~s!\\!/!g; # change \ -> / (required by Perl)
}
return "$var";
@@ -621,7 +625,7 @@
my @PATH;
my $PATH = getenv('PATH');
- if (&win32) {
+ if (&wndws) {
my @PATHEXT = split (';', getenv('PATHEXT'));
push (@PATHEXT, ''); # in case argument contains an extension
@PATH = split (';', $PATH);
@@ -788,7 +792,7 @@
my ($prog, $infile, $outfile, $removeIn, @extraargs) = @_;
my $progQuote = quotify_path_with_spaces($prog);
- if (win32()) {
+ if (wndws()) {
$infile =~ s!/!\\!g;
$outfile =~ s!/!\\!g;
}
@@ -821,7 +825,7 @@
sub diskfree {
my $td = shift;
my ($output, $retval);
- if (win32()) {
+ if (wndws()) {
# the powershell one-liner only works from win8 on.
my @winver = Win32::GetOSVersion();
if ($winver[1]<=6 && $winver[2]<=1) {
@@ -904,7 +908,7 @@
sub get_user_home {
return $user_home_dir if ($user_home_dir);
- $user_home_dir = getenv (win32() ? 'USERPROFILE' : 'HOME') || '~';
+ $user_home_dir = getenv (wndws() ? 'USERPROFILE' : 'HOME') || '~';
return $user_home_dir;
}
@@ -939,7 +943,7 @@
sub dirname_and_basename {
my $path=shift;
my ($share, $base) = ("", "");
- if (win32) {
+ if (wndws()) {
$path=~s!\\!/!g;
}
# do not try to make sense of paths ending with /..
@@ -948,7 +952,7 @@
# eliminate `/.' path components
while ($path =~ s!/\./!/!) {};
# UNC path? => first split in $share = //xxx/yy and $path = /zzzz
- if (win32() and $path =~ m!^(//[^/]+/[^/]+)(.*)$!) {
+ if (wndws() and $path =~ m!^(//[^/]+/[^/]+)(.*)$!) {
($share, $path) = ($1, $2);
if ($path =~ m!^/?$!) {
$path = $share;
@@ -1006,7 +1010,7 @@
sub tl_abs_path {
my $path = shift;
- if (win32) {
+ if (wndws()) {
$path=~s!\\!/!g;
}
if (-e $path) {
@@ -1016,13 +1020,13 @@
} else{
# collapse /./ components
$path =~ s!/\./!/!g;
- # no support for .. path components or for win32 long-path syntax
+ # no support for .. path components or for windows long-path syntax
# (//?/ path prefix)
die "Unsupported path syntax" if $path =~ m!/\.\./! || $path =~ m!/\.\.$!
|| $path =~ m!^\.\.!;
- die "Unsupported path syntax" if win32() && $path =~ m!^//\?/!;
+ die "Unsupported path syntax" if wndws() && $path =~ m!^//\?/!;
if ($path !~ m!^(.:)?/!) { # relative path
- if (win32() && $path =~ /^.:/) { # drive letter
+ if (wndws() && $path =~ /^.:/) { # drive letter
my $dcwd;
# starts with drive letter: current dir on drive
$dcwd = Cwd::getdcwd ($1);
@@ -1056,7 +1060,7 @@
sub dir_creatable {
my $path=shift;
#print STDERR "testing $path\n";
- $path =~ s!\\!/!g if win32;
+ $path =~ s!\\!/!g if wndws;
return 0 unless -d $path;
$path .= '/' unless $path =~ m!/$!;
#print STDERR "testing $path\n";
@@ -1098,7 +1102,7 @@
sub dir_writable {
my ($path) = @_;
return 0 unless -d $path;
- $path =~ s!\\!/!g if win32;
+ $path =~ s!\\!/!g if wndws;
$path .= '/' unless $path =~ m!/$!;
my $i = 0;
my $f;
@@ -1142,9 +1146,9 @@
$ret = 1;
} else {
my $subdir = "";
- # win32 is special as usual: we need to separate //servername/ part
+ # windows is special as usual: we need to separate //servername/ part
# from the UNC path, since (! -d //servername/) tests true
- $subdir = $& if ( win32() && ($tree =~ s!^//[^/]+/!!) );
+ $subdir = $& if ( wndws() && ($tree =~ s!^//[^/]+/!!) );
my @dirs = split (/[\/\\]/, $tree);
for my $dir (@dirs) {
@@ -1617,13 +1621,13 @@
# what should we do with not existing entries????
next if (! -r "$f");
my $abs_f = Cwd::abs_path ($f);
- # the following is necessary because on win32,
+ # the following is necessary because on windows,
# abs_path("tl-portable")
# returns
# c:\tl test\...
# and not forward slashes, while, if there is already a forward /
# in the path, also the rest is done with forward slashes.
- $abs_f =~ s!\\!/!g if win32();
+ $abs_f =~ s!\\!/!g if wndws();
if (!$abs_f) {
warn ("oops, no abs_path($f) from " . `pwd`);
next;
@@ -1883,7 +1887,7 @@
sub _do_postaction_fileassoc {
my ($how, $mode, $tlpobj, $pa) = @_;
- return 1 unless win32();
+ return 1 unless wndws();
my ($errors, %keyval) =
parse_into_keywords($pa, qw/extension filetype/);
@@ -1921,7 +1925,7 @@
sub _do_postaction_filetype {
my ($how, $tlpobj, $pa) = @_;
- return 1 unless win32();
+ return 1 unless wndws();
my ($errors, %keyval) =
parse_into_keywords($pa, qw/name cmd/);
@@ -1966,7 +1970,7 @@
# associated program shows up in `open with' menu
sub _do_postaction_progid {
my ($how, $tlpobj, $pa) = @_;
- return 1 unless win32();
+ return 1 unless wndws();
my ($errors, %keyval) =
parse_into_keywords($pa, qw/extension filetype/);
@@ -2016,7 +2020,7 @@
return 0;
}
my $file = $keyval{'file'};
- if (win32() && defined($keyval{'filew32'})) {
+ if (wndws() && defined($keyval{'filew32'})) {
$file = $keyval{'filew32'};
}
my $texdir = `kpsewhich -var-value=TEXMFROOT`;
@@ -2046,7 +2050,7 @@
sub _do_postaction_shortcut {
my ($how, $tlpobj, $do_menu, $do_desktop, $pa) = @_;
- return 1 unless win32();
+ return 1 unless wndws();
my ($errors, %keyval) =
parse_into_keywords($pa, qw/type name icon cmd args hide/);
@@ -2317,7 +2321,7 @@
my $plat_bindir = "$Master/bin/$arch";
# nothing to do with symlinks on Windows, of course.
- return if win32();
+ return if wndws();
my $info_dir = "$Master/texmf-dist/doc/info";
if ($mode eq "add") {
@@ -2403,7 +2407,7 @@
sub w32_add_to_path {
my ($bindir, $multiuser) = @_;
- return if (!win32());
+ return if (!wndws());
my $path = TeXLive::TLWinGoo::get_system_env() -> {'/Path'};
$path =~ s/[\s\x00]+$//;
@@ -2648,7 +2652,7 @@
# on w32 don't extract file modified time, because AV soft can open
# files in the mean time causing time stamp modification to fail
- my $taropt = win32() ? "xmf" : "xf";
+ my $taropt = wndws() ? "xmf" : "xf";
if (system($tar, $taropt, $tarfile) != 0) {
tlwarn("TLUtils::untar: $tar $taropt $tarfile failed (in $targetdir)\n");
$ret = 0;
@@ -3146,7 +3150,7 @@
sub _download_file_program {
my ($url, $dest, $type) = @_;
- if (win32()) {
+ if (wndws()) {
$dest =~ s!/!\\!g;
}
@@ -3195,7 +3199,7 @@
=cut
sub nulldev {
- return (&win32()) ? 'nul' : '/dev/null';
+ return (&wndws()) ? 'nul' : '/dev/null';
}
=item C<get_full_line ($fh)>
@@ -4058,7 +4062,7 @@
# Unfortunately we have lots of special characters.
# On Windows, backslashes are normal but will already have been changed
# to slashes by tl_abs_path. And we should only check for : on Unix.
- my $colon = win32() ? "" : ":";
+ my $colon = wndws() ? "" : ":";
if ($texdir =~ /[,$colon;\\{}\$]/) {
if ($warn) {
print " !! TEXDIR value has problematic characters: $orig_texdir\n";
@@ -4071,7 +4075,7 @@
return 0;
}
# w32: for now, reject the root of a samba share
- return 0 if win32() && $texdir =~ m!^//[^/]+/[^/]+$!;
+ return 0 if wndws() && $texdir =~ m!^//[^/]+/[^/]+$!;
# if texdir already exists, make sure we can write into it.
return dir_writable($texdir) if (-d $texdir);
@@ -4102,7 +4106,7 @@
sub quotify_path_with_spaces {
my $p = shift;
- my $m = win32() ? '[+=^&();,!%\s]' : '.';
+ my $m = wndws() ? '[+=^&();,!%\s]' : '.';
if ( $p =~ m/$m/ ) {
$p =~ s/"//g; # remove any existing double quotes
$p = "\"$p\"";
@@ -4150,13 +4154,13 @@
sub native_slashify {
my ($r) = @_;
- $r =~ s!/!\\!g if win32();
+ $r =~ s!/!\\!g if wndws();
return $r;
}
sub forward_slashify {
my ($r) = @_;
- $r =~ s!\\!/!g if win32();
+ $r =~ s!\\!/!g if wndws();
return $r;
}
@@ -4238,7 +4242,7 @@
#
sub query_ctan_mirror_curl {
my $max_trial = 3;
- my $warg = (win32() ? '-w "%{url_effective}" ' : "-w '%{url_effective}' ");
+ my $warg = (wndws() ? '-w "%{url_effective}" ' : "-w '%{url_effective}' ");
for (my $i = 1; $i <= $max_trial; $i++) {
# -L -> follow redirects
# -s -> silent
@@ -4845,7 +4849,7 @@
die "mktexupd: exec file does not exist: $file" if (! -f $file);
}
}
- my $delim= (&win32)? ';' : ':';
+ my $delim= (&wndws)? ';' : ':';
my $TEXMFDBS;
chomp($TEXMFDBS=`kpsewhich --show-path="ls-R"`);
@@ -4855,8 +4859,8 @@
foreach my $path (keys %files) {
foreach my $db (@texmfdbs) {
$db=substr($db, -1) if ($db=~m|/$|); # strip leading /
- $db = lc($db) if win32();
- my $up = (win32() ? lc($path) : $path);
+ $db = lc($db) if wndws();
+ my $up = (wndws() ? lc($path) : $path);
if (substr($up, 0, length("$db/")) eq "$db/") {
# we appended a / because otherwise "texmf" is recognized as a
# substring of "texmf-dist".
@@ -4988,7 +4992,7 @@
sub prepend_own_path {
my $bindir = dirname(Cwd::abs_path(which('kpsewhich')));
- if (win32()) {
+ if (wndws()) {
$bindir =~ s!\\!/!g;
$ENV{'PATH'} = "$bindir;$ENV{PATH}";
} else {
Modified: branches/stable/source/src/texk/web2c/ChangeLog
===================================================================
--- branches/stable/source/src/texk/web2c/ChangeLog 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/ChangeLog 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,3 +1,31 @@
+2023-02-14 Hironori Kitagawa <h_kitagawa2001 at yahoo.co.jp>
+
+ * tests/fn-generate.perl:
+ Avoid errors on parallel test processing.
+ Report from Ken Brown.
+
+2023-02-13 Karl Berry <karl at freefriends.org>
+
+ * enctexdir/enctex-pdftex.ch: move "\special shipout"
+ change here, from enctex2.ch, so it is not applied to tex (which
+ doesn't have it).
+
+2023-02-12 Phelype Oleinik <phe.h.o1 at gmail.com>
+ and Karl Berry <karl at freefriends.org>
+
+ * enctexdir/enctex2.ch: make parallel change for ``late''
+ \special shipout. This code is what avoids the invalid
+ write_stream(tail):=null assignment in the original code.
+ See pdftex.web (Implement \.{\\special}) for more.
+
+2023-01-28 TANAKA Takuji <ttk at t-lab.opal.ne.jp>
+
+ * Makefile.in, ac/web2c.ac (ptex, uptex):
+ Revert options --enable-(u)ptex(-synctex) for configure.
+ By default, we do not build binaries of (u)pTeX (ptex, uptex)
+ and we use alias of e-upTeX (eptex, euptex) for them.
+ https://github.com/texjporg/tex-jp-build/issues/32
+
2023-01-15 TANAKA Takuji <ttk at t-lab.opal.ne.jp>
* configure.ac, ac/web2c.ac (ptex, uptex):
Modified: branches/stable/source/src/texk/web2c/Makefile.in
===================================================================
--- branches/stable/source/src/texk/web2c/Makefile.in 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/Makefile.in 2023-02-21 22:38:24 UTC (rev 903)
@@ -112,21 +112,22 @@
$(am__EXEEXT_20) $(am__EXEEXT_21) $(am__EXEEXT_22) \
$(am__EXEEXT_23) $(am__EXEEXT_24) $(am__EXEEXT_25) \
$(am__EXEEXT_26) $(am__EXEEXT_27) $(am__EXEEXT_28) \
- $(am__EXEEXT_29)
+ $(am__EXEEXT_29) $(am__EXEEXT_30) $(am__EXEEXT_31)
noinst_PROGRAMS = tangleboot$(EXEEXT) ctangleboot$(EXEEXT) \
- $(am__EXEEXT_30) $(am__EXEEXT_31) $(am__EXEEXT_32) \
- $(am__EXEEXT_33) $(am__EXEEXT_34) $(am__EXEEXT_35) \
- $(am__EXEEXT_36) $(am__EXEEXT_37) $(am__EXEEXT_38) \
- $(am__EXEEXT_39) $(am__EXEEXT_40)
-TESTS = tangle.test $(am__EXEEXT_43) ctiedir/ctie.test \
+ $(am__EXEEXT_32) $(am__EXEEXT_33) $(am__EXEEXT_34) \
+ $(am__EXEEXT_35) $(am__EXEEXT_36) $(am__EXEEXT_37) \
+ $(am__EXEEXT_38) $(am__EXEEXT_39) $(am__EXEEXT_40) \
+ $(am__EXEEXT_41) $(am__EXEEXT_42)
+TESTS = tangle.test $(am__EXEEXT_45) ctiedir/ctie.test \
cwebdir/cweave.test tiedir/tie.test $(am__append_6) \
$(am__append_16) $(am__append_25) $(am__append_34) \
$(am__append_42) $(am__append_55) $(am__append_56) \
- $(am__append_58) $(am__append_63) $(am__append_67) \
- $(am__append_70) $(am__append_75) $(am__append_78) \
- $(am__append_99) $(am__append_100) $(am__append_101) \
- $(am__append_102) $(am__append_110) $(am__append_112) \
- $(am__append_114) $(am__append_141) libmd5/md5.test
+ $(am__append_58) $(am__append_62) $(am__EXEEXT_46) \
+ $(am__append_68) $(am__append_73) $(am__append_76) \
+ $(am__append_79) $(am__append_84) $(am__append_87) \
+ $(am__append_108) $(am__append_109) $(am__append_110) \
+ $(am__append_111) $(am__append_119) $(am__append_121) \
+ $(am__append_123) $(am__append_150) libmd5/md5.test
@WEB_TRUE at am__append_1 = $(web_programs)
@WEB_TRUE at am__append_2 = $(web_tests)
@TEX_TRUE at am__append_3 = tex
@@ -191,70 +192,69 @@
@ETEX_TRUE at am__append_58 = $(etex_tests)
@ETEX_TRUE at am__append_59 = etrip.diffs
@ETEX_TRUE at am__append_60 = etrip-clean
- at EPTEX_TRUE@am__append_61 = eptex
- at EPTEX_TRUE@am__append_62 = eptex$(EXEEXT):ptex
- at EPTEX_TRUE@am__append_63 = $(eptex_tests)
- at EPTEX_TRUE@am__append_64 = eptrip.diffs
- at EPTEX_TRUE@am__append_65 = eptrip-clean
-
-#if UPTEX
-#bin_PROGRAMS += uptex
-#endif UPTEX
- at UPWEB_TRUE@am__append_66 = $(upweb_programs)
-
-#if UPTEX
-#TESTS += $(uptex_tests)
-#TRIPTRAP += uptrip.diffs
-#TRIPTRAP_CLEAN += uptrip-clean
-#endif UPTEX
- at UPWEB_TRUE@am__append_67 = $(upweb_tests)
- at EUPTEX_TRUE@am__append_68 = euptex
- at EUPTEX_TRUE@am__append_69 = euptex$(EXEEXT):uptex
- at EUPTEX_TRUE@am__append_70 = $(euptex_tests)
- at EUPTEX_TRUE@am__append_71 = euptrip.diffs
- at EUPTEX_TRUE@am__append_72 = euptrip-clean
- at HITEX_TRUE@am__append_73 = hitex hishrink histretch
- at HITEX_TRUE@am__append_74 = himktables
- at HITEX_TRUE@am__append_75 = $(hitex_tests)
- at MINGW32_TRUE@am__append_76 = \
+ at PTEX_TRUE@am__append_61 = ptex
+ at PTEX_TRUE@am__append_62 = $(ptex_tests)
+ at PTEX_TRUE@am__append_63 = ptrip.diffs
+ at PTEX_TRUE@am__append_64 = ptrip-clean
+ at PWEB_TRUE@am__append_65 = $(pweb_tests)
+ at EPTEX_TRUE@am__append_66 = eptex
+ at EPTEX_TRUE@@PTEX_FALSE at am__append_67 = eptex$(EXEEXT):ptex
+ at EPTEX_TRUE@am__append_68 = $(eptex_tests)
+ at EPTEX_TRUE@am__append_69 = eptrip.diffs
+ at EPTEX_TRUE@am__append_70 = eptrip-clean
+ at UPTEX_TRUE@am__append_71 = uptex
+ at UPWEB_TRUE@am__append_72 = $(upweb_programs)
+ at UPTEX_TRUE@am__append_73 = $(uptex_tests)
+ at UPTEX_TRUE@am__append_74 = uptrip.diffs
+ at UPTEX_TRUE@am__append_75 = uptrip-clean
+ at UPWEB_TRUE@am__append_76 = $(upweb_tests)
+ at EUPTEX_TRUE@am__append_77 = euptex
+ at EUPTEX_TRUE@@UPTEX_FALSE at am__append_78 = euptex$(EXEEXT):uptex
+ at EUPTEX_TRUE@am__append_79 = $(euptex_tests)
+ at EUPTEX_TRUE@am__append_80 = euptrip.diffs
+ at EUPTEX_TRUE@am__append_81 = euptrip-clean
+ at HITEX_TRUE@am__append_82 = hitex hishrink histretch
+ at HITEX_TRUE@am__append_83 = himktables
+ at HITEX_TRUE@am__append_84 = $(hitex_tests)
+ at MINGW32_TRUE@am__append_85 = \
@MINGW32_TRUE@ pdftexdir/regex/regex.c \
@MINGW32_TRUE@ pdftexdir/regex/regex.h
- at PDFTEX_TRUE@am__append_77 = pdftex ttf2afm pdftosrc
- at PDFTEX_TRUE@am__append_78 = $(pdftex_tests) $(ttf2afm_tests) \
+ at PDFTEX_TRUE@am__append_86 = pdftex ttf2afm pdftosrc
+ at PDFTEX_TRUE@am__append_87 = $(pdftex_tests) $(ttf2afm_tests) \
@PDFTEX_TRUE@ $(pdftosrc_tests)
- at LUATEX_TRUE@am__append_79 = luatex
- at LUATEX_TRUE@@WIN32_TRUE at am__append_80 = call_luatex
- at LUATEX_TRUE@@WIN32_TRUE at am__append_81 = install-luatex-links
- at LUATEX_TRUE@@WIN32_TRUE at am__append_82 = uninstall-luatex-links
- at LUATEX_TRUE@@WIN32_FALSE at am__append_83 = luatex$(EXEEXT):texlua luatex$(EXEEXT):texluac
- at LUAHBTEX_TRUE@am__append_84 = luahbtex
- at LUAHBTEX_TRUE@@WIN32_TRUE at am__append_85 = call_luahbtex
- at LUAHBTEX_TRUE@@WIN32_TRUE at am__append_86 = install-luahbtex-links
- at LUAHBTEX_TRUE@@WIN32_TRUE at am__append_87 = uninstall-luahbtex-links
+ at LUATEX_TRUE@am__append_88 = luatex
+ at LUATEX_TRUE@@WIN32_TRUE at am__append_89 = call_luatex
+ at LUATEX_TRUE@@WIN32_TRUE at am__append_90 = install-luatex-links
+ at LUATEX_TRUE@@WIN32_TRUE at am__append_91 = uninstall-luatex-links
+ at LUATEX_TRUE@@WIN32_FALSE at am__append_92 = luatex$(EXEEXT):texlua luatex$(EXEEXT):texluac
+ at LUAHBTEX_TRUE@am__append_93 = luahbtex
+ at LUAHBTEX_TRUE@@WIN32_TRUE at am__append_94 = call_luahbtex
+ at LUAHBTEX_TRUE@@WIN32_TRUE at am__append_95 = install-luahbtex-links
+ at LUAHBTEX_TRUE@@WIN32_TRUE at am__append_96 = uninstall-luahbtex-links
# keep texlua[c] as links to luatex unless luatex is not installed.
- at LUAHBTEX_TRUE@@LUATEX_FALSE@@WIN32_FALSE at am__append_88 = luahbtex$(EXEEXT):texlua luahbtex$(EXEEXT):texluac
- at LUAJITTEX_TRUE@am__append_89 = luajittex
- at LUAJITTEX_TRUE@@WIN32_TRUE at am__append_90 = call_luajittex
- at LUAJITTEX_TRUE@@WIN32_TRUE at am__append_91 = install-luajittex-links
- at LUAJITTEX_TRUE@@WIN32_TRUE at am__append_92 = uninstall-luajittex-links
- at LUAJITTEX_TRUE@@WIN32_FALSE at am__append_93 = luajittex$(EXEEXT):texluajit luajittex$(EXEEXT):texluajitc
- at LUAJITHBTEX_TRUE@am__append_94 = luajithbtex
- at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__append_95 = call_luajithbtex
- at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__append_96 = install-luajithbtex-links
- at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__append_97 = uninstall-luajithbtex-links
+ at LUAHBTEX_TRUE@@LUATEX_FALSE@@WIN32_FALSE at am__append_97 = luahbtex$(EXEEXT):texlua luahbtex$(EXEEXT):texluac
+ at LUAJITTEX_TRUE@am__append_98 = luajittex
+ at LUAJITTEX_TRUE@@WIN32_TRUE at am__append_99 = call_luajittex
+ at LUAJITTEX_TRUE@@WIN32_TRUE at am__append_100 = install-luajittex-links
+ at LUAJITTEX_TRUE@@WIN32_TRUE at am__append_101 = uninstall-luajittex-links
+ at LUAJITTEX_TRUE@@WIN32_FALSE at am__append_102 = luajittex$(EXEEXT):texluajit luajittex$(EXEEXT):texluajitc
+ at LUAJITHBTEX_TRUE@am__append_103 = luajithbtex
+ at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__append_104 = call_luajithbtex
+ at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__append_105 = install-luajithbtex-links
+ at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__append_106 = uninstall-luajithbtex-links
# keep texluajit[c] as links to luajittex unless luajittex is not installed.
- at LUAJITHBTEX_TRUE@@LUAJITTEX_FALSE@@WIN32_FALSE at am__append_98 = luajithbtex$(EXEEXT):texluajit luajithbtex$(EXEEXT):texluajitc
- at LUATEX_TRUE@am__append_99 = $(luatex_tests)
- at LUAHBTEX_TRUE@am__append_100 = $(luahbtex_tests)
- at LUAJITTEX_TRUE@am__append_101 = $(luajittex_tests)
- at LUAJITHBTEX_TRUE@am__append_102 = $(luajithbtex_tests)
- at XETEX_TRUE@am__append_103 = xetex
- at XETEX_MACOSX_TRUE@am__append_104 = -DXETEX_MAC
- at XETEX_MACOSX_TRUE@am__append_105 = -std=c++11
- at XETEX_MACOSX_FALSE@am__append_106 = $(FONTCONFIG_INCLUDES)
- at XETEX_MACOSX_FALSE@am__append_107 = $(FONTCONFIG_LIBS)
- at XETEX_MACOSX_TRUE@am__append_108 = \
+ at LUAJITHBTEX_TRUE@@LUAJITTEX_FALSE@@WIN32_FALSE at am__append_107 = luajithbtex$(EXEEXT):texluajit luajithbtex$(EXEEXT):texluajitc
+ at LUATEX_TRUE@am__append_108 = $(luatex_tests)
+ at LUAHBTEX_TRUE@am__append_109 = $(luahbtex_tests)
+ at LUAJITTEX_TRUE@am__append_110 = $(luajittex_tests)
+ at LUAJITHBTEX_TRUE@am__append_111 = $(luajithbtex_tests)
+ at XETEX_TRUE@am__append_112 = xetex
+ at XETEX_MACOSX_TRUE@am__append_113 = -DXETEX_MAC
+ at XETEX_MACOSX_TRUE@am__append_114 = -std=c++11
+ at XETEX_MACOSX_FALSE@am__append_115 = $(FONTCONFIG_INCLUDES)
+ at XETEX_MACOSX_FALSE@am__append_116 = $(FONTCONFIG_LIBS)
+ at XETEX_MACOSX_TRUE@am__append_117 = \
@XETEX_MACOSX_TRUE@ xetexdir/XeTeXFontInst_Mac.cpp \
@XETEX_MACOSX_TRUE@ xetexdir/XeTeXFontInst_Mac.h \
@XETEX_MACOSX_TRUE@ xetexdir/XeTeXFontMgr_Mac.mm \
@@ -261,84 +261,84 @@
@XETEX_MACOSX_TRUE@ xetexdir/XeTeXFontMgr_Mac.h \
@XETEX_MACOSX_TRUE@ xetexdir/XeTeX_mac.c
- at XETEX_MACOSX_FALSE@am__append_109 = \
+ at XETEX_MACOSX_FALSE@am__append_118 = \
@XETEX_MACOSX_FALSE@ xetexdir/XeTeXFontMgr_FC.cpp \
@XETEX_MACOSX_FALSE@ xetexdir/XeTeXFontMgr_FC.h
- at XETEX_TRUE@am__append_110 = $(xetex_tests)
- at OTANGLE_TRUE@am__append_111 = $(omegaware_programs)
- at OTANGLE_TRUE@am__append_112 = $(OTANGLE_tests) $(OMFONTS_tests)
- at ALEPH_TRUE@am__append_113 = aleph
- at ALEPH_TRUE@am__append_114 = $(aleph_tests)
- at SYNCTEX_TRUE@am__append_115 = synctex
- at SYNCTEX_TRUE@am__append_116 = $(LTLIBSYNCTEX)
- at SYNCTEX_TRUE@am__append_117 = $(LIBSYNCTEX)
- at MINGW32_TRUE@am__append_118 = $(KPATHSEA_INCLUDES)
- at MINGW32_TRUE@am__append_119 = -lshlwapi $(KPATHSEA_LIBS)
- at MINGW32_TRUE@am__append_120 = -lshlwapi
- at TEX_SYNCTEX_TRUE@am__append_121 = -I$(srcdir)/synctexdir \
+ at XETEX_TRUE@am__append_119 = $(xetex_tests)
+ at OTANGLE_TRUE@am__append_120 = $(omegaware_programs)
+ at OTANGLE_TRUE@am__append_121 = $(OTANGLE_tests) $(OMFONTS_tests)
+ at ALEPH_TRUE@am__append_122 = aleph
+ at ALEPH_TRUE@am__append_123 = $(aleph_tests)
+ at SYNCTEX_TRUE@am__append_124 = synctex
+ at SYNCTEX_TRUE@am__append_125 = $(LTLIBSYNCTEX)
+ at SYNCTEX_TRUE@am__append_126 = $(LIBSYNCTEX)
+ at MINGW32_TRUE@am__append_127 = $(KPATHSEA_INCLUDES)
+ at MINGW32_TRUE@am__append_128 = -lshlwapi $(KPATHSEA_LIBS)
+ at MINGW32_TRUE@am__append_129 = -lshlwapi
+ at TEX_SYNCTEX_TRUE@am__append_130 = -I$(srcdir)/synctexdir \
@TEX_SYNCTEX_TRUE@ $(ZLIB_INCLUDES) -D__SyncTeX__ \
@TEX_SYNCTEX_TRUE@ -DSYNCTEX_ENGINE_H=\"synctex-tex.h\"
- at TEX_SYNCTEX_TRUE@am__append_122 = $(ZLIB_LIBS)
- at TEX_SYNCTEX_TRUE@am__append_123 = $(ZLIB_DEPEND)
- at TEX_SYNCTEX_TRUE@am__append_124 = \
+ at TEX_SYNCTEX_TRUE@am__append_131 = $(ZLIB_LIBS)
+ at TEX_SYNCTEX_TRUE@am__append_132 = $(ZLIB_DEPEND)
+ at TEX_SYNCTEX_TRUE@am__append_133 = \
@TEX_SYNCTEX_TRUE@ synctexdir/synctex.c \
@TEX_SYNCTEX_TRUE@ synctexdir/synctex.h \
@TEX_SYNCTEX_TRUE@ synctexdir/synctex-common.h \
@TEX_SYNCTEX_TRUE@ synctexdir/synctex-tex.h
- at ETEX_SYNCTEX_TRUE@am__append_125 = -I$(srcdir)/synctexdir \
+ at ETEX_SYNCTEX_TRUE@am__append_134 = -I$(srcdir)/synctexdir \
@ETEX_SYNCTEX_TRUE@ $(ZLIB_INCLUDES) -D__SyncTeX__ \
@ETEX_SYNCTEX_TRUE@ -DSYNCTEX_ENGINE_H=\"synctex-etex.h\"
- at ETEX_SYNCTEX_TRUE@am__append_126 = $(ZLIB_LIBS)
- at ETEX_SYNCTEX_TRUE@am__append_127 = $(ZLIB_DEPEND)
- at ETEX_SYNCTEX_TRUE@am__append_128 = \
+ at ETEX_SYNCTEX_TRUE@am__append_135 = $(ZLIB_LIBS)
+ at ETEX_SYNCTEX_TRUE@am__append_136 = $(ZLIB_DEPEND)
+ at ETEX_SYNCTEX_TRUE@am__append_137 = \
@ETEX_SYNCTEX_TRUE@ synctexdir/synctex.c \
@ETEX_SYNCTEX_TRUE@ synctexdir/synctex.h \
@ETEX_SYNCTEX_TRUE@ synctexdir/synctex-common.h \
@ETEX_SYNCTEX_TRUE@ synctexdir/synctex-etex.h
- at EPTEX_SYNCTEX_TRUE@am__append_129 = -I$(srcdir)/synctexdir \
+ at EPTEX_SYNCTEX_TRUE@am__append_138 = -I$(srcdir)/synctexdir \
@EPTEX_SYNCTEX_TRUE@ $(ZLIB_INCLUDES) -D__SyncTeX__ \
@EPTEX_SYNCTEX_TRUE@ -DSYNCTEX_ENGINE_H=\"synctex-eptex.h\"
- at EPTEX_SYNCTEX_TRUE@am__append_130 = $(ZLIB_LIBS)
- at EPTEX_SYNCTEX_TRUE@am__append_131 = $(ZLIB_DEPEND)
- at EPTEX_SYNCTEX_TRUE@am__append_132 = \
+ at EPTEX_SYNCTEX_TRUE@am__append_139 = $(ZLIB_LIBS)
+ at EPTEX_SYNCTEX_TRUE@am__append_140 = $(ZLIB_DEPEND)
+ at EPTEX_SYNCTEX_TRUE@am__append_141 = \
@EPTEX_SYNCTEX_TRUE@ synctexdir/synctex.c \
@EPTEX_SYNCTEX_TRUE@ synctexdir/synctex.h \
@EPTEX_SYNCTEX_TRUE@ synctexdir/synctex-common.h \
@EPTEX_SYNCTEX_TRUE@ synctexdir/synctex-eptex.h
- at EUPTEX_SYNCTEX_TRUE@am__append_133 = -I$(srcdir)/synctexdir \
+ at EUPTEX_SYNCTEX_TRUE@am__append_142 = -I$(srcdir)/synctexdir \
@EUPTEX_SYNCTEX_TRUE@ $(ZLIB_INCLUDES) -D__SyncTeX__ \
@EUPTEX_SYNCTEX_TRUE@ -DSYNCTEX_ENGINE_H=\"synctex-euptex.h\"
- at EUPTEX_SYNCTEX_TRUE@am__append_134 = $(ZLIB_LIBS)
- at EUPTEX_SYNCTEX_TRUE@am__append_135 = $(ZLIB_DEPEND)
- at EUPTEX_SYNCTEX_TRUE@am__append_136 = \
+ at EUPTEX_SYNCTEX_TRUE@am__append_143 = $(ZLIB_LIBS)
+ at EUPTEX_SYNCTEX_TRUE@am__append_144 = $(ZLIB_DEPEND)
+ at EUPTEX_SYNCTEX_TRUE@am__append_145 = \
@EUPTEX_SYNCTEX_TRUE@ synctexdir/synctex.c \
@EUPTEX_SYNCTEX_TRUE@ synctexdir/synctex.h \
@EUPTEX_SYNCTEX_TRUE@ synctexdir/synctex-common.h \
@EUPTEX_SYNCTEX_TRUE@ synctexdir/synctex-euptex.h
- at PDFTEX_SYNCTEX_TRUE@am__append_137 = -I$(srcdir)/synctexdir \
+ at PDFTEX_SYNCTEX_TRUE@am__append_146 = -I$(srcdir)/synctexdir \
@PDFTEX_SYNCTEX_TRUE@ -D__SyncTeX__ \
@PDFTEX_SYNCTEX_TRUE@ -DSYNCTEX_ENGINE_H=\"synctex-pdftex.h\"
- at PDFTEX_SYNCTEX_TRUE@am__append_138 = \
+ at PDFTEX_SYNCTEX_TRUE@am__append_147 = \
@PDFTEX_SYNCTEX_TRUE@ synctexdir/synctex.c \
@PDFTEX_SYNCTEX_TRUE@ synctexdir/synctex.h \
@PDFTEX_SYNCTEX_TRUE@ synctexdir/synctex-common.h \
@PDFTEX_SYNCTEX_TRUE@ synctexdir/synctex-pdftex.h
- at XETEX_SYNCTEX_TRUE@am__append_139 = -I$(srcdir)/synctexdir \
+ at XETEX_SYNCTEX_TRUE@am__append_148 = -I$(srcdir)/synctexdir \
@XETEX_SYNCTEX_TRUE@ -D__SyncTeX__ \
@XETEX_SYNCTEX_TRUE@ -DSYNCTEX_ENGINE_H=\"synctex-xetex.h\"
- at XETEX_SYNCTEX_TRUE@am__append_140 = \
+ at XETEX_SYNCTEX_TRUE@am__append_149 = \
@XETEX_SYNCTEX_TRUE@ synctexdir/synctex.c \
@XETEX_SYNCTEX_TRUE@ synctexdir/synctex.h \
@XETEX_SYNCTEX_TRUE@ synctexdir/synctex-common.h \
@XETEX_SYNCTEX_TRUE@ synctexdir/synctex-xetex.h
- at SYNCTEX_TRUE@am__append_141 = $(synctex_tests)
+ at SYNCTEX_TRUE@am__append_150 = $(synctex_tests)
subdir = .
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/m4/web2c-disable.m4 \
@@ -421,36 +421,38 @@
@PMP_TRUE at am__EXEEXT_14 = pmpost$(EXEEXT)
@UPMP_TRUE at am__EXEEXT_15 = upmpost$(EXEEXT)
@ETEX_TRUE at am__EXEEXT_16 = etex$(EXEEXT)
- at EPTEX_TRUE@am__EXEEXT_17 = eptex$(EXEEXT)
- at UPWEB_TRUE@am__EXEEXT_18 = $(am__EXEEXT_2)
- at EUPTEX_TRUE@am__EXEEXT_19 = euptex$(EXEEXT)
- at HITEX_TRUE@am__EXEEXT_20 = hitex$(EXEEXT) hishrink$(EXEEXT) \
+ at PTEX_TRUE@am__EXEEXT_17 = ptex$(EXEEXT)
+ at EPTEX_TRUE@am__EXEEXT_18 = eptex$(EXEEXT)
+ at UPTEX_TRUE@am__EXEEXT_19 = uptex$(EXEEXT)
+ at UPWEB_TRUE@am__EXEEXT_20 = $(am__EXEEXT_2)
+ at EUPTEX_TRUE@am__EXEEXT_21 = euptex$(EXEEXT)
+ at HITEX_TRUE@am__EXEEXT_22 = hitex$(EXEEXT) hishrink$(EXEEXT) \
@HITEX_TRUE@ histretch$(EXEEXT)
- at PDFTEX_TRUE@am__EXEEXT_21 = pdftex$(EXEEXT) ttf2afm$(EXEEXT) \
+ at PDFTEX_TRUE@am__EXEEXT_23 = pdftex$(EXEEXT) ttf2afm$(EXEEXT) \
@PDFTEX_TRUE@ pdftosrc$(EXEEXT)
- at LUATEX_TRUE@am__EXEEXT_22 = luatex$(EXEEXT)
- at LUAHBTEX_TRUE@am__EXEEXT_23 = luahbtex$(EXEEXT)
- at LUAJITTEX_TRUE@am__EXEEXT_24 = luajittex$(EXEEXT)
- at LUAJITHBTEX_TRUE@am__EXEEXT_25 = luajithbtex$(EXEEXT)
- at XETEX_TRUE@am__EXEEXT_26 = xetex$(EXEEXT)
- at OTANGLE_TRUE@am__EXEEXT_27 = $(am__EXEEXT_3)
- at ALEPH_TRUE@am__EXEEXT_28 = aleph$(EXEEXT)
- at SYNCTEX_TRUE@am__EXEEXT_29 = synctex$(EXEEXT)
+ at LUATEX_TRUE@am__EXEEXT_24 = luatex$(EXEEXT)
+ at LUAHBTEX_TRUE@am__EXEEXT_25 = luahbtex$(EXEEXT)
+ at LUAJITTEX_TRUE@am__EXEEXT_26 = luajittex$(EXEEXT)
+ at LUAJITHBTEX_TRUE@am__EXEEXT_27 = luajithbtex$(EXEEXT)
+ at XETEX_TRUE@am__EXEEXT_28 = xetex$(EXEEXT)
+ at OTANGLE_TRUE@am__EXEEXT_29 = $(am__EXEEXT_3)
+ at ALEPH_TRUE@am__EXEEXT_30 = aleph$(EXEEXT)
+ at SYNCTEX_TRUE@am__EXEEXT_31 = synctex$(EXEEXT)
am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(libdir)" \
"$(DESTDIR)$(libdir)" "$(DESTDIR)$(man1dir)" \
"$(DESTDIR)$(man5dir)" "$(DESTDIR)$(pkgconfigdir)" \
"$(DESTDIR)$(syncincludedir)"
- at MF_TRUE@@WIN32_TRUE at am__EXEEXT_30 = call_mf$(EXEEXT)
- at MFLUA_TRUE@@WIN32_TRUE at am__EXEEXT_31 = call_mflua$(EXEEXT)
- at MFLUAJIT_TRUE@@WIN32_TRUE at am__EXEEXT_32 = call_mfluajit$(EXEEXT)
- at MP_TRUE@@WIN32_TRUE at am__EXEEXT_33 = call_mpost$(EXEEXT)
- at PMP_TRUE@@WIN32_TRUE at am__EXEEXT_34 = call_pmpost$(EXEEXT)
- at UPMP_TRUE@@WIN32_TRUE at am__EXEEXT_35 = call_upmpost$(EXEEXT)
- at HITEX_TRUE@am__EXEEXT_36 = himktables$(EXEEXT)
- at LUATEX_TRUE@@WIN32_TRUE at am__EXEEXT_37 = call_luatex$(EXEEXT)
- at LUAHBTEX_TRUE@@WIN32_TRUE at am__EXEEXT_38 = call_luahbtex$(EXEEXT)
- at LUAJITTEX_TRUE@@WIN32_TRUE at am__EXEEXT_39 = call_luajittex$(EXEEXT)
- at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__EXEEXT_40 = \
+ at MF_TRUE@@WIN32_TRUE at am__EXEEXT_32 = call_mf$(EXEEXT)
+ at MFLUA_TRUE@@WIN32_TRUE at am__EXEEXT_33 = call_mflua$(EXEEXT)
+ at MFLUAJIT_TRUE@@WIN32_TRUE at am__EXEEXT_34 = call_mfluajit$(EXEEXT)
+ at MP_TRUE@@WIN32_TRUE at am__EXEEXT_35 = call_mpost$(EXEEXT)
+ at PMP_TRUE@@WIN32_TRUE at am__EXEEXT_36 = call_pmpost$(EXEEXT)
+ at UPMP_TRUE@@WIN32_TRUE at am__EXEEXT_37 = call_upmpost$(EXEEXT)
+ at HITEX_TRUE@am__EXEEXT_38 = himktables$(EXEEXT)
+ at LUATEX_TRUE@@WIN32_TRUE at am__EXEEXT_39 = call_luatex$(EXEEXT)
+ at LUAHBTEX_TRUE@@WIN32_TRUE at am__EXEEXT_40 = call_luahbtex$(EXEEXT)
+ at LUAJITTEX_TRUE@@WIN32_TRUE at am__EXEEXT_41 = call_luajittex$(EXEEXT)
+ at LUAJITHBTEX_TRUE@@WIN32_TRUE at am__EXEEXT_42 = \
@LUAJITHBTEX_TRUE@@WIN32_TRUE@ call_luajithbtex$(EXEEXT)
PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS)
am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
@@ -1554,12 +1556,18 @@
pooltype_OBJECTS = $(nodist_pooltype_OBJECTS)
pooltype_LDADD = $(LDADD)
pooltype_DEPENDENCIES = $(proglib) $(am__DEPENDENCIES_1)
+dist_ptex_OBJECTS = ptexdir/ptex-ptexextra.$(OBJEXT)
+am__objects_57 = ptex-ptexini.$(OBJEXT) ptex-ptex0.$(OBJEXT)
+nodist_ptex_OBJECTS = $(am__objects_57) ptex-ptex-pool.$(OBJEXT)
+ptex_OBJECTS = $(dist_ptex_OBJECTS) $(nodist_ptex_OBJECTS)
+am__DEPENDENCIES_11 = libkanji.a $(pproglib) $(am__DEPENDENCIES_1) \
+ $(am__DEPENDENCIES_2) $(am__DEPENDENCIES_1)
am_synctex_OBJECTS = synctexdir/synctex-synctex_main.$(OBJEXT)
synctex_OBJECTS = $(am_synctex_OBJECTS)
-am__DEPENDENCIES_11 = $(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1)
- at MINGW32_TRUE@am__DEPENDENCIES_12 = $(am__DEPENDENCIES_1)
-synctex_DEPENDENCIES = $(am__DEPENDENCIES_11) $(am__DEPENDENCIES_1) \
- $(am__DEPENDENCIES_12)
+am__DEPENDENCIES_12 = $(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1)
+ at MINGW32_TRUE@am__DEPENDENCIES_13 = $(am__DEPENDENCIES_1)
+synctex_DEPENDENCIES = $(am__DEPENDENCIES_12) $(am__DEPENDENCIES_1) \
+ $(am__DEPENDENCIES_13)
nodist_tangle_OBJECTS = tangle.$(OBJEXT)
tangle_OBJECTS = $(nodist_tangle_OBJECTS)
tangle_LDADD = $(LDADD)
@@ -1570,14 +1578,14 @@
am__dist_tex_SOURCES_DIST = texextra.c synctexdir/synctex.c \
synctexdir/synctex.h synctexdir/synctex-common.h \
synctexdir/synctex-tex.h
- at TEX_SYNCTEX_TRUE@am__objects_57 = synctexdir/tex-synctex.$(OBJEXT)
-dist_tex_OBJECTS = tex-texextra.$(OBJEXT) $(am__objects_57)
-am__objects_58 = tex-texini.$(OBJEXT) tex-tex0.$(OBJEXT)
-nodist_tex_OBJECTS = $(am__objects_58) tex-tex-pool.$(OBJEXT)
+ at TEX_SYNCTEX_TRUE@am__objects_58 = synctexdir/tex-synctex.$(OBJEXT)
+dist_tex_OBJECTS = tex-texextra.$(OBJEXT) $(am__objects_58)
+am__objects_59 = tex-texini.$(OBJEXT) tex-tex0.$(OBJEXT)
+nodist_tex_OBJECTS = $(am__objects_59) tex-tex-pool.$(OBJEXT)
tex_OBJECTS = $(dist_tex_OBJECTS) $(nodist_tex_OBJECTS)
- at TEX_SYNCTEX_TRUE@am__DEPENDENCIES_13 = $(am__DEPENDENCIES_1)
+ at TEX_SYNCTEX_TRUE@am__DEPENDENCIES_14 = $(am__DEPENDENCIES_1)
tex_DEPENDENCIES = $(am__DEPENDENCIES_2) $(am__DEPENDENCIES_1) \
- $(am__DEPENDENCIES_13)
+ $(am__DEPENDENCIES_14)
nodist_tftopl_OBJECTS = tftopl.$(OBJEXT)
tftopl_OBJECTS = $(nodist_tftopl_OBJECTS)
tftopl_LDADD = $(LDADD)
@@ -1596,39 +1604,39 @@
am_upbibtex_OBJECTS =
nodist_upbibtex_OBJECTS = upbibtex-upbibtex.$(OBJEXT)
upbibtex_OBJECTS = $(am_upbibtex_OBJECTS) $(nodist_upbibtex_OBJECTS)
-am__DEPENDENCIES_14 = libukanji.a $(pproglib) $(am__DEPENDENCIES_1) \
+am__DEPENDENCIES_15 = libukanji.a $(pproglib) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_2) $(am__DEPENDENCIES_1)
am_updvitype_OBJECTS =
nodist_updvitype_OBJECTS = updvitype-updvitype.$(OBJEXT)
updvitype_OBJECTS = $(am_updvitype_OBJECTS) \
$(nodist_updvitype_OBJECTS)
-am__objects_59 = upmpost-pmp.$(OBJEXT)
-am__objects_60 = upmpost-pmpmath.$(OBJEXT)
-am__objects_61 = upmpost-pmpmathbinary.$(OBJEXT)
-am__objects_62 = upmpost-pmpmathdecimal.$(OBJEXT)
-am__objects_63 = upmpost-pmpmathdouble.$(OBJEXT)
-am__objects_64 = upmpost-pmpstrings.$(OBJEXT)
-am__objects_65 = upmpost-pmpxout.$(OBJEXT)
-am__objects_66 = upmpost-ppngout.$(OBJEXT)
-am__objects_67 = upmpost-ppsout.$(OBJEXT)
-am__objects_68 = upmpost-psvgout.$(OBJEXT)
-am__objects_69 = $(am__objects_59) $(am__objects_60) $(am__objects_61) \
- $(am__objects_62) $(am__objects_63) upmpost-pmpost.$(OBJEXT) \
- $(am__objects_64) $(am__objects_65) $(am__objects_66) \
- $(am__objects_67) $(am__objects_68) upmpost-ptfmin.$(OBJEXT)
-nodist_upmpost_OBJECTS = $(am__objects_69)
+am__objects_60 = upmpost-pmp.$(OBJEXT)
+am__objects_61 = upmpost-pmpmath.$(OBJEXT)
+am__objects_62 = upmpost-pmpmathbinary.$(OBJEXT)
+am__objects_63 = upmpost-pmpmathdecimal.$(OBJEXT)
+am__objects_64 = upmpost-pmpmathdouble.$(OBJEXT)
+am__objects_65 = upmpost-pmpstrings.$(OBJEXT)
+am__objects_66 = upmpost-pmpxout.$(OBJEXT)
+am__objects_67 = upmpost-ppngout.$(OBJEXT)
+am__objects_68 = upmpost-ppsout.$(OBJEXT)
+am__objects_69 = upmpost-psvgout.$(OBJEXT)
+am__objects_70 = $(am__objects_60) $(am__objects_61) $(am__objects_62) \
+ $(am__objects_63) $(am__objects_64) upmpost-pmpost.$(OBJEXT) \
+ $(am__objects_65) $(am__objects_66) $(am__objects_67) \
+ $(am__objects_68) $(am__objects_69) upmpost-ptfmin.$(OBJEXT)
+nodist_upmpost_OBJECTS = $(am__objects_70)
upmpost_OBJECTS = $(nodist_upmpost_OBJECTS)
-am__DEPENDENCIES_15 = $(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
+am__DEPENDENCIES_16 = $(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) libmputil.a
-upmpost_DEPENDENCIES = $(am__DEPENDENCIES_15)
+upmpost_DEPENDENCIES = $(am__DEPENDENCIES_16)
am_uppltotf_OBJECTS =
nodist_uppltotf_OBJECTS = uppltotf-uppltotf.$(OBJEXT)
uppltotf_OBJECTS = $(am_uppltotf_OBJECTS) $(nodist_uppltotf_OBJECTS)
dist_uptex_OBJECTS = uptexdir/uptex-uptexextra.$(OBJEXT)
-am__objects_70 = uptex-uptexini.$(OBJEXT) uptex-uptex0.$(OBJEXT)
-nodist_uptex_OBJECTS = $(am__objects_70) uptex-uptex-pool.$(OBJEXT)
+am__objects_71 = uptex-uptexini.$(OBJEXT) uptex-uptex0.$(OBJEXT)
+nodist_uptex_OBJECTS = $(am__objects_71) uptex-uptex-pool.$(OBJEXT)
uptex_OBJECTS = $(dist_uptex_OBJECTS) $(nodist_uptex_OBJECTS)
am_uptftopl_OBJECTS =
nodist_uptftopl_OBJECTS = uptftopl-uptftopl.$(OBJEXT)
@@ -1666,20 +1674,20 @@
xetexdir/xetex_version.h synctexdir/synctex.c \
synctexdir/synctex.h synctexdir/synctex-common.h \
synctexdir/synctex-xetex.h
- at XETEX_SYNCTEX_TRUE@am__objects_71 = \
+ at XETEX_SYNCTEX_TRUE@am__objects_72 = \
@XETEX_SYNCTEX_TRUE@ synctexdir/xetex-synctex.$(OBJEXT)
dist_xetex_OBJECTS = xetexdir/xetex-xetexextra.$(OBJEXT) \
- $(am__objects_71)
-am__objects_72 = xetex-xetexini.$(OBJEXT) xetex-xetex0.$(OBJEXT)
-nodist_xetex_OBJECTS = $(am__objects_72) xetex-xetex-pool.$(OBJEXT)
+ $(am__objects_72)
+am__objects_73 = xetex-xetexini.$(OBJEXT) xetex-xetex0.$(OBJEXT)
+nodist_xetex_OBJECTS = $(am__objects_73) xetex-xetex-pool.$(OBJEXT)
xetex_OBJECTS = $(dist_xetex_OBJECTS) $(nodist_xetex_OBJECTS)
- at XETEX_MACOSX_FALSE@am__DEPENDENCIES_16 = $(am__DEPENDENCIES_1)
-am__DEPENDENCIES_17 = $(libxetex) $(am__DEPENDENCIES_1) \
+ at XETEX_MACOSX_FALSE@am__DEPENDENCIES_17 = $(am__DEPENDENCIES_1)
+am__DEPENDENCIES_18 = $(libxetex) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
$(am__DEPENDENCIES_1) $(am__DEPENDENCIES_1) \
- $(am__DEPENDENCIES_1) libmd5.a $(am__DEPENDENCIES_16)
-xetex_DEPENDENCIES = $(am__DEPENDENCIES_17) $(am__DEPENDENCIES_2) \
+ $(am__DEPENDENCIES_1) libmd5.a $(am__DEPENDENCIES_17)
+xetex_DEPENDENCIES = $(am__DEPENDENCIES_18) $(am__DEPENDENCIES_2) \
$(am__DEPENDENCIES_1)
xetex_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CXX $(AM_LIBTOOLFLAGS) \
$(LIBTOOLFLAGS) --mode=link $(CXXLD) $(xetex_CXXFLAGS) \
@@ -1774,11 +1782,13 @@
./$(DEPDIR)/pmpost-pmpxout.Po ./$(DEPDIR)/pmpost-ppngout.Po \
./$(DEPDIR)/pmpost-ppsout.Po ./$(DEPDIR)/pmpost-psvgout.Po \
./$(DEPDIR)/pmpost-ptfmin.Po ./$(DEPDIR)/pooltype.Po \
- ./$(DEPDIR)/tangle.Po ./$(DEPDIR)/tangleboot.Po \
- ./$(DEPDIR)/tex-tex-pool.Po ./$(DEPDIR)/tex-tex0.Po \
- ./$(DEPDIR)/tex-texextra.Po ./$(DEPDIR)/tex-texini.Po \
- ./$(DEPDIR)/tftopl.Po ./$(DEPDIR)/tie-tie.Po \
- ./$(DEPDIR)/twill.Po ./$(DEPDIR)/upbibtex-upbibtex.Po \
+ ./$(DEPDIR)/ptex-ptex-pool.Po ./$(DEPDIR)/ptex-ptex0.Po \
+ ./$(DEPDIR)/ptex-ptexini.Po ./$(DEPDIR)/tangle.Po \
+ ./$(DEPDIR)/tangleboot.Po ./$(DEPDIR)/tex-tex-pool.Po \
+ ./$(DEPDIR)/tex-tex0.Po ./$(DEPDIR)/tex-texextra.Po \
+ ./$(DEPDIR)/tex-texini.Po ./$(DEPDIR)/tftopl.Po \
+ ./$(DEPDIR)/tie-tie.Po ./$(DEPDIR)/twill.Po \
+ ./$(DEPDIR)/upbibtex-upbibtex.Po \
./$(DEPDIR)/updvitype-updvitype.Po ./$(DEPDIR)/upmpost-pmp.Po \
./$(DEPDIR)/upmpost-pmpmath.Po \
./$(DEPDIR)/upmpost-pmpmathbinary.Po \
@@ -2339,6 +2349,7 @@
pdftexdir/regex/$(DEPDIR)/libpdftex_a-regexec.Po \
ptexdir/$(DEPDIR)/libkanji_a-kanji.Po \
ptexdir/$(DEPDIR)/libkanji_a-kanji_dump.Po \
+ ptexdir/$(DEPDIR)/ptex-ptexextra.Po \
synctexdir/$(DEPDIR)/eptex-synctex.Po \
synctexdir/$(DEPDIR)/etex-synctex.Po \
synctexdir/$(DEPDIR)/euptex-synctex.Po \
@@ -2488,22 +2499,22 @@
$(nodist_EXTRA_pdftosrc_SOURCES) $(nodist_pktogf_SOURCES) \
$(nodist_pktype_SOURCES) $(nodist_pltotf_SOURCES) \
$(nodist_pmpost_SOURCES) $(nodist_pooltype_SOURCES) \
- $(synctex_SOURCES) $(nodist_tangle_SOURCES) \
- $(nodist_tangleboot_SOURCES) $(dist_tex_SOURCES) \
- $(nodist_tex_SOURCES) $(nodist_tftopl_SOURCES) \
- $(nodist_tie_SOURCES) $(ttf2afm_SOURCES) \
- $(EXTRA_ttf2afm_SOURCES) $(nodist_twill_SOURCES) \
- $(upbibtex_SOURCES) $(nodist_upbibtex_SOURCES) \
- $(updvitype_SOURCES) $(nodist_updvitype_SOURCES) \
- $(nodist_upmpost_SOURCES) $(uppltotf_SOURCES) \
- $(nodist_uppltotf_SOURCES) $(dist_uptex_SOURCES) \
- $(nodist_uptex_SOURCES) $(uptftopl_SOURCES) \
- $(nodist_uptftopl_SOURCES) $(nodist_vftovp_SOURCES) \
- $(nodist_vptovf_SOURCES) $(nodist_weave_SOURCES) \
- $(nodist_wofm2opl_SOURCES) $(nodist_wopl2ofm_SOURCES) \
- $(nodist_wovf2ovp_SOURCES) $(nodist_wovp2ovf_SOURCES) \
- $(dist_xetex_SOURCES) $(nodist_xetex_SOURCES) \
- $(nodist_EXTRA_xetex_SOURCES)
+ $(dist_ptex_SOURCES) $(nodist_ptex_SOURCES) $(synctex_SOURCES) \
+ $(nodist_tangle_SOURCES) $(nodist_tangleboot_SOURCES) \
+ $(dist_tex_SOURCES) $(nodist_tex_SOURCES) \
+ $(nodist_tftopl_SOURCES) $(nodist_tie_SOURCES) \
+ $(ttf2afm_SOURCES) $(EXTRA_ttf2afm_SOURCES) \
+ $(nodist_twill_SOURCES) $(upbibtex_SOURCES) \
+ $(nodist_upbibtex_SOURCES) $(updvitype_SOURCES) \
+ $(nodist_updvitype_SOURCES) $(nodist_upmpost_SOURCES) \
+ $(uppltotf_SOURCES) $(nodist_uppltotf_SOURCES) \
+ $(dist_uptex_SOURCES) $(nodist_uptex_SOURCES) \
+ $(uptftopl_SOURCES) $(nodist_uptftopl_SOURCES) \
+ $(nodist_vftovp_SOURCES) $(nodist_vptovf_SOURCES) \
+ $(nodist_weave_SOURCES) $(nodist_wofm2opl_SOURCES) \
+ $(nodist_wopl2ofm_SOURCES) $(nodist_wovf2ovp_SOURCES) \
+ $(nodist_wovp2ovf_SOURCES) $(dist_xetex_SOURCES) \
+ $(nodist_xetex_SOURCES) $(nodist_EXTRA_xetex_SOURCES)
DIST_SOURCES = $(libff_a_SOURCES) $(libkanji_a_SOURCES) \
$(libluaharfbuzz_a_SOURCES) $(libluajitharfbuzz_a_SOURCES) \
$(dist_libluajittex_a_SOURCES) $(dist_libluatex_a_SOURCES) \
@@ -2520,11 +2531,11 @@
$(dist_mf_SOURCES) $(dist_mf_nowin_SOURCES) \
$(dist_mflua_SOURCES) $(dist_mfluajit_SOURCES) \
$(am__dist_pdftex_SOURCES_DIST) $(pdftosrc_SOURCES) \
- $(synctex_SOURCES) $(am__dist_tex_SOURCES_DIST) \
- $(ttf2afm_SOURCES) $(EXTRA_ttf2afm_SOURCES) \
- $(upbibtex_SOURCES) $(updvitype_SOURCES) $(uppltotf_SOURCES) \
- $(dist_uptex_SOURCES) $(uptftopl_SOURCES) \
- $(am__dist_xetex_SOURCES_DIST)
+ $(dist_ptex_SOURCES) $(synctex_SOURCES) \
+ $(am__dist_tex_SOURCES_DIST) $(ttf2afm_SOURCES) \
+ $(EXTRA_ttf2afm_SOURCES) $(upbibtex_SOURCES) \
+ $(updvitype_SOURCES) $(uppltotf_SOURCES) $(dist_uptex_SOURCES) \
+ $(uptftopl_SOURCES) $(am__dist_xetex_SOURCES_DIST)
RECURSIVE_TARGETS = all-recursive check-recursive cscopelist-recursive \
ctags-recursive dvi-recursive html-recursive info-recursive \
install-data-recursive install-dvi-recursive \
@@ -2730,14 +2741,15 @@
bases=`echo $$bases`
AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
-am__EXEEXT_41 = bibtex.test dvicopy.test dvitype.test gftodvi.test \
+am__EXEEXT_43 = bibtex.test dvicopy.test dvitype.test gftodvi.test \
gftopk.test gftype.test mft.test patgen.test pktogf.test \
pktype.test pltotf.test pooltype.test tftopl.test vftovp.test \
vptovf.test weave.test twill.test
-am__EXEEXT_42 = $(am__EXEEXT_41) tests/bibtex-openout-test.pl \
+am__EXEEXT_44 = $(am__EXEEXT_43) tests/bibtex-openout-test.pl \
tests/bibtex-longline-test.pl tests/bibtex-mem.test \
tests/bibtex-bigauth.test tests/bibtex-auxinclude.test
- at WEB_TRUE@am__EXEEXT_43 = $(am__EXEEXT_42)
+ at WEB_TRUE@am__EXEEXT_45 = $(am__EXEEXT_44)
+am__EXEEXT_46 =
TEST_SUITE_LOG = test-suite.log
am__test_logs1 = $(TESTS:=.log)
am__test_logs2 = $(am__test_logs1:@EXEEXT at .log=.log)
@@ -2964,7 +2976,7 @@
NMEDIT = @NMEDIT@
OBJCXX = @OBJCXX@
OBJCXXDEPMODE = @OBJCXXDEPMODE@
-OBJCXXFLAGS = @OBJCXXFLAGS@ $(am__append_105)
+OBJCXXFLAGS = @OBJCXXFLAGS@ $(am__append_114)
OBJDUMP = @OBJDUMP@
OBJEXT = @OBJEXT@
OTANGLE = @OTANGLE@
@@ -3111,8 +3123,8 @@
libluaharfbuzz.a libluajitharfbuzz.a libxetex.a libsynctex.a \
libmd5.a
EXTRA_LTLIBRARIES = libsynctex.la
-lib_LIBRARIES = $(am__append_117)
-lib_LTLIBRARIES = $(am__append_116)
+lib_LIBRARIES = $(am__append_126)
+lib_LTLIBRARIES = $(am__append_125)
dist_man_MANS = synctexdir/man1/synctex.1 synctexdir/man5/synctex.5
nodist_man_MANS =
TEST_EXTENSIONS = .pl .test
@@ -3199,12 +3211,13 @@
etexdir/etrip/trip2.in $(ptex_web_srcs) $(ptex_ch_srcs) \
ptexdir/ptex.defines ptexdir/COPYRIGHT ptexdir/COPYRIGHT.jis \
ptexdir/ChangeLog ptexdir/Changes.txt ptexdir/INSTALL.txt \
- ptexdir/README.txt ptexdir/tests/nissya.bst \
- ptexdir/tests/sample.bib tests/testfield.bst tests/enc-asc.bib \
- tests/enc-jis.bib tests/enc-sjis.bib tests/enc-euc.bib \
- tests/enc-utf8.bib tests/enc-utf8a.bib tests/enc-utf8b.bib \
- tests/enc-amb0.bib tests/enc-amb1.bib tests/enc-amb2.bib \
- tests/enc.aux tests/enc-e.aux tests/enc-s.aux tests/enc-u.aux \
+ ptexdir/README.txt $(ptex_tests) $(pweb_tests) \
+ ptexdir/tests/nissya.bst ptexdir/tests/sample.bib \
+ tests/testfield.bst tests/enc-asc.bib tests/enc-jis.bib \
+ tests/enc-sjis.bib tests/enc-euc.bib tests/enc-utf8.bib \
+ tests/enc-utf8a.bib tests/enc-utf8b.bib tests/enc-amb0.bib \
+ tests/enc-amb1.bib tests/enc-amb2.bib tests/enc.aux \
+ tests/enc-e.aux tests/enc-s.aux tests/enc-u.aux \
tests/enc-p.bbl tests/enc-ep.bbl tests/enc-sp.bbl \
tests/enc-up.bbl tests/memdata1.bst tests/memdata2.bst \
tests/memdata3.bst ptexdir/tests/ptex3.tex \
@@ -3551,81 +3564,86 @@
$(nodist_etex_SOURCES) etex.web etex.ch etex-web2c etex.p \
etex.pool etex-tangle etrip.diffs ewprob.log ewprob.tex \
$(nodist_ptex_SOURCES) ptex.web ptex.ch ptex-web2c ptex.p \
- ptex.pool ptex-tangle ptests/nissya_bib.* ptests/xexampl.aux \
- ptests/xexampl.bbl ptests/xexampl.blg ptests/xenc*.* \
- ptests/fn*.* ptests/memtest.bib ptests/memtest?.* \
- ptests/xstory.dvityp ptests/xpagenum.typ ptests/xptex[34]*.typ \
- ptests/xcmr10.tfm ptests/xcmr10.pl ptests/xsample*.typ \
- ptests/x*min10.* ptests/xchcode*.* ptests/xskipjfmp.* \
- ptrip.diffs $(nodist_eptex_SOURCES) eptex.web eptex.ch \
- eptex-web2c eptex.p eptex.pool eptex-tangle eptrip.diffs \
- pdfprimitive-eptex.* $(nodist_uptex_SOURCES) uptex.web \
- uptex.ch uptex-web2c uptex.p uptex.pool uptex-tangle \
- $(upweb_programs:=.c) $(upweb_programs:=.h) \
- $(upweb_programs:=.p) $(upweb_programs:=-web2c) \
- $(upweb_programs:=.web) uptests/nissya_bib.* \
- uptests/xexampl.aux uptests/xexampl.bbl uptests/xexampl.blg \
- uptests/xenc*.* uptests/fn*.* uptests/memtest.bib \
- uptests/memtest?.* uptests/xstory.dvityp uptests/xpagenum.typ \
- uptests/x*ptex[34]*.typ uptests/xcmr10.tfm uptests/xcmr10.pl \
- uptests/xsample*.typ uptests/x*min10.* uptests/xchcode*.* \
- uptests/xtestnewu.* uptests/xuparse.* uptests/yuparse.* \
- uptests/ygkhuge*.* uptests/xskipjfmp.* uptrip.diffs \
- $(nodist_euptex_SOURCES) euptex.web euptex.ch euptex-web2c \
- euptex.p euptex.pool euptex-tangle euptrip.diffs \
- pdfprimitive-euptex.* $(nodist_hitex_SOURCES) \
- $(nodist_hishrink_SOURCES) $(nodist_histretch_SOURCES) \
- hiformat-tangle hitex-tangle hello.log rule.log \
- $(nodist_pdftex_SOURCES) pdftex-final.ch pdftex-web2c pdftex.p \
- pdftex.pool pdftex-tangle pwprob.log pwprob.tex pdfimage.fmt \
- pdfimage.log pdfimage.pdf expanded.log cnfline.log \
- partoken-ok.log partoken-xfail.log pdftests/fn*.* postV3.afm \
- postV7.afm test-13.pdf test-13.xref test-15.pdf test-15.xref \
- $(nodist_libluatex_sources) luaimage.* luajitimage.* \
- $(nodist_xetex_SOURCES) xetex.web xetex-final.ch xetex-web2c \
- xetex.p xetex.pool xetex-tangle bug73.fmt bug73.log bug73.out \
- bug73.tex filedump.log filedump.out filedump.tex xetests/fn*.* \
- $(omegaware_programs:=.c) $(omegaware_programs:=.h) \
- $(omegaware_programs:=.p) $(omegaware_programs:=-web2c) \
- ofm2opl.web opl2ofm.web ovf2ovp.web ovp2ovf.web \
- omegaware/bad*.* omegaware/tests/charwdr.* \
- omegaware/tests/charwdv.* omegaware/tests/xcheck* \
- omegaware/tests/xlevel1.* omegaware/tests/xlig*.* ofont*vf \
- omegaware/tests/xpagenum.* omegaware/tests/xofont* \
- omegaware/tests/Cherokee.tfm omegaware/tests/OCherokee.ofm \
- omegaware/tests/OCherokee.opl omegaware/tests/OCherokee.ovf \
- omegaware/tests/xCherokee.* omegaware/tests/xOCherokee.* \
- ocftest.* omegaware/tests/xinbmp* omegaware/tests/xoverbmp* \
- omegaware/tests/xrealnum.* omegaware/tests/xrepeated.* \
- omegaware/tests/sample*.ofm omegaware/tests/sample*.ovf \
- omegaware/tests/sample1-h.opl omegaware/tests/xsample*.out \
- omegaware/tests/shortend.* omegaware/tests/specialhex.ofm \
- omegaware/tests/specialhex.opl omegaware/tests/specialhex.ovf \
- omegaware/tests/xspecialhex.* omegaware/tests/yrepeat* \
- omegaware/tests/*yarabic* $(nodist_aleph_SOURCES) aleph.web \
- aleph.ch aleph-web2c aleph.p aleph.pool aleph-tangle
+ ptex.pool ptex-tangle $(pweb_programs:=.c) \
+ $(pweb_programs:=.h) $(pweb_programs:=.p) \
+ $(pweb_programs:=-web2c) $(pweb_programs:=.web) \
+ ptests/nissya_bib.* ptests/xexampl.aux ptests/xexampl.bbl \
+ ptests/xexampl.blg ptests/xenc*.* ptests/fn*.* \
+ ptests/memtest.bib ptests/memtest?.* ptests/xstory.dvityp \
+ ptests/xpagenum.typ ptests/xptex[34]*.typ ptests/xcmr10.tfm \
+ ptests/xcmr10.pl ptests/xsample*.typ ptests/x*min10.* \
+ ptests/xchcode*.* ptests/xskipjfmp.* ptrip.diffs \
+ $(nodist_eptex_SOURCES) eptex.web eptex.ch eptex-web2c eptex.p \
+ eptex.pool eptex-tangle eptrip.diffs pdfprimitive-eptex.* \
+ $(nodist_uptex_SOURCES) uptex.web uptex.ch uptex-web2c uptex.p \
+ uptex.pool uptex-tangle $(upweb_programs:=.c) \
+ $(upweb_programs:=.h) $(upweb_programs:=.p) \
+ $(upweb_programs:=-web2c) $(upweb_programs:=.web) \
+ uptests/nissya_bib.* uptests/xexampl.aux uptests/xexampl.bbl \
+ uptests/xexampl.blg uptests/xenc*.* uptests/fn*.* \
+ uptests/memtest.bib uptests/memtest?.* uptests/xstory.dvityp \
+ uptests/xpagenum.typ uptests/x*ptex[34]*.typ \
+ uptests/xcmr10.tfm uptests/xcmr10.pl uptests/xsample*.typ \
+ uptests/x*min10.* uptests/xchcode*.* uptests/xtestnewu.* \
+ uptests/xuparse.* uptests/yuparse.* uptests/ygkhuge*.* \
+ uptests/xskipjfmp.* uptrip.diffs $(nodist_euptex_SOURCES) \
+ euptex.web euptex.ch euptex-web2c euptex.p euptex.pool \
+ euptex-tangle euptrip.diffs pdfprimitive-euptex.* \
+ $(nodist_hitex_SOURCES) $(nodist_hishrink_SOURCES) \
+ $(nodist_histretch_SOURCES) hiformat-tangle hitex-tangle \
+ hello.log rule.log $(nodist_pdftex_SOURCES) pdftex-final.ch \
+ pdftex-web2c pdftex.p pdftex.pool pdftex-tangle pwprob.log \
+ pwprob.tex pdfimage.fmt pdfimage.log pdfimage.pdf expanded.log \
+ cnfline.log partoken-ok.log partoken-xfail.log pdftests/fn*.* \
+ postV3.afm postV7.afm test-13.pdf test-13.xref test-15.pdf \
+ test-15.xref $(nodist_libluatex_sources) luaimage.* \
+ luajitimage.* $(nodist_xetex_SOURCES) xetex.web xetex-final.ch \
+ xetex-web2c xetex.p xetex.pool xetex-tangle bug73.fmt \
+ bug73.log bug73.out bug73.tex filedump.log filedump.out \
+ filedump.tex xetests/fn*.* $(omegaware_programs:=.c) \
+ $(omegaware_programs:=.h) $(omegaware_programs:=.p) \
+ $(omegaware_programs:=-web2c) ofm2opl.web opl2ofm.web \
+ ovf2ovp.web ovp2ovf.web omegaware/bad*.* \
+ omegaware/tests/charwdr.* omegaware/tests/charwdv.* \
+ omegaware/tests/xcheck* omegaware/tests/xlevel1.* \
+ omegaware/tests/xlig*.* ofont*vf omegaware/tests/xpagenum.* \
+ omegaware/tests/xofont* omegaware/tests/Cherokee.tfm \
+ omegaware/tests/OCherokee.ofm omegaware/tests/OCherokee.opl \
+ omegaware/tests/OCherokee.ovf omegaware/tests/xCherokee.* \
+ omegaware/tests/xOCherokee.* ocftest.* omegaware/tests/xinbmp* \
+ omegaware/tests/xoverbmp* omegaware/tests/xrealnum.* \
+ omegaware/tests/xrepeated.* omegaware/tests/sample*.ofm \
+ omegaware/tests/sample*.ovf omegaware/tests/sample1-h.opl \
+ omegaware/tests/xsample*.out omegaware/tests/shortend.* \
+ omegaware/tests/specialhex.ofm omegaware/tests/specialhex.opl \
+ omegaware/tests/specialhex.ovf omegaware/tests/xspecialhex.* \
+ omegaware/tests/yrepeat* omegaware/tests/*yarabic* \
+ $(nodist_aleph_SOURCES) aleph.web aleph.ch aleph-web2c aleph.p \
+ aleph.pool aleph-tangle
CLEANFILES = $(EXTRA_PROGRAMS) $(EXTRA_LIBRARIES) $(EXTRA_LTLIBRARIES)
TRIPTRAP_CLEAN = $(am__append_8) $(am__append_18) $(am__append_27) \
$(am__append_36) $(am__append_44) $(am__append_60) \
- $(am__append_65) $(am__append_72)
+ $(am__append_64) $(am__append_70) $(am__append_75) \
+ $(am__append_81)
TRIPTRAP = $(am__append_7) $(am__append_17) $(am__append_26) \
$(am__append_35) $(am__append_43) $(am__append_59) \
- $(am__append_64) $(am__append_71)
+ $(am__append_63) $(am__append_69) $(am__append_74) \
+ $(am__append_80)
bin_links = $(am__append_5) $(am__append_14) $(am__append_15) \
$(am__append_24) $(am__append_33) $(am__append_41) \
- $(am__append_49) $(am__append_54) $(am__append_62) \
+ $(am__append_49) $(am__append_54) $(am__append_67) \
upbibtex$(EXEEXT):pbibtex updvitype$(EXEEXT):pdvitype \
uppltotf$(EXEEXT):ppltotf uptftopl$(EXEEXT):ptftopl \
- $(am__append_69) $(am__append_83) $(am__append_88) \
- $(am__append_93) $(am__append_98)
+ $(am__append_78) $(am__append_92) $(am__append_97) \
+ $(am__append_102) $(am__append_107)
install_exe_links = $(am__append_12) $(am__append_22) $(am__append_31) \
$(am__append_39) $(am__append_47) $(am__append_52) \
- $(am__append_81) $(am__append_86) $(am__append_91) \
- $(am__append_96)
+ $(am__append_90) $(am__append_95) $(am__append_100) \
+ $(am__append_105)
uninstall_exe_links = $(am__append_13) $(am__append_23) \
$(am__append_32) $(am__append_40) $(am__append_48) \
- $(am__append_53) $(am__append_82) $(am__append_87) \
- $(am__append_92) $(am__append_97)
+ $(am__append_53) $(am__append_91) $(am__append_96) \
+ $(am__append_101) $(am__append_106)
NEVER_DIST = `find . $(NEVER_NAMES)` cwebdir/cweave.log \
cwebdir/cweave.trs cwebdir/ctwill.log cwebdir/ctwill.trs \
cwebdir/refsort.log cwebdir/refsort.trs cwebdir/twinx.log \
@@ -3801,18 +3819,18 @@
initex_CPPFLAGS = -DEXEPROG=\"tex.exe\"
nodist_initex_SOURCES = callexe.c
initex_LDADD =
-tex_CPPFLAGS = $(AM_CPPFLAGS) $(am__append_121)
+tex_CPPFLAGS = $(AM_CPPFLAGS) $(am__append_130)
# With --enable-ipc, TeX may need to link with -lsocket.
-tex_LDADD = $(LDADD) $(ipc_socketlibs) $(am__append_122)
+tex_LDADD = $(LDADD) $(ipc_socketlibs) $(am__append_131)
# TeX C sources
tex_c_h = texini.c tex0.c texcoerce.h texd.h
nodist_tex_SOURCES = $(tex_c_h) tex-pool.c
-dist_tex_SOURCES = texextra.c $(am__append_124)
+dist_tex_SOURCES = texextra.c $(am__append_133)
# We must create texd.h before building the tex_OBJECTS.
-tex_prereq = texd.h $(am__append_123)
+tex_prereq = texd.h $(am__append_132)
tex_ch_srcs = \
tex.web \
tex.ch \
@@ -4308,10 +4326,10 @@
mplibdir/pngout.w mplibdir/mpmath.w mplibdir/mpmathbinary.w \
mplibdir/mpmathdecimal.w mplibdir/mpmathdouble.w \
mplibdir/mpstrings.w mplibdir/tfmin.w
-etex_CPPFLAGS = $(AM_CPPFLAGS) $(ZLIB_INCLUDES) $(am__append_125)
+etex_CPPFLAGS = $(AM_CPPFLAGS) $(ZLIB_INCLUDES) $(am__append_134)
# With --enable-ipc, e-TeX may need to link with -lsocket.
-etex_LDADD = $(LDADD) $(ZLIB_LIBS) $(ipc_socketlibs) $(am__append_126)
+etex_LDADD = $(LDADD) $(ZLIB_LIBS) $(ipc_socketlibs) $(am__append_135)
etex_DEPENDENCIES = $(ZLIB_DEPEND)
# e-TeX C sources
@@ -4318,11 +4336,11 @@
etex_c_h = etexini.c etex0.c etexcoerce.h etexd.h
nodist_etex_SOURCES = $(etex_c_h) etex-pool.c
dist_etex_SOURCES = etexdir/etexextra.c etexdir/etexextra.h \
- etexdir/etex_version.h $(am__append_128)
+ etexdir/etex_version.h $(am__append_137)
# We must create etexd.h and etexdir/etex_version.h before building the
# etex_OBJECTS.
-etex_prereq = etexd.h etexdir/etex_version.h $(am__append_127)
+etex_prereq = etexd.h etexdir/etex_version.h $(am__append_136)
etex_web_srcs = \
tex.web \
etexdir/etex.ch
@@ -4346,11 +4364,25 @@
ptex_cppflags = $(PTEXENC_INCLUDES) $(AM_CPPFLAGS) $(ZLIB_INCLUDES)
ptex_ldadd = libkanji.a $(pproglib) $(PTEXENC_LIBS) $(LDADD) $(ZLIB_LIBS)
ptex_dependencies = libkanji.a $(pproglib) $(PTEXENC_DEPEND) $(ZLIB_DEPEND) $(default_dependencies)
+p_tangle = $(tangle_silent)WEBINPUTS=.:$(srcdir)/ptexdir:$(srcdir) $(buildenv) $(TANGLE)
pproglib = lib/libp.a
libkanji_a_SOURCES = ptexdir/kanji.c ptexdir/kanji.h ptexdir/kanji_dump.c
libkanji_a_CPPFLAGS = $(ptex_cppflags)
+#if PWEB
+#bin_PROGRAMS += $(pweb_programs)
+#endif PWEB
+#EXTRA_PROGRAMS += ptex $(pweb_programs)
ptex_CPPFLAGS = $(ptex_cppflags)
+# With --enable-ipc, pTeX may need to link with -lsocket.
+ptex_LDADD = $(ptex_ldadd) $(ipc_socketlibs)
+ptex_DEPENDENCIES = $(ptex_dependencies)
+
+# pTeX C sources
+ptex_c_h = ptexini.c ptex0.c ptexcoerce.h ptexd.h
+nodist_ptex_SOURCES = $(ptex_c_h) ptex-pool.c
+dist_ptex_SOURCES = ptexdir/ptexextra.c ptexdir/ptexextra.h ptexdir/ptex_version.h
+
# We must create ptexd.h and ptexdir/ptex_version.h before building the ptex_OBJECTS.
ptex_prereq = ptexd.h ptexdir/ptex_version.h
ptex_web_srcs = \
@@ -4365,12 +4397,16 @@
$(ptex_ch_synctex) \
tex-binpool.ch
+
+# pTeX Tests
+#
+ptex_tests = ptexdir/ptriptest.test ptexdir/pver.test ptexdir/wcfname.test
eptex_CPPFLAGS = $(PTEXENC_INCLUDES) $(AM_CPPFLAGS) -I$(srcdir)/libmd5 \
- $(ZLIB_INCLUDES) $(am__append_129)
+ $(ZLIB_INCLUDES) $(am__append_138)
# With --enable-ipc, e-pTeX may need to link with -lsocket.
eptex_LDADD = libkanji.a $(pproglib) $(PTEXENC_LIBS) $(LDADD) \
- $(ipc_socketlibs) libmd5.a $(ZLIB_LIBS) $(am__append_130)
+ $(ipc_socketlibs) libmd5.a $(ZLIB_LIBS) $(am__append_139)
eptex_DEPENDENCIES = libkanji.a $(pproglib) $(PTEXENC_DEPEND) $(default_dependencies) libmd5.a $(ZLIB_DEPEND)
# e-pTeX C sources
@@ -4377,11 +4413,11 @@
eptex_c_h = eptexini.c eptex0.c eptexcoerce.h eptexd.h
nodist_eptex_SOURCES = $(eptex_c_h) eptex-pool.c
dist_eptex_SOURCES = eptexdir/eptexextra.c eptexdir/eptexextra.h \
- eptexdir/eptex_version.h $(am__append_132)
+ eptexdir/eptex_version.h $(am__append_141)
# We must create eptexd.h and eptexdir/eptex_version.h before building the eptex_OBJECTS.
eptex_prereq = eptexd.h etexdir/etex_version.h ptexdir/ptex_version.h \
- eptexdir/eptex_version.h $(am__append_131)
+ eptexdir/eptex_version.h $(am__append_140)
eptex_web_srcs = \
tex.web \
etexdir/etex.ch \
@@ -4463,6 +4499,9 @@
uptftopl_CPPFLAGS = $(uptex_cppflags)
uptftopl_LDADD = $(uptex_ldadd)
uptftopl_DEPENDENCIES = $(uptex_dependencies)
+
+# upTeX Tests
+uptex_tests = uptexdir/uptriptest.test uptexdir/ptriptest.test uptexdir/upver.test uptexdir/upkcat.test uptexdir/wcfname.test
# uppPLtoTF/upTFtoPL
upweb_tests = uptexdir/upbibtex.test uptexdir/updvitype.test \
uptexdir/uppltotf.test uptexdir/uptftopl.test \
@@ -4472,11 +4511,11 @@
uptexdir/yokotate.test uptexdir/skipjfmp.test \
uptexdir/newjfm.test uptexdir/uparse.test uptexdir/gkhuge.test
euptex_CPPFLAGS = $(PTEXENC_INCLUDES) $(AM_CPPFLAGS) \
- -I$(srcdir)/libmd5 $(ZLIB_INCLUDES) $(am__append_133)
+ -I$(srcdir)/libmd5 $(ZLIB_INCLUDES) $(am__append_142)
# With --enable-ipc, e-upTeX may need to link with -lsocket.
euptex_LDADD = libukanji.a $(pproglib) $(PTEXENC_LIBS) $(LDADD) \
- $(ipc_socketlibs) libmd5.a $(ZLIB_LIBS) $(am__append_134)
+ $(ipc_socketlibs) libmd5.a $(ZLIB_LIBS) $(am__append_143)
euptex_DEPENDENCIES = libukanji.a $(pproglib) $(PTEXENC_DEPEND) $(default_dependencies) libmd5.a $(ZLIB_DEPEND)
# e-upTeX C sources
@@ -4483,12 +4522,12 @@
euptex_c_h = euptexini.c euptex0.c euptexcoerce.h euptexd.h
nodist_euptex_SOURCES = $(euptex_c_h) euptex-pool.c
dist_euptex_SOURCES = euptexdir/euptexextra.c euptexdir/euptexextra.h \
- $(am__append_136)
+ $(am__append_145)
# We must create euptexd.h and [eu]ptexdir/[eu]ptex_version.h before building the euptex_OBJECTS.
euptex_prereq = euptexd.h etexdir/etex_version.h \
ptexdir/ptex_version.h eptexdir/eptex_version.h \
- uptexdir/uptex_version.h $(am__append_135)
+ uptexdir/uptex_version.h $(am__append_144)
euptex_web_srcs = \
tex.web \
etexdir/etex.ch \
@@ -4600,7 +4639,7 @@
pdftexdir/writejbig2.c pdftexdir/writejpg.c \
pdftexdir/writepng.c pdftexdir/writet1.c pdftexdir/writet3.c \
pdftexdir/writettf.c pdftexdir/writettf.h pdftexdir/writezip.c \
- $(am__append_76)
+ $(am__append_85)
@MINGW32_TRUE at REGEX_INCLUDES = -I$(srcdir)/pdftexdir/regex
EXTRA_libpdftex_a_SOURCES = pdftexdir/macnames.c \
pdftexdir/regex/regcomp.c pdftexdir/regex/regex_internal.c \
@@ -4616,7 +4655,7 @@
# Force Automake to use CXXLD for linking
nodist_EXTRA_pdftex_SOURCES = dummy.cxx
pdf_tangle = WEBINPUTS=.:$(srcdir)/pdftexdir AM_V_P=$(AM_V_P) $(SHELL) ./tangle-sh $@ $(TANGLE)
-pdftex_CPPFLAGS = $(pdftex_cppflags) $(am__append_137)
+pdftex_CPPFLAGS = $(pdftex_cppflags) $(am__append_146)
pdftex_CXXFLAGS = $(WARNING_CXXFLAGS)
# With --enable-ipc, pdfTeX may need to link with -lsocket.
@@ -4629,7 +4668,7 @@
nodist_pdftex_SOURCES = $(pdftex_c_h) pdftex-pool.c
dist_pdftex_SOURCES = pdftexdir/pdftexextra.c pdftexdir/pdftexextra.h \
pdftexdir/pdftex_version.h pdftexdir/etex_version.h \
- $(am__append_138)
+ $(am__append_147)
pdftex_ch_srcs = \
pdftexdir/pdftex.web \
pdftexdir/tex.ch0 \
@@ -5306,18 +5345,18 @@
xetex_cppflags = $(AM_CPPFLAGS) -I$(srcdir)/xetexdir $(ICU_INCLUDES) \
$(FREETYPE2_INCLUDES) $(TECKIT_INCLUDES) $(HARFBUZZ_INCLUDES) \
$(GRAPHITE2_INCLUDES) $(LIBPNG_INCLUDES) $(ZLIB_INCLUDES) \
- $(PPLIB_INCLUDES) -I$(srcdir)/libmd5 $(am__append_104) \
- $(am__append_106)
+ $(PPLIB_INCLUDES) -I$(srcdir)/libmd5 $(am__append_113) \
+ $(am__append_115)
xetex_ldadd = $(libxetex) $(HARFBUZZ_LIBS) $(GRAPHITE2_LIBS) \
$(ICU_LIBS) $(ICU_LIBS_EXTRA) $(TECKIT_LIBS) $(LIBPNG_LIBS) \
$(FREETYPE2_LIBS) $(PPLIB_LIBS) $(ZLIB_LIBS) libmd5.a \
- $(am__append_107)
+ $(am__append_116)
xetex_dependencies = $(proglib) $(KPATHSEA_DEPEND) $(ICU_DEPEND) \
$(TECKIT_DEPEND) $(HARFBUZZ_DEPEND) $(GRAPHITE2_DEPEND) \
$(LIBPNG_DEPEND) $(FREETYPE2_DEPEND) $(ZLIB_DEPEND) \
$(PPLIB_DEPEND) libmd5.a
@XETEX_MACOSX_TRUE at xetex_LDFLAGS = -framework ApplicationServices -framework Cocoa
-xetex_CPPFLAGS = $(xetex_cppflags) $(am__append_139)
+xetex_CPPFLAGS = $(xetex_cppflags) $(am__append_148)
xetex_CFLAGS = $(WARNING_CFLAGS)
xetex_CXXFLAGS = # $(WARNING_CXXFLAGS)
xetex_LDADD = $(xetex_ldadd) $(LDADD) $(ipc_socketlibs)
@@ -5326,7 +5365,7 @@
nodist_xetex_SOURCES = $(xetex_c_h) xetex-pool.c
dist_xetex_SOURCES = xetexdir/xetexextra.c xetexdir/xetexextra.h \
xetexdir/etex_version.h xetexdir/xetex_version.h \
- $(am__append_140)
+ $(am__append_149)
xetex_ch_srcs = \
xetexdir/xetex.web \
xetexdir/tex.ch0 \
@@ -5358,7 +5397,7 @@
xetexdir/image/jpegimage.h xetexdir/image/mfileio.c \
xetexdir/image/mfileio.h xetexdir/image/numbers.c \
xetexdir/image/numbers.h xetexdir/image/pngimage.c \
- xetexdir/image/pngimage.h $(am__append_108) $(am__append_109)
+ xetexdir/image/pngimage.h $(am__append_117) $(am__append_118)
# We must create xetexd.h etc. before building the libxetex_a_OBJECTS.
libxetex_prereq = xetexd.h $(xetex_dependencies)
@@ -5438,7 +5477,8 @@
alephdir/eonewdir.ch \
alephdir/eover.ch \
alephdir/eopage.ch \
- alephdir/eochar.ch
+ alephdir/eochar.ch \
+ alephdir/latespecial.ch
# Generate aleph.ch
@@ -5463,13 +5503,13 @@
synctex_SOURCES = \
synctexdir/synctex_main.c
-synctex_CPPFLAGS = -I$(srcdir)/synctexdir $(am__append_118)
-synctex_LDADD = $(libsynctex) $(ZLIB_LIBS) $(am__append_119)
+synctex_CPPFLAGS = -I$(srcdir)/synctexdir $(am__append_127)
+synctex_LDADD = $(libsynctex) $(ZLIB_LIBS) $(am__append_128)
libsynctex = $(LTLIBSYNCTEX) $(LIBSYNCTEX)
libsynctex_la_CPPFLAGS = -I$(srcdir)/synctexdir $(ZLIB_INCLUDES) -DSYNCTEX_USE_LOCAL_HEADER
libsynctex_a_CPPFLAGS = $(libsynctex_la_CPPFLAGS)
libsynctex_la_LDFLAGS = -rpath @libdir@ -bindir @bindir@ -no-undefined -version-info $(SYNCTEX_LT_VERSINFO)
-libsynctex_la_LIBADD = $(ZLIB_LIBS) $(am__append_120)
+libsynctex_la_LIBADD = $(ZLIB_LIBS) $(am__append_129)
libsynctex_la_SOURCES = \
synctexdir/synctex_parser.c \
synctexdir/synctex_parser_local.h \
@@ -8197,6 +8237,12 @@
pooltype$(EXEEXT): $(pooltype_OBJECTS) $(pooltype_DEPENDENCIES) $(EXTRA_pooltype_DEPENDENCIES)
@rm -f pooltype$(EXEEXT)
$(AM_V_CCLD)$(LINK) $(pooltype_OBJECTS) $(pooltype_LDADD) $(LIBS)
+ptexdir/ptex-ptexextra.$(OBJEXT): ptexdir/$(am__dirstamp) \
+ ptexdir/$(DEPDIR)/$(am__dirstamp)
+
+ptex$(EXEEXT): $(ptex_OBJECTS) $(ptex_DEPENDENCIES) $(EXTRA_ptex_DEPENDENCIES)
+ @rm -f ptex$(EXEEXT)
+ $(AM_V_CCLD)$(LINK) $(ptex_OBJECTS) $(ptex_LDADD) $(LIBS)
synctexdir/synctex-synctex_main.$(OBJEXT): synctexdir/$(am__dirstamp) \
synctexdir/$(DEPDIR)/$(am__dirstamp)
@@ -8485,6 +8531,9 @@
@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/pmpost-psvgout.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/pmpost-ptfmin.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/pooltype.Po at am__quote@ # am--include-marker
+ at AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/ptex-ptex-pool.Po at am__quote@ # am--include-marker
+ at AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/ptex-ptex0.Po at am__quote@ # am--include-marker
+ at AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/ptex-ptexini.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/tangle.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/tangleboot.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)/tex-tex-pool.Po at am__quote@ # am--include-marker
@@ -9065,6 +9114,7 @@
@AMDEP_TRUE@@am__include@ @am__quote at pdftexdir/regex/$(DEPDIR)/libpdftex_a-regexec.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ptexdir/$(DEPDIR)/libkanji_a-kanji.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at ptexdir/$(DEPDIR)/libkanji_a-kanji_dump.Po at am__quote@ # am--include-marker
+ at AMDEP_TRUE@@am__include@ @am__quote at ptexdir/$(DEPDIR)/ptex-ptexextra.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at synctexdir/$(DEPDIR)/eptex-synctex.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at synctexdir/$(DEPDIR)/etex-synctex.Po at am__quote@ # am--include-marker
@AMDEP_TRUE@@am__include@ @am__quote at synctexdir/$(DEPDIR)/euptex-synctex.Po at am__quote@ # am--include-marker
@@ -18007,6 +18057,62 @@
@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
@am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(pmpost_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o pmpost-ptfmin.obj `if test -f 'ptfmin.c'; then $(CYGPATH_W) 'ptfmin.c'; else $(CYGPATH_W) '$(srcdir)/ptfmin.c'; fi`
+ptexdir/ptex-ptexextra.o: ptexdir/ptexextra.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptexdir/ptex-ptexextra.o -MD -MP -MF ptexdir/$(DEPDIR)/ptex-ptexextra.Tpo -c -o ptexdir/ptex-ptexextra.o `test -f 'ptexdir/ptexextra.c' || echo '$(srcdir)/'`ptexdir/ptexextra.c
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) ptexdir/$(DEPDIR)/ptex-ptexextra.Tpo ptexdir/$(DEPDIR)/ptex-ptexextra.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptexdir/ptexextra.c' object='ptexdir/ptex-ptexextra.o' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptexdir/ptex-ptexextra.o `test -f 'ptexdir/ptexextra.c' || echo '$(srcdir)/'`ptexdir/ptexextra.c
+
+ptexdir/ptex-ptexextra.obj: ptexdir/ptexextra.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptexdir/ptex-ptexextra.obj -MD -MP -MF ptexdir/$(DEPDIR)/ptex-ptexextra.Tpo -c -o ptexdir/ptex-ptexextra.obj `if test -f 'ptexdir/ptexextra.c'; then $(CYGPATH_W) 'ptexdir/ptexextra.c'; else $(CYGPATH_W) '$(srcdir)/ptexdir/ptexextra.c'; fi`
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) ptexdir/$(DEPDIR)/ptex-ptexextra.Tpo ptexdir/$(DEPDIR)/ptex-ptexextra.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptexdir/ptexextra.c' object='ptexdir/ptex-ptexextra.obj' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptexdir/ptex-ptexextra.obj `if test -f 'ptexdir/ptexextra.c'; then $(CYGPATH_W) 'ptexdir/ptexextra.c'; else $(CYGPATH_W) '$(srcdir)/ptexdir/ptexextra.c'; fi`
+
+ptex-ptexini.o: ptexini.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptex-ptexini.o -MD -MP -MF $(DEPDIR)/ptex-ptexini.Tpo -c -o ptex-ptexini.o `test -f 'ptexini.c' || echo '$(srcdir)/'`ptexini.c
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/ptex-ptexini.Tpo $(DEPDIR)/ptex-ptexini.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptexini.c' object='ptex-ptexini.o' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptex-ptexini.o `test -f 'ptexini.c' || echo '$(srcdir)/'`ptexini.c
+
+ptex-ptexini.obj: ptexini.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptex-ptexini.obj -MD -MP -MF $(DEPDIR)/ptex-ptexini.Tpo -c -o ptex-ptexini.obj `if test -f 'ptexini.c'; then $(CYGPATH_W) 'ptexini.c'; else $(CYGPATH_W) '$(srcdir)/ptexini.c'; fi`
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/ptex-ptexini.Tpo $(DEPDIR)/ptex-ptexini.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptexini.c' object='ptex-ptexini.obj' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptex-ptexini.obj `if test -f 'ptexini.c'; then $(CYGPATH_W) 'ptexini.c'; else $(CYGPATH_W) '$(srcdir)/ptexini.c'; fi`
+
+ptex-ptex0.o: ptex0.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptex-ptex0.o -MD -MP -MF $(DEPDIR)/ptex-ptex0.Tpo -c -o ptex-ptex0.o `test -f 'ptex0.c' || echo '$(srcdir)/'`ptex0.c
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/ptex-ptex0.Tpo $(DEPDIR)/ptex-ptex0.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptex0.c' object='ptex-ptex0.o' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptex-ptex0.o `test -f 'ptex0.c' || echo '$(srcdir)/'`ptex0.c
+
+ptex-ptex0.obj: ptex0.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptex-ptex0.obj -MD -MP -MF $(DEPDIR)/ptex-ptex0.Tpo -c -o ptex-ptex0.obj `if test -f 'ptex0.c'; then $(CYGPATH_W) 'ptex0.c'; else $(CYGPATH_W) '$(srcdir)/ptex0.c'; fi`
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/ptex-ptex0.Tpo $(DEPDIR)/ptex-ptex0.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptex0.c' object='ptex-ptex0.obj' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptex-ptex0.obj `if test -f 'ptex0.c'; then $(CYGPATH_W) 'ptex0.c'; else $(CYGPATH_W) '$(srcdir)/ptex0.c'; fi`
+
+ptex-ptex-pool.o: ptex-pool.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptex-ptex-pool.o -MD -MP -MF $(DEPDIR)/ptex-ptex-pool.Tpo -c -o ptex-ptex-pool.o `test -f 'ptex-pool.c' || echo '$(srcdir)/'`ptex-pool.c
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/ptex-ptex-pool.Tpo $(DEPDIR)/ptex-ptex-pool.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptex-pool.c' object='ptex-ptex-pool.o' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptex-ptex-pool.o `test -f 'ptex-pool.c' || echo '$(srcdir)/'`ptex-pool.c
+
+ptex-ptex-pool.obj: ptex-pool.c
+ at am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT ptex-ptex-pool.obj -MD -MP -MF $(DEPDIR)/ptex-ptex-pool.Tpo -c -o ptex-ptex-pool.obj `if test -f 'ptex-pool.c'; then $(CYGPATH_W) 'ptex-pool.c'; else $(CYGPATH_W) '$(srcdir)/ptex-pool.c'; fi`
+ at am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/ptex-ptex-pool.Tpo $(DEPDIR)/ptex-ptex-pool.Po
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='ptex-pool.c' object='ptex-ptex-pool.obj' libtool=no @AMDEPBACKSLASH@
+ at AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
+ at am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(ptex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o ptex-ptex-pool.obj `if test -f 'ptex-pool.c'; then $(CYGPATH_W) 'ptex-pool.c'; else $(CYGPATH_W) '$(srcdir)/ptex-pool.c'; fi`
+
synctexdir/synctex-synctex_main.o: synctexdir/synctex_main.c
@am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(synctex_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT synctexdir/synctex-synctex_main.o -MD -MP -MF synctexdir/$(DEPDIR)/synctex-synctex_main.Tpo -c -o synctexdir/synctex-synctex_main.o `test -f 'synctexdir/synctex_main.c' || echo '$(srcdir)/'`synctexdir/synctex_main.c
@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) synctexdir/$(DEPDIR)/synctex-synctex_main.Tpo synctexdir/$(DEPDIR)/synctex-synctex_main.Po
@@ -19722,6 +19828,9 @@
-rm -f ./$(DEPDIR)/pmpost-psvgout.Po
-rm -f ./$(DEPDIR)/pmpost-ptfmin.Po
-rm -f ./$(DEPDIR)/pooltype.Po
+ -rm -f ./$(DEPDIR)/ptex-ptex-pool.Po
+ -rm -f ./$(DEPDIR)/ptex-ptex0.Po
+ -rm -f ./$(DEPDIR)/ptex-ptexini.Po
-rm -f ./$(DEPDIR)/tangle.Po
-rm -f ./$(DEPDIR)/tangleboot.Po
-rm -f ./$(DEPDIR)/tex-tex-pool.Po
@@ -20302,6 +20411,7 @@
-rm -f pdftexdir/regex/$(DEPDIR)/libpdftex_a-regexec.Po
-rm -f ptexdir/$(DEPDIR)/libkanji_a-kanji.Po
-rm -f ptexdir/$(DEPDIR)/libkanji_a-kanji_dump.Po
+ -rm -f ptexdir/$(DEPDIR)/ptex-ptexextra.Po
-rm -f synctexdir/$(DEPDIR)/eptex-synctex.Po
-rm -f synctexdir/$(DEPDIR)/etex-synctex.Po
-rm -f synctexdir/$(DEPDIR)/euptex-synctex.Po
@@ -20496,6 +20606,9 @@
-rm -f ./$(DEPDIR)/pmpost-psvgout.Po
-rm -f ./$(DEPDIR)/pmpost-ptfmin.Po
-rm -f ./$(DEPDIR)/pooltype.Po
+ -rm -f ./$(DEPDIR)/ptex-ptex-pool.Po
+ -rm -f ./$(DEPDIR)/ptex-ptex0.Po
+ -rm -f ./$(DEPDIR)/ptex-ptexini.Po
-rm -f ./$(DEPDIR)/tangle.Po
-rm -f ./$(DEPDIR)/tangleboot.Po
-rm -f ./$(DEPDIR)/tex-tex-pool.Po
@@ -21076,6 +21189,7 @@
-rm -f pdftexdir/regex/$(DEPDIR)/libpdftex_a-regexec.Po
-rm -f ptexdir/$(DEPDIR)/libkanji_a-kanji.Po
-rm -f ptexdir/$(DEPDIR)/libkanji_a-kanji_dump.Po
+ -rm -f ptexdir/$(DEPDIR)/ptex-ptexextra.Po
-rm -f synctexdir/$(DEPDIR)/eptex-synctex.Po
-rm -f synctexdir/$(DEPDIR)/etex-synctex.Po
-rm -f synctexdir/$(DEPDIR)/euptex-synctex.Po
@@ -21805,6 +21919,8 @@
# Generate ptex.ch
ptex.ch: tie$(EXEEXT) ptex.web $(ptex_ch_srcs)
$(tie_c) ptex.web $(ptex_ch_srcs)
+ptexdir/ptriptest.log: ptex$(EXEEXT) dvitype$(EXEEXT) pltotf$(EXEEXT) tftopl$(EXEEXT)
+ptexdir/pver.log ptexdir/wcfname.log: ptex$(EXEEXT)
ptrip.diffs: ptex$(EXEEXT) dvitype$(EXEEXT) pltotf$(EXEEXT) tftopl$(EXEEXT)
$(triptrap_diffs) $@
.PHONY: ptrip-clean
@@ -21910,10 +22026,7 @@
$(up_tangle) uptftopl uptftopl
uptftopl.web: tie$(EXEEXT) tftopl.web tftopl.ch
$(tie_m) tftopl.web tftopl.ch
-
-# upTeX Tests
-#uptex_tests = uptexdir/uptriptest.test uptexdir/upver.test uptexdir/upkcat.test uptexdir/wcfname.test
-uptexdir/uptriptest.log: uptex$(EXEEXT) dvitype$(EXEEXT) pltotf$(EXEEXT) tftopl$(EXEEXT)
+uptexdir/uptriptest.log uptexdir/ptriptest.log: uptex$(EXEEXT) dvitype$(EXEEXT) pltotf$(EXEEXT) tftopl$(EXEEXT)
uptexdir/upver.log uptexdir/upkcat.log uptexdir/wcfname.log: uptex$(EXEEXT)
uptexdir/upbibtex.log: upbibtex$(EXEEXT)
uptexdir/updvitype.log: updvitype$(EXEEXT)
Modified: branches/stable/source/src/texk/web2c/NEWS
===================================================================
--- branches/stable/source/src/texk/web2c/NEWS 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/NEWS 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,19 @@
This file records noteworthy changes. (Public domain.)
+2023 (for TeX Live 2023)
+
+* (u)pTeX: now using as aliases of e(u)ptex. Also support guessing input
+ encodings with these and (u)pbibtex.
+
+* bibtex: check options early to avoid looking for texmf.cnf unnecessarily;
+ use max_print_line texmf.cnf variable.
+
+* ctangle: with option +u, transliterate UTF-8 in C source.
+
+* mflua{,jit}: add potrace support.
+
+
2022 (for TeX Live 2022, 21 March 2022)
* new hitex engine included, which outputs HINT files for display on
Modified: branches/stable/source/src/texk/web2c/ac/web2c.ac
===================================================================
--- branches/stable/source/src/texk/web2c/ac/web2c.ac 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/ac/web2c.ac 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,4 +1,4 @@
-dnl $Id: web2c.ac 65543 2023-01-15 05:09:14Z takuji $
+dnl $Id: web2c.ac 65655 2023-01-28 05:27:55Z takuji $
# texk/web2c/ac/web2c.ac: configure.ac fragment for TL subdir
dnl
dnl Copyright 2015-2021 Karl Berry <tex-live at tug.org>
@@ -31,7 +31,9 @@
m4_define([kpse_tex_progs], [dnl
[[tex], [yes], [no], [TeX], []],
[[etex], [no], [yes], [e-TeX], [zlib]],
+[[ptex], [no], [yes], [pTeX], [ptexenc zlib]],
[[eptex], [yes], [yes], [e-pTeX], [ptexenc zlib]],
+[[uptex], [no], [yes], [upTeX], [ptexenc zlib]],
[[euptex], [yes], [yes], [e-upTeX], [ptexenc zlib]],
[[aleph], [yes], [], [Aleph], []],
[[hitex], [yes], [], [HiTeX], [zlib]],
Modified: branches/stable/source/src/texk/web2c/configure
===================================================================
--- branches/stable/source/src/texk/web2c/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for Web2C 2023/dev.
+# Generated by GNU Autoconf 2.71 for Web2C 2023.
#
# Report bugs to <tex-k at tug.org>.
#
@@ -629,8 +629,8 @@
# Identity of this package.
PACKAGE_NAME='Web2C'
PACKAGE_TARNAME='web2c'
-PACKAGE_VERSION='2023/dev'
-PACKAGE_STRING='Web2C 2023/dev'
+PACKAGE_VERSION='2023'
+PACKAGE_STRING='Web2C 2023'
PACKAGE_BUGREPORT='tex-k at tug.org'
PACKAGE_URL=''
@@ -834,10 +834,18 @@
EUPTEX_SYNCTEX_TRUE
EUPTEX_FALSE
EUPTEX_TRUE
+UPTEX_SYNCTEX_FALSE
+UPTEX_SYNCTEX_TRUE
+UPTEX_FALSE
+UPTEX_TRUE
EPTEX_SYNCTEX_FALSE
EPTEX_SYNCTEX_TRUE
EPTEX_FALSE
EPTEX_TRUE
+PTEX_SYNCTEX_FALSE
+PTEX_SYNCTEX_TRUE
+PTEX_FALSE
+PTEX_TRUE
ETEX_SYNCTEX_FALSE
ETEX_SYNCTEX_TRUE
ETEX_FALSE
@@ -1034,8 +1042,12 @@
enable_tex_synctex
enable_etex
enable_etex_synctex
+enable_ptex
+enable_ptex_synctex
enable_eptex
enable_eptex_synctex
+enable_uptex
+enable_uptex_synctex
enable_euptex
enable_euptex_synctex
enable_aleph
@@ -1663,7 +1675,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures Web2C 2023/dev to adapt to many kinds of systems.
+\`configure' configures Web2C 2023 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1738,7 +1750,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of Web2C 2023/dev:";;
+ short | recursive ) echo "Configuration of Web2C 2023:";;
esac
cat <<\_ACEOF
@@ -1773,8 +1785,12 @@
--enable-tex-synctex build TeX with SyncTeX support
--enable-etex compile and install e-TeX
--disable-etex-synctex build e-TeX without SyncTeX support
+ --enable-ptex compile and install pTeX
+ --disable-ptex-synctex build pTeX without SyncTeX support
--disable-eptex do not compile and install e-pTeX
--disable-eptex-synctex build e-pTeX without SyncTeX support
+ --enable-uptex compile and install upTeX
+ --disable-uptex-synctex build upTeX without SyncTeX support
--disable-euptex do not compile and install e-upTeX
--disable-euptex-synctex build e-upTeX without SyncTeX support
--disable-aleph do not compile and install Aleph
@@ -1960,7 +1976,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-Web2C configure 2023/dev
+Web2C configure 2023
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -2950,7 +2966,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by Web2C $as_me 2023/dev, which was
+It was created by Web2C $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -3926,7 +3942,7 @@
-WEB2CVERSION=2023/dev
+WEB2CVERSION=2023
am__api_version='1.16'
@@ -9491,7 +9507,7 @@
# Define the identity of the package.
PACKAGE='web2c'
- VERSION='2023/dev'
+ VERSION='2023'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -19712,6 +19728,28 @@
test "x$enable_web2c:$enable_etex" = xyes:yes && {
need_zlib=yes
}
+# Check whether --enable-ptex was given.
+if test ${enable_ptex+y}
+then :
+ enableval=$enable_ptex;
+fi
+case $enable_ptex in #(
+ yes | no) :
+ ;; #(
+ *) :
+ enable_ptex=no ;;
+esac
+
+# Check whether --enable-ptex-synctex was given.
+if test ${enable_ptex_synctex+y}
+then :
+ enableval=$enable_ptex_synctex;
+fi
+
+test "x$enable_web2c:$enable_ptex" = xyes:yes && {
+ need_ptexenc=yes
+ need_zlib=yes
+}
# Check whether --enable-eptex was given.
if test ${enable_eptex+y}
then :
@@ -19734,6 +19772,28 @@
need_ptexenc=yes
need_zlib=yes
}
+# Check whether --enable-uptex was given.
+if test ${enable_uptex+y}
+then :
+ enableval=$enable_uptex;
+fi
+case $enable_uptex in #(
+ yes | no) :
+ ;; #(
+ *) :
+ enable_uptex=no ;;
+esac
+
+# Check whether --enable-uptex-synctex was given.
+if test ${enable_uptex_synctex+y}
+then :
+ enableval=$enable_uptex_synctex;
+fi
+
+test "x$enable_web2c:$enable_uptex" = xyes:yes && {
+ need_ptexenc=yes
+ need_zlib=yes
+}
# Check whether --enable-euptex was given.
if test ${enable_euptex+y}
then :
@@ -22376,6 +22436,35 @@
ETEX_SYNCTEX_TRUE='#'
ETEX_SYNCTEX_FALSE=
fi
+ if test "x$enable_ptex" = xyes; then
+ PTEX_TRUE=
+ PTEX_FALSE='#'
+else
+ PTEX_TRUE='#'
+ PTEX_FALSE=
+fi
+
+case $enable_native_texlive_build:$enable_ptex_synctex in #(
+ yes:yes | no:yes | no:no) :
+ ;; #(
+ *) :
+ if test -z "$enable_ptex_synctex"
+then :
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: Assuming \`--enable-ptex-synctex=yes'" >&5
+printf "%s\n" "$as_me: Assuming \`--enable-ptex-synctex=yes'" >&6;}
+else $as_nop
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: Enforcing \`--enable-ptex-synctex=yes' (native TeX Live build)" >&5
+printf "%s\n" "$as_me: WARNING: Enforcing \`--enable-ptex-synctex=yes' (native TeX Live build)" >&2;}
+fi
+ enable_ptex_synctex=yes ;;
+esac
+ if test "x$enable_ptex_synctex" = xyes; then
+ PTEX_SYNCTEX_TRUE=
+ PTEX_SYNCTEX_FALSE='#'
+else
+ PTEX_SYNCTEX_TRUE='#'
+ PTEX_SYNCTEX_FALSE=
+fi
if test "x$enable_eptex" = xyes; then
EPTEX_TRUE=
EPTEX_FALSE='#'
@@ -22405,6 +22494,35 @@
EPTEX_SYNCTEX_TRUE='#'
EPTEX_SYNCTEX_FALSE=
fi
+ if test "x$enable_uptex" = xyes; then
+ UPTEX_TRUE=
+ UPTEX_FALSE='#'
+else
+ UPTEX_TRUE='#'
+ UPTEX_FALSE=
+fi
+
+case $enable_native_texlive_build:$enable_uptex_synctex in #(
+ yes:yes | no:yes | no:no) :
+ ;; #(
+ *) :
+ if test -z "$enable_uptex_synctex"
+then :
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: Assuming \`--enable-uptex-synctex=yes'" >&5
+printf "%s\n" "$as_me: Assuming \`--enable-uptex-synctex=yes'" >&6;}
+else $as_nop
+ { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: Enforcing \`--enable-uptex-synctex=yes' (native TeX Live build)" >&5
+printf "%s\n" "$as_me: WARNING: Enforcing \`--enable-uptex-synctex=yes' (native TeX Live build)" >&2;}
+fi
+ enable_uptex_synctex=yes ;;
+esac
+ if test "x$enable_uptex_synctex" = xyes; then
+ UPTEX_SYNCTEX_TRUE=
+ UPTEX_SYNCTEX_FALSE='#'
+else
+ UPTEX_SYNCTEX_TRUE='#'
+ UPTEX_SYNCTEX_FALSE=
+fi
if test "x$enable_euptex" = xyes; then
EUPTEX_TRUE=
EUPTEX_FALSE='#'
@@ -25260,7 +25378,7 @@
Report bugs to <bug-libtool at gnu.org>."
lt_cl_version="\
-Web2C config.lt 2023/dev
+Web2C config.lt 2023
configured by $0, generated by GNU Autoconf 2.71.
Copyright (C) 2011 Free Software Foundation, Inc.
@@ -28300,6 +28418,14 @@
as_fn_error $? "conditional \"ETEX_SYNCTEX\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
+if test -z "${PTEX_TRUE}" && test -z "${PTEX_FALSE}"; then
+ as_fn_error $? "conditional \"PTEX\" was never defined.
+Usually this means the macro was only invoked conditionally." "$LINENO" 5
+fi
+if test -z "${PTEX_SYNCTEX_TRUE}" && test -z "${PTEX_SYNCTEX_FALSE}"; then
+ as_fn_error $? "conditional \"PTEX_SYNCTEX\" was never defined.
+Usually this means the macro was only invoked conditionally." "$LINENO" 5
+fi
if test -z "${EPTEX_TRUE}" && test -z "${EPTEX_FALSE}"; then
as_fn_error $? "conditional \"EPTEX\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
@@ -28308,6 +28434,14 @@
as_fn_error $? "conditional \"EPTEX_SYNCTEX\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
+if test -z "${UPTEX_TRUE}" && test -z "${UPTEX_FALSE}"; then
+ as_fn_error $? "conditional \"UPTEX\" was never defined.
+Usually this means the macro was only invoked conditionally." "$LINENO" 5
+fi
+if test -z "${UPTEX_SYNCTEX_TRUE}" && test -z "${UPTEX_SYNCTEX_FALSE}"; then
+ as_fn_error $? "conditional \"UPTEX_SYNCTEX\" was never defined.
+Usually this means the macro was only invoked conditionally." "$LINENO" 5
+fi
if test -z "${EUPTEX_TRUE}" && test -z "${EUPTEX_FALSE}"; then
as_fn_error $? "conditional \"EUPTEX\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
@@ -28807,7 +28941,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by Web2C $as_me 2023/dev, which was
+This file was extended by Web2C $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -28879,7 +29013,7 @@
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-Web2C config.status 2023/dev
+Web2C config.status 2023
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
Modified: branches/stable/source/src/texk/web2c/doc/web2c.info
===================================================================
--- branches/stable/source/src/texk/web2c/doc/web2c.info 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/doc/web2c.info 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,4 +1,4 @@
-This is web2c.info, produced by makeinfo version 6.8 from web2c.texi.
+This is web2c.info, produced by makeinfo version 6.5 from web2c.texi.
This file documents the installation and use of the programs in Web2c,
an implementation of Donald Knuth's TeX system.
@@ -58,7 +58,7 @@
This document describes how to install and use the programs in the Web2c
implementation of the TeX system, especially for Unix systems. It
-corresponds to Web2c version 2022, released in January 2022.
+corresponds to Web2c version 2023, released in February 2022.
* Menu:
@@ -83,7 +83,7 @@
1 Introduction
**************
-This manual corresponds to version 2022 of Web2c, released in January
+This manual corresponds to version 2023 of Web2c, released in February
2022.
"Web2c" (also spelled Web2C) is the name of a TeX implementation,
@@ -3570,7 +3570,7 @@
* -base=BASE: Determining the memory dump to use.
(line 15)
* -base=DUMPNAME: Common options. (line 39)
-* -change=CHFILE: mft invocation. (line 62)
+* -change=CHFILE: mft invocation. (line 63)
* -charcode-format=TYPE: tftopl invocation. (line 27)
* -charcode-format=TYPE <1>: vftovp invocation. (line 30)
* -cnf-line: Common options. (line 25)
@@ -3632,7 +3632,7 @@
* -shell-restricted: tex invocation. (line 122)
* -show-opcodes: dvitype invocation. (line 52)
* -strict: tangle invocation. (line 46)
-* -style=MFTFILE: mft invocation. (line 66)
+* -style=MFTFILE: mft invocation. (line 67)
* -T: mpost invocation. (line 111)
* -terse: bibtex invocation. (line 28)
* -tex=TEXPROGRAM: mpost invocation. (line 114)
@@ -3782,7 +3782,7 @@
* c-sources Makefile target: Additional targets. (line 12)
* caveats for \input filenames: \input filename caveats.
(line 6)
-* change files, and MFT: mft invocation. (line 62)
+* change files, and MFT: mft invocation. (line 63)
* change files, and Tangle: tangle invocation. (line 11)
* change files, and Weave: weave invocation. (line 14)
* changing error messages style: Common options. (line 31)
@@ -3802,7 +3802,7 @@
(line 69)
* cm.base: Initial Metafont. (line 26)
* cmbase.mf: Initial Metafont. (line 26)
-* cmbase.mft: mft invocation. (line 72)
+* cmbase.mft: mft invocation. (line 73)
* cmmf.base not recommended: Initial Metafont. (line 26)
* color, in DVItoMP: dvitomp invocation. (line 15)
* comments, in TCX files: TCX files. (line 70)
@@ -3815,7 +3815,7 @@
(line 6)
* Computer Modern fonts, and Troff: mpost invocation. (line 61)
* Computer Modern macros: Initial Metafont. (line 26)
-* Computer Modern Typefaces, production of: mft invocation. (line 72)
+* Computer Modern Typefaces, production of: mft invocation. (line 73)
* configuration: Installation. (line 6)
* configuration file reading: Path searching. (line 6)
* configuration file values: Runtime options. (line 6)
@@ -3888,7 +3888,7 @@
* e response at error prompt: Editor invocation. (line 6)
* e-circumflex: \charsubdef. (line 20)
* e-TeX: TeX extensions. (line 20)
-* e.mft: mft invocation. (line 72)
+* e.mft: mft invocation. (line 73)
* EC fonts: tex invocation. (line 41)
* EC fonts <1>: mf invocation. (line 24)
* editing of bitmap fonts: Font utilities available elsewhere.
@@ -4140,7 +4140,7 @@
(line 15)
* MetaPost input files: mpost invocation. (line 26)
* MetaPost invocation: mpost invocation. (line 6)
-* MetaPost source, prettyprinting: mft invocation. (line 77)
+* MetaPost source, prettyprinting: mft invocation. (line 79)
* MetaPost, initial: Initial MetaPost. (line 6)
* MetaPost, TeX, and Metafont: Three programs. (line 6)
* metatype1: Font utilities available elsewhere.
@@ -4257,7 +4257,7 @@
* plain.bst: Basic BibTeX style files.
(line 11)
* plain.fmt: Initial TeX. (line 13)
-* plain.mft: mft invocation. (line 66)
+* plain.mft: mft invocation. (line 67)
* pltotf: pltotf invocation. (line 6)
* pool file, writing: tangle invocation. (line 16)
* Poole, Simon: Online Metafont graphics.
@@ -4303,7 +4303,7 @@
* quoted filename for \input: \input quoted filename.
(line 6)
* Raichle, Bernd: MLTeX. (line 6)
-* reading, additional: Introduction. (line 71)
+* reading, additional: Introduction. (line 72)
* readonly directory, running TeX in: Output file location.
(line 15)
* readonly directory, running TeX in <1>: Output file location.
@@ -4366,7 +4366,7 @@
* string pool, writing: tangle invocation. (line 16)
* string representation: pooltype invocation. (line 30)
* style design, for BibTeX: bibtex invocation. (line 49)
-* style files: mft invocation. (line 66)
+* style files: mft invocation. (line 67)
* substitutions of font glyphs: MLTeX. (line 6)
* sun: Online Metafont graphics.
(line 42)
@@ -4553,82 +4553,77 @@
Tag Table:
Node: Top2759
-Node: Introduction3833
-Node: Installation7591
-Node: configure options9635
-Node: Compile-time options11657
-Node: Additional targets12759
-Node: Triptrap14036
-Node: Commonalities15539
-Node: Option conventions16196
-Node: Common options17419
-Node: Path searching22037
-Node: Output file location23009
-Node: Three programs24311
-Node: Runtime options25018
-Node: Initial and virgin28159
-Node: Memory dumps29108
-Node: Creating memory dumps29560
-Node: Determining the memory dump to use30767
-Node: Hardware and memory dumps32344
-Node: Editor invocation35094
-Node: \input filenames35957
-Node: \input quoted filename37508
-Node: \input braced filename38285
-Node: \input filename caveats39215
-Node: TeX40729
-Node: tex invocation41897
-Node: Initial TeX48883
-Node: Formats50247
-Node: Languages and hyphenation53064
-Node: MLTeX53494
-Node: \charsubdef55122
-Node: \tracingcharsubdef57445
-Node: TCX files58020
-Node: patgen invocation63460
-Node: Shell escapes64167
-Node: IPC and TeX67747
-Node: TeX extensions68317
-Node: Metafont71098
-Node: mf invocation72386
-Node: Initial Metafont76223
-Node: Modes77853
-Node: Online Metafont graphics80103
-Node: gftodvi invocation83528
-Node: mft invocation86348
-Node: MetaPost90346
-Node: mpost invocation91182
-Node: Initial MetaPost96218
-Node: dvitomp invocation97140
-Node: BibTeX97805
-Node: bibtex invocation98166
-Node: Basic BibTeX style files100640
-Node: WEB101970
-Node: tangle invocation103179
-Node: weave invocation105303
-Node: pooltype invocation106710
-Node: DVI utilities107840
-Node: dvicopy invocation108774
-Node: dvitype invocation110059
-Node: dvitype output example112390
-Node: Font utilities115443
-Node: Font file formats116623
-Node: gftopk invocation119890
-Node: pktogf invocation121081
-Node: pktype invocation122247
-Node: gftype invocation125070
-Node: tftopl invocation129573
-Node: pltotf invocation134166
-Node: vftovp invocation135217
-Node: vptovf invocation137452
-Node: Font utilities available elsewhere138479
-Node: Legalisms140684
-Node: References142131
-Node: Index146264
+Node: Introduction3834
+Node: Installation7593
+Node: configure options9637
+Node: Compile-time options11659
+Node: Additional targets12761
+Node: Triptrap14038
+Node: Commonalities15541
+Node: Option conventions16198
+Node: Common options17421
+Node: Path searching22039
+Node: Output file location23011
+Node: Three programs24313
+Node: Runtime options25020
+Node: Initial and virgin28161
+Node: Memory dumps29110
+Node: Creating memory dumps29562
+Node: Determining the memory dump to use30769
+Node: Hardware and memory dumps32346
+Node: Editor invocation35096
+Node: \input filenames35959
+Node: \input quoted filename37510
+Node: \input braced filename38287
+Node: \input filename caveats39217
+Node: TeX40731
+Node: tex invocation41899
+Node: Initial TeX48885
+Node: Formats50249
+Node: Languages and hyphenation53066
+Node: MLTeX53496
+Node: \charsubdef55124
+Node: \tracingcharsubdef57447
+Node: TCX files58022
+Node: patgen invocation63462
+Node: Shell escapes64169
+Node: IPC and TeX67749
+Node: TeX extensions68319
+Node: Metafont71100
+Node: mf invocation72388
+Node: Initial Metafont76225
+Node: Modes77855
+Node: Online Metafont graphics80105
+Node: gftodvi invocation83530
+Node: mft invocation86350
+Node: MetaPost90348
+Node: mpost invocation91184
+Node: Initial MetaPost96220
+Node: dvitomp invocation97142
+Node: BibTeX97807
+Node: bibtex invocation98168
+Node: Basic BibTeX style files100642
+Node: WEB101972
+Node: tangle invocation103181
+Node: weave invocation105305
+Node: pooltype invocation106712
+Node: DVI utilities107842
+Node: dvicopy invocation108776
+Node: dvitype invocation110061
+Node: dvitype output example112392
+Node: Font utilities115445
+Node: Font file formats116625
+Node: gftopk invocation119892
+Node: pktogf invocation121083
+Node: pktype invocation122249
+Node: gftype invocation125072
+Node: tftopl invocation129575
+Node: pltotf invocation134168
+Node: vftovp invocation135219
+Node: vptovf invocation137454
+Node: Font utilities available elsewhere138481
+Node: Legalisms140686
+Node: References142133
+Node: Index146266
End Tag Table
-
-
-Local Variables:
-coding: utf-8
-End:
Modified: branches/stable/source/src/texk/web2c/doc/web2c.texi
===================================================================
--- branches/stable/source/src/texk/web2c/doc/web2c.texi 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/doc/web2c.texi 2023-02-21 22:38:24 UTC (rev 903)
@@ -11,8 +11,8 @@
\fi
@end tex
- at set version 2022
- at set month-year January 2022
+ at set version 2023
+ at set month-year February 2022
@c Define new indices for commands in auxiliary files, filenames, and options.
@defcodeindex cm
Modified: branches/stable/source/src/texk/web2c/enctexdir/enctex-pdftex.ch
===================================================================
--- branches/stable/source/src/texk/web2c/enctexdir/enctex-pdftex.ch 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/enctexdir/enctex-pdftex.ch 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,8 +1,8 @@
-% $Id: enctex-pdftex.ch 60992 2021-11-07 22:51:07Z karl $
+% $Id: enctex-pdftex.ch 65813 2023-02-13 16:30:22Z karl $
% enctex1.ch is applied first.
-% Then this change is applied for pdfTeX et al.,
-% assuming that tracingstacklevels.ch, partoken.ch, and showstream.ch has been included,
-% as specified in the *.am files.
+% Then this change is applied for pdfTeX et al. (but not TeX),
+% assuming that tracingstacklevels.ch, partoken.ch, and showstream.ch
+% have been included, as specified in the *.am files.
% encTeX: \mubytein \mubyteout \mubytelog and \specialout
@x [17.236] l.4954
@@ -14,3 +14,24 @@
@d spec_out_code=web2c_int_base+9 {if positive then print specials by mubytes}
@d web2c_int_pars=web2c_int_base+10 {total number of web2c's integer parameters}
@z
+
+% see pdftex.web for more about this.
+ at x [53.1353] - encTeX: late \special stores specialout and mubyteout values
+begin new_whatsit(latespecial_node,write_node_size); write_stream(tail):=null;
+p:=scan_toks(false,false); write_tokens(tail):=def_ref;
+ at y
+begin new_whatsit(latespecial_node,write_node_size);
+if spec_out + mubyte_zero < 0 then write_stream(tail) := 0
+else if spec_out + mubyte_zero >= 2*mubyte_zero then
+ write_stream(tail) := 2*mubyte_zero - 1
+ else write_stream(tail) := spec_out + mubyte_zero;
+if mubyte_out + mubyte_zero < 0 then write_mubyte(tail) := 0
+else if mubyte_out + mubyte_zero >= 2*mubyte_zero then
+ write_mubyte(tail) := 2*mubyte_zero - 1
+ else write_mubyte(tail) := mubyte_out + mubyte_zero;
+if (spec_out = 2) or (spec_out = 3) then
+ if (mubyte_out > 2) or (mubyte_out = -1) or (mubyte_out = -2) then
+ write_noexpanding := true;
+p:=scan_toks(false,false); write_tokens(tail):=def_ref;
+write_noexpanding := false;
+ at z
Modified: branches/stable/source/src/texk/web2c/enctexdir/enctex2.ch
===================================================================
--- branches/stable/source/src/texk/web2c/enctexdir/enctex2.ch 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/enctexdir/enctex2.ch 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,4 +1,4 @@
-% $Id: enctex2.ch 57736 2021-02-13 23:02:37Z karl $
+% $Id: enctex2.ch 65809 2023-02-12 23:58:22Z karl $
% enctex2.ch: bulk of the encTeX implementation, common to all engines
% supporting encTeX.
Modified: branches/stable/source/src/texk/web2c/pdftexdir/ChangeLog
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/ChangeLog 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/ChangeLog 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,3 +1,72 @@
+2023-02-21 Phelype Oleinik <phelype.oleinik at latex-project.org>
+
+ * pdftex.web: reduce memory usage for \special shipout,
+ a la HH/luatex.
+
+2023-02-14 Thanh Han The <hanthethanh at gmail.com>
+
+ * writet1.c (cs_mark) <CS_SEAC>: look for the composite(d) glyphs too,
+ to include in /CharSet. Original report from John Lienhard
+ for Lucida: https://tug.org/pipermail/lucida/2023-February/000922.html
+ Also happens with DejaVuSerif: tests/31-CharSet-miss-composite-char.
+ (pdftex r902)
+
+2023-02-14 Thanh Han The <hanthethanh at gmail.com>
+
+ * tounicode.c (set_glyph_unicode): take new glyph_unicode_entry arg.
+ (is_last_byte_valid): new fn.
+ (write_tounicode): stop writing range when last byte of a
+ beginbfrange is no longer valid, that is, >255.
+ Report from Ben JW:
+ https://tug.org/pipermail/tex-live/2023-February/048845.html
+ and corresponding veraPDF issue:
+ https://github.com/veraPDF/veraPDF-library/issues/1253#issuecomment-1420125850
+
+2023-02-14 Hironori Kitagawa <h_kitagawa2001 at yahoo.co.jp>
+
+ * wcfname.test:
+ Avoid errors on parallel test processing.
+ Report from Ken Brown.
+
+2023-02-12 Phelype Oleinik <phe.h.o1 at gmail.com>
+ and Karl Berry <karl at freefriends.org>
+
+ * pdftex.web (Implement \.{\\special}): add comments explaining
+ that write_stream(tail):=null is an overflow assignment with the
+ current memory_word structure, and is overwritten in enctex2.ch.
+
+2023-02-11 Thanh Han The <hanthethanh at gmail.com>
+
+ * pdftex.ch (pdf_font_has_space_char): xmalloc and maintain new array.
+ * pdftex.web (pdf_init_font): update pdf_font_has_space_char array.
+ (pdf_read_dummy_font): use pdf_space_font_name instead of
+ hardwired "dummy-space".
+ (pdf_begin_string): use real space char if pdf_font_has_space_char,
+ else call pdf_insert_interword_space.
+ (pdf_space_font_code): new \pdfspacefont primitive.
+ (Put each ...): define it.
+ (Cases of |print_cmd_chr|...): print it.
+ (Declare act...): switch on it.
+ (Implement \.{\\pdfspacefont}): implement it.
+ (Glob...): declare pdf_space_font_name.
+ (Set init...): initialize it.
+ * pdftex.defines,
+ * ptexlib.h,
+ * mapfile.c (hasspacechar, pdfmaplinesp): new fns.
+ * NEWS: mention new behavior.
+
+2021-02-17 Karl Berry <karl at tug.org>
+
+ * NEWS,
+ * pdftex_version.h,
+ * pdftex.web (pdftex_revision, pdftex_version_string):
+ version [1.40.]25 for TL23.
+
+2023-12-28 Thanh Han The <hanthethanh at gmail.com>
+
+ * pdftex.web: use real space char for \pdfinterwordspaceon,
+ but only works for fonts containing the real space char.
+
2023-01-20 Phelype Oleinik <phe.h.o1 at gmail.com>
* pdftex.web: implement shipout keyword for delayed expansion
Modified: branches/stable/source/src/texk/web2c/pdftexdir/NEWS
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/NEWS 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/NEWS 2023-02-21 22:38:24 UTC (rev 903)
@@ -3,13 +3,25 @@
- new keyword `shipout' for \special and \pdfliteral, delaying
expansion until the node is shipped out, like non-\immediate \write.
- new primitive \pdfinfoomitdict to omit /Info dictionary completely.
- - new primitive \pdfomitprocset to control omitting /ProcSet array;
+ - new primitive \pdfomitprocset to control omitting /ProcSet array:
/ProcSet is included if this parameter is negative, or if this
parameter is zero and pdftex is generating PDF 1.x output.
+ - with \pdfinterwordspaceon, if the current font's encoding has a /space
+ character at slot 32, it is used; otherwise, the /space from the
+ (new) default font "pdftexspace" is used. That default font can be
+ overridden with the new primitive \pdfspacefont. This same new
+ procedure is used for \pdffakespace.
+ (In the past, the inserted fake space was always taken from the font
+ "dummy-space", which contained a tiny space character. It turns out
+ a normally-sized space character works with more viewers.)
- bugfixes:
- finish omission of /Info dict when \pdfomitinfodict is not 0.
-
+ - generated beginbfrange should no longer be invalid with certain
+ characters (that is, no longer have have a last byte >255).
+ - include base and accent glyph in /CharSet when the Type 1 seac
+ operator is used (e.g., Lucida, DejaVu Serif).
+
pdfTeX 3.141592653-2.6-1.40.24 (TeX Live 2022)
- changes:
- new primitive \showstream to redirect \show output.
@@ -35,6 +47,13 @@
different nesting level than \pdfstartlink".
- dump \pdfglyphtounicode assignments in fmt file.
- ttf2afm outputs name information.
+ - If \tracinglostchars is set to 3 or more, missing characters will
+ result in an error, not just a message in the log file, and the
+ missing character code will be shown in hex.
+ - A new integer parameter \tracingstacklevels, if positive, and
+ \tracingmacros is also positive, causes a prefix indicating the macro
+ expansion depth to be output on each relevant log line. Also, macro
+ logging is truncated at a depth >= the parameter value.
- bugfixes:
- avoid crash in unusual autoexpand cases.
Modified: branches/stable/source/src/texk/web2c/pdftexdir/mapfile.c
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/mapfile.c 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/mapfile.c 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
/* mapfile.c: handling of map files/lines
-Copyright 1996-2018 Han The Thanh, <thanh at pdftex.org>
+Copyright 1996-2023 Han The Thanh, <thanh at pdftex.org>
This file is part of pdfTeX.
@@ -661,11 +661,12 @@
boolean hasspacechar(internalfontnumber f)
{
+ fm_entry *fm;
+ fe_entry *fe;
if (!isscalable(f))
return false;
- fm_entry *fm = (fm_entry *)pdffontmap[f];
- fe_entry *fe;
+ fm = (fm_entry *)pdffontmap[f];
/* if a font is not re-encoded via its map entry, we assume it has no space char */
if (is_reencoded(fm) && (fe = get_fe_entry(fm->encname)) != NULL) {
Modified: branches/stable/source/src/texk/web2c/pdftexdir/pdftex.ch
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/pdftex.ch 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/pdftex.ch 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,4 +1,4 @@
-% Copyright 1996-2014 Han The Thanh, <thanh at pdftex.org>
+% Copyright 1996-2023 Han The Thanh, <thanh at pdftex.org>
%
% This file is part of pdfTeX.
%
Modified: branches/stable/source/src/texk/web2c/pdftexdir/pdftex.defines
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/pdftex.defines 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/pdftex.defines 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
{ pdftex.defines: Web2C pseudo-Pascal identifiers for pdfTeX.
-Copyright 1996-2018 Han The Thanh, <thanh at pdftex.org>
+Copyright 1996-2023 Han The Thanh, <thanh at pdftex.org>
This file is part of pdfTeX.
Modified: branches/stable/source/src/texk/web2c/pdftexdir/pdftex.web
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/pdftex.web 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/pdftex.web 2023-02-21 22:38:24 UTC (rev 903)
@@ -307,8 +307,8 @@
{printed when \eTeX\ starts}
@#
@d pdftex_version==140 { \.{\\pdftexversion} }
- at d pdftex_revision=="24" { \.{\\pdftexrevision} }
- at d pdftex_version_string=='-1.40.24' {current \pdfTeX\ version}
+ at d pdftex_revision=="25" { \.{\\pdftexrevision} }
+ at d pdftex_version_string=='-1.40.25' {current \pdfTeX\ version}
@#
@d pdfTeX_banner=='This is pdfTeX, Version 3.141592653',eTeX_version_string,pdftex_version_string
{printed when \pdfTeX\ starts}
@@ -15967,9 +15967,7 @@
@!pdf_last_f: internal_font_number; {last font in PDF output page}
@!pdf_last_fs: internal_font_number; {last font size in PDF output page}
@!pdf_dummy_font: internal_font_number; {font used to insert artificial interword spaces}
-@!pdf_dummy_font: internal_font_number; {font used to insert artificial interword spaces}
-
@ Following procedures implement low-level subroutines to convert \TeX{}
internal structures to PDF page description.
@@ -18513,6 +18511,7 @@
procedure pdf_out_literal(p:pointer);
var old_setting:0..max_selector; {holds print |selector|}
s: str_number;
+ h: halfword;
@!q,@!r:pointer; {temporary variables for list manipulation}
@!old_mode:integer; {saved |mode|}
begin
@@ -18520,14 +18519,17 @@
if subtype(p)=pdf_lateliteral_node then
begin @<Expand macros in the token list
and make |link(def_ref)| point to the result@>;
- pdf_literal_data(p):=def_ref;
- end;
+ h:=def_ref;
+ end
+ else h:=pdf_literal_data(p);
selector:=new_string;
- show_token_list(link(pdf_literal_data(p)),null,pool_size-pool_ptr);
+ show_token_list(link(h),null,pool_size-pool_ptr);
selector:=old_setting;
s := make_string;
literal(s, pdf_literal_mode(p), false);
flush_str(s);
+ if subtype(p)=pdf_lateliteral_node then
+ flush_list(def_ref);
end;
procedure pdf_out_colorstack(p:pointer);
@@ -18638,6 +18640,7 @@
procedure pdf_special(p: pointer);
var old_setting:0..max_selector; {holds print |selector|}
s: str_number;
+ h: halfword;
@!q,@!r:pointer; {temporary variables for list manipulation}
@!old_mode:integer; {saved |mode|}
begin
@@ -18646,14 +18649,17 @@
if subtype(p)=latespecial_node then
begin @<Expand macros in the token list
and make |link(def_ref)| point to the result@>;
- write_tokens(p):=def_ref;
- end;
+ h:=def_ref;
+ end
+ else h:=write_tokens(p);
selector:=new_string;
- show_token_list(link(write_tokens(p)),null,pool_size-pool_ptr);
+ show_token_list(link(h),null,pool_size-pool_ptr);
selector:=old_setting;
s := make_string;
literal(s, scan_special, true);
flush_str(s);
+ if subtype(p)=latespecial_node then
+ flush_list(def_ref);
end;
procedure pdf_print_toks(p: pointer); {print tokens list |p|}
@@ -34005,6 +34011,21 @@
list as in \.{\\xdef} and \.{\\mark}. When marked with \.{shipout}, we keep
tokens unexpanded for now.
+Unfortunately, the |write_stream(tail):=null| done here is not a valid
+assignment in Web2C, because |null| (a.k.a.\ |min_halfword|) is a large
+negative number ($-268435455 = -@"FFFFFFF$, set in \.{tex.ch}); too
+large to fit in the {\bf short} structure element that's being assigned.
+The warning from gcc~8.5.0 was:
+
+\.{pdftex0.c: In function 'doextension':}
+\.{pdftex0.c:37849:40: warning: overflow in conversion from 'long int' to 'short int'}
+\.{changes value from '-268435455' to '1' [-Woverflow]}\hfil\break
+\.{ mem [curlist .tailfield + 1 ].hh.b0 = -268435455L ;}
+
+The correct thing to do is not immediately evident. However, for Web2C,
+it does not matter, because these lines are changed for enc\TeX, in
+\.{enctex2.ch}, and now zero is assigned, instead of |null|.
+
@<Implement \.{\\special}@>=
begin if scan_keyword("shipout") then
begin new_whatsit(latespecial_node,write_node_size); write_stream(tail):=null;
@@ -35946,6 +35967,7 @@
procedure special_out(@!p:pointer);
var old_setting:0..max_selector; {holds print |selector|}
@!k:pool_pointer; {index into |str_pool|}
+@!h:halfword;
@!q,@!r:pointer; {temporary variables for list manipulation}
@!old_mode:integer; {saved |mode|}
begin synch_h; synch_v;@/
@@ -35954,10 +35976,11 @@
if subtype(p)=latespecial_node then
begin @<Expand macros in the token list
and make |link(def_ref)| point to the result@>;
- write_tokens(p):=def_ref;
- end;
+ h:=def_ref;
+ end
+else h:=write_tokens(p);
selector:=new_string;
-show_token_list(link(write_tokens(p)),null,pool_size-pool_ptr);
+show_token_list(link(h),null,pool_size-pool_ptr);
selector:=old_setting;
str_room(1);
if cur_length<256 then
@@ -35967,6 +35990,8 @@
end;
for k:=str_start[str_ptr] to pool_ptr-1 do dvi_out(so(str_pool[k]));
pool_ptr:=str_start[str_ptr]; {erase the string}
+if subtype(p)=latespecial_node then
+ flush_list(def_ref);
end;
@ To write a token list, we must run it through \TeX's scanner, expanding
Modified: branches/stable/source/src/texk/web2c/pdftexdir/pdftex_version.h
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/pdftex_version.h 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/pdftex_version.h 2023-02-21 22:38:24 UTC (rev 903)
@@ -1 +1 @@
-#define PDFTEX_VERSION "1.40.24"
+#define PDFTEX_VERSION "1.40.25"
Modified: branches/stable/source/src/texk/web2c/pdftexdir/ptexlib.h
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/ptexlib.h 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/ptexlib.h 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
/* ptexlib.h: macros for pdfTeX library code.
-Copyright 1996-2021 Han The Thanh, <thanh at pdftex.org>
+Copyright 1996-2023 Han The Thanh, <thanh at pdftex.org>
This file is part of pdfTeX.
Modified: branches/stable/source/src/texk/web2c/pdftexdir/tounicode.c
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/tounicode.c 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/tounicode.c 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
/*
-Copyright 2006-2021 Han The Thanh, <thanh at pdftex.org>
+Copyright 2006-2023 Han The Thanh, <thanh at pdftex.org>
This file is part of pdfTeX.
Modified: branches/stable/source/src/texk/web2c/pdftexdir/wcfname.test
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/wcfname.test 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/wcfname.test 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh -vx
#
-# Copyright 2022 Japanese TeX Development Community <issue at texjp.org>
+# Copyright 2022-2023 Japanese TeX Development Community <issue at texjp.org>
# You may freely use, modify and/or distribute this file.
test -d pdftests || mkdir -p pdftests
@@ -8,12 +8,11 @@
rc=0
-TEXMFCNF=$srcdir/../kpathsea
-TEXINPUTS=pdftests:.
-export TEXMFCNF TEXINPUTS
+TEXMFCNF=$srcdir/../kpathsea; export TEXMFCNF
+TEXINPUTS=pdftests:.; export TEXINPUTS
-perl $srcdir/tests/fn-generate.perl || exit 128
-mv fn*-utf8.tex pdftests/; rm -f fn*.tex
+perl $srcdir/tests/fn-generate.perl pdftests || exit 128
+rm -f pdftests/fn*-euc.tex pdftests/fn*-sjis.tex
if [ "$COMSPEC" != "" ]; then
echo "*** We guess OS is Windows."
Modified: branches/stable/source/src/texk/web2c/pdftexdir/writet1.c
===================================================================
--- branches/stable/source/src/texk/web2c/pdftexdir/writet1.c 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/pdftexdir/writet1.c 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
/*
-Copyright 1996-2018 Han The Thanh <thanh at pdftex.org>
+Copyright 1996-2023 Han The Thanh <thanh at pdftex.org>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
@@ -1247,8 +1247,11 @@
mark_cs(standard_glyph_names[a1]);
mark_cs(standard_glyph_names[a2]);
if (fd_cur->gl_tree != NULL) {
- avl_probe(fd_cur->gl_tree, standard_glyph_names[a1]);
- avl_probe(fd_cur->gl_tree, standard_glyph_names[a2]);
+ /* base and accent characters are needed in CharSet */
+ avl_probe(fd_cur->gl_tree,
+ (void *) standard_glyph_names[a1]);
+ avl_probe(fd_cur->gl_tree,
+ (void *) standard_glyph_names[a2]);
}
break;
default:
Modified: branches/stable/source/src/texk/web2c/tests/fn-generate.perl
===================================================================
--- branches/stable/source/src/texk/web2c/tests/fn-generate.perl 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/tests/fn-generate.perl 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#!/usr/bin/env perl
#
-# Copyright 2022 Japanese TeX Development Community <issue at texjp.org>
+# Copyright 2022-2023 Japanese TeX Development Community <issue at texjp.org>
# You may freely use, modify and/or distribute this file.
use strict;
@@ -12,6 +12,7 @@
chomp;
my ($encname, $fname0, $fname1) = split ' ', $_;
+ $fname0 = "$ARGV[0]/$fname0" if @ARGV;
my $src = &make_str($encname, $fname0, $fname1);
open(my $ofh, '>', $fname0) or die "Cannot open $fname0:$!";
Modified: branches/stable/source/src/texk/web2c/web2c/configure
===================================================================
--- branches/stable/source/src/texk/web2c/web2c/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/texk/web2c/web2c/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for Web2C Tools 2023/dev.
+# Generated by GNU Autoconf 2.71 for Web2C Tools 2023.
#
# Report bugs to <tex-k at tug.org>.
#
@@ -621,8 +621,8 @@
# Identity of this package.
PACKAGE_NAME='Web2C Tools'
PACKAGE_TARNAME='web2c-tools'
-PACKAGE_VERSION='2023/dev'
-PACKAGE_STRING='Web2C Tools 2023/dev'
+PACKAGE_VERSION='2023'
+PACKAGE_STRING='Web2C Tools 2023'
PACKAGE_BUGREPORT='tex-k at tug.org'
PACKAGE_URL=''
@@ -1365,7 +1365,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures Web2C Tools 2023/dev to adapt to many kinds of systems.
+\`configure' configures Web2C Tools 2023 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1436,7 +1436,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of Web2C Tools 2023/dev:";;
+ short | recursive ) echo "Configuration of Web2C Tools 2023:";;
esac
cat <<\_ACEOF
@@ -1559,7 +1559,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-Web2C Tools configure 2023/dev
+Web2C Tools configure 2023
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -2315,7 +2315,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by Web2C Tools $as_me 2023/dev, which was
+It was created by Web2C Tools $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -8637,7 +8637,7 @@
# Define the identity of the package.
PACKAGE='web2c-tools'
- VERSION='2023/dev'
+ VERSION='2023'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -15371,7 +15371,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by Web2C Tools $as_me 2023/dev, which was
+This file was extended by Web2C Tools $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -15439,7 +15439,7 @@
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-Web2C Tools config.status 2023/dev
+Web2C Tools config.status 2023
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
Modified: branches/stable/source/src/utils/README
===================================================================
--- branches/stable/source/src/utils/README 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/utils/README 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,10 +1,10 @@
-$Id: README 64381 2022-09-14 13:18:47Z hironobu $
+$Id: README 65812 2023-02-13 01:53:20Z kakuto $
Public domain. Originally written 2005 by Karl Berry.
Extra utilities we (optionally) compile for TeX Live.
See comments in ../texk/README.
-asymptote 2.79 - checked 8mar22
+asymptote 2.85 - checked 9feb23
update to TL from CTAN, to include prebuilt doc.
see https://tug.org/texlive/build.html#asymptote
and tlpkg/bin/tl-update-asy
@@ -23,7 +23,7 @@
m-tx 0.63d - checked 14sep22
https://ctan.org/pkg/m-tx/
-pmx 2.9.8a - checked 08mar22
+pmx 3.0.0 - checked 13feb23
https://ctan.org/pkg/pmx/
ps2eps 1.70 - checked 03jul21
Modified: branches/stable/source/src/utils/configure
===================================================================
--- branches/stable/source/src/utils/configure 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/utils/configure 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for TeX Live utils 2023/dev.
+# Generated by GNU Autoconf 2.71 for TeX Live utils 2023.
#
# Report bugs to <tex-k at tug.org>.
#
@@ -610,8 +610,8 @@
# Identity of this package.
PACKAGE_NAME='TeX Live utils'
PACKAGE_TARNAME='tex-live-utils'
-PACKAGE_VERSION='2023/dev'
-PACKAGE_STRING='TeX Live utils 2023/dev'
+PACKAGE_VERSION='2023'
+PACKAGE_STRING='TeX Live utils 2023'
PACKAGE_BUGREPORT='tex-k at tug.org'
PACKAGE_URL=''
@@ -1441,7 +1441,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures TeX Live utils 2023/dev to adapt to many kinds of systems.
+\`configure' configures TeX Live utils 2023 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1512,7 +1512,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of TeX Live utils 2023/dev:";;
+ short | recursive ) echo "Configuration of TeX Live utils 2023:";;
esac
cat <<\_ACEOF
@@ -1555,11 +1555,11 @@
--enable-tex-synctex build TeX with SyncTeX support
--enable-etex compile and install e-TeX
--disable-etex-synctex build e-TeX without SyncTeX support
- --disable-ptex do not compile and install pTeX
+ --enable-ptex compile and install pTeX
--disable-ptex-synctex build pTeX without SyncTeX support
--disable-eptex do not compile and install e-pTeX
--disable-eptex-synctex build e-pTeX without SyncTeX support
- --disable-uptex do not compile and install upTeX
+ --enable-uptex compile and install upTeX
--disable-uptex-synctex build upTeX without SyncTeX support
--disable-euptex do not compile and install e-upTeX
--disable-euptex-synctex build e-upTeX without SyncTeX support
@@ -1804,7 +1804,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-TeX Live utils configure 2023/dev
+TeX Live utils configure 2023
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@@ -1927,7 +1927,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by TeX Live utils $as_me 2023/dev, which was
+It was created by TeX Live utils $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@@ -4480,7 +4480,7 @@
yes | no) :
;; #(
*) :
- enable_ptex=yes ;;
+ enable_ptex=no ;;
esac
# Check whether --enable-ptex-synctex was given.
@@ -4524,7 +4524,7 @@
yes | no) :
;; #(
*) :
- enable_uptex=yes ;;
+ enable_uptex=no ;;
esac
# Check whether --enable-uptex-synctex was given.
@@ -7016,7 +7016,7 @@
# Define the identity of the package.
PACKAGE='tex-live-utils'
- VERSION='2023/dev'
+ VERSION='2023'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@@ -8021,7 +8021,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by TeX Live utils $as_me 2023/dev, which was
+This file was extended by TeX Live utils $as_me 2023, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -8080,7 +8080,7 @@
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-TeX Live utils config.status 2023/dev
+TeX Live utils config.status 2023
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
Modified: branches/stable/source/src/version.ac
===================================================================
--- branches/stable/source/src/version.ac 2023-02-17 09:27:43 UTC (rev 902)
+++ branches/stable/source/src/version.ac 2023-02-21 22:38:24 UTC (rev 903)
@@ -1,5 +1,5 @@
-dnl $Id: version.ac 62887 2022-04-03 17:27:53Z karl $
-dnl Copyright 2016-2022 Karl Berry <tex-live at tug.org>
+dnl $Id: version.ac 65770 2023-02-09 21:26:50Z karl $
+dnl Copyright 2016-2023 Karl Berry <tex-live at tug.org>
dnl Copyright 2010-2015 Peter Breitenlohner <tex-live at tug.org>
dnl
dnl This file is free software; the copyright holder
@@ -9,4 +9,4 @@
dnl --------------------------------------------------------
dnl
dnl m4-include this file to define the current TeX Live version
-m4_define([tex_live_version], [2023/dev])
+m4_define([tex_live_version], [2023])
More information about the pdftex-commits
mailing list.