diff options
| author | Karl Berry <karl@freefriends.org> | 2023-02-09 21:26:50 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2023-02-09 21:26:50 +0000 |
| commit | 17a64c223cc48642e7e5f37094d1a75b2e111f45 (patch) | |
| tree | a68db1e94b85b3c80a685641ec24dd3a24731d8c /Build/source/texk | |
| parent | 1d76989ba8a9ed4861f7ae979511ada014cbabd7 (diff) | |
version/NEWS preparing for 2023
git-svn-id: svn://tug.org/texlive/trunk@65770 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Build/source/texk')
54 files changed, 1412 insertions, 1363 deletions
diff --git a/Build/source/texk/README b/Build/source/texk/README index 821a390e432..57babeb2cf3 100644 --- a/Build/source/texk/README +++ b/Build/source/texk/README @@ -1,5 +1,5 @@ $Id$ -Copyright 2006-2022 TeX Users Group. +Copyright 2006-2023 TeX Users Group. You may freely use, modify and/or distribute this file. This TeX Live directory contains the programs that use the kpathsea @@ -63,7 +63,7 @@ dvipos - maintained here, by us dvipsk - maintained here, by us -dvisvgm 2.14 - checked 29aug22 +dvisvgm 3.0.2 - checked 1feb23 https://dvisvgm.de/Downloads/ https://github.com/mgieseki/dvisvgm https://ctan.org/pkg/dvisvgm diff --git a/Build/source/texk/bibtex-x/configure b/Build/source/texk/bibtex-x/configure index 0d8d462e130..77db80e55a3 100755 --- a/Build/source/texk/bibtex-x/configure +++ b/Build/source/texk/bibtex-x/configure @@ -14550,7 +14550,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h diff --git a/Build/source/texk/configure b/Build/source/texk/configure index 950058142e7..5ca4f617800 100755 --- a/Build/source/texk/configure +++ b/Build/source/texk/configure @@ -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@tug.org>. # @@ -610,8 +610,8 @@ MAKEFLAGS= # 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@tug.org' PACKAGE_URL='' @@ -1441,7 +1441,7 @@ if test "$ac_init_help" = "long"; then # 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 @@ fi 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 @@ Optional Features: --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 @@ fi 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 @@ cat >config.log <<_ACEOF 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 @@ case $enable_ptex in #( yes | no) : ;; #( *) : - enable_ptex=yes ;; + enable_ptex=no ;; esac # Check whether --enable-ptex-synctex was given. @@ -4524,7 +4524,7 @@ case $enable_uptex in #( yes | no) : ;; #( *) : - enable_uptex=yes ;; + enable_uptex=no ;; esac # Check whether --enable-uptex-synctex was given. @@ -7016,7 +7016,7 @@ fi # 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 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # 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 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ 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\\" diff --git a/Build/source/texk/dtl/configure b/Build/source/texk/dtl/configure index 40f4d505c6a..2279f8a2930 100755 --- a/Build/source/texk/dtl/configure +++ b/Build/source/texk/dtl/configure @@ -14417,7 +14417,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h kpse_save_CPPFLAGS=$CPPFLAGS diff --git a/Build/source/texk/dvidvi/configure b/Build/source/texk/dvidvi/configure index 586796f6cd7..9800fa5a829 100755 --- a/Build/source/texk/dvidvi/configure +++ b/Build/source/texk/dvidvi/configure @@ -14119,7 +14119,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h # We don't use libpathsea, so add '-DNO_DEBUG' not to overload fopen. diff --git a/Build/source/texk/dviout-util/configure b/Build/source/texk/dviout-util/configure index 00def8974d0..fd93717816b 100755 --- a/Build/source/texk/dviout-util/configure +++ b/Build/source/texk/dviout-util/configure @@ -14124,7 +14124,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h kpse_save_CPPFLAGS=$CPPFLAGS diff --git a/Build/source/texk/dvipdfm-x/ChangeLog b/Build/source/texk/dvipdfm-x/ChangeLog index 76720ecc08a..cbb89c2e9b1 100644 --- a/Build/source/texk/dvipdfm-x/ChangeLog +++ b/Build/source/texk/dvipdfm-x/ChangeLog @@ -1,3 +1,9 @@ +2023-02-09 Karl Berry <karl@freefriends.org> + + * xbb.c (show_version), + * configure.ac, + * dvipdfmx.c (show_version): copyright 2023. + 2022-07-10 TANAKA Takuji <ttk@t-lab.opal.ne.jp> * {dvipdfmx,spc_pdfm}.c, dpxconf.{c,h}, man/dvipdfmx.1: diff --git a/Build/source/texk/dvipdfm-x/configure.ac b/Build/source/texk/dvipdfm-x/configure.ac index b12cf018d7a..3caa2a4c995 100644 --- a/Build/source/texk/dvipdfm-x/configure.ac +++ b/Build/source/texk/dvipdfm-x/configure.ac @@ -1,7 +1,7 @@ dnl $Id$ dnl Process this file with autoconf to produce a configure script. dnl -dnl Copyright 2016-2020 Karl Berry <tex-live@tug.org> +dnl Copyright 2016-2023 Karl Berry <tex-live@tug.org> dnl Copyright 2009-2015 Peter Breitenlohner <tex-live@tug.org> dnl dnl This file is free software; the copyright holder diff --git a/Build/source/texk/dvipdfm-x/dvipdfmx.c b/Build/source/texk/dvipdfm-x/dvipdfmx.c index 3b066a3f1d6..ec397db4cf2 100644 --- a/Build/source/texk/dvipdfm-x/dvipdfmx.c +++ b/Build/source/texk/dvipdfm-x/dvipdfmx.c @@ -2,7 +2,7 @@ DVIPDFMx, an eXtended version of DVIPDFM by Mark A. Wicks. - Copyright (C) 2002-2021 by Jin-Hwan Cho, Matthias Franz, and Shunsaku Hirata, + Copyright (C) 2002-2023 by Jin-Hwan Cho, Matthias Franz, and Shunsaku Hirata, the DVIPDFMx project team. Copyright (c) 2006 SIL. (xdvipdfmx extensions for XeTeX support) @@ -175,8 +175,8 @@ show_version (void) if (*my_name == 'x') printf ("an extended version of DVIPDFMx, which in turn was\n"); printf ("an extended version of dvipdfm-0.13.2c developed by Mark A. Wicks.\n"); - printf ("\nCopyright (C) 2002-2021 the DVIPDFMx project team\n"); - printf ("Copyright (C) 2006-2021 SIL International.\n"); + printf ("\nCopyright (C) 2002-2023 the DVIPDFMx project team\n"); + printf ("Copyright (C) 2006-2023 SIL International.\n"); printf ("\nThis is free software; you can redistribute it and/or modify\n"); printf ("it under the terms of the GNU General Public License as published by\n"); printf ("the Free Software Foundation; either version 2 of the License, or\n"); @@ -1182,7 +1182,7 @@ main (int argc, char *argv[]) /* PDF trailer ID. */ if (!has_id) { #define PRODUCER \ -"%s-%s, Copyright 2002-2021 by Jin-Hwan Cho, Matthias Franz, and Shunsaku Hirata" +"%s-%s, Copyright 2002-2023 by Jin-Hwan Cho, Matthias Franz, and Shunsaku Hirata" char producer[256]; sprintf(producer, PRODUCER, my_name, VERSION); diff --git a/Build/source/texk/dvipdfm-x/xbb.c b/Build/source/texk/dvipdfm-x/xbb.c index 00b30501680..e21c232d30c 100644 --- a/Build/source/texk/dvipdfm-x/xbb.c +++ b/Build/source/texk/dvipdfm-x/xbb.c @@ -1,5 +1,5 @@ /* This is extractbb, a bounding box extraction program. - Copyright (C) 2008-2021 by Jin-Hwan Cho and Matthias Franz + Copyright (C) 2008-2023 by Jin-Hwan Cho and Matthias Franz and the dvipdfmx project team. This program is free software; you can redistribute it and/or modify @@ -52,7 +52,7 @@ static int Include_Page = 1; static void show_version(void) { fprintf (stdout, "\nThis is %s Version " VERSION "\n", my_name); - fprintf (stdout, "\nCopyright (C) 2008-2021 by Jin-Hwan Cho and Matthias Franz\n"); + fprintf (stdout, "\nCopyright (C) 2008-2023 by Jin-Hwan Cho and Matthias Franz\n"); fprintf (stdout, "\nThis is free software; you can redistribute it and/or modify\n"); fprintf (stdout, "it under the terms of the GNU General Public License as published by\n"); fprintf (stdout, "the Free Software Foundation; either version 2 of the License, or\n"); diff --git a/Build/source/texk/dvipsk/ChangeLog b/Build/source/texk/dvipsk/ChangeLog index fd8a0d3bd4a..56d2d2710d0 100644 --- a/Build/source/texk/dvipsk/ChangeLog +++ b/Build/source/texk/dvipsk/ChangeLog @@ -1,3 +1,12 @@ +2022-01-18 Karl Berry <karl@freefriends.org> + + * NEWS, + * afm2tfm.c, + * dvips.c, + * dvips.h, + * dvips.texi, + * configure.ac: version 2023.1 and copyright 2023. + 2022-09-02 TANAKA Takuji <ttk@t-lab.opal.ne.jp> * dvips.c: diff --git a/Build/source/texk/dvipsk/NEWS b/Build/source/texk/dvipsk/NEWS index 8fff2070587..35a57719b0f 100644 --- a/Build/source/texk/dvipsk/NEWS +++ b/Build/source/texk/dvipsk/NEWS @@ -1,6 +1,9 @@ $Id$ This file records noteworthy changes. (Public domain.) +dvips 2023.1 (TeX Live 2023): + Check --help and --version early to avoid looking for texmf.cnf. + dvips 2022.1 (TeX Live 2022): New option (and config file directive) -landscaperotate: try to automatically match rotated page content and paper sizes; in the past, diff --git a/Build/source/texk/dvipsk/afm2tfm.c b/Build/source/texk/dvipsk/afm2tfm.c index 80cd5e3c511..1c2a3f52637 100644 --- a/Build/source/texk/dvipsk/afm2tfm.c +++ b/Build/source/texk/dvipsk/afm2tfm.c @@ -1562,9 +1562,9 @@ writevpl(void) static void version(FILE *f) { - fputs ("afm2tfm(k) (dvips(k) 2022.1) 8.4\n", f); + fputs ("afm2tfm(k) (dvips(k) 2023.1) 8.4\n", f); fprintf (f, "%s\n", kpathsea_version_string); - fputs ("Copyright 2022 Radical Eye Software.\n\ + fputs ("Copyright 2023 Radical Eye Software.\n\ There is NO warranty. You may redistribute this software\n\ under the terms of the GNU General Public License\n\ and the Dvips copyright.\n\ diff --git a/Build/source/texk/dvipsk/configure b/Build/source/texk/dvipsk/configure index 9b531c91603..54f8997186b 100755 --- a/Build/source/texk/dvipsk/configure +++ b/Build/source/texk/dvipsk/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.71 for dvipsk (TeX Live) 2022.1. +# Generated by GNU Autoconf 2.71 for dvipsk (TeX Live) 2023.1. # # Report bugs to <tex-k@tug.org>. # @@ -629,8 +629,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='dvipsk (TeX Live)' PACKAGE_TARNAME='dvipsk--tex-live-' -PACKAGE_VERSION='2022.1' -PACKAGE_STRING='dvipsk (TeX Live) 2022.1' +PACKAGE_VERSION='2023.1' +PACKAGE_STRING='dvipsk (TeX Live) 2023.1' PACKAGE_BUGREPORT='tex-k@tug.org' PACKAGE_URL='' @@ -1375,7 +1375,7 @@ if test "$ac_init_help" = "long"; then # 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 dvipsk (TeX Live) 2022.1 to adapt to many kinds of systems. +\`configure' configures dvipsk (TeX Live) 2023.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1447,7 +1447,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of dvipsk (TeX Live) 2022.1:";; + short | recursive ) echo "Configuration of dvipsk (TeX Live) 2023.1:";; esac cat <<\_ACEOF @@ -1566,7 +1566,7 @@ fi test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -dvipsk (TeX Live) configure 2022.1 +dvipsk (TeX Live) configure 2023.1 generated by GNU Autoconf 2.71 Copyright (C) 2021 Free Software Foundation, Inc. @@ -2322,7 +2322,7 @@ cat >config.log <<_ACEOF This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by dvipsk (TeX Live) $as_me 2022.1, which was +It was created by dvipsk (TeX Live) $as_me 2023.1, which was generated by GNU Autoconf 2.71. Invocation command line was $ $0$ac_configure_args_raw @@ -8645,7 +8645,7 @@ fi # Define the identity of the package. PACKAGE='dvipsk--tex-live-' - VERSION='2022.1' + VERSION='2023.1' printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h @@ -14453,7 +14453,7 @@ fi -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h kpse_save_CPPFLAGS=$CPPFLAGS @@ -14863,7 +14863,7 @@ Usage: $0 [OPTIONS] Report bugs to <bug-libtool@gnu.org>." lt_cl_version="\ -dvipsk (TeX Live) config.lt 2022.1 +dvipsk (TeX Live) config.lt 2023.1 configured by $0, generated by GNU Autoconf 2.71. Copyright (C) 2011 Free Software Foundation, Inc. @@ -16468,7 +16468,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by dvipsk (TeX Live) $as_me 2022.1, which was +This file was extended by dvipsk (TeX Live) $as_me 2023.1, which was generated by GNU Autoconf 2.71. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -16536,7 +16536,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config='$ac_cs_config_escaped' ac_cs_version="\\ -dvipsk (TeX Live) config.status 2022.1 +dvipsk (TeX Live) config.status 2023.1 configured by $0, generated by GNU Autoconf 2.71, with options \\"\$ac_cs_config\\" diff --git a/Build/source/texk/dvipsk/configure.ac b/Build/source/texk/dvipsk/configure.ac index c98785b14c3..510e698b7ea 100644 --- a/Build/source/texk/dvipsk/configure.ac +++ b/Build/source/texk/dvipsk/configure.ac @@ -1,14 +1,14 @@ dnl $Id$ dnl Process this file with autoconf to produce a configure script. dnl -dnl Copyright 2016-2022 Karl Berry <tex-live@tug.org> +dnl Copyright 2016-2023 Karl Berry <tex-live@tug.org> dnl Copyright 2009-2015 Peter Breitenlohner <tex-live@tug.org> dnl dnl This file is free software; the copyright holder dnl gives unlimited permission to copy and/or distribute it, dnl with or without modifications, as long as this notice is preserved. dnl -AC_INIT([dvipsk (TeX Live)], [2022.1], [tex-k@tug.org]) +AC_INIT([dvipsk (TeX Live)], [2023.1], [tex-k@tug.org]) AC_PREREQ([2.65]) AC_CONFIG_SRCDIR([dvips.c]) AC_CONFIG_AUX_DIR([../../build-aux]) diff --git a/Build/source/texk/dvipsk/dvips.h b/Build/source/texk/dvipsk/dvips.h index 8f0603826bc..b97994548f2 100644 --- a/Build/source/texk/dvipsk/dvips.h +++ b/Build/source/texk/dvipsk/dvips.h @@ -1,5 +1,5 @@ /* $Id$ - * Copyright 1986-2022 Tomas Rokicki. + * Copyright 1986-2023 Tomas Rokicki. * This is dvips, a freely redistributable PostScript driver * for dvi files. You may freely use, modify and/or distribute this * program or any portion thereof. @@ -15,7 +15,7 @@ #define CD_IDX(i) ((i>=MAX_2BYTES_CODE ? MAX_2BYTES_CODE : i)) #define BANNER \ -"This is dvips(k) " VERSION " (" TL_VERSION ") Copyright 2022 Radical Eye Software" +"This is dvips(k) " VERSION " (" TL_VERSION ") Copyright 2023 Radical Eye Software" #define BANNER2 "(www.radicaleye.com)" #ifdef KPATHSEA #include "config.h" diff --git a/Build/source/texk/dvipsk/dvips.info b/Build/source/texk/dvipsk/dvips.info index 34086bc9dc3..93020bf9632 100644 --- a/Build/source/texk/dvipsk/dvips.info +++ b/Build/source/texk/dvipsk/dvips.info @@ -1,6 +1,6 @@ -This is dvips.info, produced by makeinfo version 6.8 from dvips.texi. +This is dvips.info, produced by makeinfo version 6.5 from dvips.texi. -This manual documents Dvips version 2022.1 (January 2022), a program to +This manual documents Dvips version 2023.1 (February 2022), a program to translate a DVI file into PostScript. You may freely use, modify and/or distribute this file. INFO-DIR-SECTION TeX @@ -16,7 +16,7 @@ File: dvips.info, Node: Top, Next: Why Dvips, Up: (dir) Dvips ***** -This manual documents Dvips version 2022.1 (January 2022), a program to +This manual documents Dvips version 2023.1 (February 2022), a program to translate a DVI file into PostScript. You may freely use, modify and/or distribute this file. @@ -4754,88 +4754,83 @@ Index Tag Table: -Node: Top520 -Node: Why Dvips1269 -Node: Installation3852 -Node: config.ps installation4787 -Node: PostScript font installation7394 -Node: Ghostscript installation8314 -Node: Diagnosing problems9253 -Node: Debug options10344 -Node: No output11348 -Node: Small or inverted12814 -Node: Printer errors13532 -Node: Long documents fail14864 -Node: Including graphics fails15205 -Node: Invoking Dvips16444 -Node: Basic usage17035 -Node: Command-line options18033 -Node: Option summary18481 -Node: Option details20756 -Node: Environment variables41579 -Node: Config files44440 -Node: Configuration file searching45110 -Node: Configuration file commands48307 -Node: Paper size and landscape56512 -Node: papersize special58137 -Node: Config file paper sizes59844 -Node: Paper trays64867 -Node: Interaction with PostScript66201 -Node: PostScript figures66854 -Node: Bounding box67580 -Node: \includegraphics70952 -Node: EPSF macros73244 -Node: EPSF scaling75212 -Node: EPSF clipping77782 -Node: psfile special78424 -Node: Dynamic creation of graphics80816 -Node: Fonts in figures82134 -Node: Header files83784 -Node: Including headers from TeX84990 -Node: Including headers from the command line87028 -Node: Headers and memory usage88127 -Node: Literal PS89338 -Node: " special89920 -Node: ps special90661 -Node: Literal headers92159 -Node: PostScript hooks92868 -Node: Literal examples94964 -Node: Hypertext96418 -Node: Hypertext caveats97592 -Node: Hypertext specials101720 -Node: PostScript fonts104354 -Node: Font concepts105471 -Node: Metric files106701 -Node: Glyph files109481 -Node: Virtual fonts111840 -Node: Encodings113995 -Node: Bitmap font encodings116397 -Node: PostScript typesetting118927 -Node: Making a font available122024 -Node: Invoking afm2tfm127058 -Node: Changing font encodings128078 -Node: Changing TeX encodings128869 -Node: Changing PostScript encodings129971 -Node: Changing both encodings131315 -Node: Reencoding with Afm2tfm131989 -Node: Encoding file format135092 -Node: Special font effects139296 -Node: Afm2tfm options141556 -Node: psfonts.map145081 -Node: Color149811 -Node: Color macro files150855 -Node: User-definable colors154065 -Node: Color subtleties155341 -Node: Ted Turner156993 -Node: Color device configuration158218 -Node: Color support details160662 -Node: Color specifications161040 -Node: Color specials162444 -Node: Index164573 +Node: Top521 +Node: Why Dvips1271 +Node: Installation3854 +Node: config.ps installation4789 +Node: PostScript font installation7396 +Node: Ghostscript installation8316 +Node: Diagnosing problems9255 +Node: Debug options10346 +Node: No output11350 +Node: Small or inverted12816 +Node: Printer errors13534 +Node: Long documents fail14866 +Node: Including graphics fails15207 +Node: Invoking Dvips16446 +Node: Basic usage17037 +Node: Command-line options18035 +Node: Option summary18483 +Node: Option details20758 +Node: Environment variables41581 +Node: Config files44442 +Node: Configuration file searching45112 +Node: Configuration file commands48309 +Node: Paper size and landscape56514 +Node: papersize special58139 +Node: Config file paper sizes59846 +Node: Paper trays64869 +Node: Interaction with PostScript66203 +Node: PostScript figures66856 +Node: Bounding box67582 +Node: \includegraphics70954 +Node: EPSF macros73246 +Node: EPSF scaling75214 +Node: EPSF clipping77784 +Node: psfile special78426 +Node: Dynamic creation of graphics80818 +Node: Fonts in figures82136 +Node: Header files83786 +Node: Including headers from TeX84992 +Node: Including headers from the command line87030 +Node: Headers and memory usage88129 +Node: Literal PS89340 +Node: " special89922 +Node: ps special90663 +Node: Literal headers92161 +Node: PostScript hooks92870 +Node: Literal examples94966 +Node: Hypertext96420 +Node: Hypertext caveats97594 +Node: Hypertext specials101722 +Node: PostScript fonts104356 +Node: Font concepts105473 +Node: Metric files106703 +Node: Glyph files109483 +Node: Virtual fonts111842 +Node: Encodings113997 +Node: Bitmap font encodings116399 +Node: PostScript typesetting118929 +Node: Making a font available122026 +Node: Invoking afm2tfm127060 +Node: Changing font encodings128080 +Node: Changing TeX encodings128871 +Node: Changing PostScript encodings129973 +Node: Changing both encodings131317 +Node: Reencoding with Afm2tfm131991 +Node: Encoding file format135094 +Node: Special font effects139298 +Node: Afm2tfm options141558 +Node: psfonts.map145083 +Node: Color149813 +Node: Color macro files150857 +Node: User-definable colors154067 +Node: Color subtleties155343 +Node: Ted Turner156995 +Node: Color device configuration158220 +Node: Color support details160664 +Node: Color specifications161042 +Node: Color specials162446 +Node: Index164575 End Tag Table - - -Local Variables: -coding: utf-8 -End: diff --git a/Build/source/texk/dvipsk/dvips.texi b/Build/source/texk/dvipsk/dvips.texi index ee493c75cef..4716e997d0b 100644 --- a/Build/source/texk/dvipsk/dvips.texi +++ b/Build/source/texk/dvipsk/dvips.texi @@ -2,8 +2,8 @@ @setfilename dvips.info @settitle Dvips: A DVI-to-PostScript translator -@set version 2022.1 -@set month-year January 2022 +@set version 2023.1 +@set month-year February 2022 @copying This manual documents Dvips version @value{version} diff --git a/Build/source/texk/kpathsea/ChangeLog b/Build/source/texk/kpathsea/ChangeLog index 602513759b5..2515064b087 100644 --- a/Build/source/texk/kpathsea/ChangeLog +++ b/Build/source/texk/kpathsea/ChangeLog @@ -1,3 +1,11 @@ +2023-02-09 Karl Berry <karl@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@freefriends.org> * doc/kpathsea.texi (Supported file formats): add .lua (LUAINPUTS). diff --git a/Build/source/texk/kpathsea/NEWS b/Build/source/texk/kpathsea/NEWS index 497abb858de..322fe14bd26 100644 --- a/Build/source/texk/kpathsea/NEWS +++ b/Build/source/texk/kpathsea/NEWS @@ -1,6 +1,10 @@ $Id$ 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.) diff --git a/Build/source/texk/kpathsea/c-auto.in b/Build/source/texk/kpathsea/c-auto.in index 1877cfe725e..d011f8d24f1 100644 --- a/Build/source/texk/kpathsea/c-auto.in +++ b/Build/source/texk/kpathsea/c-auto.in @@ -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 diff --git a/Build/source/texk/kpathsea/configure b/Build/source/texk/kpathsea/configure index adf88b5566e..64cc225cb5c 100755 --- a/Build/source/texk/kpathsea/configure +++ b/Build/source/texk/kpathsea/configure @@ -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@tug.org>. # @@ -621,8 +621,8 @@ MAKEFLAGS= # 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@tug.org' PACKAGE_URL='' @@ -1376,7 +1376,7 @@ if test "$ac_init_help" = "long"; then # 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 @@ fi 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 @@ fi 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 @@ cat >config.log <<_ACEOF 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,14 +3091,14 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu -KPSEVERSION=6.3.5/dev +KPSEVERSION=6.3.5 KPSE_LT_VERSINFO=9:5:3 - WEB2CVERSION=" (TeX Live 2023/dev)" + WEB2CVERSION=" (TeX Live 2023)" am__api_version='1.16' @@ -8663,7 +8663,7 @@ fi # 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 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # 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 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ 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\\" diff --git a/Build/source/texk/kpathsea/doc/kpathsea.info b/Build/source/texk/kpathsea/doc/kpathsea.info index 5db4b49c732..32cddefe1b5 100644 --- a/Build/source/texk/kpathsea/doc/kpathsea.info +++ b/Build/source/texk/kpathsea/doc/kpathsea.info @@ -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 @@ Kpathsea library **************** 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,21 +61,21 @@ File: kpathsea.info, Node: Introduction, Next: unixtex.ftp, Prev: Top, Up: T 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. 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 @@ See accompanying files for the text of the GNU licenses, or <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 @@ File: kpathsea.info, Node: History, Up: Introduction 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 @@ February 1990, but I may have done some work before then. In any case, 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,14 +159,14 @@ because of the path searching. Autoconf was being developed by David 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. 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,18 +175,18 @@ path-searching features in Kpathsea that I plan to, driven beyond my 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 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 @@ respect to the overall TeX Live build, where Kpathsea is now maintained. 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 @@ released as a separate packages. Their sources are now maintained as 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,52 +234,52 @@ File: kpathsea.info, Node: Security, Next: TeX directory structure, Prev: uni ********** 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. 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 @@ from <https://ctan.org/pkg/tds> (*note unixtex.ftp::). 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 @@ File: kpathsea.info, Node: Searching overview, Next: Path sources, Up: Path s 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,17 +413,17 @@ specification is matched against the contents of the database. If the database does not exist, or does not apply to this path element, or contains no matches, the filesystem is searched (if this was -not forbidden by 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 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,32 +435,32 @@ needed on a particular run. 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. 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 @@ File: kpathsea.info, Node: Path sources, Next: Path expansion, Prev: Searchin 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 @@ expansion::). * 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 @@ File: kpathsea.info, Node: Config files, Up: Path sources 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 @@ Here is a configuration file fragment illustrating most of these points: 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 @@ File: kpathsea.info, Node: Path expansion, Next: Casefolding search, Prev: Pa 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 @@ File: kpathsea.info, Node: Default expansion, Next: Variable expansion, Up: P ----------------------- 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 @@ unpredictable results, so installers beware.) 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 @@ then the final value used for searching will be: /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 @@ trailing ‘:’ ignored in the first case and expanded in the second: /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 @@ File: kpathsea.info, Node: Variable expansion, Next: Tilde expansion, Prev: D 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 @@ File: kpathsea.info, Node: Tilde expansion, Next: Brace expansion, Prev: Vari 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 @@ File: kpathsea.info, Node: Brace expansion, Next: KPSE_DOT expansion, Prev: T 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 @@ Two or more consecutive slashes in a path element following a directory D is replaced by all subdirectories of D: first those subdirectories directly under D, then the subsubdirectories under those, and so on. At each level, the order in which the directories are searched is -unspecified. (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 @@ it. 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 @@ path element allows for checking the filesystem, a second check is made 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 @@ documents between case-insensitive (file)systems and case-sensitive 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 @@ Kpathsea behavior. 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 @@ mismatches are rare to begin with, and name collisions with respect only 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,30 +961,30 @@ steps: 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. 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 @@ Kpathsea goes to some lengths to minimize disk accesses for searches 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 @@ to the files listed in ‘ls-R’. 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 @@ File: kpathsea.info, Node: Filename aliases, Next: Database format, Prev: ls- 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 @@ File: kpathsea.info, Node: Database format, Prev: Filename aliases, Up: Filen 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,21 +1158,21 @@ the ‘-R’ option, as follows. 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: 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 @@ accepted. * 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 @@ filename, and returns the first file found. 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,151 +1330,151 @@ filename, and returns the first file found. 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 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 @@ File: kpathsea.info, Node: Auxiliary tasks, Next: Standard options, Prev: Spe 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 @@ File: kpathsea.info, Node: Standard options, Prev: Auxiliary tasks, Up: Invok 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 @@ particularly). 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 @@ finding files (see the next section). Some also define additional 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 @@ searches are the exception, as described in the next section). 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 @@ File: kpathsea.info, Node: Glyph lookup, Next: Suppressing warnings, Prev: Fi ================ 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 @@ successful lookup. 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 @@ File: kpathsea.info, Node: Basic glyph lookup, Next: Fontmap, Up: Glyph looku 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 @@ File: kpathsea.info, Node: Fontmap, Next: Fallback font, Prev: Basic glyph lo ------------- 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 @@ fonts equivalent. 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 @@ File: kpathsea.info, Node: Fallback font, Prev: Fontmap, Up: Glyph lookup ------------------- 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 @@ Kpathsea provides a way to suppress selected usually-harmless warnings; 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 @@ diagnostics to standard error. 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 @@ change the defaults are: --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,34 +2364,34 @@ translation. 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 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 @@ File: kpathsea.info, Node: Calling sequence, Next: Program-specific files, Pr 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 @@ this: 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. - - 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). + '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). 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 @@ Many programs will need to find some configuration files. Kpathsea 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 @@ File: kpathsea.info, Node: Programming with config files, Prev: Program-specif 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 @@ File: kpathsea.info, Node: Bug checklist, Next: Mailing lists, Up: Reporting 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@tug.org>. @@ -2616,60 +2616,60 @@ known (*note Common problems::). 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 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 @@ File: kpathsea.info, Node: Debugging, Next: Logging, Prev: Mailing lists, Up 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 @@ it easily. For example, in Bourne-compatible shells: (*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 @@ search. This may be useful in finding good candidates for deletion when 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 @@ The second word is the filename. 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 @@ execution, ... * 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 @@ If a program complains it cannot find fonts (or other input files), any 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 @@ debugging options helpful. *Note Debugging::. 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 @@ If your program takes an excessively long time to find fonts or other 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 @@ quality of output. Some DVI-to-whatever programs, such as Dvips, try to 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 @@ configuration file: 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 @@ names for most devices (additional submissions are welcome). 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 @@ running a normal input file, the problem is usually a compiler bug 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 @@ also recommend reporting a bug to the GCC mailing list; see *note 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 @@ Index (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 @@ Index * 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 @@ Index * 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 @@ Index 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: diff --git a/Build/source/texk/kpathsea/doc/kpathsea.texi b/Build/source/texk/kpathsea/doc/kpathsea.texi index ffbc12043ca..ce95244b31a 100644 --- a/Build/source/texk/kpathsea/doc/kpathsea.texi +++ b/Build/source/texk/kpathsea/doc/kpathsea.texi @@ -2,13 +2,13 @@ @setfilename kpathsea.info @settitle Kpathsea: A library for path searching -@set version 6.3.4 -@set month-year December 2022 +@set version 6.3.5 +@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 diff --git a/Build/source/texk/kpathsea/kpsewhich.c b/Build/source/texk/kpathsea/kpsewhich.c index 63a72322456..32f83b00af7 100644 --- a/Build/source/texk/kpathsea/kpsewhich.c +++ b/Build/source/texk/kpathsea/kpsewhich.c @@ -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 @@ read_command_line (kpathsea kpse, int argc, string *argv) } 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"); diff --git a/Build/source/texk/kpathsea/version.ac b/Build/source/texk/kpathsea/version.ac index e66e4404de7..9a42df5dcd3 100644 --- a/Build/source/texk/kpathsea/version.ac +++ b/Build/source/texk/kpathsea/version.ac @@ -1,5 +1,5 @@ dnl $Id$ -dnl Copyright 2016-2022 Karl Berry <tex-live@tug.org> +dnl Copyright 2016-2023 Karl Berry <tex-live@tug.org> dnl Copyright 2011-2015 Peter Breitenlohner <tex-live@tug.org> dnl dnl This file is free software; the copyright holder @@ -20,4 +20,4 @@ dnl append "dev", to distinguish binaries built between releases. 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]) diff --git a/Build/source/texk/makeindexk/configure b/Build/source/texk/makeindexk/configure index 8a0c56923a5..1e9f8029fbc 100755 --- a/Build/source/texk/makeindexk/configure +++ b/Build/source/texk/makeindexk/configure @@ -14114,7 +14114,7 @@ ac_config_headers="$ac_config_headers c-auto.h:c-auto.in" -printf "%s\n" "#define TEX_LIVE_VERSION \"2023/dev\"" >>confdefs.h +printf "%s\n" "#define TEX_LIVE_VERSION \"2023\"" >>confdefs.h ac_fn_c_check_header_compile "$LINENO" "ctype.h" "ac_cv_header_ctype_h" "$ac_includes_default" diff --git a/Build/source/texk/mendexk/COPYRIGHT b/Build/source/texk/mendexk/COPYRIGHT index 02646827031..d9c728b80fb 100644 --- a/Build/source/texk/mendexk/COPYRIGHT +++ b/Build/source/texk/mendexk/COPYRIGHT @@ -1,5 +1,5 @@ Copyright (C) 1995 ASCII Corporation, 2009 ASCII MEDIA WORKS -Copyright (C) 2017-2022 Japanese TeX Development Community +Copyright (C) 2017-2023 Japanese TeX Development Community All rights reserved. Redistribution and use in source and binary forms, with or without diff --git a/Build/source/texk/mendexk/configure b/Build/source/texk/mendexk/configure index c7f4a8c2763..3bc57c6af23 100755 --- a/Build/source/texk/mendexk/configure +++ b/Build/source/texk/mendexk/configure @@ -14116,7 +14116,7 @@ ac_config_headers="$ac_config_headers c-auto.h:c-auto.in" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking if C99 variadic macros are supported" >&5 diff --git a/Build/source/texk/mendexk/main.c b/Build/source/texk/mendexk/main.c index 51fdd403d9f..60d8aec6102 100644 --- a/Build/source/texk/mendexk/main.c +++ b/Build/source/texk/mendexk/main.c @@ -177,7 +177,7 @@ int main(int argc, char **argv) default: fprintf(stderr,"mendex - Japanese index processor, %s (%s) (%s).\n",VERSION, get_enc_string(), TL_VERSION); - fprintf(stderr," Copyright 2009 ASCII MEDIA WORKS, 2017-2022 Japanese TeX Development Community\n"); + fprintf(stderr," Copyright 2009 ASCII MEDIA WORKS, 2017-2023 Japanese TeX Development Community\n"); fprintf(stderr,"usage:\n"); fprintf(stderr,"%% mendex [-ilqrcgfEJSU] [-s sty] [-d dic] [-o ind] [-t log] [-p no] [-I enc] [--[no-]guess-input-enc] [--] [idx0 idx1 ...]\n"); fprintf(stderr,"options:\n"); diff --git a/Build/source/texk/ps2pk/configure b/Build/source/texk/ps2pk/configure index b3d0f0ea560..f3bf3705503 100755 --- a/Build/source/texk/ps2pk/configure +++ b/Build/source/texk/ps2pk/configure @@ -14351,7 +14351,7 @@ ac_config_headers="$ac_config_headers c-auto.h:c-auto.in" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h for ac_prog in kpsewhich diff --git a/Build/source/texk/ptexenc/ChangeLog b/Build/source/texk/ptexenc/ChangeLog index c3a94f55a0c..5ce8ef83fba 100644 --- a/Build/source/texk/ptexenc/ChangeLog +++ b/Build/source/texk/ptexenc/ChangeLog @@ -1,3 +1,7 @@ +2023-02-09 Karl Berry <karl@tug.org> + + * version.ac: remove /dev, for TL23. + 2023-01-01 TANAKA Takuji <ttk@t-lab.opal.ne.jp> * ptexenc.c, ptexenc/ptexenc.h: diff --git a/Build/source/texk/ptexenc/c-auto.in b/Build/source/texk/ptexenc/c-auto.in index 40e4044f9e7..4ed61a5d3ef 100644 --- a/Build/source/texk/ptexenc/c-auto.in +++ b/Build/source/texk/ptexenc/c-auto.in @@ -6,7 +6,7 @@ #define PTEXENC_C_AUTO_H /* ptexenc: the version string. */ -#define PTEXENCVERSION "ptexenc version 1.4.2/dev" +#define PTEXENCVERSION "ptexenc version 1.4.3" /* Define to 1 if the `closedir' function returns void instead of int. */ #undef CLOSEDIR_VOID diff --git a/Build/source/texk/ptexenc/configure b/Build/source/texk/ptexenc/configure index 838e8791635..cb57cabeb09 100755 --- a/Build/source/texk/ptexenc/configure +++ b/Build/source/texk/ptexenc/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.71 for ptexenc 1.4.2/dev. +# Generated by GNU Autoconf 2.71 for ptexenc 1.4.3. # # Report bugs to <tex-k@tug.org>. # @@ -629,8 +629,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='ptexenc' PACKAGE_TARNAME='ptexenc' -PACKAGE_VERSION='1.4.2/dev' -PACKAGE_STRING='ptexenc 1.4.2/dev' +PACKAGE_VERSION='1.4.3' +PACKAGE_STRING='ptexenc 1.4.3' PACKAGE_BUGREPORT='tex-k@tug.org' PACKAGE_URL='' @@ -1375,7 +1375,7 @@ if test "$ac_init_help" = "long"; then # 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 ptexenc 1.4.2/dev to adapt to many kinds of systems. +\`configure' configures ptexenc 1.4.3 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1446,7 +1446,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of ptexenc 1.4.2/dev:";; + short | recursive ) echo "Configuration of ptexenc 1.4.3:";; esac cat <<\_ACEOF @@ -1566,7 +1566,7 @@ fi test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -ptexenc configure 1.4.2/dev +ptexenc configure 1.4.3 generated by GNU Autoconf 2.71 Copyright (C) 2021 Free Software Foundation, Inc. @@ -2090,7 +2090,7 @@ cat >config.log <<_ACEOF This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by ptexenc $as_me 1.4.2/dev, which was +It was created by ptexenc $as_me 1.4.3, which was generated by GNU Autoconf 2.71. Invocation command line was $ $0$ac_configure_args_raw @@ -2850,10 +2850,10 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu -PTEXENCVERSION=1.4.2/dev +PTEXENCVERSION=1.4.3 -PTEXENC_LT_VERSINFO=5:2:4 +PTEXENC_LT_VERSINFO=5:3:4 am__api_version='1.16' @@ -8418,7 +8418,7 @@ fi # Define the identity of the package. PACKAGE='ptexenc' - VERSION='1.4.2/dev' + VERSION='1.4.3' printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h @@ -14528,7 +14528,7 @@ Usage: $0 [OPTIONS] Report bugs to <bug-libtool@gnu.org>." lt_cl_version="\ -ptexenc config.lt 1.4.2/dev +ptexenc config.lt 1.4.3 configured by $0, generated by GNU Autoconf 2.71. Copyright (C) 2011 Free Software Foundation, Inc. @@ -16255,7 +16255,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by ptexenc $as_me 1.4.2/dev, which was +This file was extended by ptexenc $as_me 1.4.3, which was generated by GNU Autoconf 2.71. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -16323,7 +16323,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config='$ac_cs_config_escaped' ac_cs_version="\\ -ptexenc config.status 1.4.2/dev +ptexenc config.status 1.4.3 configured by $0, generated by GNU Autoconf 2.71, with options \\"\$ac_cs_config\\" diff --git a/Build/source/texk/ptexenc/version.ac b/Build/source/texk/ptexenc/version.ac index 3fba4330175..416f6eef498 100644 --- a/Build/source/texk/ptexenc/version.ac +++ b/Build/source/texk/ptexenc/version.ac @@ -11,4 +11,4 @@ dnl Keep package and shared library versions the same; dnl see kpathsea/version.ac. dnl dnl This file is m4-included from configure.ac. -m4_define([ptexenc_version], [1.4.3/dev]) +m4_define([ptexenc_version], [1.4.3]) diff --git a/Build/source/texk/seetexk/configure b/Build/source/texk/seetexk/configure index 88a1ed61cf7..aef32a4f071 100755 --- a/Build/source/texk/seetexk/configure +++ b/Build/source/texk/seetexk/configure @@ -14117,7 +14117,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h ac_fn_c_check_func "$LINENO" "strerror" "ac_cv_func_strerror" diff --git a/Build/source/texk/texlive/configure b/Build/source/texk/texlive/configure index 7f01885b930..dcc0864da60 100755 --- a/Build/source/texk/texlive/configure +++ b/Build/source/texk/texlive/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.71 for TeX Live Scripts 2023/dev. +# Generated by GNU Autoconf 2.71 for TeX Live Scripts 2023. # # Report bugs to <tex-k@tug.org>. # @@ -610,8 +610,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='TeX Live Scripts' PACKAGE_TARNAME='tex-live-scripts' -PACKAGE_VERSION='2023/dev' -PACKAGE_STRING='TeX Live Scripts 2023/dev' +PACKAGE_VERSION='2023' +PACKAGE_STRING='TeX Live Scripts 2023' PACKAGE_BUGREPORT='tex-k@tug.org' PACKAGE_URL='' @@ -1281,7 +1281,7 @@ if test "$ac_init_help" = "long"; then # 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 Scripts 2023/dev to adapt to many kinds of systems. +\`configure' configures TeX Live Scripts 2023 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1349,7 +1349,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of TeX Live Scripts 2023/dev:";; + short | recursive ) echo "Configuration of TeX Live Scripts 2023:";; esac cat <<\_ACEOF @@ -1445,7 +1445,7 @@ fi test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -TeX Live Scripts configure 2023/dev +TeX Live Scripts configure 2023 generated by GNU Autoconf 2.71 Copyright (C) 2021 Free Software Foundation, Inc. @@ -1521,7 +1521,7 @@ cat >config.log <<_ACEOF 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 Scripts $as_me 2023/dev, which was +It was created by TeX Live Scripts $as_me 2023, which was generated by GNU Autoconf 2.71. Invocation command line was $ $0$ac_configure_args_raw @@ -2786,7 +2786,7 @@ fi # Define the identity of the package. PACKAGE='tex-live-scripts' - VERSION='2023/dev' + VERSION='2023' printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h @@ -4914,7 +4914,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by TeX Live Scripts $as_me 2023/dev, which was +This file was extended by TeX Live Scripts $as_me 2023, which was generated by GNU Autoconf 2.71. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -4973,7 +4973,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config='$ac_cs_config_escaped' ac_cs_version="\\ -TeX Live Scripts config.status 2023/dev +TeX Live Scripts config.status 2023 configured by $0, generated by GNU Autoconf 2.71, with options \\"\$ac_cs_config\\" diff --git a/Build/source/texk/ttf2pk2/configure b/Build/source/texk/ttf2pk2/configure index 704823a07fa..f835ee326e6 100755 --- a/Build/source/texk/ttf2pk2/configure +++ b/Build/source/texk/ttf2pk2/configure @@ -14131,7 +14131,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for library containing floor" >&5 diff --git a/Build/source/texk/ttfdump/configure b/Build/source/texk/ttfdump/configure index b7b2b7180c4..410aad8c8ed 100755 --- a/Build/source/texk/ttfdump/configure +++ b/Build/source/texk/ttfdump/configure @@ -14383,7 +14383,7 @@ ac_config_headers="$ac_config_headers config.h" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h kpse_save_CPPFLAGS=$CPPFLAGS diff --git a/Build/source/texk/upmendex/COPYRIGHT b/Build/source/texk/upmendex/COPYRIGHT index 50cd28cd581..c978845afc1 100644 --- a/Build/source/texk/upmendex/COPYRIGHT +++ b/Build/source/texk/upmendex/COPYRIGHT @@ -1,5 +1,5 @@ Copyright (C) 1995 ASCII Corporation, 2009 ASCII MEDIA WORKS, - 2015-2022 TANAKA Takuji + 2015-2023 TANAKA Takuji All rights reserved. Redistribution and use in source and binary forms, with or without diff --git a/Build/source/texk/upmendex/configure b/Build/source/texk/upmendex/configure index 34ccf41dd5d..834f9622029 100755 --- a/Build/source/texk/upmendex/configure +++ b/Build/source/texk/upmendex/configure @@ -14509,7 +14509,7 @@ ac_config_headers="$ac_config_headers c-auto.h:c-auto.in" -printf "%s\n" "#define TL_VERSION \"TeX Live 2023/dev\"" >>confdefs.h +printf "%s\n" "#define TL_VERSION \"TeX Live 2023\"" >>confdefs.h { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking if C99 variadic macros are supported" >&5 diff --git a/Build/source/texk/upmendex/main.c b/Build/source/texk/upmendex/main.c index c94280ff933..ed8b95d836a 100644 --- a/Build/source/texk/upmendex/main.c +++ b/Build/source/texk/upmendex/main.c @@ -151,7 +151,7 @@ int main(int argc, char **argv) default: fprintf(stderr,"upmendex - index processor, %s (%s).\n",VERSION, TL_VERSION); - fprintf(stderr," Copyright 2009 ASCII MEDIA WORKS, 2015-2022 TANAKA Takuji\n"); + fprintf(stderr," Copyright 2009 ASCII MEDIA WORKS, 2015-2023 TANAKA Takuji\n"); fprintf(stderr," using ICU version %s\n",icu_version); fprintf(stderr,"usage:\n"); fprintf(stderr,"%% upmendex [-ilqrcgf] [-s sty] [-d dic] [-o ind] [-t log] [-p no] [--] [idx0 idx1 ...]\n"); diff --git a/Build/source/texk/web2c/NEWS b/Build/source/texk/web2c/NEWS index edbe29bbff5..c73a3e3378e 100644 --- a/Build/source/texk/web2c/NEWS +++ b/Build/source/texk/web2c/NEWS @@ -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 diff --git a/Build/source/texk/web2c/configure b/Build/source/texk/web2c/configure index 19f6e71e401..92daef31631 100755 --- a/Build/source/texk/web2c/configure +++ b/Build/source/texk/web2c/configure @@ -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@tug.org>. # @@ -629,8 +629,8 @@ MAKEFLAGS= # 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@tug.org' PACKAGE_URL='' @@ -1675,7 +1675,7 @@ if test "$ac_init_help" = "long"; then # 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]... @@ -1750,7 +1750,7 @@ fi 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 @@ -1976,7 +1976,7 @@ fi 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. @@ -2966,7 +2966,7 @@ cat >config.log <<_ACEOF 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 @@ -3942,7 +3942,7 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu -WEB2CVERSION=2023/dev +WEB2CVERSION=2023 am__api_version='1.16' @@ -9507,7 +9507,7 @@ fi # Define the identity of the package. PACKAGE='web2c' - VERSION='2023/dev' + VERSION='2023' printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h @@ -25378,7 +25378,7 @@ Usage: $0 [OPTIONS] Report bugs to <bug-libtool@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. @@ -28941,7 +28941,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # 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 @@ -29013,7 +29013,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ 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\\" diff --git a/Build/source/texk/web2c/doc/web2c.info b/Build/source/texk/web2c/doc/web2c.info index de5ce04906e..724f07c4771 100644 --- a/Build/source/texk/web2c/doc/web2c.info +++ b/Build/source/texk/web2c/doc/web2c.info @@ -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 @@ Web2c 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 @@ File: web2c.info, Node: Introduction, Next: Installation, Prev: Top, Up: Top 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 @@ Index * -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 @@ Index * -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 @@ Index * 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 @@ Index (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 @@ Index (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 @@ Index * 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 @@ Index (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 @@ Index * 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 @@ Index * 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 @@ Index * 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 @@ Index 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: diff --git a/Build/source/texk/web2c/doc/web2c.texi b/Build/source/texk/web2c/doc/web2c.texi index 23d827c5fc6..bde46587aac 100644 --- a/Build/source/texk/web2c/doc/web2c.texi +++ b/Build/source/texk/web2c/doc/web2c.texi @@ -11,8 +11,8 @@ The latest version is available from ftp://ftp.tug.org/tex/texinfo.tex.} \fi @end tex -@set version 2022 -@set month-year January 2022 +@set version 2023 +@set month-year February 2022 @c Define new indices for commands in auxiliary files, filenames, and options. @defcodeindex cm diff --git a/Build/source/texk/web2c/pdftexdir/ChangeLog b/Build/source/texk/web2c/pdftexdir/ChangeLog index 74f7d3b48c9..26e28f1ef9c 100644 --- a/Build/source/texk/web2c/pdftexdir/ChangeLog +++ b/Build/source/texk/web2c/pdftexdir/ChangeLog @@ -1,3 +1,10 @@ +2021-02-17 Karl Berry <karl@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@gmail.com> * pdftex.web: use real space char for \pdfinterwordspaceon, diff --git a/Build/source/texk/web2c/pdftexdir/pdftex.web b/Build/source/texk/web2c/pdftexdir/pdftex.web index 0d3cdd52090..b92e7564a17 100644 --- a/Build/source/texk/web2c/pdftexdir/pdftex.web +++ b/Build/source/texk/web2c/pdftexdir/pdftex.web @@ -307,8 +307,8 @@ known as `\eTeX'. {printed when \eTeX\ starts} @# @d pdftex_version==140 { \.{\\pdftexversion} } -@d pdftex_revision=="24" { \.{\\pdftexrevision} } -@d pdftex_version_string=='-1.40.24' {current \pdfTeX\ version} +@d pdftex_revision=="25" { \.{\\pdftexrevision} } +@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} diff --git a/Build/source/texk/web2c/pdftexdir/pdftex_version.h b/Build/source/texk/web2c/pdftexdir/pdftex_version.h index 493b324a99c..3f342bcd808 100644 --- a/Build/source/texk/web2c/pdftexdir/pdftex_version.h +++ b/Build/source/texk/web2c/pdftexdir/pdftex_version.h @@ -1 +1 @@ -#define PDFTEX_VERSION "1.40.24" +#define PDFTEX_VERSION "1.40.25" diff --git a/Build/source/texk/web2c/web2c/configure b/Build/source/texk/web2c/web2c/configure index 6b0f7ecbd2d..2874fe77f97 100755 --- a/Build/source/texk/web2c/web2c/configure +++ b/Build/source/texk/web2c/web2c/configure @@ -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@tug.org>. # @@ -621,8 +621,8 @@ MAKEFLAGS= # 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@tug.org' PACKAGE_URL='' @@ -1365,7 +1365,7 @@ if test "$ac_init_help" = "long"; then # 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 @@ fi 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 @@ fi 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 @@ cat >config.log <<_ACEOF 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 @@ fi # 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 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # 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 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ 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\\" diff --git a/Build/source/texk/web2c/xetexdir/ChangeLog b/Build/source/texk/web2c/xetexdir/ChangeLog index 9e0ad2868b1..ad75eb86e25 100644 --- a/Build/source/texk/web2c/xetexdir/ChangeLog +++ b/Build/source/texk/web2c/xetexdir/ChangeLog @@ -1,3 +1,10 @@ +2021-02-17 Karl Berry <karl@tug.org> + + * NEWS, + * xetex_version.h, + * xetex.web (xetex_revision, xetex_version_string): + version 0.999995 for TL23. + 2022-12-28 TANAKA Takuji <ttk@t-lab.opal.ne.jp> * wcfname.test, am/xetex.am: diff --git a/Build/source/texk/web2c/xetexdir/NEWS b/Build/source/texk/web2c/xetexdir/NEWS index a82669be713..1fb4a87d727 100644 --- a/Build/source/texk/web2c/xetexdir/NEWS +++ b/Build/source/texk/web2c/xetexdir/NEWS @@ -1,5 +1,8 @@ ============================================================== -XeTeX 0.999994 +XeTeX 0.999995 + +============================================================== +XeTeX 0.999994 (February 2022) * New wrapper scripts xetex-unsafe and xelatex-unsafe for XeTeX documents requiring PSTricks transparency. For safety, use LuaTeX instead. diff --git a/Build/source/texk/web2c/xetexdir/xetex.web b/Build/source/texk/web2c/xetexdir/xetex.web index 4871d9d588e..bb107758871 100644 --- a/Build/source/texk/web2c/xetexdir/xetex.web +++ b/Build/source/texk/web2c/xetexdir/xetex.web @@ -1,5 +1,5 @@ % Copyright (c) 1994-2008 by SIL International -% Copyright (c) 2009-2022 by Jonathan Kew +% Copyright (c) 2009-2023 by Jonathan Kew % Copyright (c) 2010-2012 by Han The Thanh % Copyright (c) 2012-2013 by Khaled Hosny @@ -319,8 +319,8 @@ known as `\eTeX'. @d eTeX_version_string=='-2.6' {current \eTeX\ version} @# @d XeTeX_version=0 { \.{\\XeTeXversion} } -@d XeTeX_revision==".999994" { \.{\\XeTeXrevision} } -@d XeTeX_version_string=='-0.999994' {current \XeTeX\ version} +@d XeTeX_revision==".999995" { \.{\\XeTeXrevision} } +@d XeTeX_version_string=='-0.999995' {current \XeTeX\ version} @# @d XeTeX_banner=='This is XeTeX, Version 3.141592653',eTeX_version_string,XeTeX_version_string {printed when \XeTeX\ starts} diff --git a/Build/source/texk/web2c/xetexdir/xetex_version.h b/Build/source/texk/web2c/xetexdir/xetex_version.h index 0775de56589..06996fcec3d 100644 --- a/Build/source/texk/web2c/xetexdir/xetex_version.h +++ b/Build/source/texk/web2c/xetexdir/xetex_version.h @@ -1 +1 @@ -#define XETEX_VERSION "0.999994" +#define XETEX_VERSION "0.999995" |