diff options
Diffstat (limited to 'Master/texmf-dist/doc/kpathsea/kpathsea.html')
| -rw-r--r-- | Master/texmf-dist/doc/kpathsea/kpathsea.html | 2112 |
1 files changed, 1011 insertions, 1101 deletions
diff --git a/Master/texmf-dist/doc/kpathsea/kpathsea.html b/Master/texmf-dist/doc/kpathsea/kpathsea.html index 1099a4a469a..64fca6da621 100644 --- a/Master/texmf-dist/doc/kpathsea/kpathsea.html +++ b/Master/texmf-dist/doc/kpathsea/kpathsea.html @@ -2,7 +2,7 @@ <html> <!-- This file documents the Kpathsea library for path searching. -Copyright (C) 1996-2018 Karl Berry & Olaf Weber. +Copyright (C) 1996-2019 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 @@ -18,7 +18,7 @@ Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the TeX Users Group. --> -<!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ --> +<!-- Created by GNU Texinfo 6.6, http://www.gnu.org/software/texinfo/ --> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Kpathsea: A library for path searching</title> @@ -36,23 +36,14 @@ approved by the TeX Users Group. --> <!-- a.summary-letter {text-decoration: none} blockquote.indentedblock {margin-right: 0em} -blockquote.smallindentedblock {margin-right: 0em; font-size: smaller} -blockquote.smallquotation {font-size: smaller} div.display {margin-left: 3.2em} div.example {margin-left: 3.2em} div.lisp {margin-left: 3.2em} -div.smalldisplay {margin-left: 3.2em} -div.smallexample {margin-left: 3.2em} -div.smalllisp {margin-left: 3.2em} kbd {font-style: oblique} pre.display {font-family: inherit} pre.format {font-family: inherit} pre.menu-comment {font-family: serif} pre.menu-preformatted {font-family: serif} -pre.smalldisplay {font-family: inherit; font-size: smaller} -pre.smallexample {font-size: smaller} -pre.smallformat {font-family: inherit; font-size: smaller} -pre.smalllisp {font-size: smaller} span.nolinebreak {white-space: nowrap} span.roman {font-family: initial; font-weight: normal} span.sansserif {font-family: sans-serif; font-weight: normal} @@ -74,169 +65,165 @@ ul.no-bullet {list-style: none} -<a name="SEC_Contents"></a> +<span id="SEC_Contents"></span> <h2 class="contents-heading">Table of Contents</h2> <div class="contents"> <ul class="no-bullet"> - <li><a name="toc-Introduction-1" href="#Introduction">1 Introduction</a> + <li><a id="toc-Introduction-1" href="#Introduction">1 Introduction</a> <ul class="no-bullet"> - <li><a name="toc-History-1" href="#History">1.1 History</a></li> + <li><a id="toc-History-1" href="#History">1.1 History</a></li> </ul></li> - <li><a name="toc-unixtex_002eftp_003a-Obtaining-TeX" href="#unixtex_002eftp">2 <samp>unixtex.ftp</samp>: Obtaining TeX</a></li> - <li><a name="toc-Security-1" href="#Security">3 Security</a></li> - <li><a name="toc-TeX-directory-structure-1" href="#TeX-directory-structure">4 TeX directory structure</a></li> - <li><a name="toc-Path-searching-1" href="#Path-searching">5 Path searching</a> + <li><a id="toc-unixtex_002eftp_003a-Obtaining-TeX" href="#unixtex_002eftp">2 <samp>unixtex.ftp</samp>: Obtaining TeX</a></li> + <li><a id="toc-Security-1" href="#Security">3 Security</a></li> + <li><a id="toc-TeX-directory-structure-1" href="#TeX-directory-structure">4 TeX directory structure</a></li> + <li><a id="toc-Path-searching-1" href="#Path-searching">5 Path searching</a> <ul class="no-bullet"> - <li><a name="toc-Searching-overview-1" href="#Searching-overview">5.1 Searching overview</a></li> - <li><a name="toc-Path-sources-1" href="#Path-sources">5.2 Path sources</a> + <li><a id="toc-Searching-overview-1" href="#Searching-overview">5.1 Searching overview</a></li> + <li><a id="toc-Path-sources-1" href="#Path-sources">5.2 Path sources</a> <ul class="no-bullet"> - <li><a name="toc-Config-files-1" href="#Config-files">5.2.1 Config files</a></li> + <li><a id="toc-Config-files-1" href="#Config-files">5.2.1 Config files</a></li> </ul></li> - <li><a name="toc-Path-expansion-1" href="#Path-expansion">5.3 Path expansion</a> + <li><a id="toc-Path-expansion-1" href="#Path-expansion">5.3 Path expansion</a> <ul class="no-bullet"> - <li><a name="toc-Default-expansion-1" href="#Default-expansion">5.3.1 Default expansion</a></li> - <li><a name="toc-Variable-expansion-1" href="#Variable-expansion">5.3.2 Variable expansion</a></li> - <li><a name="toc-Tilde-expansion-1" href="#Tilde-expansion">5.3.3 Tilde expansion</a></li> - <li><a name="toc-Brace-expansion-1" href="#Brace-expansion">5.3.4 Brace expansion</a></li> - <li><a name="toc-KPSE_005fDOT-expansion-1" href="#KPSE_005fDOT-expansion">5.3.5 <code>KPSE_DOT</code> expansion</a></li> - <li><a name="toc-Subdirectory-expansion-1" href="#Subdirectory-expansion">5.3.6 Subdirectory expansion</a></li> + <li><a id="toc-Default-expansion-1" href="#Default-expansion">5.3.1 Default expansion</a></li> + <li><a id="toc-Variable-expansion-1" href="#Variable-expansion">5.3.2 Variable expansion</a></li> + <li><a id="toc-Tilde-expansion-1" href="#Tilde-expansion">5.3.3 Tilde expansion</a></li> + <li><a id="toc-Brace-expansion-1" href="#Brace-expansion">5.3.4 Brace expansion</a></li> + <li><a id="toc-KPSE_005fDOT-expansion-1" href="#KPSE_005fDOT-expansion">5.3.5 <code>KPSE_DOT</code> expansion</a></li> + <li><a id="toc-Subdirectory-expansion-1" href="#Subdirectory-expansion">5.3.6 Subdirectory expansion</a></li> </ul></li> - <li><a name="toc-Casefolding-search-1" href="#Casefolding-search">5.4 Casefolding search</a> + <li><a id="toc-Casefolding-search-1" href="#Casefolding-search">5.4 Casefolding search</a> <ul class="no-bullet"> - <li><a name="toc-Casefolding-rationale-1" href="#Casefolding-rationale">5.4.1 Casefolding rationale</a></li> - <li><a name="toc-Casefolding-examples-1" href="#Casefolding-examples">5.4.2 Casefolding examples</a></li> + <li><a id="toc-Casefolding-rationale-1" href="#Casefolding-rationale">5.4.1 Casefolding rationale</a></li> + <li><a id="toc-Casefolding-examples-1" href="#Casefolding-examples">5.4.2 Casefolding examples</a></li> </ul></li> - <li><a name="toc-Filename-database-_0028ls_002dR_0029" href="#Filename-database">5.5 Filename database (<code>ls-R</code>)</a> + <li><a id="toc-Filename-database-_0028ls_002dR_0029" href="#Filename-database">5.5 Filename database (<code>ls-R</code>)</a> <ul class="no-bullet"> - <li><a name="toc-ls_002dR-1" href="#ls_002dR">5.5.1 <samp>ls-R</samp></a></li> - <li><a name="toc-Filename-aliases-1" href="#Filename-aliases">5.5.2 Filename aliases</a></li> - <li><a name="toc-Database-format-1" href="#Database-format">5.5.3 Database format</a></li> + <li><a id="toc-ls_002dR-1" href="#ls_002dR">5.5.1 <samp>ls-R</samp></a></li> + <li><a id="toc-Filename-aliases-1" href="#Filename-aliases">5.5.2 Filename aliases</a></li> + <li><a id="toc-Database-format-1" href="#Database-format">5.5.3 Database format</a></li> </ul></li> - <li><a name="toc-kpsewhich_003a-Standalone-path-searching" href="#Invoking-kpsewhich">5.6 <code>kpsewhich</code>: Standalone path searching</a> + <li><a id="toc-kpsewhich_003a-Standalone-path-searching" href="#Invoking-kpsewhich">5.6 <code>kpsewhich</code>: Standalone path searching</a> <ul class="no-bullet"> - <li><a name="toc-Path-searching-options-1" href="#Path-searching-options">5.6.1 Path searching options</a></li> - <li><a name="toc-Specially_002drecognized-files-for-kpsewhich" href="#Specially_002drecognized-files">5.6.2 Specially-recognized files for <code>kpsewhich</code></a></li> - <li><a name="toc-Auxiliary-tasks-1" href="#Auxiliary-tasks">5.6.3 Auxiliary tasks</a></li> - <li><a name="toc-Standard-options-1" href="#Standard-options">5.6.4 Standard options</a></li> + <li><a id="toc-Path-searching-options-1" href="#Path-searching-options">5.6.1 Path searching options</a></li> + <li><a id="toc-Specially_002drecognized-files-for-kpsewhich" href="#Specially_002drecognized-files">5.6.2 Specially-recognized files for <code>kpsewhich</code></a></li> + <li><a id="toc-Auxiliary-tasks-1" href="#Auxiliary-tasks">5.6.3 Auxiliary tasks</a></li> + <li><a id="toc-Standard-options-1" href="#Standard-options">5.6.4 Standard options</a></li> </ul></li> </ul></li> - <li><a name="toc-TeX-support-1" href="#TeX-support">6 TeX support</a> + <li><a id="toc-TeX-support-1" href="#TeX-support">6 TeX support</a> <ul class="no-bullet"> - <li><a name="toc-Supported-file-formats-1" href="#Supported-file-formats">6.1 Supported file formats</a></li> - <li><a name="toc-File-lookup-1" href="#File-lookup">6.2 File lookup</a></li> - <li><a name="toc-Glyph-lookup-1" href="#Glyph-lookup">6.3 Glyph lookup</a> + <li><a id="toc-Supported-file-formats-1" href="#Supported-file-formats">6.1 Supported file formats</a></li> + <li><a id="toc-File-lookup-1" href="#File-lookup">6.2 File lookup</a></li> + <li><a id="toc-Glyph-lookup-1" href="#Glyph-lookup">6.3 Glyph lookup</a> <ul class="no-bullet"> - <li><a name="toc-Basic-glyph-lookup-1" href="#Basic-glyph-lookup">6.3.1 Basic glyph lookup</a></li> - <li><a name="toc-Fontmap-1" href="#Fontmap">6.3.2 Fontmap</a></li> - <li><a name="toc-Fallback-font-1" href="#Fallback-font">6.3.3 Fallback font</a></li> + <li><a id="toc-Basic-glyph-lookup-1" href="#Basic-glyph-lookup">6.3.1 Basic glyph lookup</a></li> + <li><a id="toc-Fontmap-1" href="#Fontmap">6.3.2 Fontmap</a></li> + <li><a id="toc-Fallback-font-1" href="#Fallback-font">6.3.3 Fallback font</a></li> </ul></li> - <li><a name="toc-Suppressing-warnings-1" href="#Suppressing-warnings">6.4 Suppressing warnings</a></li> - <li><a name="toc-mktex-scripts-1" href="#mktex-scripts">6.5 <samp>mktex</samp> scripts</a> + <li><a id="toc-Suppressing-warnings-1" href="#Suppressing-warnings">6.4 Suppressing warnings</a></li> + <li><a id="toc-mktex-scripts-1" href="#mktex-scripts">6.5 <samp>mktex</samp> scripts</a> <ul class="no-bullet"> - <li><a name="toc-mktex-configuration-1" href="#mktex-configuration">6.5.1 <samp>mktex</samp> configuration</a></li> - <li><a name="toc-mktex-script-names-1" href="#mktex-script-names">6.5.2 <samp>mktex</samp> script names</a></li> - <li><a name="toc-mktex-script-arguments-1" href="#mktex-script-arguments">6.5.3 <samp>mktex</samp> script arguments</a></li> + <li><a id="toc-mktex-configuration-1" href="#mktex-configuration">6.5.1 <samp>mktex</samp> configuration</a></li> + <li><a id="toc-mktex-script-names-1" href="#mktex-script-names">6.5.2 <samp>mktex</samp> script names</a></li> + <li><a id="toc-mktex-script-arguments-1" href="#mktex-script-arguments">6.5.3 <samp>mktex</samp> script arguments</a></li> </ul></li> </ul></li> - <li><a name="toc-Programming-1" href="#Programming">7 Programming</a> + <li><a id="toc-Programming-1" href="#Programming">7 Programming</a> <ul class="no-bullet"> - <li><a name="toc-Programming-overview-1" href="#Programming-overview">7.1 Programming overview</a></li> - <li><a name="toc-Calling-sequence-1" href="#Calling-sequence">7.2 Calling sequence</a></li> - <li><a name="toc-Program_002dspecific-files-1" href="#Program_002dspecific-files">7.3 Program-specific files</a></li> - <li><a name="toc-Programming-with-config-files-1" href="#Programming-with-config-files">7.4 Programming with config files</a></li> + <li><a id="toc-Programming-overview-1" href="#Programming-overview">7.1 Programming overview</a></li> + <li><a id="toc-Calling-sequence-1" href="#Calling-sequence">7.2 Calling sequence</a></li> + <li><a id="toc-Program_002dspecific-files-1" href="#Program_002dspecific-files">7.3 Program-specific files</a></li> + <li><a id="toc-Programming-with-config-files-1" href="#Programming-with-config-files">7.4 Programming with config files</a></li> </ul></li> - <li><a name="toc-Reporting-bugs-1" href="#Reporting-bugs">8 Reporting bugs</a> + <li><a id="toc-Reporting-bugs-1" href="#Reporting-bugs">8 Reporting bugs</a> <ul class="no-bullet"> - <li><a name="toc-Bug-checklist-1" href="#Bug-checklist">8.1 Bug checklist</a></li> - <li><a name="toc-Mailing-lists-1" href="#Mailing-lists">8.2 Mailing lists</a></li> - <li><a name="toc-Debugging-1" href="#Debugging">8.3 Debugging</a></li> - <li><a name="toc-Logging-1" href="#Logging">8.4 Logging</a></li> - <li><a name="toc-Common-problems-1" href="#Common-problems">8.5 Common problems</a> + <li><a id="toc-Bug-checklist-1" href="#Bug-checklist">8.1 Bug checklist</a></li> + <li><a id="toc-Mailing-lists-1" href="#Mailing-lists">8.2 Mailing lists</a></li> + <li><a id="toc-Debugging-1" href="#Debugging">8.3 Debugging</a></li> + <li><a id="toc-Logging-1" href="#Logging">8.4 Logging</a></li> + <li><a id="toc-Common-problems-1" href="#Common-problems">8.5 Common problems</a> <ul class="no-bullet"> - <li><a name="toc-Unable-to-find-files-1" href="#Unable-to-find-files">8.5.1 Unable to find files</a></li> - <li><a name="toc-Slow-path-searching-1" href="#Slow-path-searching">8.5.2 Slow path searching</a></li> - <li><a name="toc-Unable-to-generate-fonts-1" href="#Unable-to-generate-fonts">8.5.3 Unable to generate fonts</a></li> - <li><a name="toc-TeX-or-Metafont-failing-1" href="#TeX-or-Metafont-failing">8.5.4 TeX or Metafont failing</a></li> + <li><a id="toc-Unable-to-find-files-1" href="#Unable-to-find-files">8.5.1 Unable to find files</a></li> + <li><a id="toc-Slow-path-searching-1" href="#Slow-path-searching">8.5.2 Slow path searching</a></li> + <li><a id="toc-Unable-to-generate-fonts-1" href="#Unable-to-generate-fonts">8.5.3 Unable to generate fonts</a></li> + <li><a id="toc-TeX-or-Metafont-failing-1" href="#TeX-or-Metafont-failing">8.5.4 TeX or Metafont failing</a></li> </ul></li> </ul></li> - <li><a name="toc-Index-1" href="#Index">Index</a></li> + <li><a id="toc-Index-1" href="#Index">Index</a></li> </ul> </div> -<a name="Top"></a> -<div class="header"> +<span id="Top"></span><div class="header"> <p> Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Up: <a href="http://tug.org/texinfohtml" accesskey="u" rel="up">(dir)</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Kpathsea-library"></a> -<h1 class="top">Kpathsea library</h1> +<span id="Kpathsea-library"></span><h1 class="top">Kpathsea library</h1> <p>This manual documents the Kpathsea library for path searching. It -corresponds to version 6.3.0, released in -February 2018. +corresponds to version 6.3.1, released in +February 2019. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Introduction" accesskey="1">Introduction</a>:</td><td> </td><td align="left" valign="top">Overview and history. +<tr><td align="left" valign="top">• <a href="#Introduction" accesskey="1">Introduction</a></td><td> </td><td align="left" valign="top">Overview and history. </td></tr> <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment"> -</pre></th></tr><tr><td align="left" valign="top">• <a href="#unixtex_002eftp" accesskey="2">unixtex.ftp</a>:</td><td> </td><td align="left" valign="top">Obtaining TeX software. +</pre></th></tr><tr><td align="left" valign="top">• <a href="#unixtex_002eftp" accesskey="2">unixtex.ftp</a></td><td> </td><td align="left" valign="top">Obtaining TeX software. </td></tr> -<tr><td align="left" valign="top">• <a href="#Security" accesskey="3">Security</a>:</td><td> </td><td align="left" valign="top">Who can write what files, etc. +<tr><td align="left" valign="top">• <a href="#Security" accesskey="3">Security</a></td><td> </td><td align="left" valign="top">Who can write what files, etc. </td></tr> -<tr><td align="left" valign="top">• <a href="#TeX-directory-structure" accesskey="4">TeX directory structure</a>:</td><td> </td><td align="left" valign="top">Managing the horde of TeX input files. +<tr><td align="left" valign="top">• <a href="#TeX-directory-structure" accesskey="4">TeX directory structure</a></td><td> </td><td align="left" valign="top">Managing the horde of TeX input files. </td></tr> <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment"> -</pre></th></tr><tr><td align="left" valign="top">• <a href="#Path-searching" accesskey="5">Path searching</a>:</td><td> </td><td align="left" valign="top">How filename lookups work. +</pre></th></tr><tr><td align="left" valign="top">• <a href="#Path-searching" accesskey="5">Path searching</a></td><td> </td><td align="left" valign="top">How filename lookups work. </td></tr> -<tr><td align="left" valign="top">• <a href="#TeX-support" accesskey="6">TeX support</a>:</td><td> </td><td align="left" valign="top">Special support for TeX-related file lookups. +<tr><td align="left" valign="top">• <a href="#TeX-support" accesskey="6">TeX support</a></td><td> </td><td align="left" valign="top">Special support for TeX-related file lookups. </td></tr> <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment"> -</pre></th></tr><tr><td align="left" valign="top">• <a href="#Programming" accesskey="7">Programming</a>:</td><td> </td><td align="left" valign="top">How to use Kpathsea features in your program. +</pre></th></tr><tr><td align="left" valign="top">• <a href="#Programming" accesskey="7">Programming</a></td><td> </td><td align="left" valign="top">How to use Kpathsea features in your program. </td></tr> <tr><th colspan="3" align="left" valign="top"><pre class="menu-comment"> -</pre></th></tr><tr><td align="left" valign="top">• <a href="#Reporting-bugs" accesskey="8">Reporting bugs</a>:</td><td> </td><td align="left" valign="top">Where and how to report bugs. +</pre></th></tr><tr><td align="left" valign="top">• <a href="#Reporting-bugs" accesskey="8">Reporting bugs</a></td><td> </td><td align="left" valign="top">Where and how to report bugs. </td></tr> -<tr><td align="left" valign="top">• <a href="#Index" accesskey="9">Index</a>:</td><td> </td><td align="left" valign="top">General index. +<tr><td align="left" valign="top">• <a href="#Index" accesskey="9">Index</a></td><td> </td><td align="left" valign="top">General index. </td></tr> </table> <hr> -<a name="Introduction"></a> -<div class="header"> +<span id="Introduction"></span><div class="header"> <p> Next: <a href="#unixtex_002eftp" accesskey="n" rel="next">unixtex.ftp</a>, Previous: <a href="#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Introduction-1"></a> -<h2 class="chapter">1 Introduction</h2> +<span id="Introduction-1"></span><h2 class="chapter">1 Introduction</h2> -<a name="index-introduction"></a> -<a name="index-fundamental-purpose-of-Kpathsea"></a> +<span id="index-introduction"></span> +<span id="index-fundamental-purpose-of-Kpathsea"></span> -<p>This manual corresponds to version 6.3.0 of the Kpathsea -library, released in February 2018. +<p>This manual corresponds to version 6.3.1 of the Kpathsea +library, released in February 2019. </p> <p>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. </p> -<a name="index-programs-using-the-library"></a> +<span id="index-programs-using-the-library"></span> <p>The following software, all of which is maintained in parallel, uses this library: </p> <ul> <li> Dviljk (see the ‘<samp>dvilj</samp>’ man page) -</li><li> Dvipsk (see <cite><a href="http://tug.org/texinfohtml/dvips.html#Top">Dvips: A DVI driver</a></cite>) +</li><li> Dvipsk (see <cite><a href="https://tug.org/texinfohtml/dvips.html#Top">Dvips: A DVI driver</a></cite>) </li><li> GNU font utilities (see <cite><a href="fontu.html#Top">GNU font utilities</a></cite>) -</li><li> Web2c (see <cite><a href="http://tug.org/texinfohtml/web2c.html#Top">Web2c: A TeX implementation</a></cite>) +</li><li> Web2c (see <cite><a href="https://tug.org/texinfohtml/web2c.html#Top">Web2c: A TeX implementation</a></cite>) </li><li> Xdvik (see the ‘<samp>xdvi</samp>’ man page) </li></ul> @@ -245,17 +232,17 @@ this library: <p>Kpathsea is now maintained as part of the TeX Live distribution (<a href="http://tug.org/texlive">http://tug.org/texlive</a>), which includes several more Kpathsea-using programs. For information on configuration, building, -installing, and more, see <cite><a href="http://tug.org/texinfohtml/tlbuild.html#Top">Building TeX Live</a></cite>. +installing, and more, see <cite><a href="https://tug.org/texinfohtml/tlbuild.html#Top">Building TeX Live</a></cite>. </p> -<a name="index-interface_002c-not-frozen"></a> -<a name="index-comments_002c-making"></a> -<a name="index-suggestions_002c-making"></a> +<span id="index-interface_002c-not-frozen"></span> +<span id="index-comments_002c-making"></span> +<span id="index-suggestions_002c-making"></span> <p>The library is still actively maintained. If you have comments or suggestions, please send along (see <a href="#Reporting-bugs">Reporting bugs</a>). </p> -<a name="index-conditions-for-use"></a> -<a name="index-license-for-using-the-library"></a> -<a name="index-GNU-General-Public-License"></a> +<span id="index-conditions-for-use"></span> +<span id="index-license-for-using-the-library"></span> +<span id="index-GNU-General-Public-License"></span> <p>The Kpathsea library is distributed under the GNU Library General Public License (LGPL), version 2.1 or (at your option) any later version. In short, this means if you write a program using the @@ -266,7 +253,7 @@ you have to distribute the source to your program using the library, although we hope you will. See accompanying files for the text of the GNU licenses, or <a href="http2://www.gnu.org/licenses">http2://www.gnu.org/licenses</a>. </p> -<a name="index-TeX-Users-Group"></a> +<span id="index-TeX-Users-Group"></span> <p>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 @@ -275,36 +262,34 @@ proceedings, and arranges courses on TeX for all levels of users throughout the world. See <a href="https://tug.org">https://tug.org</a> for information. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#History" accesskey="1">History</a>:</td><td> </td><td align="left" valign="top"> +<tr><td align="left" valign="top">• <a href="#History" accesskey="1">History</a></td><td> </td><td align="left" valign="top"> </td></tr> </table> <hr> -<a name="History"></a> -<div class="header"> +<span id="History"></span><div class="header"> <p> Up: <a href="#Introduction" accesskey="u" rel="up">Introduction</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="History-1"></a> -<h3 class="section">1.1 History</h3> +<span id="History-1"></span><h3 class="section">1.1 History</h3> -<a name="index-history-of-Kpathsea"></a> +<span id="index-history-of-Kpathsea"></span> -<a name="index-Knuth_002c-Donald-E_002e"></a> +<span id="index-Knuth_002c-Donald-E_002e"></span> <p>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 <cite>Digital Typography</cite>, among other places. </p> -<a name="index-Morgan_002c-Tim"></a> -<a name="index-Rokicki_002c-Tom"></a> -<a name="index-Berry_002c-Karl"></a> -<a name="index-VAX-11_002f750"></a> -<a name="index-Sun-2"></a> -<a name="index-pxp-Pascal-preprocessor"></a> -<a name="index-pc-Pascal-compiler"></a> +<span id="index-Morgan_002c-Tim"></span> +<span id="index-Rokicki_002c-Tom"></span> +<span id="index-Berry_002c-Karl"></span> +<span id="index-VAX-11_002f750"></span> +<span id="index-Sun-2"></span> +<span id="index-pxp-Pascal-preprocessor"></span> +<span id="index-pc-Pascal-compiler"></span> <p>[Karl writes.] My first ChangeLog entry for Web2c seems to be 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 @@ -324,7 +309,7 @@ to implement subdirectory searching, since I couldn’t stand putting everything in one big directory, and also couldn’t stand having to explicitly specify <samp>cm</samp>, <samp>pandora</samp>, … in a path. </p> -<a name="index-Vojta_002c-Paul"></a> +<span id="index-Vojta_002c-Paul"></span> <p>In the first incarnation, I just hacked separately on each 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, @@ -339,22 +324,22 @@ 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.) </p> -<a name="index-MacKenzie_002c-David"></a> +<span id="index-MacKenzie_002c-David"></span> <p>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 of the different configuration strategies of each program, not so much because of the path searching. Autoconf was being developed by David MacKenzie and others, and I was adapting it to TeX and friends. </p> -<a name="index-zuhn_002c-david"></a> +<span id="index-zuhn_002c-david"></span> <p>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 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. </p> -<a name="index-Walsh_002c-Norman"></a> -<a name="index-Neumann_002c-Gustaf"></a> +<span id="index-Walsh_002c-Norman"></span> +<span id="index-Neumann_002c-Gustaf"></span> <p>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 builtin LJ4 fonts @@ -371,14 +356,14 @@ 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…) </p> -<a name="index-Weber_002c-Olaf"></a> +<span id="index-Weber_002c-Olaf"></span> <p>[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. </p> -<a name="index-Hoekwater_002c-Taco"></a> -<a name="index-Breitenlohner_002c-Peter"></a> +<span id="index-Hoekwater_002c-Taco"></span> +<span id="index-Breitenlohner_002c-Peter"></span> <p>[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 @@ -392,21 +377,19 @@ where Kpathsea is now maintained. <hr> -<a name="unixtex_002eftp"></a> -<div class="header"> +<span id="unixtex_002eftp"></span><div class="header"> <p> Next: <a href="#Security" accesskey="n" rel="next">Security</a>, Previous: <a href="#Introduction" accesskey="p" rel="prev">Introduction</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="unixtex_002eftp_003a-Obtaining-TeX"></a> -<h2 class="chapter">2 <samp>unixtex.ftp</samp>: Obtaining TeX</h2> +<span id="unixtex_002eftp_003a-Obtaining-TeX"></span><h2 class="chapter">2 <samp>unixtex.ftp</samp>: Obtaining TeX</h2> -<a name="index-obtaining-TeX"></a> -<a name="index-retrieving-TeX"></a> +<span id="index-obtaining-TeX"></span> +<span id="index-retrieving-TeX"></span> -<a name="index-unixtex_002eftp"></a> -<a name="index-tug_002eorg"></a> -<a name="index-www_002etug_002eorg"></a> -<a name="index-ftp_002etug_002eorg"></a> +<span id="index-unixtex_002eftp"></span> +<span id="index-tug_002eorg"></span> +<span id="index-www_002etug_002eorg"></span> +<span id="index-ftp_002etug_002eorg"></span> <p>This is <a href="https://tug.org/tex/unixtex.ftp">https://tug.org/tex/unixtex.ftp</a>, last updated 28 November 2017. Email <a href="mailto:tex-k@tug.org">tex-k@tug.org</a> with comments or questions. @@ -422,9 +405,9 @@ distributions. separate packages. Their sources are now maintained as part of TeX Live. </p> -<a name="index-ftp_002ecs_002estanford_002eedu"></a> -<a name="index-tex_002eweb"></a> -<a name="index-Knuth_002c-Donald-E_002e_002c-archive-of-programs-by"></a> +<span id="index-ftp_002ecs_002estanford_002eedu"></span> +<span id="index-tex_002eweb"></span> +<span id="index-Knuth_002c-Donald-E_002e_002c-archive-of-programs-by"></span> <p>The host <tt>ftp.cs.stanford.edu</tt> is the original source for the files for which Donald Knuth is directly responsible: <samp>tex.web</samp>, <samp>plain.tex</samp>, etc. However, unless you want to undertake the @@ -441,36 +424,34 @@ Comprehensive TeX Archive Network), <a href="https://ctan.org">https://ctan.org< <hr> -<a name="Security"></a> -<div class="header"> +<span id="Security"></span><div class="header"> <p> Next: <a href="#TeX-directory-structure" accesskey="n" rel="next">TeX directory structure</a>, Previous: <a href="#unixtex_002eftp" accesskey="p" rel="prev">unixtex.ftp</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Security-1"></a> -<h2 class="chapter">3 Security</h2> +<span id="Security-1"></span><h2 class="chapter">3 Security</h2> -<a name="index-security-considerations"></a> +<span id="index-security-considerations"></span> <p>None of the programs in the TeX system require any special system privileges, so there’s no first-level security concern of people gaining illegitimate root access. </p> -<a name="index-trojan-horse-attack"></a> -<a name="index-_002erhosts_002c-writable-by-TeX"></a> +<span id="index-trojan-horse-attack"></span> +<span id="index-_002erhosts_002c-writable-by-TeX"></span> <p>A TeX document, however, can write to arbitrary files, e.g., <samp>~/.rhosts</samp>, 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 -<samp>texmf.cnf</samp>. See <a href="http://tug.org/texinfohtml/web2c.html#tex-invocation">tex invocation</a> in <cite>Web2c</cite>. MetaPost has +<samp>texmf.cnf</samp>. See <a href="https://tug.org/texinfohtml/web2c.html#tex-invocation">tex invocation</a> in <cite>Web2c</cite>. MetaPost has the same issue. </p> <p>Dvips, Xdvi, and TeX can also execute shell commands under some -circumstances. To disable this, see the ‘<samp>-R</samp>’ option in <a href="http://tug.org/texinfohtml/dvips.html#Option-details">Option -details</a> in <cite>Dvips</cite>, the xdvi man page, and <a href="http://tug.org/texinfohtml/web2c.html#tex-invocation">tex +circumstances. To disable this, see the ‘<samp>-R</samp>’ option in <a href="https://tug.org/texinfohtml/dvips.html#Option-details">Option +details</a> in <cite>Dvips</cite>, the xdvi man page, and <a href="https://tug.org/texinfohtml/web2c.html#tex-invocation">tex invocation</a> in <cite>Web2c</cite>, respectively. </p> -<a name="index-local-cache-of-fonts"></a> -<a name="index-cache-of-fonts_002c-local"></a> +<span id="index-local-cache-of-fonts"></span> +<span id="index-cache-of-fonts_002c-local"></span> <p>Another security issue arises because it’s very useful—almost necessary—to make arbitrary fonts on user demand with <code>mktexpk</code> and friends. Where do these files get installed? By default, the @@ -479,20 +460,20 @@ and friends. Where do these files get installed? By default, the it may not suit your situation because it means that a local cache of fonts is created on every machine. </p> -<a name="index-globally-writable-directories"></a> +<span id="index-globally-writable-directories"></span> <p>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 <code>VARTEXFONTS</code> in <samp>texmf.cnf</samp> to refer to some globally known directory. See <a href="#mktex-configuration">mktex configuration</a>. </p> -<a name="index-append_002donly-directories-and-mktexpk"></a> +<span id="index-append_002donly-directories-and-mktexpk"></span> <p>The first restriction you can apply is to make newly-created directories under <samp>texmf</samp> be append-only with an option in <samp>mktex.cnf</samp>. See <a href="#mktex-configuration">mktex configuration</a>. </p> -<a name="index-group_002dwritable-directories"></a> -<a name="index-setgid-scripts"></a> +<span id="index-group_002dwritable-directories"></span> +<span id="index-setgid-scripts"></span> <p>Another approach is to establish a group (or user) for TeX files, make the <samp>texmf</samp> tree writable only to that group (or user), and make <code>mktexpk</code> et al. setgid to that group (or setuid to that @@ -500,14 +481,14 @@ 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.) </p> -<a name="index-file-permissions"></a> -<a name="index-permissions_002c-file"></a> +<span id="index-file-permissions"></span> +<span id="index-permissions_002c-file"></span> <p>The <samp>mktex…</samp> 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. </p> -<a name="index-directory-permissions"></a> -<a name="index-permissions_002c-directory"></a> +<span id="index-directory-permissions"></span> +<span id="index-permissions_002c-directory"></span> <p>Any directories created by the <samp>mktex…</samp> scripts have the same permissions as their parent directory, unless the <code>appendonlydir</code> feature is used, in which case the sticky bit is @@ -515,19 +496,17 @@ always set. </p> <hr> -<a name="TeX-directory-structure"></a> -<div class="header"> +<span id="TeX-directory-structure"></span><div class="header"> <p> Next: <a href="#Path-searching" accesskey="n" rel="next">Path searching</a>, Previous: <a href="#Security" accesskey="p" rel="prev">Security</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="TeX-directory-structure-1"></a> -<h2 class="chapter">4 TeX directory structure</h2> +<span id="TeX-directory-structure-1"></span><h2 class="chapter">4 TeX directory structure</h2> -<a name="index-TEXMF"></a> -<a name="index-TeX-directory-structure"></a> -<a name="index-directory-structure_002c-for-TeX-files"></a> -<a name="index-skeleton-TeX-directory"></a> -<a name="index-TDS"></a> +<span id="index-TEXMF"></span> +<span id="index-TeX-directory-structure"></span> +<span id="index-directory-structure_002c-for-TeX-files"></span> +<span id="index-skeleton-TeX-directory"></span> +<span id="index-TDS"></span> <p>This section describes the default installation hierarchy of the distribution. It conforms to both the GNU coding standards and the @@ -613,50 +592,46 @@ extracted from the TDS document: <hr> -<a name="Path-searching"></a> -<div class="header"> +<span id="Path-searching"></span><div class="header"> <p> Next: <a href="#TeX-support" accesskey="n" rel="next">TeX support</a>, Previous: <a href="#TeX-directory-structure" accesskey="p" rel="prev">TeX directory structure</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Path-searching-1"></a> -<h2 class="chapter">5 Path searching</h2> +<span id="Path-searching-1"></span><h2 class="chapter">5 Path searching</h2> -<a name="index-path-searching"></a> +<span id="index-path-searching"></span> <p>This chapter describes the generic path searching mechanism Kpathsea provides. For information about searching for particular file types (e.g., TeX fonts), see the next chapter. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Searching-overview" accesskey="1">Searching overview</a>:</td><td> </td><td align="left" valign="top">Basic scheme for searching. +<tr><td align="left" valign="top">• <a href="#Searching-overview" accesskey="1">Searching overview</a></td><td> </td><td align="left" valign="top">Basic scheme for searching. </td></tr> -<tr><td align="left" valign="top">• <a href="#Path-sources" accesskey="2">Path sources</a>:</td><td> </td><td align="left" valign="top">Where search paths can be defined. +<tr><td align="left" valign="top">• <a href="#Path-sources" accesskey="2">Path sources</a></td><td> </td><td align="left" valign="top">Where search paths can be defined. </td></tr> -<tr><td align="left" valign="top">• <a href="#Path-expansion" accesskey="3">Path expansion</a>:</td><td> </td><td align="left" valign="top">Special constructs in search paths. +<tr><td align="left" valign="top">• <a href="#Path-expansion" accesskey="3">Path expansion</a></td><td> </td><td align="left" valign="top">Special constructs in search paths. </td></tr> -<tr><td align="left" valign="top">• <a href="#Casefolding-search" accesskey="4">Casefolding search</a>:</td><td> </td><td align="left" valign="top">Fallback to case-insensitive search. +<tr><td align="left" valign="top">• <a href="#Casefolding-search" accesskey="4">Casefolding search</a></td><td> </td><td align="left" valign="top">Fallback to case-insensitive search. </td></tr> -<tr><td align="left" valign="top">• <a href="#Filename-database" accesskey="5">Filename database</a>:</td><td> </td><td align="left" valign="top">Using an externally-built list to search. +<tr><td align="left" valign="top">• <a href="#Filename-database" accesskey="5">Filename database</a></td><td> </td><td align="left" valign="top">Using an externally-built list to search. </td></tr> -<tr><td align="left" valign="top">• <a href="#Invoking-kpsewhich" accesskey="6">Invoking kpsewhich</a>:</td><td> </td><td align="left" valign="top">Standalone path lookup. +<tr><td align="left" valign="top">• <a href="#Invoking-kpsewhich" accesskey="6">Invoking kpsewhich</a></td><td> </td><td align="left" valign="top">Standalone path lookup. </td></tr> </table> <hr> -<a name="Searching-overview"></a> -<div class="header"> +<span id="Searching-overview"></span><div class="header"> <p> Next: <a href="#Path-sources" accesskey="n" rel="next">Path sources</a>, Up: <a href="#Path-searching" accesskey="u" rel="up">Path searching</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Searching-overview-1"></a> -<h3 class="section">5.1 Searching overview</h3> +<span id="Searching-overview-1"></span><h3 class="section">5.1 Searching overview</h3> -<a name="index-searching-overview"></a> -<a name="index-path-searching_002c-overview"></a> -<a name="index-overview-of-path-searching"></a> +<span id="index-searching-overview"></span> +<span id="index-path-searching_002c-overview"></span> +<span id="index-overview-of-path-searching"></span> -<a name="index-search-path_002c-defined"></a> +<span id="index-search-path_002c-defined"></span> <p>A <em>search path</em> is a colon-separated list of <em>path elements</em>, 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 @@ -664,24 +639,24 @@ come from (a combination of) many sources; see below. To look up a file the path in turn: first <samp>./foo</samp>, then <samp>/dir/foo</samp>, returning the first match (or possibly all matches). </p> -<a name="index-magic-characters"></a> -<a name="index-_003a-may-not-be-_003a"></a> -<a name="index-_002f-may-not-be-_002f"></a> +<span id="index-magic-characters"></span> +<span id="index-_003a-may-not-be-_003a"></span> +<span id="index-_002f-may-not-be-_002f"></span> <p>The “colon” and “slash” mentioned here aren’t necessarily ‘<samp>:</samp>’ and ‘<samp>/</samp>’ on non-Unix systems. Kpathsea tries to adapt to other operating systems’ conventions. </p> -<a name="index-database-search"></a> -<a name="index-searching-the-database"></a> +<span id="index-database-search"></span> +<span id="index-searching-the-database"></span> <p>To check a particular path element <var>e</var>, Kpathsea first sees if a prebuilt database (see <a href="#Filename-database">Filename database</a>) applies to <var>e</var>, i.e., if the database is in a directory that is a prefix of <var>e</var>. If so, the path specification is matched against the contents of the database. </p> -<a name="index-floating-directories"></a> -<a name="index-filesystem-search"></a> -<a name="index-disk-search"></a> -<a name="index-searching-the-disk"></a> +<span id="index-floating-directories"></span> +<span id="index-filesystem-search"></span> +<span id="index-disk-search"></span> +<span id="index-searching-the-disk"></span> <p>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 ‘<samp>!!</samp>’ and if the file being @@ -691,10 +666,10 @@ 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.) </p> -<a name="index-must-exist"></a> -<a name="index-VF-files_002c-not-found"></a> -<a name="index-cmr10_002evf"></a> -<a name="index-_005copenin"></a> +<span id="index-must-exist"></span> +<span id="index-VF-files_002c-not-found"></span> +<span id="index-cmr10_002evf"></span> +<span id="index-_005copenin"></span> <p>The “file must exist” condition comes into play with VF files and input files read by the TeX ‘<samp>\openin</samp>’ command. These files might very well not exist (consider <samp>cmr10.vf</samp>), and so it would @@ -714,7 +689,7 @@ final check is made for a case-insensitive match. Thus, looking for a name like ‘<samp>./FooBar.TeX</samp>’ will match a file ‘<samp>./foobar.tex</samp>’, and vice versa. This is not done on Windows. See <a href="#Casefolding-search">Casefolding search</a>. </p> -<a name="index-expansion_002c-path-element"></a> +<span id="index-expansion_002c-path-element"></span> <p>Although the simplest and most common path element is a directory name, Kpathsea supports additional features in search paths: layered default values, environment variable names, config file values, users’ home @@ -724,21 +699,21 @@ 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. </p> -<a name="index-absolute-filenames"></a> -<a name="index-relative-filenames"></a> -<a name="index-explicitly-relative-filenames"></a> -<a name="index-filenames_002c-absolute-or-explicitly-relative"></a> +<span id="index-absolute-filenames"></span> +<span id="index-relative-filenames"></span> +<span id="index-explicitly-relative-filenames"></span> +<span id="index-filenames_002c-absolute-or-explicitly-relative"></span> <p>Exception to all of the above: If the filename being searched for is absolute or explicitly relative, i.e., starts with ‘<samp>/</samp>’ or ‘<samp>./</samp>’ or ‘<samp>../</samp>’, Kpathsea simply checks if that file exists, with a fallback to a casefolding match if needed and enabled, as described above. </p> -<a name="index-permission-denied"></a> -<a name="index-unreadable-files"></a> -<a name="index-access-warnings"></a> -<a name="index-warnings_002c-file-access"></a> -<a name="index-lost_002bfound-directory"></a> -<a name="index-TEX_005fHUSH"></a> +<span id="index-permission-denied"></span> +<span id="index-unreadable-files"></span> +<span id="index-access-warnings"></span> +<span id="index-warnings_002c-file-access"></span> +<span id="index-lost_002bfound-directory"></span> +<span id="index-TEX_005fHUSH"></span> <p>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 @@ -752,37 +727,35 @@ algorithm when searching for a file of a particular type (see <a href="#File-loo </p> <hr> -<a name="Path-sources"></a> -<div class="header"> +<span id="Path-sources"></span><div class="header"> <p> Next: <a href="#Path-expansion" accesskey="n" rel="next">Path expansion</a>, Previous: <a href="#Searching-overview" accesskey="p" rel="prev">Searching overview</a>, Up: <a href="#Path-searching" accesskey="u" rel="up">Path searching</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Path-sources-1"></a> -<h3 class="section">5.2 Path sources</h3> +<span id="Path-sources-1"></span><h3 class="section">5.2 Path sources</h3> -<a name="index-path-sources"></a> -<a name="index-sources-for-search-paths"></a> +<span id="index-path-sources"></span> +<span id="index-sources-for-search-paths"></span> <p>A search path or other configuration value can come from many sources. In the order in which Kpathsea looks for them: </p> <ol> -<li> <a name="index-environment-variable_002c-source-for-path"></a> +<li> <span id="index-environment-variable_002c-source-for-path"></span> A user-set environment variable, e.g., <code>TEXINPUTS</code>. Environment variables with an underscore and the program name appended override; for example, <code>TEXINPUTS_latex</code> overrides <code>TEXINPUTS</code> if the program being run is named ‘<samp>latex</samp>’. </li><li> A program-specific configuration file, e.g., an ‘<samp>S /a:/b</samp>’ line in -Dvips’ <samp>config.ps</samp> (see <a href="http://tug.org/texinfohtml/dvips.html#Config-files">Config files</a> in <cite>Dvips</cite>). +Dvips’ <samp>config.ps</samp> (see <a href="https://tug.org/texinfohtml/dvips.html#Config-files">Config files</a> in <cite>Dvips</cite>). -</li><li> <a name="index-configuration-file_002c-source-for-path"></a> -<a name="index-Kpathsea-config-file_002c-source-for-path"></a> -<a name="index-texmf_002ecnf_002c-source-for-path"></a> +</li><li> <span id="index-configuration-file_002c-source-for-path"></span> +<span id="index-Kpathsea-config-file_002c-source-for-path"></span> +<span id="index-texmf_002ecnf_002c-source-for-path"></span> A line in a Kpathsea configuration file <samp>texmf.cnf</samp>, e.g., ‘<samp>TEXINPUTS=/c:/d</samp>’ (see below). -</li><li> <a name="index-compilation-value_002c-source-for-path"></a> +</li><li> <span id="index-compilation-value_002c-source-for-path"></span> The compile-time default (specified in <samp>kpathsea/paths.h</samp>). </li></ol> @@ -792,25 +765,23 @@ debugging options (see <a href="#Debugging">Debugging</a>). <p>These sources may be combined via default expansion (see <a href="#Default-expansion">Default expansion</a>). </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Config-files" accesskey="1">Config files</a>:</td><td> </td><td align="left" valign="top">Kpathsea’s runtime config files (texmf.cnf). +<tr><td align="left" valign="top">• <a href="#Config-files" accesskey="1">Config files</a></td><td> </td><td align="left" valign="top">Kpathsea’s runtime config files (texmf.cnf). </td></tr> </table> <hr> -<a name="Config-files"></a> -<div class="header"> +<span id="Config-files"></span><div class="header"> <p> Up: <a href="#Path-sources" accesskey="u" rel="up">Path sources</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Config-files-1"></a> -<h4 class="subsection">5.2.1 Config files</h4> +<span id="Config-files-1"></span><h4 class="subsection">5.2.1 Config files</h4> -<a name="index-config-files"></a> -<a name="index-texmf_002ecnf_002c-definition-for"></a> +<span id="index-config-files"></span> +<span id="index-texmf_002ecnf_002c-definition-for"></span> -<a name="index-runtime-configuration-files"></a> -<a name="index-TEXMFCNF"></a> +<span id="index-runtime-configuration-files"></span> +<span id="index-TEXMFCNF"></span> <p>As mentioned above, Kpathsea reads <em>runtime configuration files</em> named <samp>texmf.cnf</samp> for search path and other definitions. The search path used to look for these configuration files is named @@ -824,9 +795,9 @@ just the first one found; definitions in earlier files override those in later files. Thus, if the search path is ‘<samp>.:$TEXMF</samp>’, values from <samp>./texmf.cnf</samp> override those from <samp>$TEXMF/texmf.cnf</samp>. </p> -<a name="index-KPATHSEA_005fWARNING"></a> -<a name="index-warning_002c-about-missing-texmf_002ecnf"></a> -<a name="index-texmf_002ecnf-missing_002c-warning-about"></a> +<span id="index-KPATHSEA_005fWARNING"></span> +<span id="index-warning_002c-about-missing-texmf_002ecnf"></span> +<span id="index-texmf_002ecnf-missing_002c-warning-about"></span> <p>If Kpathsea cannot find any <samp>texmf.cnf</samp> file, it reports a warning including all the directories it checked. If you don’t want to see this warning, set the environment variable @@ -838,7 +809,7 @@ to look at the distributed <samp>texmf.cnf</samp>, which uses or at least mentions most features. The format of <samp>texmf.cnf</samp> files follows: </p> <ul> -<li> <a name="index-comments_002c-in-texmf_002ecnf"></a> +<li> <span id="index-comments_002c-in-texmf_002ecnf"></span> Comments start with ‘<samp>%</samp>’, either at the beginning of a line or preceded by whitespace, and continue to the end of the line. That is, as with most shells, a ‘<samp>%</samp>’ in the “middle” of a value does not @@ -849,13 +820,13 @@ start a comment. Examples: var = a%b % but the value of var will be "a%b". </pre></div> -</li><li> <a name="index-blank-lines_002c-in-texmf_002ecnf"></a> +</li><li> <span id="index-blank-lines_002c-in-texmf_002ecnf"></span> Blank lines are ignored. -</li><li> <a name="index-backslash_002dnewline"></a> -<a name="index-continuation-character"></a> -<a name="index-whitespace_002c-not-ignored-on-continuation-lines"></a> -<a name="index-_005c_002c-line-continuation-in-texmf_002ecnf"></a> +</li><li> <span id="index-backslash_002dnewline"></span> +<span id="index-continuation-character"></span> +<span id="index-whitespace_002c-not-ignored-on-continuation-lines"></span> +<span id="index-_005c_002c-line-continuation-in-texmf_002ecnf"></span> A ‘<samp>\</samp>’ 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. @@ -868,7 +839,7 @@ lines is not ignored. <p>where the ‘<samp>=</samp>’ and surrounding whitespace is optional. </p> -</li><li> <a name="index-identifiers_002c-characters-valid-in"></a> +</li><li> <span id="index-identifiers_002c-characters-valid-in"></span> The <var>variable</var> name may contain any character other than whitespace, ‘<samp>=</samp>’, or ‘<samp>.</samp>’, but sticking to ‘<samp>A-Za-z_</samp>’ is safest. @@ -878,7 +849,7 @@ component of <code>argv[0]</code> is) <var>progname</var> or <samp><var>progname</var>.{exe,bat,cmd,...}</samp>. Most notably, this allows different flavors of TeX to have different search paths. -</li><li> <a name="index-right_002dhand-side-of-variable-assignments"></a> +</li><li> <span id="index-right_002dhand-side-of-variable-assignments"></span> <var>value</var> may contain any characters except ‘<samp>%</samp>’ and ‘<samp>@</samp>’. (These restrictions are only necessary because of the processing done on <samp>texmf.cnf</samp> at build time, so you can stick those characters @@ -907,8 +878,8 @@ TEXINPUTS.latex2e = $latex2e_inputs TEXINPUTS.latex = $latex2e_inputs </pre></div> -<a name="index-shell-scripts-as-configuration-files"></a> -<a name="index-configuration-files-as-shell-scripts_002e"></a> +<span id="index-shell-scripts-as-configuration-files"></span> +<span id="index-configuration-files-as-shell-scripts_002e"></span> <p>This format has obvious similarities to Bourne shell scripts—change the comment character to <code>#</code>, disallow spaces around the <code>=</code>, and get rid of the <code>.<var>name</var></code> convention, and it @@ -917,21 +888,19 @@ advantage in this, since all the information would have to passed back to Kpathsea and parsed there anyway, since the <code>sh</code> process couldn’t affect its parent’s environment. </p> -<a name="index-cnf_002ec"></a> +<span id="index-cnf_002ec"></span> <p>The implementation of all this is in <samp>kpathsea/cnf.c</samp>. </p> <hr> -<a name="Path-expansion"></a> -<div class="header"> +<span id="Path-expansion"></span><div class="header"> <p> Next: <a href="#Casefolding-search" accesskey="n" rel="next">Casefolding search</a>, Previous: <a href="#Path-sources" accesskey="p" rel="prev">Path sources</a>, Up: <a href="#Path-searching" accesskey="u" rel="up">Path searching</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Path-expansion-1"></a> -<h3 class="section">5.3 Path expansion</h3> +<span id="Path-expansion-1"></span><h3 class="section">5.3 Path expansion</h3> -<a name="index-path-expansion"></a> -<a name="index-expansion_002c-search-path"></a> +<span id="index-path-expansion"></span> +<span id="index-expansion_002c-search-path"></span> <p>Kpathsea recognizes certain special characters and constructions in search paths, similar to that in shells. As a general example: @@ -942,37 +911,35 @@ contain a directory or file <samp>baz</samp>. <p>These expansions are explained in the sections below. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Default-expansion" accesskey="1">Default expansion</a>:</td><td> </td><td align="left" valign="top">a: or :a or a::b expands to a default. +<tr><td align="left" valign="top">• <a href="#Default-expansion" accesskey="1">Default expansion</a></td><td> </td><td align="left" valign="top">a: or :a or a::b expands to a default. </td></tr> -<tr><td align="left" valign="top">• <a href="#Variable-expansion" accesskey="2">Variable expansion</a>:</td><td> </td><td align="left" valign="top">$foo and ${foo} expand to environment values. +<tr><td align="left" valign="top">• <a href="#Variable-expansion" accesskey="2">Variable expansion</a></td><td> </td><td align="left" valign="top">$foo and ${foo} expand to environment values. </td></tr> -<tr><td align="left" valign="top">• <a href="#Tilde-expansion" accesskey="3">Tilde expansion</a>:</td><td> </td><td align="left" valign="top">~ and ~user expand to home directories. +<tr><td align="left" valign="top">• <a href="#Tilde-expansion" accesskey="3">Tilde expansion</a></td><td> </td><td align="left" valign="top">~ and ~user expand to home directories. </td></tr> -<tr><td align="left" valign="top">• <a href="#Brace-expansion" accesskey="4">Brace expansion</a>:</td><td> </td><td align="left" valign="top">a{foo,bar}b expands to afoob abarb. +<tr><td align="left" valign="top">• <a href="#Brace-expansion" accesskey="4">Brace expansion</a></td><td> </td><td align="left" valign="top">a{foo,bar}b expands to afoob abarb. </td></tr> -<tr><td align="left" valign="top">• <a href="#KPSE_005fDOT-expansion" accesskey="5">KPSE_DOT expansion</a>:</td><td> </td><td align="left" valign="top">. is replaced with $KPSE_DOT if it is defined. +<tr><td align="left" valign="top">• <a href="#KPSE_005fDOT-expansion" accesskey="5">KPSE_DOT expansion</a></td><td> </td><td align="left" valign="top">. is replaced with $KPSE_DOT if it is defined. </td></tr> -<tr><td align="left" valign="top">• <a href="#Subdirectory-expansion" accesskey="6">Subdirectory expansion</a>:</td><td> </td><td align="left" valign="top">a// and a//b recursively expand to subdirs. +<tr><td align="left" valign="top">• <a href="#Subdirectory-expansion" accesskey="6">Subdirectory expansion</a></td><td> </td><td align="left" valign="top">a// and a//b recursively expand to subdirs. </td></tr> </table> <hr> -<a name="Default-expansion"></a> -<div class="header"> +<span id="Default-expansion"></span><div class="header"> <p> Next: <a href="#Variable-expansion" accesskey="n" rel="next">Variable expansion</a>, Up: <a href="#Path-expansion" accesskey="u" rel="up">Path expansion</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Default-expansion-1"></a> -<h4 class="subsection">5.3.1 Default expansion</h4> +<span id="Default-expansion-1"></span><h4 class="subsection">5.3.1 Default expansion</h4> -<a name="index-_003a_003a-expansion"></a> -<a name="index-doubled-colons"></a> -<a name="index-leading-colons"></a> -<a name="index-trailing-colons"></a> -<a name="index-extra-colons"></a> -<a name="index-default-expansion"></a> -<a name="index-expansion_002c-default"></a> +<span id="index-_003a_003a-expansion"></span> +<span id="index-doubled-colons"></span> +<span id="index-leading-colons"></span> +<span id="index-trailing-colons"></span> +<span id="index-extra-colons"></span> +<span id="index-default-expansion"></span> +<span id="index-expansion_002c-default"></span> <p>If the highest-priority search path (see <a href="#Path-sources">Path sources</a>) contains an <em>extra colon</em> (i.e., leading, trailing, or doubled), Kpathsea @@ -1018,7 +985,7 @@ Or, with Dvips’ configuration files, that an extra colon in 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. -<a name="index-Bach_002c-Johann-Sebastian"></a> +<span id="index-Bach_002c-Johann-Sebastian"></span> </p> <p>Technicality: Since it would be useless to insert the default value in more than one place, Kpathsea changes only one extra ‘<samp>:</samp>’ and leaves @@ -1026,26 +993,24 @@ any others in place (they will eventually be ignored). Kpathsea checks first for a leading ‘<samp>:</samp>’, then a trailing ‘<samp>:</samp>’, then a doubled ‘<samp>:</samp>’. </p> -<a name="index-kdefault_002ec"></a> +<span id="index-kdefault_002ec"></span> <p>You can trace this by debugging “paths” (see <a href="#Debugging">Debugging</a>). Default expansion is implemented in the source file <samp>kpathsea/kdefault.c</samp>. </p> <hr> -<a name="Variable-expansion"></a> -<div class="header"> +<span id="Variable-expansion"></span><div class="header"> <p> Next: <a href="#Tilde-expansion" accesskey="n" rel="next">Tilde expansion</a>, Previous: <a href="#Default-expansion" accesskey="p" rel="prev">Default expansion</a>, Up: <a href="#Path-expansion" accesskey="u" rel="up">Path expansion</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Variable-expansion-1"></a> -<h4 class="subsection">5.3.2 Variable expansion</h4> +<span id="Variable-expansion-1"></span><h4 class="subsection">5.3.2 Variable expansion</h4> -<a name="index-_0024-expansion"></a> -<a name="index-environment-variables-in-paths"></a> -<a name="index-variable-expansion"></a> -<a name="index-expansion_002c-variable"></a> -<a name="index-texmf_002ecnf_002c-and-variable-expansion"></a> +<span id="index-_0024-expansion"></span> +<span id="index-environment-variables-in-paths"></span> +<span id="index-variable-expansion"></span> +<span id="index-expansion_002c-variable"></span> +<span id="index-texmf_002ecnf_002c-and-variable-expansion"></span> <p>‘<samp>$foo</samp>’ or ‘<samp>${foo}</samp>’ in a path element is replaced by (1) the value of an environment variable ‘<samp>foo</samp>’ (if defined); (2) the value @@ -1058,8 +1023,8 @@ of everything up to the next ‘<samp>}</samp>’ (braces may not be nes variable names). Otherwise, Kpathsea gives a warning and ignores the ‘<samp>$</samp>’ and its following character. </p> -<a name="index-quoting-variable-values"></a> -<a name="index-shell-variables"></a> +<span id="index-quoting-variable-values"></span> +<span id="index-shell-variables"></span> <p>You must quote the <tt>$</tt>’s and braces as necessary for your shell. <em>Shell</em> variable values cannot be seen by Kpathsea, i.e., ones defined by <code>set</code> in C shells and without <code>export</code> in Bourne @@ -1080,27 +1045,25 @@ setenv TEXINPUTS .:$tex:${tex}prev for general variable expansions. These are only recognized when search paths are initialized (see <a href="#Path-sources">Path sources</a>). </p> -<a name="index-variable_002ec"></a> +<span id="index-variable_002ec"></span> <p>Variable expansion is implemented in the source file <samp>kpathsea/variable.c</samp>. </p> <hr> -<a name="Tilde-expansion"></a> -<div class="header"> +<span id="Tilde-expansion"></span><div class="header"> <p> Next: <a href="#Brace-expansion" accesskey="n" rel="next">Brace expansion</a>, Previous: <a href="#Variable-expansion" accesskey="p" rel="prev">Variable expansion</a>, Up: <a href="#Path-expansion" accesskey="u" rel="up">Path expansion</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Tilde-expansion-1"></a> -<h4 class="subsection">5.3.3 Tilde expansion</h4> +<span id="Tilde-expansion-1"></span><h4 class="subsection">5.3.3 Tilde expansion</h4> -<a name="index-_007e-expansion"></a> -<a name="index-home-directories-in-paths"></a> -<a name="index-tilde-expansion"></a> -<a name="index-expansion_002c-tilde"></a> +<span id="index-_007e-expansion"></span> +<span id="index-home-directories-in-paths"></span> +<span id="index-tilde-expansion"></span> +<span id="index-expansion_002c-tilde"></span> -<a name="index-HOME_002c-as-_007e-expansion"></a> -<a name="index-USERPROFILE_002c-as-_007e-expansion"></a> +<span id="index-HOME_002c-as-_007e-expansion"></span> +<span id="index-USERPROFILE_002c-as-_007e-expansion"></span> <p>A leading ‘<samp>~</samp>’ in a path element is replaced by the value of the environment variable <code>HOME</code>, or <samp>.</samp> if <code>HOME</code> is not set. On Windows, the environment variable <code>USERPROFILE</code> is @@ -1117,30 +1080,28 @@ checked instead of <code>HOME</code>. <p>will prepend a directory <samp>mymacros</samp> in your home directory to the default path. </p> -<a name="index-root-user"></a> -<a name="index-trailing-_002f-in-home-directory"></a> -<a name="index-_002f_002c-trailing-in-home-directory"></a> +<span id="index-root-user"></span> +<span id="index-trailing-_002f-in-home-directory"></span> +<span id="index-_002f_002c-trailing-in-home-directory"></span> <p>As a special case, if a home directory ends in ‘<samp>/</samp>’, the trailing slash is dropped, to avoid inadvertently creating a ‘<samp>//</samp>’ construct in the path. For example, if the home directory of the user ‘<samp>root</samp>’ is ‘<samp>/</samp>’, the path element ‘<samp>~root/mymacros</samp>’ expands to just ‘<samp>/mymacros</samp>’, not ‘<samp>//mymacros</samp>’. </p> -<a name="index-tilde_002ec"></a> +<span id="index-tilde_002ec"></span> <p>Tilde expansion is implemented in the source file <samp>kpathsea/tilde.c</samp>. </p> <hr> -<a name="Brace-expansion"></a> -<div class="header"> +<span id="Brace-expansion"></span><div class="header"> <p> Next: <a href="#KPSE_005fDOT-expansion" accesskey="n" rel="next">KPSE_DOT expansion</a>, Previous: <a href="#Tilde-expansion" accesskey="p" rel="prev">Tilde expansion</a>, Up: <a href="#Path-expansion" accesskey="u" rel="up">Path expansion</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Brace-expansion-1"></a> -<h4 class="subsection">5.3.4 Brace expansion</h4> +<span id="Brace-expansion-1"></span><h4 class="subsection">5.3.4 Brace expansion</h4> -<a name="index-_007b-expansion"></a> -<a name="index-brace-expansion"></a> +<span id="index-_007b-expansion"></span> +<span id="index-brace-expansion"></span> <p>‘<samp>x{<var>a</var>,<var>b</var>}y</samp>’ expands to ‘<samp>x<var>a</var>y:x<var>b</var>y</samp>’. For example: @@ -1150,7 +1111,7 @@ For example: </pre></div> <p>expands to ‘<samp>foo/1/baz:foo/2/baz</samp>’. ‘<samp>:</samp>’ is the path -separator on the current system; e.g., on a DOS system, it’s ‘<samp>;</samp>’. +separator on the current system; e.g., on a Windows system, it’s ‘<samp>;</samp>’. </p> <p>Braces can be nested; for example, ‘<samp>x{A,B{1,2}}y</samp>’ expands to ‘<samp>xAy:xB1y:xB2y</samp>’. @@ -1159,30 +1120,28 @@ separator on the current system; e.g., on a DOS system, it’s ‘<samp> ‘<samp>x{A,B}{1,2}y</samp>’ expands to ‘<samp>x{A,B}1y:x{A,B}2y</samp>’, which expands to ‘<samp>xA1y:xB1y:xA2y:xB2y</samp>’. </p> -<a name="index-multiple-TeX-hierarchies"></a> +<span id="index-multiple-TeX-hierarchies"></span> <p>This feature can be used to implement multiple TeX hierarchies, by assigning a brace list to <code>$TEXMF</code>, as mentioned in <samp>texmf.in</samp>. </p> <p>You can also use the path separator instead of the comma. The last -example could have been written ‘<samp>x{A:B}{1:2}y</samp>’. +example could have been written ‘<samp>x{A:B}{1:2}y</samp>’ (on Unix). </p> -<a name="index-expand_002ec"></a> +<span id="index-expand_002ec"></span> <p>Brace expansion is implemented in the source file <samp>kpathsea/expand.c</samp>. </p> <hr> -<a name="KPSE_005fDOT-expansion"></a> -<div class="header"> +<span id="KPSE_005fDOT-expansion"></span><div class="header"> <p> Next: <a href="#Subdirectory-expansion" accesskey="n" rel="next">Subdirectory expansion</a>, Previous: <a href="#Brace-expansion" accesskey="p" rel="prev">Brace expansion</a>, Up: <a href="#Path-expansion" accesskey="u" rel="up">Path expansion</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="KPSE_005fDOT-expansion-1"></a> -<h4 class="subsection">5.3.5 <code>KPSE_DOT</code> expansion</h4> +<span id="KPSE_005fDOT-expansion-1"></span><h4 class="subsection">5.3.5 <code>KPSE_DOT</code> expansion</h4> -<a name="index-KPSE_005fDOT-expansion"></a> +<span id="index-KPSE_005fDOT-expansion"></span> <p>When <code>KPSE_DOT</code> is defined in the environment, it names a directory that should be considered the current directory for the purpose of @@ -1192,19 +1151,17 @@ change the working directory. You should not ever define it yourself. </p> <hr> -<a name="Subdirectory-expansion"></a> -<div class="header"> +<span id="Subdirectory-expansion"></span><div class="header"> <p> Previous: <a href="#KPSE_005fDOT-expansion" accesskey="p" rel="prev">KPSE_DOT expansion</a>, Up: <a href="#Path-expansion" accesskey="u" rel="up">Path expansion</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Subdirectory-expansion-1"></a> -<h4 class="subsection">5.3.6 Subdirectory expansion</h4> +<span id="Subdirectory-expansion-1"></span><h4 class="subsection">5.3.6 Subdirectory expansion</h4> -<a name="index-_002f_002f"></a> -<a name="index-subdirectory-searching"></a> -<a name="index-expansion_002c-subdirectory"></a> +<span id="index-_002f_002f"></span> +<span id="index-subdirectory-searching"></span> +<span id="index-expansion_002c-subdirectory"></span> -<a name="index-alphabetical-order_002c-not"></a> +<span id="index-alphabetical-order_002c-not"></span> <p>Two or more consecutive slashes in a path element following a directory <var>d</var> is replaced by all subdirectories of <var>d</var>: first those subdirectories directly under <var>d</var>, then the subsubdirectories under @@ -1222,14 +1179,14 @@ subdirectories which match those components are included. For example, <p>‘<samp>//</samp>’ at the beginning of a path is ignored; you didn’t really want to search every directory on the system, did you? </p> -<a name="index-trick-for-detecting-leaf-directories"></a> -<a name="index-leaf-directory-trick"></a> -<a name="index-Farwell_002c-Matthew"></a> -<a name="index-MacKenzie_002c-David-1"></a> +<span id="index-trick-for-detecting-leaf-directories"></span> +<span id="index-leaf-directory-trick"></span> +<span id="index-Farwell_002c-Matthew"></span> +<span id="index-MacKenzie_002c-David-1"></span> <p>I should mention one related implementation trick, which I took from GNU find. Matthew Farwell suggested it, and David MacKenzie implemented it. </p> -<a name="index-st_005fnlink"></a> +<span id="index-st_005fnlink"></span> <p>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 <samp>.</samp> and one for <samp>..</samp>). @@ -1242,11 +1199,11 @@ and do no more work. regular files, <code>st_nlink</code> will be 3, and Kpathsea has to stat every one of those 501 entries. Therein lies slowness. </p> -<a name="index-ST_005fNLINK_005fTRICK"></a> +<span id="index-ST_005fNLINK_005fTRICK"></span> <p>You can disable the trick by undefining <code>ST_NLINK_TRICK</code> in <samp>kpathsea/config.h</samp>. (It is undefined by default except under Unix.) </p> -<a name="index-elt_002ddirs_002ec"></a> +<span id="index-elt_002ddirs_002ec"></span> <p>Unfortunately, in some cases files in leaf directories are <code>stat</code>’d: if the path specification is, say, ‘<samp>$TEXMF/fonts//pk//</samp>’, then files in a subdirectory @@ -1256,22 +1213,20 @@ be explained without reference to the implementation, so read curious. And if you can find a way to <em>solve</em> the problem, please let me know. </p> -<a name="index-elt_002ddirs_002ec-1"></a> +<span id="index-elt_002ddirs_002ec-1"></span> <p>Subdirectory expansion is implemented in the source file <samp>kpathsea/elt-dirs.c</samp>. </p> <hr> -<a name="Casefolding-search"></a> -<div class="header"> +<span id="Casefolding-search"></span><div class="header"> <p> Next: <a href="#Filename-database" accesskey="n" rel="next">Filename database</a>, Previous: <a href="#Path-expansion" accesskey="p" rel="prev">Path expansion</a>, Up: <a href="#Path-searching" accesskey="u" rel="up">Path searching</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Casefolding-search-1"></a> -<h3 class="section">5.4 Casefolding search</h3> +<span id="Casefolding-search-1"></span><h3 class="section">5.4 Casefolding search</h3> -<a name="index-casefolding-search"></a> -<a name="index-search_002c-case_002dinsensitive"></a> +<span id="index-casefolding-search"></span> +<span id="index-search_002c-case_002dinsensitive"></span> <p>In Kpathsea version 6.3.0 (released with TeX Live 2018), a new fallback search was implemented on Unix-like systems, including Macs: @@ -1279,35 +1234,33 @@ for each path element in turn, if no match is found by the normal search, and the path element allows for checking the filesystem, a second check is made for a case-insensitive match. </p> -<a name="index-texmf_005fcasefold_005fsearch"></a> +<span id="index-texmf_005fcasefold_005fsearch"></span> <p>This is enabled at compile-time on Unix systems, and enabled at runtime by setting the configuration variable <code>texmf_casefold_search</code>, to a true value, e.g., ‘<samp>1</samp>’; this is done by default in TeX Live. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Casefolding-rationale" accesskey="1">Rationale</a>:</td><td> </td><td align="left" valign="top"> +<tr><td align="left" valign="top">• <a href="#Casefolding-rationale" accesskey="1">Rationale</a></td><td> </td><td align="left" valign="top"> </td></tr> -<tr><td align="left" valign="top">• <a href="#Casefolding-examples" accesskey="2">Examples</a>:</td><td> </td><td align="left" valign="top"> +<tr><td align="left" valign="top">• <a href="#Casefolding-examples" accesskey="2">Examples</a></td><td> </td><td align="left" valign="top"> </td></tr> </table> <hr> -<a name="Casefolding-rationale"></a> -<div class="header"> +<span id="Casefolding-rationale"></span><div class="header"> <p> Next: <a href="#Casefolding-examples" accesskey="n" rel="next">Casefolding examples</a>, Up: <a href="#Casefolding-search" accesskey="u" rel="up">Casefolding search</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Casefolding-rationale-1"></a> -<h4 class="subsection">5.4.1 Casefolding rationale</h4> +<span id="Casefolding-rationale-1"></span><h4 class="subsection">5.4.1 Casefolding rationale</h4> -<a name="index-casefolding-fallback-rationale"></a> -<a name="index-rationale-for-casefolding-fallback"></a> -<a name="index-system_002ddependent-casefolding-behavior"></a> +<span id="index-casefolding-fallback-rationale"></span> +<span id="index-rationale-for-casefolding-fallback"></span> +<span id="index-system_002ddependent-casefolding-behavior"></span> -<a name="index-filesystem_002c-case_002d_0028in_0029sensitive"></a> -<a name="index-Apple-filesystem_002c-case_002dinsensitive"></a> -<a name="index-Mac-filesystem_002c-case_002dinsensitive"></a> +<span id="index-filesystem_002c-case_002d_0028in_0029sensitive"></span> +<span id="index-Apple-filesystem_002c-case_002dinsensitive"></span> +<span id="index-Mac-filesystem_002c-case_002dinsensitive"></span> <p>The purpose of the fallback casefolding search is to ease moving complex documents between case-insensitive (file)systems and case-sensitive ones. In particular, Apple decided to make the default @@ -1324,7 +1277,7 @@ whatever reason, it has become much more common since Apple also went to a case-insensitive filesystem. Hence the move to change the Kpathsea behavior now. </p> -<a name="index-Windows-and-casefolding"></a> +<span id="index-Windows-and-casefolding"></span> <p>The fallback case-insensitive search is omitted at compile-time on Windows, where (for practical purposes) all file names are case-insensitive at the kernel level, and so the normal search will @@ -1334,16 +1287,14 @@ always been true. </p> <hr> -<a name="Casefolding-examples"></a> -<div class="header"> +<span id="Casefolding-examples"></span><div class="header"> <p> Previous: <a href="#Casefolding-rationale" accesskey="p" rel="prev">Casefolding rationale</a>, Up: <a href="#Casefolding-search" accesskey="u" rel="up">Casefolding search</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Casefolding-examples-1"></a> -<h4 class="subsection">5.4.2 Casefolding examples</h4> +<span id="Casefolding-examples-1"></span><h4 class="subsection">5.4.2 Casefolding examples</h4> -<a name="index-casefolding-examples"></a> -<a name="index-examples_002c-of-casefolding-searches"></a> +<span id="index-casefolding-examples"></span> +<span id="index-examples_002c-of-casefolding-searches"></span> <p>The casefolding implementation prefers exact matches to casefolded matches within a given path element, so as to retain most @@ -1424,8 +1375,8 @@ tr ':' '\n' </tmp/texdirs >/tmp/texdirlist # colons to newlines find `cat /tmp/texdirlist` -iname somefile.tex -print </tmp/texdirlist </pre></div> -<a name="index-Findutils_002c-GNU-package"></a> -<a name="index-_002diname_002c-find-predicate"></a> +<span id="index-Findutils_002c-GNU-package"></span> +<span id="index-_002diname_002c-find-predicate"></span> <p>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 <code>find</code> does not support @@ -1436,7 +1387,7 @@ only useful for debugging. If your <code>find</code> does not support <samp>kpathsea/pathsearch.c</samp>. Two implementation points: </p> <ul> -<li> <a name="index-access-system-call"></a> +<li> <span id="index-access-system-call"></span> 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 @@ -1452,17 +1403,15 @@ happens with the elements of the leaf directory. <hr> -<a name="Filename-database"></a> -<div class="header"> +<span id="Filename-database"></span><div class="header"> <p> Next: <a href="#Invoking-kpsewhich" accesskey="n" rel="next">Invoking kpsewhich</a>, Previous: <a href="#Casefolding-search" accesskey="p" rel="prev">Casefolding search</a>, Up: <a href="#Path-searching" accesskey="u" rel="up">Path searching</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Filename-database-_0028ls_002dR_0029"></a> -<h3 class="section">5.5 Filename database (<code>ls-R</code>)</h3> +<span id="Filename-database-_0028ls_002dR_0029"></span><h3 class="section">5.5 Filename database (<code>ls-R</code>)</h3> -<a name="index-filename-database"></a> -<a name="index-database_002c-for-filenames"></a> -<a name="index-externally_002dbuilt-filename-database"></a> +<span id="index-filename-database"></span> +<span id="index-database_002c-for-filenames"></span> +<span id="index-externally_002dbuilt-filename-database"></span> <p>Kpathsea goes to some lengths to minimize disk accesses for searches (see <a href="#Subdirectory-expansion">Subdirectory expansion</a>). Nevertheless, in practice searching @@ -1481,26 +1430,24 @@ to “8.3” filename conventions in source files. source file <samp>kpathsea/db.c</samp>. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#ls_002dR" accesskey="1">ls-R</a>:</td><td> </td><td align="left" valign="top">The main filename database. +<tr><td align="left" valign="top">• <a href="#ls_002dR" accesskey="1">ls-R</a></td><td> </td><td align="left" valign="top">The main filename database. </td></tr> -<tr><td align="left" valign="top">• <a href="#Filename-aliases" accesskey="2">Filename aliases</a>:</td><td> </td><td align="left" valign="top">Aliases for those names. +<tr><td align="left" valign="top">• <a href="#Filename-aliases" accesskey="2">Filename aliases</a></td><td> </td><td align="left" valign="top">Aliases for those names. </td></tr> -<tr><td align="left" valign="top">• <a href="#Database-format" accesskey="3">Database format</a>:</td><td> </td><td align="left" valign="top">Syntax details of the database file. +<tr><td align="left" valign="top">• <a href="#Database-format" accesskey="3">Database format</a></td><td> </td><td align="left" valign="top">Syntax details of the database file. </td></tr> </table> <hr> -<a name="ls_002dR"></a> -<div class="header"> +<span id="ls_002dR"></span><div class="header"> <p> Next: <a href="#Filename-aliases" accesskey="n" rel="next">Filename aliases</a>, Up: <a href="#Filename-database" accesskey="u" rel="up">Filename database</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="ls_002dR-1"></a> -<h4 class="subsection">5.5.1 <samp>ls-R</samp></h4> +<span id="ls_002dR-1"></span><h4 class="subsection">5.5.1 <samp>ls-R</samp></h4> -<a name="index-ls_002dR-database-file"></a> -<a name="index-TEXMFDBS"></a> +<span id="index-ls_002dR-database-file"></span> +<span id="index-TEXMFDBS"></span> <p>As mentioned above, you must name the main filename database <samp>ls-R</samp>. You can put one at the root of each TeX installation @@ -1515,14 +1462,14 @@ hierarchies. follow symbolic links as necessary, etc. It’s also invoked by the distributed ‘<samp>mktex…</samp>’ scripts. </p> -<a name="index-ls_002dR_002c-simplest-build"></a> +<span id="index-ls_002dR_002c-simplest-build"></span> <p>At its simplest, though, you can build <samp>ls-R</samp> with the command </p><div class="example"> <pre class="example">cd <var>/your/texmf/root</var> && ls -LAR ./ >ls-R </pre></div> -<p><a name="index-_002d_002dcolor_003dtty"></a> -<a name="index-_002fetc_002fprofile-and-aliases"></a> +<p><span id="index-_002d_002dcolor_003dtty"></span> +<span id="index-_002fetc_002fprofile-and-aliases"></span> presuming your <code>ls</code> produces the right output format (see the section below). GNU <code>ls</code>, for example, outputs in this format. Also presuming your <code>ls</code> hasn’t been aliased in a system file @@ -1536,29 +1483,29 @@ almost certainly want to invoke it via <code>cron</code>, so when you make changes in the installed files (say if you install a new LaTeX package), <samp>ls-R</samp> will be automatically updated. </p> -<a name="index-_002dA-option-to-ls"></a> -<a name="index-dot-files"></a> -<a name="index-_002e-files"></a> -<a name="index-_002e-directories_002c-ignored"></a> -<a name="index-_002etex-file_002c-included-in-ls_002dR"></a> +<span id="index-_002dA-option-to-ls"></span> +<span id="index-dot-files"></span> +<span id="index-_002e-files"></span> +<span id="index-_002e-directories_002c-ignored"></span> +<span id="index-_002etex-file_002c-included-in-ls_002dR"></span> <p>The ‘<samp>-A</samp>’ option to <code>ls</code> includes files beginning with ‘<samp>.</samp>’ (except for <samp>.</samp> and <samp>..</samp>), such as the file <samp>.tex</samp> included with the LaTeX tools package. (On the other hand, <em>directories</em> whose names begin with ‘<samp>.</samp>’ are always ignored.) </p> -<a name="index-symbolic-links_002c-and-ls_002dR"></a> -<a name="index-_002dL-option-to-ls"></a> +<span id="index-symbolic-links_002c-and-ls_002dR"></span> +<span id="index-_002dL-option-to-ls"></span> <p>If your system does not support symbolic links, omit the ‘<samp>-L</samp>’. </p> -<a name="index-automounter_002c-and-ls_002dR"></a> -<a name="index-NFS-and-ls_002dR"></a> +<span id="index-automounter_002c-and-ls_002dR"></span> +<span id="index-NFS-and-ls_002dR"></span> <p><code>ls -LAR <var>/your/texmf/root</var></code> will also work. But using ‘<samp>./</samp>’ avoids embedding absolute pathnames, so the hierarchy can be easily transported. It also avoids possible trouble with automounters or other network filesystem conventions. </p> -<a name="index-warning-about-unusable-ls_002dR"></a> -<a name="index-unusable-ls_002dR-warning"></a> +<span id="index-warning-about-unusable-ls_002dR"></span> +<span id="index-unusable-ls_002dR-warning"></span> <p>Kpathsea warns you if it finds an <samp>ls-R</samp> file, but the file does not contain any usable entries. The usual culprit is running plain ‘<samp>ls -R</samp>’ instead of ‘<samp>ls -LR ./</samp>’ or ‘<samp>ls -R @@ -1566,8 +1513,8 @@ not contain any usable entries. The usual culprit is running plain name starting with a ‘<samp>.</samp>’ (perhaps if you are using AFS); Kpathsea ignores everything under such directories. </p> -<a name="index-_0021_0021-in-path-specifications"></a> -<a name="index-disk-searching_002c-avoiding"></a> +<span id="index-_0021_0021-in-path-specifications"></span> +<span id="index-disk-searching_002c-avoiding"></span> <p>Because the database may be out-of-date for a particular run, if a file is not found in the database, by default Kpathsea goes ahead and searches the disk. If a particular path element begins with ‘<samp>!!</samp>’, @@ -1579,16 +1526,14 @@ is not in any of the default search paths. </p> <hr> -<a name="Filename-aliases"></a> -<div class="header"> +<span id="Filename-aliases"></span><div class="header"> <p> Next: <a href="#Database-format" accesskey="n" rel="next">Database format</a>, Previous: <a href="#ls_002dR" accesskey="p" rel="prev">ls-R</a>, Up: <a href="#Filename-database" accesskey="u" rel="up">Filename database</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Filename-aliases-1"></a> -<h4 class="subsection">5.5.2 Filename aliases</h4> +<span id="Filename-aliases-1"></span><h4 class="subsection">5.5.2 Filename aliases</h4> -<a name="index-filename-aliases"></a> -<a name="index-aliases_002c-for-filenames"></a> +<span id="index-filename-aliases"></span> +<span id="index-aliases_002c-for-filenames"></span> <p>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 @@ -1616,16 +1561,14 @@ aliases. </p> <hr> -<a name="Database-format"></a> -<div class="header"> +<span id="Database-format"></span><div class="header"> <p> Previous: <a href="#Filename-aliases" accesskey="p" rel="prev">Filename aliases</a>, Up: <a href="#Filename-database" accesskey="u" rel="up">Filename database</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Database-format-1"></a> -<h4 class="subsection">5.5.3 Database format</h4> +<span id="Database-format-1"></span><h4 class="subsection">5.5.3 Database format</h4> -<a name="index-format-of-external-database"></a> -<a name="index-database_002c-format-of"></a> +<span id="index-format-of-external-database"></span> +<span id="index-database_002c-format-of"></span> <p>The “database” read by Kpathsea is a line-oriented file of plain text. The format is that generated by GNU (and most other) <code>ls</code> @@ -1670,17 +1613,15 @@ btxdoc.bib <hr> -<a name="Invoking-kpsewhich"></a> -<div class="header"> +<span id="Invoking-kpsewhich"></span><div class="header"> <p> Previous: <a href="#Filename-database" accesskey="p" rel="prev">Filename database</a>, Up: <a href="#Path-searching" accesskey="u" rel="up">Path searching</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="kpsewhich_003a-Standalone-path-searching"></a> -<h3 class="section">5.6 <code>kpsewhich</code>: Standalone path searching</h3> +<span id="kpsewhich_003a-Standalone-path-searching"></span><h3 class="section">5.6 <code>kpsewhich</code>: Standalone path searching</h3> -<a name="index-kpsewhich"></a> -<a name="index-path-searching_002c-standalone"></a> -<a name="index-standalone-path-searching"></a> +<span id="index-kpsewhich"></span> +<span id="index-path-searching_002c-standalone"></span> +<span id="index-standalone-path-searching"></span> <p>The Kpsewhich program exercises the path searching functionality independent of any particular application. This can also be useful as a @@ -1699,27 +1640,25 @@ Options can start with either ‘<samp>-</samp>’ or ‘<samp>--</s abbreviation is accepted. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Path-searching-options" accesskey="1">Path searching options</a>:</td><td> </td><td align="left" valign="top">Changing the mode, resolution, etc. +<tr><td align="left" valign="top">• <a href="#Path-searching-options" accesskey="1">Path searching options</a></td><td> </td><td align="left" valign="top">Changing the mode, resolution, etc. </td></tr> -<tr><td align="left" valign="top">• <a href="#Specially_002drecognized-files" accesskey="2">Specially-recognized files</a>:</td><td> </td><td align="left" valign="top">Default formats for texmf.cnf, etc. +<tr><td align="left" valign="top">• <a href="#Specially_002drecognized-files" accesskey="2">Specially-recognized files</a></td><td> </td><td align="left" valign="top">Default formats for texmf.cnf, etc. </td></tr> -<tr><td align="left" valign="top">• <a href="#Auxiliary-tasks" accesskey="3">Auxiliary tasks</a>:</td><td> </td><td align="left" valign="top">Path and variable expansion, etc. +<tr><td align="left" valign="top">• <a href="#Auxiliary-tasks" accesskey="3">Auxiliary tasks</a></td><td> </td><td align="left" valign="top">Path and variable expansion, etc. </td></tr> -<tr><td align="left" valign="top">• <a href="#Standard-options" accesskey="4">Standard options</a>:</td><td> </td><td align="left" valign="top">‘<samp>--help</samp>’ and ‘<samp>--version</samp>’. +<tr><td align="left" valign="top">• <a href="#Standard-options" accesskey="4">Standard options</a></td><td> </td><td align="left" valign="top">‘<samp>--help</samp>’ and ‘<samp>--version</samp>’. </td></tr> </table> <hr> -<a name="Path-searching-options"></a> -<div class="header"> +<span id="Path-searching-options"></span><div class="header"> <p> Next: <a href="#Specially_002drecognized-files" accesskey="n" rel="next">Specially-recognized files</a>, Up: <a href="#Invoking-kpsewhich" accesskey="u" rel="up">Invoking kpsewhich</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Path-searching-options-1"></a> -<h4 class="subsection">5.6.1 Path searching options</h4> +<span id="Path-searching-options-1"></span><h4 class="subsection">5.6.1 Path searching options</h4> -<a name="index-path-searching-options"></a> +<span id="index-path-searching-options"></span> <p>Kpsewhich looks up each non-option argument on the command line as a filename, and returns the first file found. @@ -1728,16 +1667,18 @@ filename, and returns the first file found. </p> <dl compact="compact"> <dt>‘<samp>--all</samp>’</dt> -<dd><a name="index-_002d_002dall"></a> -<a name="index-all-matches_002c-finding"></a> +<dd><span id="index-_002d_002dall"></span> +<span id="index-all-matches_002c-finding"></span> <p>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). +than one match, just one will be reported (chosen effectively at +random). Exception: with the glyph formats (<code>pk</code>, <code>gf</code>), +this option has no effect and only the first match is returned. </p> </dd> <dt>‘<samp>--casefold-search</samp>’</dt> <dt>‘<samp>--no-casefold-search</samp>’</dt> -<dd><a name="index-_002d_002dcasefold_002dsearch"></a> -<a name="index-_002d_002dno_002dcasefold_002dsearch"></a> +<dd><span id="index-_002d_002dcasefold_002dsearch"></span> +<span id="index-_002d_002dno_002dcasefold_002dsearch"></span> <p>Explicitly enable or disable the fallback to a case-insensitive search on Unix platforms (see <a href="#Casefolding-search">Casefolding search</a>); no effect on Windows. The default is enabled, set in <code>texmf.cnf</code>. Disabling @@ -1748,17 +1689,17 @@ casefolding itself. </p> </dd> <dt>‘<samp>--dpi=<var>num</var></samp>’</dt> -<dd><a name="index-_002d_002ddpi_003dnum"></a> -<a name="index-_002dD-num"></a> -<a name="index-resolution_002c-setting"></a> +<dd><span id="index-_002d_002ddpi_003dnum"></span> +<span id="index-_002dD-num"></span> +<span id="index-resolution_002c-setting"></span> <p>Set the resolution to <var>num</var>; this only affects ‘<samp>gf</samp>’ and ‘<samp>pk</samp>’ lookups. ‘<samp>-D</samp>’ is a synonym, for compatibility with Dvips. Default is 600. </p> </dd> <dt>‘<samp>--engine=<var>name</var></samp>’</dt> -<dd><a name="index-_002d_002dengine_003dname"></a> -<a name="index-engine-name"></a> +<dd><span id="index-_002d_002dengine_003dname"></span> +<span id="index-engine-name"></span> <p>Set the engine name to <var>name</var>. 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. @@ -1777,7 +1718,7 @@ namely ‘<samp>$TEXMF/web2c{/$engine,}</samp>’.) </p> </dd> <dt>‘<samp>--format=<var>name</var></samp>’</dt> -<dd><a name="index-_002d_002dformat_003dname"></a> +<dd><span id="index-_002d_002dformat_003dname"></span> <p>Set the format for lookup to <var>name</var>. By default, the format is guessed from the filename, with ‘<samp>tex</samp>’ being used if nothing else fits. The recognized filename extensions (including any leading @@ -1862,16 +1803,16 @@ bltxml: .bltxml </p> </dd> <dt>‘<samp>--interactive</samp>’</dt> -<dd><a name="index-_002d_002dinteractive"></a> -<a name="index-interactive-query"></a> +<dd><span id="index-_002d_002dinteractive"></span> +<span id="index-interactive-query"></span> <p>After processing the command line, read additional filenames to look up from standard input. </p> </dd> <dt>‘<samp>--mktex=<var>filetype</var></samp>’</dt> <dt>‘<samp>--no-mktex=<var>filetype</var></samp>’</dt> -<dd><a name="index-_002d_002dmktex_003dfiletype"></a> -<a name="index-_002d_002dno_002dmktex_003dfiletype"></a> +<dd><span id="index-_002d_002dmktex_003dfiletype"></span> +<span id="index-_002d_002dno_002dmktex_003dfiletype"></span> <p>Turn on or off the ‘<samp>mktex</samp>’ script associated with <var>filetype</var>. Usual values for <var>filetype</var> are ‘<samp>pk</samp>’, ‘<samp>mf</samp>’, ‘<samp>tex</samp>’, and ‘<samp>tfm</samp>’. By default, all are off in Kpsewhich, even if they @@ -1880,20 +1821,20 @@ are enabled for TeX. This option implies setting </p> </dd> <dt>‘<samp>--mode=<var>string</var></samp>’</dt> -<dd><a name="index-_002d_002dmode_003dstring"></a> +<dd><span id="index-_002d_002dmode_003dstring"></span> <p>Set the mode name to <var>string</var>; this also only affects ‘<samp>gf</samp>’ and ‘<samp>pk</samp>’ lookups. No default: any mode will be found. See <a href="#mktex-script-arguments">mktex script arguments</a>. </p> </dd> <dt>‘<samp>--must-exist</samp>’</dt> -<dd><a name="index-_002d_002dmust_002dexist"></a> +<dd><span id="index-_002d_002dmust_002dexist"></span> <p>Do everything possible to find the files, notably including searching the disk and running the ‘<samp>mktex</samp>’ scripts. By default, only the <samp>ls-R</samp> database is checked, in the interest of efficiency. </p> </dd> <dt>‘<samp>--path=<var>string</var></samp>’</dt> -<dd><a name="index-_002d_002dpath_003dstring"></a> +<dd><span id="index-_002d_002dpath_003dstring"></span> <p>Search along the path <var>string</var> (colon-separated as usual), instead of guessing the search path from the filename. ‘<samp>//</samp>’ and all the usual expansions are supported (see <a href="#Path-expansion">Path expansion</a>). This option @@ -1903,14 +1844,14 @@ directory expansion of a path, instead of doing a one-shot lookup, see </p> </dd> <dt>‘<samp>--progname=<var>name</var></samp>’</dt> -<dd><a name="index-_002d_002dprogname_003dname"></a> +<dd><span id="index-_002d_002dprogname_003dname"></span> <p>Set the program name to <var>name</var>; default is ‘<samp>kpsewhich</samp>’. This can affect the search paths via the ‘<samp>.<var>prognam</var></samp>’ feature in configuration files (see <a href="#Config-files">Config files</a>). </p> </dd> <dt>‘<samp>--subdir=<var>string</var></samp>’</dt> -<dd><a name="index-_002d_002dsubdir_003dstring"></a> +<dd><span id="index-_002d_002dsubdir_003dstring"></span> <p>Report only those matches whose directory part <em>ends</em> with <var>string</var> (compared literally, except case is ignored on a case-insensitive operating system). For example, suppose there are @@ -1990,13 +1931,11 @@ in <samp>/some/coincidental/pkg1/path/</samp>, and we wouldn’t want to mat <hr> -<a name="Specially_002drecognized-files"></a> -<div class="header"> +<span id="Specially_002drecognized-files"></span><div class="header"> <p> Next: <a href="#Auxiliary-tasks" accesskey="n" rel="next">Auxiliary tasks</a>, Previous: <a href="#Path-searching-options" accesskey="p" rel="prev">Path searching options</a>, Up: <a href="#Invoking-kpsewhich" accesskey="u" rel="up">Invoking kpsewhich</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Specially_002drecognized-files-for-kpsewhich"></a> -<h4 class="subsection">5.6.2 Specially-recognized files for <code>kpsewhich</code></h4> +<span id="Specially_002drecognized-files-for-kpsewhich"></span><h4 class="subsection">5.6.2 Specially-recognized files for <code>kpsewhich</code></h4> <p><code>kpsewhich</code> recognizes a few special filenames on the command line and defaults to using the ‘known’ file formats for them, merely @@ -2010,49 +1949,49 @@ with their corresponding format: </p> <dl compact="compact"> <dd> -<a name="index-config_002eps"></a> +<span id="index-config_002eps"></span> </dd> <dt><samp>config.ps</samp></dt> <dd><p><code>dvips config</code> </p> -<a name="index-dvipdfmx_002ecfg"></a> +<span id="index-dvipdfmx_002ecfg"></span> </dd> <dt><samp>dvipdfmx.cfg</samp></dt> <dd><p>‘<samp>other text files</samp>’ </p> -<a name="index-fmtutil_002ecnf"></a> +<span id="index-fmtutil_002ecnf"></span> </dd> <dt><samp>fmtutil.cnf</samp></dt> <dd><p>‘<samp>web2c files</samp>’ </p> -<a name="index-glyphlist_002etxt"></a> +<span id="index-glyphlist_002etxt"></span> </dd> <dt><samp>glyphlist.txt</samp></dt> <dd><p>‘<samp>map</samp>’ </p> -<a name="index-mktex_002ecnf"></a> +<span id="index-mktex_002ecnf"></span> </dd> <dt><samp>mktex.cnf</samp></dt> <dd><p>‘<samp>web2c files</samp>’ </p> -<a name="index-pdfglyphlist_002etxt"></a> +<span id="index-pdfglyphlist_002etxt"></span> </dd> <dt><samp>pdfglyphlist.txt</samp></dt> <dd><p>‘<samp>map</samp>’ </p> -<a name="index-pdftex_002ecfg"></a> -<a name="index-pdftexconfig_002etex"></a> +<span id="index-pdftex_002ecfg"></span> +<span id="index-pdftexconfig_002etex"></span> </dd> <dt><samp>pdftex.cfg</samp></dt> <dd><p>‘<samp>pdftex config</samp>’ (although <samp>pdftex.cfg</samp> is not used any more; look for the file <samp>pdftexconfig.tex</samp> instead.) </p> -<a name="index-texmf_002ecnf"></a> +<span id="index-texmf_002ecnf"></span> </dd> <dt><samp>texmf.cnf</samp></dt> <dd><p>‘<samp>cnf</samp>’ </p> -<a name="index-XDvi"></a> +<span id="index-XDvi"></span> </dd> <dt><samp>XDvi</samp></dt> <dd><p>‘<samp>other text files</samp>’ @@ -2062,38 +2001,37 @@ look for the file <samp>pdftexconfig.tex</samp> instead.) <p>A user-specified format will override the above defaults. </p> -<a name="index-tcfmgr_002emap"></a> +<span id="index-tcfmgr_002emap"></span> <p>Another useful configuration file in this regard is <samp>tcfmgr.map</samp>, found in <samp>texmf/texconfig/tcfmgr.map</samp>, which records various information about the above configuration files (among others). </p> <hr> -<a name="Auxiliary-tasks"></a> -<div class="header"> +<span id="Auxiliary-tasks"></span><div class="header"> <p> Next: <a href="#Standard-options" accesskey="n" rel="next">Standard options</a>, Previous: <a href="#Specially_002drecognized-files" accesskey="p" rel="prev">Specially-recognized files</a>, Up: <a href="#Invoking-kpsewhich" accesskey="u" rel="up">Invoking kpsewhich</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Auxiliary-tasks-1"></a> -<h4 class="subsection">5.6.3 Auxiliary tasks</h4> +<span id="Auxiliary-tasks-1"></span><h4 class="subsection">5.6.3 Auxiliary tasks</h4> -<a name="index-auxiliary-tasks"></a> +<span id="index-auxiliary-tasks"></span> <p>Kpsewhich provides some features in addition to path lookup as such: </p> <dl compact="compact"> <dt>‘<samp>--debug=<var>num</var></samp>’</dt> -<dd><a name="index-_002d_002ddebug_003dnum"></a> +<dd><span id="index-_002d_002ddebug_003dnum"></span> <p>Set debugging options to <var>num</var>. See <a href="#Debugging">Debugging</a>. </p> </dd> <dt>‘<samp>--expand-braces=<var>string</var></samp>’</dt> -<dd><a name="index-_002d_002dexpand_002dbraces_003dstring"></a> -<p>Output variable and brace expansion of <var>string</var>. See <a href="#Path-expansion">Path expansion</a>. +<dd><span id="index-_002d_002dexpand_002dbraces_003dstring"></span> +<p>Output variable, tilde, and brace expansion of <var>string</var>, which is +assumed to be a single path element. See <a href="#Path-expansion">Path expansion</a>. </p> </dd> <dt>‘<samp>--expand-path=<var>string</var></samp>’</dt> -<dd><a name="index-_002d_002dexpand_002dpath_003dstring"></a> +<dd><span id="index-_002d_002dexpand_002dpath_003dstring"></span> <p>Output the complete expansion of <var>string</var>, with each element separated by the usual path separator on the current system (‘<samp>;</samp>’ on Windows, ‘<samp>:</samp>’ otherwise). This may be useful to construct a @@ -2111,27 +2049,29 @@ $ kpsewhich --expand-path '/nonesuch' </pre></div> <p>For one-shot uses of an arbitrary (not built in to Kpathsea) path, see -‘<samp>--path</samp>’ (see <a href="#Path-searching-options">Path searching options</a>) +‘<samp>--path</samp>’ (see <a href="#Path-searching-options">Path searching options</a>). </p> </dd> <dt>‘<samp>--expand-var=<var>string</var></samp>’</dt> -<dd><a name="index-_002d_002dexpand_002dvar_003dstring"></a> -<p>Output the variable and tilde expansion of <var>string</var> -the ‘<samp>mktex…</samp>’ scripts run ‘<samp>kpsewhich ---expand-var='$TEXMF'</samp>’ to find the root of the TeX system -hierarchy. See <a href="#Path-expansion">Path expansion</a>. +<dd><span id="index-_002d_002dexpand_002dvar_003dstring"></span> +<p>Output the variable and tilde expansion of <var>string</var>. For example, +with the usual <samp>texmf.cnf</samp>, ‘<samp>kpsewhich +--expand-var='$TEXMF'</samp>’ returns the TeX system hierarchy root(s). +See <a href="#Path-expansion">Path expansion</a>. The specified <var>string</var> can contain +anything, though, not just variable references. This calls +<code>kpse_var_expand</code> (see <a href="#Programming-with-config-files">Programming with config files</a>). </p> </dd> <dt>‘<samp>--help-formats</samp>’</dt> -<dd><a name="index-_002d_002dhelp_002dformats"></a> +<dd><span id="index-_002d_002dhelp_002dformats"></span> <p>Output information about each supported format (see <a href="#Supported-file-formats">Supported file formats</a>), including the names and abbreviations, variables looked for, and the original path. </p> </dd> <dt>‘<samp>--safe-in-name=<var>name</var></samp>’</dt> <dt>‘<samp>--safe-out-name=<var>name</var></samp>’</dt> -<dd><a name="index-_002d_002dsafe_002din_002dname_003dname"></a> -<a name="index-_002d_002dsafe_002dout_002dname_003dname"></a> +<dd><span id="index-_002d_002dsafe_002din_002dname_003dname"></span> +<span id="index-_002d_002dsafe_002dout_002dname_003dname"></span> <p>Exit successfully if <var>name</var> is safe to open for reading or writing, respectively, else unsuccessfully. No output is written. These tests take account of the related Kpathsea configuration @@ -2139,56 +2079,77 @@ settings (see <a href="#Calling-sequence">Calling sequence</a>). </p> </dd> <dt>‘<samp>--show-path=<var>name</var></samp>’</dt> -<dd><a name="index-_002d_002dshow_002dpath_003dname"></a> +<dd><span id="index-_002d_002dshow_002dpath_003dname"></span> <p>Show the path that would be used for file lookups of file type <var>name</var>. Either a filename extension (‘<samp>pk</samp>’, ‘<samp>.vf</samp>’, etc.) or an integer can be used, just as with ‘<samp>--format</samp>’, described in the previous section. </p> </dd> +<dt>‘<samp>--var-brace-value=<var>variable</var></samp>’</dt> +<dd><span id="index-_002d_002dvar_002dbrace_002dvalue_003dvariable"></span> +<p>Like ‘<samp>--var-value</samp>’ (next), but also expands ‘<samp>{...}</samp>’ +constructs. (see <a href="#Brace-expansion">Brace expansion</a>). Thus, the value is assumed to +possibly be several path elements, and ‘<samp>~</samp>’ is expanded at the +beginning of each. The path separator is changed to that of the +current system in the expansion. +</p> +<p>Example: ‘<samp>FOO='.;~' kpsewhich --var-brace-value=FOO</samp>’ outputs (on +a Unix-ish system) ‘<samp>.:/home/karl</samp>’, supposing the latter is the +current user’s home directory. Note that the ‘<samp>;</samp>’ in the source +value, as commonly used in <samp>texmf.cnf</samp>, has changed to a +‘<samp>:</samp>’, as the normal path separator on the current system. (On a +Windows-ish system, the ‘<samp>;</samp>’ would remain.) +</p> +</dd> <dt>‘<samp>--var-value=<var>variable</var></samp>’</dt> -<dd><a name="index-_002d_002dvar_002dvalue_003dvariable"></a> +<dd><span id="index-_002d_002dvar_002dvalue_003dvariable"></span> <p>Outputs the value of <var>variable</var> (a simple identifier like -‘<samp>TEXMF</samp>’, with no ‘<samp>$</samp>’ or other constructs), expanding -‘<samp>$</samp>’ (see <a href="#Variable-expansion">Variable expansion</a> and ‘<samp>~</samp>’ (see <a href="#Tilde-expansion">Tilde expansion</a>) constructs, but not performing other expansions. +‘<samp>TEXMFDIST</samp>’, with no ‘<samp>$</samp>’ or other constructs), expanding +‘<samp>$</samp>’ (see <a href="#Variable-expansion">Variable expansion</a>) and ‘<samp>~</samp>’ (see <a href="#Tilde-expansion">Tilde expansion</a>) constructs in the value. ‘<samp>~</samp>’ 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. +</p> +<p>Example: ‘<samp>--var-value=texmf_casefold_search</samp>’ outputs (if the +default is not changed) ‘<samp>1</samp>’. +</p> +<p>Example to contrast with ‘<samp>--var-brace-value</samp>’: ‘<samp>FOO='.;~' +kpsewhich --var-value=FOO</samp>’ outputs ‘<samp>.;~</samp>’, i.e., the same as the +input value. </p> </dd> </dl> <hr> -<a name="Standard-options"></a> -<div class="header"> +<span id="Standard-options"></span><div class="header"> <p> Previous: <a href="#Auxiliary-tasks" accesskey="p" rel="prev">Auxiliary tasks</a>, Up: <a href="#Invoking-kpsewhich" accesskey="u" rel="up">Invoking kpsewhich</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Standard-options-1"></a> -<h4 class="subsection">5.6.4 Standard options</h4> +<span id="Standard-options-1"></span><h4 class="subsection">5.6.4 Standard options</h4> -<a name="index-standard-options"></a> +<span id="index-standard-options"></span> <p>Kpsewhich accepts the standard GNU options: </p> <ul> -<li> <a name="index-_002d_002dhelp"></a> +<li> <span id="index-_002d_002dhelp"></span> ‘<samp>--help</samp>’ prints a help message on standard output and exits successfully. -</li><li> <a name="index-_002d_002dversion"></a> +</li><li> <span id="index-_002d_002dversion"></span> ‘<samp>--version</samp>’ prints the Kpathsea version number and exits successfully. </li></ul> <hr> -<a name="TeX-support"></a> -<div class="header"> +<span id="TeX-support"></span><div class="header"> <p> Next: <a href="#Programming" accesskey="n" rel="next">Programming</a>, Previous: <a href="#Path-searching" accesskey="p" rel="prev">Path searching</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="TeX-support-1"></a> -<h2 class="chapter">6 TeX support</h2> +<span id="TeX-support-1"></span><h2 class="chapter">6 TeX support</h2> -<a name="index-TeX-support"></a> +<span id="index-TeX-support"></span> <p>Although the basic features in Kpathsea can be used for any type of path searching, it came about, as usual, with a specific application @@ -2209,33 +2170,31 @@ contents—if a GF file is (mis)named <samp>cmr10.600pk</samp>, it will be found as a PK file. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Supported-file-formats" accesskey="1">Supported file formats</a>:</td><td> </td><td align="left" valign="top">File types Kpathsea knows about. +<tr><td align="left" valign="top">• <a href="#Supported-file-formats" accesskey="1">Supported file formats</a></td><td> </td><td align="left" valign="top">File types Kpathsea knows about. </td></tr> -<tr><td align="left" valign="top">• <a href="#File-lookup" accesskey="2">File lookup</a>:</td><td> </td><td align="left" valign="top">Searching for most kinds of files. +<tr><td align="left" valign="top">• <a href="#File-lookup" accesskey="2">File lookup</a></td><td> </td><td align="left" valign="top">Searching for most kinds of files. </td></tr> -<tr><td align="left" valign="top">• <a href="#Glyph-lookup" accesskey="3">Glyph lookup</a>:</td><td> </td><td align="left" valign="top">Searching for bitmap fonts. +<tr><td align="left" valign="top">• <a href="#Glyph-lookup" accesskey="3">Glyph lookup</a></td><td> </td><td align="left" valign="top">Searching for bitmap fonts. </td></tr> -<tr><td align="left" valign="top">• <a href="#Suppressing-warnings" accesskey="4">Suppressing warnings</a>:</td><td> </td><td align="left" valign="top">Avoiding warnings via TEX_HUSH. +<tr><td align="left" valign="top">• <a href="#Suppressing-warnings" accesskey="4">Suppressing warnings</a></td><td> </td><td align="left" valign="top">Avoiding warnings via TEX_HUSH. </td></tr> -<tr><td align="left" valign="top">• <a href="#mktex-scripts" accesskey="5">mktex scripts</a>:</td><td> </td><td align="left" valign="top">Generating files at runtime. +<tr><td align="left" valign="top">• <a href="#mktex-scripts" accesskey="5">mktex scripts</a></td><td> </td><td align="left" valign="top">Generating files at runtime. </td></tr> </table> <hr> -<a name="Supported-file-formats"></a> -<div class="header"> +<span id="Supported-file-formats"></span><div class="header"> <p> Next: <a href="#File-lookup" accesskey="n" rel="next">File lookup</a>, Up: <a href="#TeX-support" accesskey="u" rel="up">TeX support</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Supported-file-formats-1"></a> -<h3 class="section">6.1 Supported file formats</h3> +<span id="Supported-file-formats-1"></span><h3 class="section">6.1 Supported file formats</h3> -<a name="index-supported-file-formats"></a> -<a name="index-file-formats_002c-supported"></a> +<span id="index-supported-file-formats"></span> +<span id="index-file-formats_002c-supported"></span> -<a name="index-environment-variables-for-TeX"></a> -<a name="index-TeX-environment-variables"></a> +<span id="index-environment-variables-for-TeX"></span> +<span id="index-TeX-environment-variables"></span> <p>Kpathsea has support for a number of file types. Each file type has a list of environment and config file variables that are checked to define @@ -2243,7 +2202,7 @@ the search path, and most have a default suffix that plays a role in 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. </p> -<a name="index-program_002dvarying-paths"></a> +<span id="index-program_002dvarying-paths"></span> <p>Since environment variables containing periods, such as ‘<samp>TEXINPUTS.latex</samp>’, are not allowed on some systems, Kpathsea looks for environment variables with an underscore, e.g., @@ -2255,77 +2214,77 @@ list by giving the ‘<samp>--help-formats</samp>’ option to <code>kps </p> <dl compact="compact"> <dt>‘<samp>afm</samp>’</dt> -<dd><a name="index-_002eafm"></a> -<a name="index-AFMFONTS"></a> -<p>(Adobe font metrics, see <a href="http://tug.org/texinfohtml/dvips.html#Metric-files">Metric files</a> in <cite>Dvips</cite>) +<dd><span id="index-_002eafm"></span> +<span id="index-AFMFONTS"></span> +<p>(Adobe font metrics, see <a href="https://tug.org/texinfohtml/dvips.html#Metric-files">Metric files</a> in <cite>Dvips</cite>) <code>AFMFONTS</code>; suffix ‘<samp>.afm</samp>’. </p> </dd> <dt>‘<samp>base</samp>’</dt> -<dd><a name="index-_002ebase"></a> -<a name="index-MFBASES"></a> -<a name="index-TEXMFINI"></a> -<p>(Metafont memory dump, see <a href="http://tug.org/texinfohtml/web2c.html#Memory-dumps">Memory dumps</a> in <cite>Web2c</cite>) +<dd><span id="index-_002ebase"></span> +<span id="index-MFBASES"></span> +<span id="index-TEXMFINI"></span> +<p>(Metafont memory dump, see <a href="https://tug.org/texinfohtml/web2c.html#Memory-dumps">Memory dumps</a> in <cite>Web2c</cite>) <code>MFBASES</code>, <code>TEXMFINI</code>; suffix ‘<samp>.base</samp>’. </p> </dd> <dt>‘<samp>bib</samp>’</dt> -<dd><a name="index-_002ebib"></a> -<a name="index-BIBINPUTS"></a> -<a name="index-TEXBIB"></a> -<p>(BibTeX bibliography source, see <a href="http://tug.org/texinfohtml/web2c.html#bibtex-invocation">bibtex invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002ebib"></span> +<span id="index-BIBINPUTS"></span> +<span id="index-TEXBIB"></span> +<p>(BibTeX bibliography source, see <a href="https://tug.org/texinfohtml/web2c.html#bibtex-invocation">bibtex invocation</a> in <cite>Web2c</cite>) <code>BIBINPUTS</code>, <code>TEXBIB</code>; suffix ‘<samp>.bib</samp>’. </p> </dd> <dt>‘<samp>bltxml</samp>’</dt> -<dd><a name="index-_002ebltxml"></a> -<a name="index-BLTXMLINPUTS"></a> +<dd><span id="index-_002ebltxml"></span> +<span id="index-BLTXMLINPUTS"></span> <p>(BibLaTeXML bibliography files for Biber, <a href="http://ctan.org/pkg/biber">http://ctan.org/pkg/biber</a>) <code>BLTXMLINPUTS</code> suffix ‘<samp>.bltxml</samp>’. </p> </dd> <dt>‘<samp>bst</samp>’</dt> -<dd><a name="index-_002ebst"></a> -<a name="index-BSTINPUTS"></a> -<p>(BibTeX style, see <a href="http://tug.org/texinfohtml/web2c.html#Basic-BibTeX-style-files">Basic BibTeX +<dd><span id="index-_002ebst"></span> +<span id="index-BSTINPUTS"></span> +<p>(BibTeX style, see <a href="https://tug.org/texinfohtml/web2c.html#Basic-BibTeX-style-files">Basic BibTeX style files</a> in <cite>Web2c</cite>) <code>BSTINPUTS</code>; suffix ‘<samp>.bst</samp>’. </p> </dd> <dt>‘<samp>clua</samp>’</dt> -<dd><a name="index-_002edll"></a> -<a name="index-_002eso"></a> -<a name="index-CLUAINPUTS"></a> +<dd><span id="index-_002edll"></span> +<span id="index-_002eso"></span> +<span id="index-CLUAINPUTS"></span> <p>(dynamic libraries for Lua, <a href="http://ctan.org/pkg/luatex">http://ctan.org/pkg/luatex</a>) <code>CLUAINPUTS</code> suffixes ‘<samp>.dll</samp>’ and ‘<samp>.so</samp>’. </p> </dd> <dt>‘<samp>cmap</samp>’</dt> -<dd><a name="index-_002ecmap"></a> -<a name="index-CMAPFONTS"></a> +<dd><span id="index-_002ecmap"></span> +<span id="index-CMAPFONTS"></span> <p>(character map files) <code>CMAPFONTS</code>; suffix ‘<samp>.cmap</samp>’. </p> </dd> <dt>‘<samp>cnf</samp>’</dt> -<dd><a name="index-_002ecnf"></a> -<a name="index-TEXMFCNF-1"></a> +<dd><span id="index-_002ecnf"></span> +<span id="index-TEXMFCNF-1"></span> <p>(Runtime configuration files, see <a href="#Config-files">Config files</a>) <code>TEXMFCNF</code>; suffix ‘<samp>.cnf</samp>’. </p> </dd> <dt>‘<samp>cweb</samp>’</dt> -<dd><a name="index-_002ew"></a> -<a name="index-_002eweb"></a> -<a name="index-CWEBINPUTS"></a> +<dd><span id="index-_002ew"></span> +<span id="index-_002eweb"></span> +<span id="index-CWEBINPUTS"></span> <p>(CWEB input files) <code>CWEBINPUTS</code>; suffixes ‘<samp>.w</samp>’, ‘<samp>.web</samp>’; @@ -2333,182 +2292,182 @@ additional suffix ‘<samp>.ch</samp>’. </p> </dd> <dt>‘<samp>dvips config</samp>’</dt> -<dd><a name="index-TEXCONFIG"></a> -<a name="index-config_002eps_002c-search-path-for"></a> -<p>(Dvips ‘<samp>config.*</samp>’ files, such as <samp>config.ps</samp>, see <a href="http://tug.org/texinfohtml/dvips.html#Config-files">Config +<dd><span id="index-TEXCONFIG"></span> +<span id="index-config_002eps_002c-search-path-for"></span> +<p>(Dvips ‘<samp>config.*</samp>’ files, such as <samp>config.ps</samp>, see <a href="https://tug.org/texinfohtml/dvips.html#Config-files">Config files</a> in <cite>Dvips</cite>) <code>TEXCONFIG</code>. </p> </dd> <dt>‘<samp>enc files</samp>’</dt> -<dd><a name="index-_002eenc"></a> -<a name="index-ENCFONTS"></a> +<dd><span id="index-_002eenc"></span> +<span id="index-ENCFONTS"></span> <p>(encoding vectors) <code>ENCFONTS</code>; suffix ‘<samp>.enc</samp>’. </p> </dd> <dt>‘<samp>fmt</samp>’</dt> -<dd><a name="index-_002efmt"></a> -<a name="index-TEXFORMATS"></a> -<a name="index-TEXMFINI-1"></a> -<p>(TeX memory dump, see <a href="http://tug.org/texinfohtml/web2c.html#Memory-dumps">Memory dumps</a> in <cite>Web2c</cite>) +<dd><span id="index-_002efmt"></span> +<span id="index-TEXFORMATS"></span> +<span id="index-TEXMFINI-1"></span> +<p>(TeX memory dump, see <a href="https://tug.org/texinfohtml/web2c.html#Memory-dumps">Memory dumps</a> in <cite>Web2c</cite>) <code>TEXFORMATS</code>, <code>TEXMFINI</code>; suffix ‘<samp>.fmt</samp>’. </p> </dd> <dt>‘<samp>font cid map</samp>’</dt> -<dd><a name="index-_002ecid"></a> -<a name="index-FONTCIDMAPS"></a> +<dd><span id="index-_002ecid"></span> +<span id="index-FONTCIDMAPS"></span> <p>(CJK mapping) <code>FONTCIDMAPS</code> suffix ‘<samp>.cid</samp>’. </p> </dd> <dt>‘<samp>font feature files</samp>’</dt> -<dd><a name="index-_002efea"></a> -<a name="index-FONTFEATURES"></a> +<dd><span id="index-_002efea"></span> +<span id="index-FONTFEATURES"></span> <p>(primarily for OpenType font features) <code>FONTFEATURES</code> suffix ‘<samp>.fea</samp>’. </p> </dd> <dt>‘<samp>gf</samp>’</dt> -<dd><a name="index-gf"></a> -<a name="index-GFFONTS"></a> -<a name="index-GLYPHFONTS"></a> -<a name="index-TEXFONTS"></a> -<p>(generic font bitmap, see <a href="http://tug.org/texinfohtml/dvips.html#Glyph-files">Glyph files</a> in <cite>Dvips</cite>) +<dd><span id="index-gf"></span> +<span id="index-GFFONTS"></span> +<span id="index-GLYPHFONTS"></span> +<span id="index-TEXFONTS"></span> +<p>(generic font bitmap, see <a href="https://tug.org/texinfohtml/dvips.html#Glyph-files">Glyph files</a> in <cite>Dvips</cite>) <code><var>program</var>FONTS</code>, <code>GFFONTS</code>, <code>GLYPHFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>gf</samp>’. </p> </dd> <dt>‘<samp>graphic/figure</samp>’</dt> -<dd><a name="index-_002eeps"></a> -<a name="index-_002eepsi"></a> -<a name="index-TEXPICTS"></a> -<a name="index-TEXINPUTS"></a> -<p>(Encapsulated PostScript figures, see <a href="http://tug.org/texinfohtml/dvips.html#PostScript-figures">PostScript figures</a> in <cite>Dvips</cite>) +<dd><span id="index-_002eeps"></span> +<span id="index-_002eepsi"></span> +<span id="index-TEXPICTS"></span> +<span id="index-TEXINPUTS"></span> +<p>(Encapsulated PostScript figures, see <a href="https://tug.org/texinfohtml/dvips.html#PostScript-figures">PostScript figures</a> in <cite>Dvips</cite>) <code>TEXPICTS</code>, <code>TEXINPUTS</code>; additional suffixes: ‘<samp>.eps</samp>’, ‘<samp>.epsi</samp>’. </p> </dd> <dt>‘<samp>ist</samp>’</dt> -<dd><a name="index-_002eist"></a> -<a name="index-TEXINDEXSTYLE"></a> -<a name="index-INDEXSTYLE"></a> +<dd><span id="index-_002eist"></span> +<span id="index-TEXINDEXSTYLE"></span> +<span id="index-INDEXSTYLE"></span> <p>(makeindex style files) <code>TEXINDEXSTYLE</code>, <code>INDEXSTYLE</code>; suffix ‘<samp>.ist</samp>’. </p> </dd> <dt>‘<samp>lig files</samp>’</dt> -<dd><a name="index-_002elig"></a> -<a name="index-LIGFONTS"></a> +<dd><span id="index-_002elig"></span> +<span id="index-LIGFONTS"></span> <p>(ligature definition files) <code>LIGFONTS</code>; suffix ‘<samp>.lig</samp>’. </p> </dd> <dt>‘<samp>ls-R</samp>’</dt> -<dd><a name="index-ls_002dR"></a> -<a name="index-TEXMFDBS-1"></a> +<dd><span id="index-ls_002dR"></span> +<span id="index-TEXMFDBS-1"></span> <p>(Filename databases, see <a href="#Filename-database">Filename database</a>) <code>TEXMFDBS</code>. </p> </dd> <dt>‘<samp>map</samp>’</dt> -<dd><a name="index-_002emap"></a> -<a name="index-TEXFONTMAPS"></a> +<dd><span id="index-_002emap"></span> +<span id="index-TEXFONTMAPS"></span> <p>(Fontmaps, see <a href="#Fontmap">Fontmap</a>) <code>TEXFONTMAPS</code>; suffix ‘<samp>.map</samp>’. </p> </dd> <dt>‘<samp>mem</samp>’</dt> -<dd><a name="index-_002emem"></a> -<a name="index-MPMEMS"></a> -<a name="index-TEXMFINI-2"></a> -<p>(MetaPost memory dump, see <a href="http://tug.org/texinfohtml/web2c.html#Memory-dumps">Memory dumps</a> in <cite>Web2c</cite>) +<dd><span id="index-_002emem"></span> +<span id="index-MPMEMS"></span> +<span id="index-TEXMFINI-2"></span> +<p>(MetaPost memory dump, see <a href="https://tug.org/texinfohtml/web2c.html#Memory-dumps">Memory dumps</a> in <cite>Web2c</cite>) <code>MPMEMS</code>, <code>TEXMFINI</code>; suffix ‘<samp>.mem</samp>’. </p> </dd> <dt>‘<samp><span class="roman">MetaPost support</span></samp>’</dt> -<dd><a name="index-MPSUPPORT"></a> -<p>(MetaPost support files, used by DMP; see <a href="http://tug.org/texinfohtml/web2c.html#dmp-invocation">dmp invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-MPSUPPORT"></span> +<p>(MetaPost support files, used by DMP; see <a href="https://tug.org/texinfohtml/web2c.html#dmp-invocation">dmp invocation</a> in <cite>Web2c</cite>) <code>MPSUPPORT</code>. </p> </dd> <dt>‘<samp>mf</samp>’</dt> -<dd><a name="index-_002emf"></a> -<a name="index-MFINPUTS"></a> -<p>(Metafont source, see <a href="http://tug.org/texinfohtml/web2c.html#mf-invocation">mf invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002emf"></span> +<span id="index-MFINPUTS"></span> +<p>(Metafont source, see <a href="https://tug.org/texinfohtml/web2c.html#mf-invocation">mf invocation</a> in <cite>Web2c</cite>) <code>MFINPUTS</code>; suffix ‘<samp>.mf</samp>’; dynamic creation program: <code>mktexmf</code>. </p> </dd> <dt>‘<samp>mfpool</samp>’</dt> -<dd><a name="index-_002epool"></a> -<a name="index-MFPOOL"></a> -<p>(Metafont program strings, see <a href="http://tug.org/texinfohtml/web2c.html#pooltype-invocation">pooltype invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002epool"></span> +<span id="index-MFPOOL"></span> +<p>(Metafont program strings, see <a href="https://tug.org/texinfohtml/web2c.html#pooltype-invocation">pooltype invocation</a> in <cite>Web2c</cite>) <code>MFPOOL</code>, <code>TEXMFINI</code>; suffix ‘<samp>.pool</samp>’. </p> </dd> <dt>‘<samp>mft</samp>’</dt> -<dd><a name="index-_002emft"></a> -<a name="index-MFTINPUTS"></a> -<p>(<code>MFT</code> style file, see <a href="http://tug.org/texinfohtml/web2c.html#mft-invocation">mft invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002emft"></span> +<span id="index-MFTINPUTS"></span> +<p>(<code>MFT</code> style file, see <a href="https://tug.org/texinfohtml/web2c.html#mft-invocation">mft invocation</a> in <cite>Web2c</cite>) <code>MFTINPUTS</code>; suffix ‘<samp>.mft</samp>’. </p> </dd> <dt>‘<samp>misc fonts</samp>’</dt> -<dd><a name="index-MISCFONTS"></a> +<dd><span id="index-MISCFONTS"></span> <p>(font-related files that don’t fit the other categories) <code>MISCFONTS</code> </p> </dd> <dt>‘<samp>mlbib</samp>’</dt> -<dd><a name="index-_002emlbib"></a> -<a name="index-MLBIBINPUTS"></a> -<a name="index-BIBINPUTS-1"></a> -<a name="index-TEXBIB-1"></a> +<dd><span id="index-_002emlbib"></span> +<span id="index-MLBIBINPUTS"></span> +<span id="index-BIBINPUTS-1"></span> +<span id="index-TEXBIB-1"></span> <p>(MlBibTeX bibliography source) <code>MLBIBINPUTS</code>, <code>BIBINPUTS</code>, <code>TEXBIB</code>; suffixes ‘<samp>.mlbib</samp>’, ‘<samp>.mlbib</samp>’. </p> </dd> <dt>‘<samp>mlbst</samp>’</dt> -<dd><a name="index-_002emlbst"></a> -<a name="index-MLBSTINPUTS"></a> -<a name="index-BSTINPUTS-1"></a> +<dd><span id="index-_002emlbst"></span> +<span id="index-MLBSTINPUTS"></span> +<span id="index-BSTINPUTS-1"></span> <p>(MlBibTeX style) <code>MLBSTINPUTS</code>, <code>BSTINPUTS</code>; suffixes ‘<samp>.mlbst</samp>’, ‘<samp>.bst</samp>’. </p> </dd> <dt>‘<samp>mp</samp>’</dt> -<dd><a name="index-_002emp"></a> -<a name="index-MPINPUTS"></a> -<p>(MetaPost source, see <a href="http://tug.org/texinfohtml/web2c.html#mpost-invocation">mpost invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002emp"></span> +<span id="index-MPINPUTS"></span> +<p>(MetaPost source, see <a href="https://tug.org/texinfohtml/web2c.html#mpost-invocation">mpost invocation</a> in <cite>Web2c</cite>) <code>MPINPUTS</code>; suffix ‘<samp>.mp</samp>’. </p> </dd> <dt>‘<samp>mppool</samp>’</dt> -<dd><a name="index-_002epool-1"></a> -<a name="index-MPPOOL"></a> -<p>(MetaPost program strings, see <a href="http://tug.org/texinfohtml/web2c.html#pooltype-invocation">pooltype invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002epool-1"></span> +<span id="index-MPPOOL"></span> +<p>(MetaPost program strings, see <a href="https://tug.org/texinfohtml/web2c.html#pooltype-invocation">pooltype invocation</a> in <cite>Web2c</cite>) <code>MPPOOL</code>, <code>TEXMFINI</code>; suffix ‘<samp>.pool</samp>’. </p> </dd> <dt>‘<samp>ocp</samp>’</dt> -<dd><a name="index-_002eocp"></a> -<a name="index-OCPINPUTS"></a> +<dd><span id="index-_002eocp"></span> +<span id="index-OCPINPUTS"></span> <p>(Omega compiled process files) <code>OCPINPUTS</code>; <br> suffix ‘<samp>.ocp</samp>’; @@ -2516,8 +2475,8 @@ dynamic creation program: <code>MakeOmegaOCP</code>. </p> </dd> <dt>‘<samp>ofm</samp>’</dt> -<dd><a name="index-_002eofm"></a> -<a name="index-OFMFONTS"></a> +<dd><span id="index-_002eofm"></span> +<span id="index-OFMFONTS"></span> <p>(Omega font metrics) <code>OFMFONTS</code>, <code>TEXFONTS</code>; <br> suffixes ‘<samp>.ofm</samp>’, ‘<samp>.tfm</samp>’; @@ -2525,55 +2484,55 @@ dynamic creation program: <code>MakeOmegaOFM</code>. </p> </dd> <dt>‘<samp>opentype fonts</samp>’</dt> -<dd><a name="index-OPENTYPEFONTS"></a> +<dd><span id="index-OPENTYPEFONTS"></span> <p>(OpenType fonts) <code>OPENTYPEFONTS</code>. </p> </dd> <dt>‘<samp>opl</samp>’</dt> -<dd><a name="index-_002eopl"></a> +<dd><span id="index-_002eopl"></span> <p>(Omega property lists) <code>OPLFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>.opl</samp>’. </p> </dd> <dt>‘<samp>otp</samp>’</dt> -<dd><a name="index-_002eotp"></a> -<a name="index-OTPINPUTS"></a> +<dd><span id="index-_002eotp"></span> +<span id="index-OTPINPUTS"></span> <p>(Omega translation process files) <code>OTPINPUTS</code>; suffix ‘<samp>.otp</samp>’. </p> </dd> <dt>‘<samp>ovf</samp>’</dt> -<dd><a name="index-_002eovf"></a> -<a name="index-OVFFONTS"></a> +<dd><span id="index-_002eovf"></span> +<span id="index-OVFFONTS"></span> <p>(Omega virtual fonts) <code>OVFFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>.ovf</samp>’. </p> </dd> <dt>‘<samp>ovp</samp>’</dt> -<dd><a name="index-_002eovp"></a> -<a name="index-OVPFONTS"></a> +<dd><span id="index-_002eovp"></span> +<span id="index-OVPFONTS"></span> <p>(Omega virtual property lists) <code>OVPFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>.ovp</samp>’. </p> </dd> <dt>‘<samp>pdftex config</samp>’</dt> -<dd><a name="index-PDFTEXCONFIG"></a> +<dd><span id="index-PDFTEXCONFIG"></span> <p>(PDFTeX-specific configuration files) <code>PDFTEXCONFIG</code>. </p> </dd> <dt>‘<samp>pk</samp>’</dt> -<dd><a name="index-_002epk"></a> -<a name="index-PKFONTS"></a> -<a name="index-TEXPKS"></a> -<a name="index-GLYPHFONTS-1"></a> -<a name="index-TEXFONTS-1"></a> -<p>(packed bitmap fonts, see <a href="http://tug.org/texinfohtml/dvips.html#Glyph-files">Glyph files</a> in <cite>Dvips</cite>) +<dd><span id="index-_002epk"></span> +<span id="index-PKFONTS"></span> +<span id="index-TEXPKS"></span> +<span id="index-GLYPHFONTS-1"></span> +<span id="index-TEXFONTS-1"></span> +<p>(packed bitmap fonts, see <a href="https://tug.org/texinfohtml/dvips.html#Glyph-files">Glyph files</a> in <cite>Dvips</cite>) <code><var>PROGRAM</var>FONTS</code> (<var>program</var> being ‘<samp>XDVI</samp>’, etc.), <code>PKFONTS</code>, <code>TEXPKS</code>, <code>GLYPHFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>pk</samp>’; @@ -2581,34 +2540,34 @@ dynamic creation program: <code>mktexpk</code>. </p> </dd> <dt>‘<samp>PostScript header</samp>’</dt> -<dd><a name="index-_002epro"></a> -<a name="index-TEXPSHEADERS"></a> -<a name="index-PSHEADERS"></a> -<p>(downloadable PostScript, see <a href="http://tug.org/texinfohtml/dvips.html#Header-files">Header files</a> in <cite>Dvips</cite>) +<dd><span id="index-_002epro"></span> +<span id="index-TEXPSHEADERS"></span> +<span id="index-PSHEADERS"></span> +<p>(downloadable PostScript, see <a href="https://tug.org/texinfohtml/dvips.html#Header-files">Header files</a> in <cite>Dvips</cite>) <code>TEXPSHEADERS</code>, <code>PSHEADERS</code>; additional suffix ‘<samp>.pro</samp>’. </p> </dd> <dt>‘<samp>ris</samp>’</dt> -<dd><a name="index-_002eris"></a> -<a name="index-RISINPUTS"></a> +<dd><span id="index-_002eris"></span> +<span id="index-RISINPUTS"></span> <p>(RIS bibliography files, primarily for Biber, <a href="http://ctan.org/pkg/biber">http://ctan.org/pkg/biber</a>) <code>RISINPUTS</code> suffix ‘<samp>.ris</samp>’. </p> </dd> <dt>‘<samp>subfont definition files</samp>’</dt> -<dd><a name="index-_002esfd"></a> -<a name="index-SFDFONTS"></a> +<dd><span id="index-_002esfd"></span> +<span id="index-SFDFONTS"></span> <p>(subfont definition files) <code>SFDFONTS</code> suffix ‘<samp>.sfd</samp>’. </p> </dd> <dt>‘<samp>tex</samp>’</dt> -<dd><a name="index-_002etex"></a> -<a name="index-TEXINPUTS-1"></a> -<p>(TeX source, see <a href="http://tug.org/texinfohtml/web2c.html#tex-invocation">tex invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002etex"></span> +<span id="index-TEXINPUTS-1"></span> +<p>(TeX source, see <a href="https://tug.org/texinfohtml/web2c.html#tex-invocation">tex invocation</a> in <cite>Web2c</cite>) <code>TEXINPUTS</code>; suffix ‘<samp>.tex</samp>’; additional suffixes: none, because such a list cannot be complete; @@ -2616,86 +2575,86 @@ dynamic creation program: <code>mktextex</code>. </p> </dd> <dt>‘<samp>TeX system documentation</samp>’</dt> -<dd><a name="index-doc-files"></a> -<a name="index-TEXDOCS"></a> +<dd><span id="index-doc-files"></span> +<span id="index-TEXDOCS"></span> <p>(Documentation files for the TeX system) <code>TEXDOCS</code>. </p> </dd> <dt>‘<samp>TeX system sources</samp>’</dt> -<dd><a name="index-source-files"></a> -<a name="index-TEXSOURCES"></a> +<dd><span id="index-source-files"></span> +<span id="index-TEXSOURCES"></span> <p>(Source files for the TeX system) <code>TEXSOURCES</code>. </p> </dd> <dt>‘<samp>texmfscripts</samp>’</dt> -<dd><a name="index-TEXMFSCRIPTS"></a> +<dd><span id="index-TEXMFSCRIPTS"></span> <p>(Architecture-independent executables distributed in the texmf trees) <code>TEXMFSCRIPTS</code>. </p> </dd> <dt>‘<samp>texpool</samp>’</dt> -<dd><a name="index-_002epool-2"></a> -<a name="index-TEXPOOL"></a> -<p>(TeX program strings, see <a href="http://tug.org/texinfohtml/web2c.html#pooltype-invocation">pooltype invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-_002epool-2"></span> +<span id="index-TEXPOOL"></span> +<p>(TeX program strings, see <a href="https://tug.org/texinfohtml/web2c.html#pooltype-invocation">pooltype invocation</a> in <cite>Web2c</cite>) <code>TEXPOOL</code>, <code>TEXMFINI</code>; suffix ‘<samp>.pool</samp>’. </p> </dd> <dt>‘<samp>tfm</samp>’</dt> -<dd><a name="index-_002etfm"></a> -<a name="index-TFMFONTS"></a> -<a name="index-TEXFONTS-2"></a> -<p>(TeX font metrics, see <a href="http://tug.org/texinfohtml/dvips.html#Metric-files">Metric files</a> in <cite>Dvips</cite>) +<dd><span id="index-_002etfm"></span> +<span id="index-TFMFONTS"></span> +<span id="index-TEXFONTS-2"></span> +<p>(TeX font metrics, see <a href="https://tug.org/texinfohtml/dvips.html#Metric-files">Metric files</a> in <cite>Dvips</cite>) <code>TFMFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>.tfm</samp>’; dynamic creation program: <code>mktextfm</code>. </p> </dd> <dt>‘<samp>Troff fonts</samp>’</dt> -<dd><a name="index-TRFONTS"></a> -<p>(Troff fonts, used by DMP; see <a href="http://tug.org/texinfohtml/web2c.html#DMP-invocation">DMP invocation</a> in <cite>Web2c</cite>) +<dd><span id="index-TRFONTS"></span> +<p>(Troff fonts, used by DMP; see <a href="https://tug.org/texinfohtml/web2c.html#DMP-invocation">DMP invocation</a> in <cite>Web2c</cite>) <code>TRFONTS</code>. </p> </dd> <dt>‘<samp>truetype fonts</samp>’</dt> -<dd><a name="index-_002ettf"></a> -<a name="index-_002ettc"></a> -<a name="index-TTFONTS"></a> +<dd><span id="index-_002ettf"></span> +<span id="index-_002ettc"></span> +<span id="index-TTFONTS"></span> <p>(TrueType outline fonts) <code>TTFONTS</code>; suffixes ‘<samp>.ttf</samp>’ and ‘<samp>.TTF</samp>’, ‘<samp>.ttc</samp>’ and ‘<samp>.TTC</samp>’, ‘<samp>.dfont</samp>’. </p> </dd> <dt>‘<samp>type1 fonts</samp>’</dt> -<dd><a name="index-_002epfa"></a> -<a name="index-_002epfb"></a> -<a name="index-T1FONTS"></a> -<a name="index-T1INPUTS"></a> -<a name="index-TEXPSHEADERS-1"></a> -<a name="index-DVIPSHEADERS"></a> -<p>(Type 1 PostScript outline fonts, see <a href="http://tug.org/texinfohtml/dvips.html#Glyph-files">Glyph files</a> in <cite>Dvips</cite>) +<dd><span id="index-_002epfa"></span> +<span id="index-_002epfb"></span> +<span id="index-T1FONTS"></span> +<span id="index-T1INPUTS"></span> +<span id="index-TEXPSHEADERS-1"></span> +<span id="index-DVIPSHEADERS"></span> +<p>(Type 1 PostScript outline fonts, see <a href="https://tug.org/texinfohtml/dvips.html#Glyph-files">Glyph files</a> in <cite>Dvips</cite>) <code>T1FONTS</code>, <code>T1INPUTS</code>, <code>TEXPSHEADERS</code>, <code>DVIPSHEADERS</code>; suffixes ‘<samp>.pfa</samp>’, ‘<samp>.pfb</samp>’. </p> </dd> <dt>‘<samp>type42 fonts</samp>’</dt> -<dd><a name="index-T42FONTS"></a> +<dd><span id="index-T42FONTS"></span> <p>(Type 42 PostScript outline fonts) <code>T42FONTS</code>. </p> </dd> <dt>‘<samp>vf</samp>’</dt> -<dd><a name="index-_002evf"></a> -<a name="index-VFFONTS"></a> -<a name="index-TEXFONTS-3"></a> -<p>(virtual fonts, see <a href="http://tug.org/texinfohtml/dvips.html#Virtual-fonts">Virtual fonts</a> in <cite>Dvips</cite>) +<dd><span id="index-_002evf"></span> +<span id="index-VFFONTS"></span> +<span id="index-TEXFONTS-3"></span> +<p>(virtual fonts, see <a href="https://tug.org/texinfohtml/dvips.html#Virtual-fonts">Virtual fonts</a> in <cite>Dvips</cite>) <code>VFFONTS</code>, <code>TEXFONTS</code>; suffix ‘<samp>.vf</samp>’. </p> </dd> <dt>‘<samp>web</samp>’</dt> -<dd><a name="index-_002eweb-1"></a> -<a name="index-WEBINPUTS"></a> +<dd><span id="index-_002eweb-1"></span> +<span id="index-WEBINPUTS"></span> <p>(WEB input files) <code>WEBINPUTS</code>; suffix ‘<samp>.web</samp>’; @@ -2703,7 +2662,7 @@ additional suffix ‘<samp>.ch</samp>’. </p> </dd> <dt>‘<samp>web2c files</samp>’</dt> -<dd><a name="index-WEB2C"></a> +<dd><span id="index-WEB2C"></span> <p>(files specific to the web2c implementation) <code>WEB2C</code>. </p></dd> @@ -2717,13 +2676,13 @@ this gives us the following table. </p> <dl compact="compact"> <dt>‘<samp>other text files</samp>’</dt> -<dd><a name="index-FOOINPUTS"></a> +<dd><span id="index-FOOINPUTS"></span> <p>(text files used by ‘<samp>foo</samp>’) <code>FOOINPUTS</code>. </p> </dd> <dt>‘<samp>other binary files</samp>’</dt> -<dd><a name="index-FOOINPUTS-1"></a> +<dd><span id="index-FOOINPUTS-1"></span> <p>(binary files used by ‘<samp>foo</samp>’) <code>FOOINPUTS</code>. </p></dd> @@ -2742,8 +2701,8 @@ non-metric) files. </li><li> Each font format has a variable of its own. -</li><li> <a name="index-XDVIFONTS"></a> -<a name="index-DVIPSFONTS"></a> +</li><li> <span id="index-XDVIFONTS"></span> +<span id="index-DVIPSFONTS"></span> Each program has its own font override path as well; e.g., <code>DVIPSFONTS</code> for Dvipsk. Again, this is for bitmaps, not metrics. @@ -2751,17 +2710,15 @@ Each program has its own font override path as well; e.g., <hr> -<a name="File-lookup"></a> -<div class="header"> +<span id="File-lookup"></span><div class="header"> <p> Next: <a href="#Glyph-lookup" accesskey="n" rel="next">Glyph lookup</a>, Previous: <a href="#Supported-file-formats" accesskey="p" rel="prev">Supported file formats</a>, Up: <a href="#TeX-support" accesskey="u" rel="up">TeX support</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="File-lookup-1"></a> -<h3 class="section">6.2 File lookup</h3> +<span id="File-lookup-1"></span><h3 class="section">6.2 File lookup</h3> -<a name="index-file-lookup"></a> -<a name="index-searching-for-files"></a> -<a name="index-TeX-file-lookup"></a> +<span id="index-file-lookup"></span> +<span id="index-searching-for-files"></span> +<span id="index-TeX-file-lookup"></span> <p>This section describes how Kpathsea searches for most files (bitmap font searches are the exception, as described in the next section). @@ -2783,9 +2740,9 @@ the fontmaps. Example: given ‘<samp>foo.bar</samp>’, we also look f run it (see <a href="#mktex-scripts">mktex scripts</a>). </li></ol> -<a name="index-extensions_002c-filename"></a> -<a name="index-suffixes_002c-filename"></a> -<a name="index-try_005fstd_005fextension_005ffirst"></a> +<span id="index-extensions_002c-filename"></span> +<span id="index-suffixes_002c-filename"></span> +<span id="index-try_005fstd_005fextension_005ffirst"></span> <p>The order in which we search for “suffixed” name (item 1) or the “as-is” name (item 2) is controlled by the <samp>try_std_extension_first</samp> configuration value. The default set @@ -2800,8 +2757,8 @@ always tried; the difference is the order in which they are tried. which *already* have an extension. A name without an extension (e.g., ‘<samp>tex story</samp>’) will always have an extension added first. </p> -<a name="index-tex_002dfile_002ec"></a> -<a name="index-kpathsea_005ffind_005ffile"></a> +<span id="index-tex_002dfile_002ec"></span> +<span id="index-kpathsea_005ffind_005ffile"></span> <p>This algorithm is implemented in the function <code>kpathsea_find_file</code> in the source file <samp>kpathsea/tex-file.c</samp>. You can watch it in action with the @@ -2809,17 +2766,15 @@ debugging options (see <a href="#Debugging">Debugging</a>). </p> <hr> -<a name="Glyph-lookup"></a> -<div class="header"> +<span id="Glyph-lookup"></span><div class="header"> <p> Next: <a href="#Suppressing-warnings" accesskey="n" rel="next">Suppressing warnings</a>, Previous: <a href="#File-lookup" accesskey="p" rel="prev">File lookup</a>, Up: <a href="#TeX-support" accesskey="u" rel="up">TeX support</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Glyph-lookup-1"></a> -<h3 class="section">6.3 Glyph lookup</h3> +<span id="Glyph-lookup-1"></span><h3 class="section">6.3 Glyph lookup</h3> -<a name="index-glyph-lookup"></a> -<a name="index-searching-for-glyphs"></a> -<a name="index-TeX-glyph-lookup"></a> +<span id="index-glyph-lookup"></span> +<span id="index-searching-for-glyphs"></span> +<span id="index-TeX-glyph-lookup"></span> <p>This section describes how Kpathsea searches for a bitmap font in GF or PK format (or either) given a font name (e.g., ‘<samp>cmr10</samp>’) and a @@ -2843,32 +2798,30 @@ generate the font (see <a href="#mktex-scripts">mktex scripts</a>) last-resort font (typically ‘<samp>cmr10</samp>’). </li></ol> -<a name="index-tex_002dglyph_002ec"></a> -<a name="index-kpathsea_005ffind_005fglyph"></a> +<span id="index-tex_002dglyph_002ec"></span> +<span id="index-kpathsea_005ffind_005fglyph"></span> <p>This is implemented in <code>kpathsea_find_glyph</code> in <samp>kpathsea/tex-glyph.c</samp>. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Basic-glyph-lookup" accesskey="1">Basic glyph lookup</a>:</td><td> </td><td align="left" valign="top">Features common to all glyph lookups. +<tr><td align="left" valign="top">• <a href="#Basic-glyph-lookup" accesskey="1">Basic glyph lookup</a></td><td> </td><td align="left" valign="top">Features common to all glyph lookups. </td></tr> -<tr><td align="left" valign="top">• <a href="#Fontmap" accesskey="2">Fontmap</a>:</td><td> </td><td align="left" valign="top">Aliases for fonts. +<tr><td align="left" valign="top">• <a href="#Fontmap" accesskey="2">Fontmap</a></td><td> </td><td align="left" valign="top">Aliases for fonts. </td></tr> -<tr><td align="left" valign="top">• <a href="#Fallback-font" accesskey="3">Fallback font</a>:</td><td> </td><td align="left" valign="top">Resolutions and fonts of last resort. +<tr><td align="left" valign="top">• <a href="#Fallback-font" accesskey="3">Fallback font</a></td><td> </td><td align="left" valign="top">Resolutions and fonts of last resort. </td></tr> </table> <hr> -<a name="Basic-glyph-lookup"></a> -<div class="header"> +<span id="Basic-glyph-lookup"></span><div class="header"> <p> Next: <a href="#Fontmap" accesskey="n" rel="next">Fontmap</a>, Up: <a href="#Glyph-lookup" accesskey="u" rel="up">Glyph lookup</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Basic-glyph-lookup-1"></a> -<h4 class="subsection">6.3.1 Basic glyph lookup</h4> +<span id="Basic-glyph-lookup-1"></span><h4 class="subsection">6.3.1 Basic glyph lookup</h4> -<a name="index-basic-glyph-lookup"></a> -<a name="index-common-features-in-glyph-lookup"></a> +<span id="index-basic-glyph-lookup"></span> +<span id="index-common-features-in-glyph-lookup"></span> <p>When Kpathsea looks for a bitmap font <var>name</var> at resolution <var>dpi</var> in a format <var>format</var>, it first checks each directory in the search @@ -2880,9 +2833,9 @@ path for a file ‘<samp><var>name</var>.<var>dpi</var><var>format</var></sa ‘<samp>dpi600/cmr10.pk</samp>’. This is how fonts are typically stored on filesystems (such as DOS) that permit only three-character extensions. </p> -<a name="index-tolerance-for-glyph-lookup"></a> -<a name="index-glyph-lookup-bitmap-tolerance"></a> -<a name="index-KPSE_005fBITMAP_005fTOLERANCE"></a> +<span id="index-tolerance-for-glyph-lookup"></span> +<span id="index-glyph-lookup-bitmap-tolerance"></span> +<span id="index-KPSE_005fBITMAP_005fTOLERANCE"></span> <p>If that fails, Kpathsea looks for a font with a close-enough <var>dpi</var>. “Close enough” is defined by the macro <code>KPSE_BITMAP_TOLERANCE</code> in <samp>kpathsea/tex-glyph.h</samp> to be <code><var>dpi</var> / 500 + 1</code>. This is @@ -2891,19 +2844,17 @@ slightly more than the 0.2% minimum allowed by the DVI standard </p> <hr> -<a name="Fontmap"></a> -<div class="header"> +<span id="Fontmap"></span><div class="header"> <p> Next: <a href="#Fallback-font" accesskey="n" rel="next">Fallback font</a>, Previous: <a href="#Basic-glyph-lookup" accesskey="p" rel="prev">Basic glyph lookup</a>, Up: <a href="#Glyph-lookup" accesskey="u" rel="up">Glyph lookup</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Fontmap-1"></a> -<h4 class="subsection">6.3.2 Fontmap</h4> +<span id="Fontmap-1"></span><h4 class="subsection">6.3.2 Fontmap</h4> -<a name="index-fontmap-files"></a> -<a name="index-font-alias-files"></a> -<a name="index-aliases-for-fonts"></a> +<span id="index-fontmap-files"></span> +<span id="index-font-alias-files"></span> +<span id="index-aliases-for-fonts"></span> -<a name="index-texfonts_002emap"></a> +<span id="index-texfonts_002emap"></span> <p>If a bitmap font or metric file is not found with the original name (see the previous section), Kpathsea looks through any <em>fontmap</em> files for an <em>alias</em> for the original font name. These files are named @@ -2914,13 +2865,13 @@ are found are read; earlier definitions override later ones. <p>This feature is intended to help in two respects: </p> <ol> -<li> <a name="index-fontnames_002c-arbitrary-length"></a> +<li> <span id="index-fontnames_002c-arbitrary-length"></span> An alias name is limited in length only by available memory, not by your filesystem. Therefore, if you want to ask for ‘<samp>Times-Roman</samp>’ instead of <samp>ptmr</samp>, you can (you get ‘<samp>ptmr8r</samp>’). -</li><li> <a name="index-circle-fonts"></a> -<a name="index-lcircle10"></a> +</li><li> <span id="index-circle-fonts"></span> +<span id="index-lcircle10"></span> A few fonts have historically had multiple names: specifically, LaTeX’s “circle font” has variously been known as <samp>circle10</samp>, <samp>lcircle10</samp>, and <samp>lcirc10</samp>. Aliases can make all the names @@ -2932,18 +2883,18 @@ file is; TeX documents will find their favorite name. <p>The format of fontmap files is straightforward: </p> <ul> -<li> <a name="index-comments_002c-in-fontmap-files"></a> +<li> <span id="index-comments_002c-in-fontmap-files"></span> Comments start with the last ‘<samp>%</samp>’ on a line and continue to the end of the line. (This provides for names that include a %, ill-advised as that may be.) -</li><li> <a name="index-whitespace_002c-in-fontmap-files"></a> +</li><li> <span id="index-whitespace_002c-in-fontmap-files"></span> Blank lines are ignored. </li><li> Each nonblank line is broken up into a series of <em>words</em>: a sequence of non-whitespace characters. -</li><li> <a name="index-include-fontmap-directive"></a> +</li><li> <span id="index-include-fontmap-directive"></span> If the first word is ‘<samp>include</samp>’, the second word is used as a filename, and it is searched for and read. @@ -2980,25 +2931,23 @@ The Fontname distribution has much more information on font naming </p> <hr> -<a name="Fallback-font"></a> -<div class="header"> +<span id="Fallback-font"></span><div class="header"> <p> Previous: <a href="#Fontmap" accesskey="p" rel="prev">Fontmap</a>, Up: <a href="#Glyph-lookup" accesskey="u" rel="up">Glyph lookup</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Fallback-font-1"></a> -<h4 class="subsection">6.3.3 Fallback font</h4> - -<a name="index-fallback-font"></a> -<a name="index-fallback-resolutions"></a> -<a name="index-font-of-last-resort"></a> -<a name="index-resolutions_002c-last_002dresort"></a> -<a name="index-last_002dresort-font"></a> - -<a name="index-DVIPSSIZES"></a> -<a name="index-XDVISIZES"></a> -<a name="index-DVILJSIZES"></a> -<a name="index-TEXSIZES"></a> -<a name="index-default_005ftexsizes"></a> +<span id="Fallback-font-1"></span><h4 class="subsection">6.3.3 Fallback font</h4> + +<span id="index-fallback-font"></span> +<span id="index-fallback-resolutions"></span> +<span id="index-font-of-last-resort"></span> +<span id="index-resolutions_002c-last_002dresort"></span> +<span id="index-last_002dresort-font"></span> + +<span id="index-DVIPSSIZES"></span> +<span id="index-XDVISIZES"></span> +<span id="index-DVILJSIZES"></span> +<span id="index-TEXSIZES"></span> +<span id="index-default_005ftexsizes"></span> <p>If a bitmap font cannot be found or created at the requested size, Kpathsea looks for the font at a set of <em>fallback resolutions</em>. You specify these resolutions as a colon-separated list (like search paths). @@ -3008,8 +2957,8 @@ Kpathsea looks first for a program-specific environment variable (e.g., variable <code>default_texsizes</code>). You can set this list to be empty if you prefer to find fonts at their stated size or not at all. </p> -<a name="index-cmr10_002c-as-fallback-font"></a> -<a name="index-kpathsea_005finit_005fprog"></a> +<span id="index-cmr10_002c-as-fallback-font"></span> +<span id="index-kpathsea_005finit_005fprog"></span> <p>Finally, if the font cannot be found even at the fallback resolutions, Kpathsea looks for a fallback font, typically <samp>cmr10</samp>. Programs must enable this feature by calling <code>kpathsea_init_prog</code> @@ -3017,18 +2966,16 @@ must enable this feature by calling <code>kpathsea_init_prog</code> </p> <hr> -<a name="Suppressing-warnings"></a> -<div class="header"> +<span id="Suppressing-warnings"></span><div class="header"> <p> Next: <a href="#mktex-scripts" accesskey="n" rel="next">mktex scripts</a>, Previous: <a href="#Glyph-lookup" accesskey="p" rel="prev">Glyph lookup</a>, Up: <a href="#TeX-support" accesskey="u" rel="up">TeX support</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Suppressing-warnings-1"></a> -<h3 class="section">6.4 Suppressing warnings</h3> +<span id="Suppressing-warnings-1"></span><h3 class="section">6.4 Suppressing warnings</h3> -<a name="index-warnings_002c-suppressing"></a> -<a name="index-suppressing-warnings"></a> +<span id="index-warnings_002c-suppressing"></span> +<span id="index-suppressing-warnings"></span> -<a name="index-TEX_005fHUSH-1"></a> +<span id="index-TEX_005fHUSH-1"></span> <p>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 @@ -3038,45 +2985,45 @@ possibilities: </p> <dl compact="compact"> <dt>‘<samp>all</samp>’ -<a name="index-all"></a> +<span id="index-all"></span> </dt> <dd><p>Suppress everything possible. </p> </dd> <dt>‘<samp>checksum</samp>’ -<a name="index-checksum"></a> +<span id="index-checksum"></span> </dt> -<dd><a name="index-mismatched-checksum-warnings"></a> +<dd><span id="index-mismatched-checksum-warnings"></span> <p>Suppress mismatched font checksum warnings. </p> </dd> <dt>‘<samp>lostchar</samp>’ -<a name="index-lostchar"></a> +<span id="index-lostchar"></span> </dt> -<dd><a name="index-missing-character-warnings"></a> +<dd><span id="index-missing-character-warnings"></span> <p>Suppress warnings when a character is missing from a font that a DVI or VF file tries to typeset. </p> </dd> <dt>‘<samp>none</samp>’ -<a name="index-none"></a> +<span id="index-none"></span> </dt> <dd><p>Don’t suppress any warnings. </p> </dd> <dt>‘<samp>readable</samp>’ -<a name="index-readable"></a> +<span id="index-readable"></span> </dt> -<dd><a name="index-unreadable-file-warnings"></a> +<dd><span id="index-unreadable-file-warnings"></span> <p>Suppress warnings about attempts to access a file whose permissions render it unreadable. </p> </dd> <dt>‘<samp>special</samp>’ -<a name="index-special"></a> +<span id="index-special"></span> </dt> -<dd><a name="index-unknown-special-warnings"></a> -<a name="index-_005cspecial_002c-suppressing-warnings-about"></a> +<dd><span id="index-unknown-special-warnings"></span> +<span id="index-_005cspecial_002c-suppressing-warnings-about"></span> <p>Suppresses warnings about an unimplemented or unparsable ‘<samp>\special</samp>’ command. </p></dd> @@ -3088,21 +3035,19 @@ appropriate. </p> <hr> -<a name="mktex-scripts"></a> -<div class="header"> +<span id="mktex-scripts"></span><div class="header"> <p> Previous: <a href="#Suppressing-warnings" accesskey="p" rel="prev">Suppressing warnings</a>, Up: <a href="#TeX-support" accesskey="u" rel="up">TeX support</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="mktex-scripts-1"></a> -<h3 class="section">6.5 <samp>mktex</samp> scripts</h3> +<span id="mktex-scripts-1"></span><h3 class="section">6.5 <samp>mktex</samp> scripts</h3> -<a name="index-mktex-scripts"></a> -<a name="index-scripts-for-file-creation"></a> +<span id="index-mktex-scripts"></span> +<span id="index-scripts-for-file-creation"></span> -<a name="index-font-set_002c-infinite"></a> -<a name="index-dynamic-creation-of-files"></a> -<a name="index-Sauter-fonts_002c-and-dynamic-source-creation"></a> -<a name="index-EC-fonts_002c-and-dynamic-source-creation"></a> +<span id="index-font-set_002c-infinite"></span> +<span id="index-dynamic-creation-of-files"></span> +<span id="index-Sauter-fonts_002c-and-dynamic-source-creation"></span> +<span id="index-EC-fonts_002c-and-dynamic-source-creation"></span> <p>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 (see <a href="#mktex-configuration">mktex configuration</a>). These are collectively @@ -3126,28 +3071,26 @@ file it created (and nothing else) to standard output; it can write diagnostics to standard error. </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#mktex-configuration" accesskey="1">config</a>:</td><td> </td><td align="left" valign="top"> +<tr><td align="left" valign="top">• <a href="#mktex-configuration" accesskey="1">config</a></td><td> </td><td align="left" valign="top"> </td></tr> -<tr><td align="left" valign="top">• <a href="#mktex-script-names" accesskey="2">names</a>:</td><td> </td><td align="left" valign="top"> +<tr><td align="left" valign="top">• <a href="#mktex-script-names" accesskey="2">names</a></td><td> </td><td align="left" valign="top"> </td></tr> -<tr><td align="left" valign="top">• <a href="#mktex-script-arguments" accesskey="3">args</a>:</td><td> </td><td align="left" valign="top"> +<tr><td align="left" valign="top">• <a href="#mktex-script-arguments" accesskey="3">args</a></td><td> </td><td align="left" valign="top"> </td></tr> </table> <hr> -<a name="mktex-configuration"></a> -<div class="header"> +<span id="mktex-configuration"></span><div class="header"> <p> Next: <a href="#mktex-script-names" accesskey="n" rel="next">mktex script names</a>, Up: <a href="#mktex-scripts" accesskey="u" rel="up">mktex scripts</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="mktex-configuration-1"></a> -<h4 class="subsection">6.5.1 <samp>mktex</samp> configuration</h4> +<span id="mktex-configuration-1"></span><h4 class="subsection">6.5.1 <samp>mktex</samp> configuration</h4> -<a name="index-mktex-script-configuration"></a> -<a name="index-configuration-of-mktex-scripts"></a> -<a name="index-enabling-mktex-scripts"></a> -<a name="index-disabling-mktex-scripts"></a> +<span id="index-mktex-script-configuration"></span> +<span id="index-configuration-of-mktex-scripts"></span> +<span id="index-enabling-mktex-scripts"></span> +<span id="index-disabling-mktex-scripts"></span> <p>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 @@ -3155,14 +3098,14 @@ absence of <code>configure</code> options specifying otherwise, everything but <samp>mktextex</samp> will be enabled by default. The <code>configure</code> options to change the defaults are: </p> -<a name="index-configure-options-for-mktex-scripts"></a> -<a name="index-_002d_002dwithout_002dmktexfmt_002ddefault"></a> -<a name="index-_002d_002dwithout_002dmktexmf_002ddefault"></a> -<a name="index-_002d_002dwithout_002dmktexocp_002ddefault"></a> -<a name="index-_002d_002dwithout_002dmktexofm_002ddefault"></a> -<a name="index-_002d_002dwithout_002dmktexpk_002ddefault"></a> -<a name="index-_002d_002dwithout_002dmktextfm_002ddefault"></a> -<a name="index-_002d_002dwith_002dmktextex_002ddefault"></a> +<span id="index-configure-options-for-mktex-scripts"></span> +<span id="index-_002d_002dwithout_002dmktexfmt_002ddefault"></span> +<span id="index-_002d_002dwithout_002dmktexmf_002ddefault"></span> +<span id="index-_002d_002dwithout_002dmktexocp_002ddefault"></span> +<span id="index-_002d_002dwithout_002dmktexofm_002ddefault"></span> +<span id="index-_002d_002dwithout_002dmktexpk_002ddefault"></span> +<span id="index-_002d_002dwithout_002dmktextfm_002ddefault"></span> +<span id="index-_002d_002dwith_002dmktextex_002ddefault"></span> <div class="example"> <pre class="example">--without-mktexfmt-default --without-mktexmf-default @@ -3177,15 +3120,15 @@ options to change the defaults are: or configuration file value named for the script is set; e.g., <samp>MKTEXPK</samp> (see <a href="#mktex-script-arguments">mktex script arguments</a>). </p> -<a name="index-fmtutils_002ecnf"></a> +<span id="index-fmtutils_002ecnf"></span> <p><code>mktexfmt</code> reads a file <samp>fmtutil.cnf</samp>, typically located in <samp>texmf/web2c/</samp> to glean its configuration information. The rest of the files and features in this section are primarily intended for the font generation scripts. </p> -<a name="index-mktex_002ecnf-1"></a> -<a name="index-mktex_002eopt"></a> -<a name="index-site-overrides-for-mktex_2026"></a> +<span id="index-mktex_002ecnf-1"></span> +<span id="index-mktex_002eopt"></span> +<span id="index-site-overrides-for-mktex_2026"></span> <p>As distributed, all the scripts source a file <samp>texmf/web2c/mktex.cnf</samp> if it exists, so you can override various defaults. @@ -3198,8 +3141,8 @@ it’s an arbitrary Bourne shell script. The distribution contains a sample <samp>mktex.cnf</samp> for you to copy and modify as you please (it is not installed anywhere). </p> -<a name="index-mktex_002eopt-1"></a> -<a name="index-MT_005fFEATURES"></a> +<span id="index-mktex_002eopt-1"></span> +<span id="index-MT_005fFEATURES"></span> <p>In addition, you can configure a number of features with the <code>MT_FEATURES</code> variable, which you can define: </p> @@ -3227,23 +3170,23 @@ directory is used. </p> <dl compact="compact"> <dt>‘<samp>appendonlydir</samp>’ -<a name="index-appendonlydir"></a> +<span id="index-appendonlydir"></span> </dt> -<dd><a name="index-directories_002c-making-append_002donly"></a> -<a name="index-mktexdir"></a> +<dd><span id="index-directories_002c-making-append_002donly"></span> +<span id="index-mktexdir"></span> <p>Tell <code>mktexdir</code> to create directories append-only, i.e., set -their sticky bit (see <a href="http://www.gnu.org/software/coreutils/manual/coreutils#Mode-Structure">Mode Structure</a> in <cite>GNU Core +their sticky bit (see <a href="https://www.gnu.org/software/coreutils/manual/coreutils#Mode-Structure">Mode Structure</a> in <cite>GNU Core Utilities</cite>). 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 enabled by default. </p> </dd> <dt>‘<samp>dosnames</samp>’ -<a name="index-dosnames"></a> +<span id="index-dosnames"></span> </dt> -<dd><a name="index-8_002e3-filenames_002c-using"></a> -<a name="index-DOS-compatible-names"></a> -<a name="index-dpinnn-directories"></a> +<dd><span id="index-8_002e3-filenames_002c-using"></span> +<span id="index-DOS-compatible-names"></span> +<span id="index-dpinnn-directories"></span> <p>Use 8.3 names; e.g., <samp>dpi600/cmr10.pk</samp> instead of <samp>cmr10.600pk</samp>. Note that this feature only affects filenames that would otherwise clash with other TeX-related filenames; <samp>mktex</samp> @@ -3264,83 +3207,83 @@ the emulation programs don’t consult <samp>mktex.opt</samp>. </p> </dd> <dt>‘<samp>fontmaps</samp>’ -<a name="index-fontmaps-1"></a> +<span id="index-fontmaps-1"></span> </dt> -<dd><a name="index-fontmaps"></a> -<a name="index-fontname"></a> +<dd><span id="index-fontmaps"></span> +<span id="index-fontname"></span> <p>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. (see <a href="fontname.html#Top">Introduction</a> in <cite>Fontname</cite>). </p> </dd> <dt>‘<samp>nomfdrivers</samp>’ -<a name="index-nomfdrivers"></a> +<span id="index-nomfdrivers"></span> </dt> -<dd><a name="index-metafont-driver-files"></a> +<dd><span id="index-metafont-driver-files"></span> <p>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. </p> </dd> <dt>‘<samp>nomode</samp>’ -<a name="index-nomode"></a> +<span id="index-nomode"></span> </dt> -<dd><a name="index-mode-directory_002c-omitting"></a> +<dd><span id="index-mode-directory_002c-omitting"></span> <p>Omit the directory level for the mode name; this is fine as long as you generate fonts for only one mode. </p> </dd> <dt>‘<samp>stripsupplier</samp>’ -<a name="index-stripsupplier"></a> +<span id="index-stripsupplier"></span> </dt> -<dd><a name="index-supplier-directory_002c-omitting"></a> +<dd><span id="index-supplier-directory_002c-omitting"></span> <p>Omit the font supplier name directory level. </p> </dd> <dt>‘<samp>striptypeface</samp>’ -<a name="index-striptypeface"></a> +<span id="index-striptypeface"></span> </dt> -<dd><a name="index-typeface-directory_002c-omitting"></a> +<dd><span id="index-typeface-directory_002c-omitting"></span> <p>Omit the font typeface name directory level. </p> </dd> <dt>‘<samp>strip</samp>’ -<a name="index-strip"></a> +<span id="index-strip"></span> </dt> -<dd><a name="index-supplier-directory_002c-omitting-1"></a> -<a name="index-typeface-directory_002c-omitting-1"></a> +<dd><span id="index-supplier-directory_002c-omitting-1"></span> +<span id="index-typeface-directory_002c-omitting-1"></span> <p>Omit the font supplier and typeface name directory levels. This feature is deprecated in favour of ‘<samp>stripsupplier</samp>’ and ‘<samp>striptypeface</samp>’. </p> </dd> <dt>‘<samp>varfonts</samp>’ -<a name="index-varfonts"></a> +<span id="index-varfonts"></span> </dt> -<dd><a name="index-_002fvar_002ftmp_002ftexfonts"></a> -<a name="index-VARTEXFONTS"></a> -<a name="index-Linux-File-System-Standard"></a> +<dd><span id="index-_002fvar_002ftmp_002ftexfonts"></span> +<span id="index-VARTEXFONTS"></span> +<span id="index-Linux-File-System-Standard"></span> <p>When this option is enabled, fonts that would otherwise be written in system texmf tree go to the <code>VARTEXFONTS</code> tree instead. The default value in <samp>kpathsea/Makefile.in</samp> is <samp>/var/tmp/texfonts</samp>. The <cite>Linux File System Standard</cite> recommends <samp>/var/tex/fonts</samp>. </p> -<a name="index-USE_005fVARTEXFONTS"></a> +<span id="index-USE_005fVARTEXFONTS"></span> <p>The ‘<samp>varfonts</samp>’ setting in <code>MT_FEATURES</code> is overridden by the <code>USE_VARTEXFONTS</code> environment variable: if set to ‘<samp>1</samp>’, the feature is enabled, and if set to ‘<samp>0</samp>’, the feature is disabled. </p> </dd> <dt>‘<samp>texmfvar</samp>’ -<a name="index-texmfvar"></a> +<span id="index-texmfvar"></span> </dt> -<dd><a name="index-TEXMFVAR"></a> +<dd><span id="index-TEXMFVAR"></span> <p>Force generated files that would go into a system tree (as defined by <code>SYSTEXMF</code>) into <code>TEXMFVAR</code>. Starting with teTeX-3.0, the variable <code>TEXMFVAR</code> is always set. The ‘<samp>varfonts</samp>’ feature takes precedence if also set. </p> -<a name="index-USE_005fTEXMFVAR"></a> +<span id="index-USE_005fTEXMFVAR"></span> <p>The ‘<samp>texmfvar</samp>’ setting in <code>MT_FEATURES</code> is overridden by the <code>USE_TEXMFVAR</code> environment variable: if set to ‘<samp>1</samp>’, the feature is enabled, and if set to ‘<samp>0</samp>’, the feature is disabled. @@ -3349,75 +3292,73 @@ feature is enabled, and if set to ‘<samp>0</samp>’, the feature is d <hr> -<a name="mktex-script-names"></a> -<div class="header"> +<span id="mktex-script-names"></span><div class="header"> <p> Next: <a href="#mktex-script-arguments" accesskey="n" rel="next">mktex script arguments</a>, Previous: <a href="#mktex-configuration" accesskey="p" rel="prev">mktex configuration</a>, Up: <a href="#mktex-scripts" accesskey="u" rel="up">mktex scripts</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="mktex-script-names-1"></a> -<h4 class="subsection">6.5.2 <samp>mktex</samp> script names</h4> +<span id="mktex-script-names-1"></span><h4 class="subsection">6.5.2 <samp>mktex</samp> script names</h4> -<a name="index-mktex-script-names"></a> -<a name="index-names-for-mktex-scripts"></a> +<span id="index-mktex-script-names"></span> +<span id="index-names-for-mktex-scripts"></span> <p>The following table shows the default name of the script for each of the file types which support runtime generation. </p> <dl compact="compact"> <dt><samp>mktexfmt</samp></dt> -<dd><a name="index-mktexfmt"></a> -<a name="index-fmtutil"></a> +<dd><span id="index-mktexfmt"></span> +<span id="index-fmtutil"></span> <p>(‘<samp>.fmt</samp>’, ‘<samp>.base</samp>’, ‘<samp>.mem</samp>’) TeX/Metafont/MetaPost formats. This script is also named <code>fmtutil</code>, and reads <samp>fmtutil.cnf</samp> for configuration information. </p> </dd> <dt><samp>mktexmf</samp></dt> -<dd><a name="index-mktexmf"></a> +<dd><span id="index-mktexmf"></span> <p>(‘<samp>.mf</samp>’) Metafont input files. </p> </dd> <dt><samp>mkocp</samp></dt> -<dd><a name="index-mkocp"></a> +<dd><span id="index-mkocp"></span> <p>(‘<samp>.ocp</samp>’) Omega compiled process files. </p> </dd> <dt><samp>mkofm</samp></dt> -<dd><a name="index-mkofm"></a> +<dd><span id="index-mkofm"></span> <p>(‘<samp>.ofm</samp>’) Omega font metric files. </p> </dd> <dt><samp>mktexpk</samp></dt> -<dd><a name="index-mktexpk"></a> +<dd><span id="index-mktexpk"></span> <p>(‘<samp>pk</samp>’) Glyph fonts. </p> </dd> <dt><samp>mktextex</samp></dt> -<dd><a name="index-mktextex"></a> +<dd><span id="index-mktextex"></span> <p>(‘<samp>.tex</samp>’) TeX input files (disabled by default). </p> </dd> <dt><samp>mktextfm</samp></dt> -<dd><a name="index-mktextfm"></a> +<dd><span id="index-mktextfm"></span> <p>(‘<samp>.tfm</samp>’) TFM files. </p></dd> </dl> -<a name="index-DVIPSMAKEPK"></a> -<a name="index-XDVIMAKEPK"></a> -<a name="index-DVILJMAKEPK"></a> +<span id="index-DVIPSMAKEPK"></span> +<span id="index-XDVIMAKEPK"></span> +<span id="index-DVILJMAKEPK"></span> <p>These names can be overridden by an environment variable specific to the program—for example, <code>DVIPSMAKEPK</code> for Dvipsk. </p> -<a name="index-missfont_002elog"></a> -<a name="index-failed-mktex_2026-script-invocation"></a> +<span id="index-missfont_002elog"></span> +<span id="index-failed-mktex_2026-script-invocation"></span> <p>If a <code>mktex…</code> script fails, the invocation is appended to a file <samp>missfont.log</samp> (by default) in the current directory. You can then execute the log file to create the missing files after fixing the problem. </p> -<a name="index-TEXMFOUTPUT"></a> -<a name="index-MISSFONT_005fLOG"></a> +<span id="index-TEXMFOUTPUT"></span> +<span id="index-MISSFONT_005fLOG"></span> <p>If the current directory is not writable and the environment variable or configuration file value <code>TEXMFOUTPUT</code> is set, its value is used. Otherwise, nothing is written. The name ‘<samp>missfont.log</samp>’ is @@ -3426,15 +3367,13 @@ configuration file value. </p> <hr> -<a name="mktex-script-arguments"></a> -<div class="header"> +<span id="mktex-script-arguments"></span><div class="header"> <p> Previous: <a href="#mktex-script-names" accesskey="p" rel="prev">mktex script names</a>, Up: <a href="#mktex-scripts" accesskey="u" rel="up">mktex scripts</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="mktex-script-arguments-1"></a> -<h4 class="subsection">6.5.3 <samp>mktex</samp> script arguments</h4> +<span id="mktex-script-arguments-1"></span><h4 class="subsection">6.5.3 <samp>mktex</samp> script arguments</h4> -<a name="index-arguments-to-mktex"></a> +<span id="index-arguments-to-mktex"></span> <p>The first argument to a <samp>mktex</samp> script is always the name of the file to be created. @@ -3466,41 +3405,37 @@ script. <hr> -<a name="Programming"></a> -<div class="header"> +<span id="Programming"></span><div class="header"> <p> Next: <a href="#Reporting-bugs" accesskey="n" rel="next">Reporting bugs</a>, Previous: <a href="#TeX-support" accesskey="p" rel="prev">TeX support</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Programming-1"></a> -<h2 class="chapter">7 Programming</h2> +<span id="Programming-1"></span><h2 class="chapter">7 Programming</h2> <p>This chapter is for programmers who wish to use Kpathsea. See <a href="#Introduction">Introduction</a>, for the conditions under which you may do so (in short, it is released under LGPLv2.1 or later). </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Programming-overview" accesskey="1">Overview</a>:</td><td> </td><td align="left" valign="top">Introduction. +<tr><td align="left" valign="top">• <a href="#Programming-overview" accesskey="1">Overview</a></td><td> </td><td align="left" valign="top">Introduction. </td></tr> -<tr><td align="left" valign="top">• <a href="#Calling-sequence" accesskey="2">Calling sequence</a>:</td><td> </td><td align="left" valign="top">Specifics of what to call. +<tr><td align="left" valign="top">• <a href="#Calling-sequence" accesskey="2">Calling sequence</a></td><td> </td><td align="left" valign="top">Specifics of what to call. </td></tr> -<tr><td align="left" valign="top">• <a href="#Program_002dspecific-files" accesskey="3">Program-specific files</a>:</td><td> </td><td align="left" valign="top">How to handle these. +<tr><td align="left" valign="top">• <a href="#Program_002dspecific-files" accesskey="3">Program-specific files</a></td><td> </td><td align="left" valign="top">How to handle these. </td></tr> -<tr><td align="left" valign="top">• <a href="#Programming-with-config-files" accesskey="4">Config</a>:</td><td> </td><td align="left" valign="top">Getting info from texmf.cnf. +<tr><td align="left" valign="top">• <a href="#Programming-with-config-files" accesskey="4">Config</a></td><td> </td><td align="left" valign="top">Getting info from texmf.cnf. </td></tr> </table> <hr> -<a name="Programming-overview"></a> -<div class="header"> +<span id="Programming-overview"></span><div class="header"> <p> Next: <a href="#Calling-sequence" accesskey="n" rel="next">Calling sequence</a>, Up: <a href="#Programming" accesskey="u" rel="up">Programming</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Programming-overview-1"></a> -<h3 class="section">7.1 Programming overview</h3> +<span id="Programming-overview-1"></span><h3 class="section">7.1 Programming overview</h3> -<a name="index-programming-overview"></a> -<a name="index-overview-of-programming-with-Kpathsea"></a> +<span id="index-programming-overview"></span> +<span id="index-overview-of-programming-with-Kpathsea"></span> <p>Aside from this manual, your best source of information is the source to the programs that use Kpathsea (see <a href="#Introduction">Introduction</a>). First, @@ -3512,8 +3447,8 @@ its own config files. Web2c is source code I also maintain, so it uses Kpathsea rather straightforwardly, but is of course complicated by the Web to C translation. </p> -<a name="index-re_002dentrant-API"></a> -<a name="index-API_002c-re_002dentrant"></a> +<span id="index-re_002dentrant-API"></span> +<span id="index-API_002c-re_002dentrant"></span> <p>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 @@ -3524,10 +3459,10 @@ 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. </p> -<a name="index-pathsearch_002eh"></a> -<a name="index-tex_002dfile_002eh"></a> -<a name="index-tex_002dglyph_002eh"></a> -<a name="index-kpathsea_002eh"></a> +<span id="index-pathsearch_002eh"></span> +<span id="index-tex_002dfile_002eh"></span> +<span id="index-tex_002dglyph_002eh"></span> +<span id="index-kpathsea_002eh"></span> <p>Beyond these examples, the <samp>.h</samp> files in the Kpathsea source describe the interfaces and functionality (and of course the <samp>.c</samp> files define the actual routines, which are the ultimate documentation). @@ -3537,15 +3472,15 @@ looking up particular kinds of files. In view of the way the headers depend on each other, it is recommended to use <code>#include <kpathsea/kpathsea.h></code>, which includes every Kpathsea header. </p> -<a name="index-config_002eh"></a> -<a name="index-c_002dauto_002eh"></a> +<span id="index-config_002eh"></span> +<span id="index-c_002dauto_002eh"></span> <p>If you want to include only specific headers, you should still consider including <samp>kpathsea/config.h</samp> before including any other Kpathsea header, as it provides symbols used in the other headers. Note that <samp>kpathsea/config.h</samp> includes <samp>kpathsea/c-auto.h</samp>, which is generated by Autoconf. </p> -<a name="index-file-types_002c-registering-new"></a> +<span id="index-file-types_002c-registering-new"></span> <p>The library provides no way for an external program to register new file types: <samp>tex-file.[ch]</samp> must be modified to do this. For example, Kpathsea has support for looking up Dvips config files, even though no @@ -3562,28 +3497,26 @@ above, of course. </p> <hr> -<a name="Calling-sequence"></a> -<div class="header"> +<span id="Calling-sequence"></span><div class="header"> <p> Next: <a href="#Program_002dspecific-files" accesskey="n" rel="next">Program-specific files</a>, Previous: <a href="#Programming-overview" accesskey="p" rel="prev">Programming overview</a>, Up: <a href="#Programming" accesskey="u" rel="up">Programming</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Calling-sequence-1"></a> -<h3 class="section">7.2 Calling sequence</h3> +<span id="Calling-sequence-1"></span><h3 class="section">7.2 Calling sequence</h3> -<a name="index-programming-with-Kpathsea"></a> -<a name="index-calling-sequence"></a> +<span id="index-programming-with-Kpathsea"></span> +<span id="index-calling-sequence"></span> <p>The typical way to use Kpathsea in your program goes something like this: </p> <ol> -<li> <a name="index-kpathsea_005fnew"></a> +<li> <span id="index-kpathsea_005fnew"></span> Call <code>kpathsea_new</code> 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 <code>kpse</code> as a placeholder for the name of this variable. -</li><li> <a name="index-kpathsea_005fset_005fprogram_005fname"></a> -<a name="index-argv_005b0_005d"></a> +</li><li> <span id="index-kpathsea_005fset_005fprogram_005fname"></span> +<span id="index-argv_005b0_005d"></span> Call <code>kpathsea_set_program_name</code> with <code>argv[0]</code> as the second argument; the third argument is a string or <code>NULL</code>. The third argument is used by Kpathsea as the program name for the @@ -3592,25 +3525,25 @@ If the third argument is <code>NULL</code>, the value of the second argument is used. This function must be called before any other use of the Kpathsea library. -<a name="index-kpse_002d_003einvocation_005fname"></a> -<a name="index-kpse_002d_003einvocation_005fshort_005fname"></a> -<a name="index-kpse_002d_003eprogram_005fname"></a> -<a name="index-error-message-macros"></a> +<span id="index-kpse_002d_003einvocation_005fname"></span> +<span id="index-kpse_002d_003einvocation_005fshort_005fname"></span> +<span id="index-kpse_002d_003eprogram_005fname"></span> +<span id="index-error-message-macros"></span> <p><code>kpathsea_set_program_name</code> always sets the variables <code>kpse->invocation_name</code> and <code>kpse->invocation_short_name</code>. These variables are used in the error message macros defined in <samp>kpathsea/lib.h</samp>. It sets the variable <code>kpse->program_name</code> to the program name it uses. </p> -<a name="index-KPATHSEA_005fDEBUG"></a> +<span id="index-KPATHSEA_005fDEBUG"></span> <p>It also initializes debugging options based on the environment variable <code>KPATHSEA_DEBUG</code> (if that is set). </p> -<a name="index-SELFAUTOLOC"></a> -<a name="index-SELFAUTODIR"></a> -<a name="index-SELFAUTOPARENT"></a> -<a name="index-symlinks_002c-resolving"></a> -<a name="index-expanding-symlinks"></a> +<span id="index-SELFAUTOLOC"></span> +<span id="index-SELFAUTODIR"></span> +<span id="index-SELFAUTOPARENT"></span> +<span id="index-symlinks_002c-resolving"></span> +<span id="index-expanding-symlinks"></span> <p>Finally, it sets the environment variables <code>SELFAUTOLOC</code>, <code>SELFAUTODIR</code> and <code>SELFAUTOPARENT</code> to the location, parent and grandparent directory of the executable, removing <samp>.</samp> and <samp>..</samp> path @@ -3619,8 +3552,8 @@ configuration file to allow people to invoke TeX from anywhere. You can use ‘<samp>kpsewhich --expand-var=\$SELFAUTOLOC</samp>’, etc., to see the values. </p> -</li><li> <a name="index-kpse_002d_003edebug-variable"></a> -<a name="index-debugging-options_002c-in-Kpathsea_002dusing-program"></a> +</li><li> <span id="index-kpse_002d_003edebug-variable"></span> +<span id="index-debugging-options_002c-in-Kpathsea_002dusing-program"></span> Set debugging options. See <a href="#Debugging">Debugging</a>. If your program doesn’t have a debugging option already, you can define one and set <code>kpse->debug</code> to the number that the user supplies (as in Dviljk @@ -3628,18 +3561,18 @@ and Web2c), or you can just omit this altogether (people can always set <code>KPATHSEA_DEBUG</code>). If you do have runtime debugging already, you need to merge Kpathsea’s options with yours (as in Dvipsk and Xdvik). -</li><li> <a name="index-client_005fpath-in-kpse_002d_003eformat_005finfo"></a> -<a name="index-kpse_002d_003eformat_005finfo"></a> -<a name="index-resident_002ec"></a> -<a name="index-config-files_002c-for-Kpathsea_002dusing-programs"></a> +</li><li> <span id="index-client_005fpath-in-kpse_002d_003eformat_005finfo"></span> +<span id="index-kpse_002d_003eformat_005finfo"></span> +<span id="index-resident_002ec"></span> +<span id="index-config-files_002c-for-Kpathsea_002dusing-programs"></span> If your program has its own configuration files that can define search paths, you should assign those paths to the <code>client_path</code> member in the appropriate element of the <code>kpse->format_info</code> array. (This array is indexed by file type; see <samp>tex-file.h</samp>.) See <samp>resident.c</samp> in Dvipsk for an example. -</li><li> <a name="index-kpathsea_005finit_005fprog-1"></a> -<a name="index-proginit_002eh"></a> +</li><li> <span id="index-kpathsea_005finit_005fprog-1"></span> +<span id="index-proginit_002eh"></span> Call <code>kpathsea_init_prog</code> (see <samp>proginit.c</samp>). 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 @@ -3648,7 +3581,7 @@ and other random information. (A search path is always initialized at the first call to find a file of that type; this eliminates much useless work, e.g., initializing the BibTeX search paths in a DVI driver.) -</li><li> <a name="index-kpathsea_005ffind_005ffile-1"></a> +</li><li> <span id="index-kpathsea_005ffind_005ffile-1"></span> The routine to actually find a file of type <var>format</var> is <samp>kpathsea_find_file</samp>. You can call <code>kpathsea_find_file</code> after doing only the first and second of the @@ -3662,7 +3595,7 @@ is <code>kpathsea_find_glyph</code>, defined in resultant filename, because fonts can be found in so many ways. See the documentation in the source. -</li><li> <a name="index-kpathsea_005fopen_005ffile"></a> +</li><li> <span id="index-kpathsea_005fopen_005ffile"></span> To actually open a file, not just return a filename, call <code>kpathsea_open_file</code>. This function takes the name to look up and a Kpathsea file format as arguments, and returns the usual <code>FILE *</code>. @@ -3671,7 +3604,7 @@ necessary (unless the search path specified ‘<samp>!!</samp>’, etc.) words, if you are looking up a VF or some other file that need not exist, don’t use this. -</li><li> <a name="index-kpathsea_005fout_005fname_005fok"></a> +</li><li> <span id="index-kpathsea_005fout_005fname_005fok"></span> TeX can write output files, via the <code>\openout</code> primitive; this opens a security hole vulnerable to Trojan horse attack: an unwitting user could run a TeX program that overwrites, say, <samp>~/.rhosts</samp>. Analogous @@ -3690,25 +3623,25 @@ synonyms for ‘<samp>r</samp>’.) The function <code>kpathsea_out_name filename as second argument, returns <code>true</code> if that filename is acceptable to be opend for output or <code>false</code> otherwise. -</li><li> <a name="index-kpathsea_005fin_005fname_005fok"></a> +</li><li> <span id="index-kpathsea_005fin_005fname_005fok"></span> Similarly, the function <code>kpathsea_in_name_ok</code>, with a filename as second argument, returns <code>true</code> if that filename is acceptable to be opend for input or <code>false</code> otherwise, depending on the value of the configuration variable <code>openin_any</code> (with ‘<samp>a</samp>’ as default). -</li><li> <a name="index-kpathsea_005ffinish"></a> +</li><li> <span id="index-kpathsea_005ffinish"></span> To close the kpathsea library instance you are using, call <code>kpathsea_finish</code>. This function closes any open log files and frees the memory used by the instance. </li></ol> -<a name="index-hash-table-routines"></a> -<a name="index-memory-allocation-routines"></a> -<a name="index-string-routines"></a> -<a name="index-reading-arbitrary_002dlength-lines"></a> -<a name="index-input-lines_002c-reading"></a> -<a name="index-lines_002c-reading-arbitrary_002dlength"></a> +<span id="index-hash-table-routines"></span> +<span id="index-memory-allocation-routines"></span> +<span id="index-string-routines"></span> +<span id="index-reading-arbitrary_002dlength-lines"></span> +<span id="index-input-lines_002c-reading"></span> +<span id="index-lines_002c-reading-arbitrary_002dlength"></span> <p>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 @@ -3716,8 +3649,8 @@ filename-related: default path, tilde, and variable expansion, <code>stat</code> calls, etc. (Perhaps someday I’ll move the former to a separate library.) </p> -<a name="index-c_002d_002a_002eh"></a> -<a name="index-autoconf_002c-recommended"></a> +<span id="index-c_002d_002a_002eh"></span> +<span id="index-autoconf_002c-recommended"></span> <p>The <samp>c-*.h</samp> 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 @@ -3726,13 +3659,11 @@ They are available from <a href="http://www.gnu.org/software">http://www.gnu.org </p> <hr> -<a name="Program_002dspecific-files"></a> -<div class="header"> +<span id="Program_002dspecific-files"></span><div class="header"> <p> Next: <a href="#Programming-with-config-files" accesskey="n" rel="next">Programming with config files</a>, Previous: <a href="#Calling-sequence" accesskey="p" rel="prev">Calling sequence</a>, Up: <a href="#Programming" accesskey="u" rel="up">Programming</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Program_002dspecific-files-1"></a> -<h3 class="section">7.3 Program-specific files</h3> +<span id="Program_002dspecific-files-1"></span><h3 class="section">7.3 Program-specific files</h3> <p>Many programs will need to find some configuration files. Kpathsea contains some support to make it easy to place them in their own @@ -3754,39 +3685,43 @@ mode. </p> <hr> -<a name="Programming-with-config-files"></a> -<div class="header"> +<span id="Programming-with-config-files"></span><div class="header"> <p> Previous: <a href="#Program_002dspecific-files" accesskey="p" rel="prev">Program-specific files</a>, Up: <a href="#Programming" accesskey="u" rel="up">Programming</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Programming-with-config-files-1"></a> -<h3 class="section">7.4 Programming with config files</h3> +<span id="Programming-with-config-files-1"></span><h3 class="section">7.4 Programming with config files</h3> -<a name="index-programming-with-config-files"></a> -<a name="index-config-files_002c-programming-with"></a> +<span id="index-programming-with-config-files"></span> +<span id="index-config-files_002c-programming-with"></span> <p>You can (and probably should) use the same <code>texmf.cnf</code> configuration file that Kpathsea uses for your program. This helps installers by keeping all configuration in one place. </p> -<a name="index-kpathsea_005fvar_005fvalue"></a> -<a name="index-variable_002eh"></a> -<a name="index-shell_005fescape_002c-example-for-code"></a> -<p>To retrieve a value <var>var</var> from config files, the best way is to call -<code>kpathsea_var_value</code> on the string <code><var>var</var></code>. This will look -first for an environment variable <var>var</var>, then a config file value. -The result will be the value found or ‘<samp>NULL</samp>’. This function is -declared in <samp>kpathsea/variable.h</samp>. For an example, see the +<span id="index-kpathsea_005fvar_005fvalue"></span> +<span id="index-variable_002eh"></span> +<span id="index-shell_005fescape_002c-example-for-code"></span> +<p>To retrieve a value for a configuration variable <var>var</var>, the best +way is to call <code>kpathsea_var_value</code> on the string +<code><var>var</var></code>. This will look first for an environment variable +<var>var</var>, then a config file value. The result will be the value +found or ‘<samp>NULL</samp>’. This function is declared in +<samp>kpathsea/variable.h</samp>. For an example, see the <code>shell_escape</code> code in <samp>web2c/lib/texmfmp.c</samp>. </p> -<p>The routine to do variable expansion in the context of a search path (as -opposed to simply retrieving a value) is <code>kpathsea_var_expand</code>, also -declared in <samp>kpathsea/variable.h</samp>. It’s generally only necessary -to set the search path structure components as explained in the previous -section, rather than using this yourself. -</p> -<a name="index-kpathsea_005fcnf_005fget"></a> -<a name="index-cnf_002eh"></a> +<p>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 <code>kpathsea_var_expand</code>, also declared in +<samp>kpathsea/variable.h</samp>. 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 <code>$FOO</code> constructs in the argument to +<code>kpathsea_var_expand</code> are returned literally (<code>"$FOO"</code>), +while undefined <code>${FOO}</code> constructs are expanded to the empty +string. +</p> +<span id="index-kpathsea_005fcnf_005fget"></span> +<span id="index-cnf_002eh"></span> <p>If for some reason you want to retrieve a value <em>only</em> from a config file, not automatically looking for a corresponding environment variable, call <code>kpathsea_cnf_get</code> (declared in <samp>kpathsea/cnf.h</samp>) @@ -3796,19 +3731,17 @@ with the string <var>var</var>. </p> <hr> -<a name="Reporting-bugs"></a> -<div class="header"> +<span id="Reporting-bugs"></span><div class="header"> <p> Next: <a href="#Index" accesskey="n" rel="next">Index</a>, Previous: <a href="#Programming" accesskey="p" rel="prev">Programming</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Reporting-bugs-1"></a> -<h2 class="chapter">8 Reporting bugs</h2> +<span id="Reporting-bugs-1"></span><h2 class="chapter">8 Reporting bugs</h2> -<a name="index-reporting-bugs"></a> -<a name="index-bugs_002c-reporting"></a> +<span id="index-reporting-bugs"></span> +<span id="index-bugs_002c-reporting"></span> -<a name="index-tex_002dk_0040tug_002eorg-_0028bug-address_0029"></a> -<a name="index-bug-address"></a> +<span id="index-tex_002dk_0040tug_002eorg-_0028bug-address_0029"></span> +<span id="index-bug-address"></span> <p>If you have problems or suggestions, please report them to <a href="mailto:tex-k@tug.org">tex-k@tug.org</a> using the bug checklist below. </p> @@ -3817,30 +3750,28 @@ inconsistent behavior, but unclear or incomplete explanations, typos, wrong fonts, … </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Bug-checklist" accesskey="1">Bug checklist</a>:</td><td> </td><td align="left" valign="top">What to include in a good bug report. +<tr><td align="left" valign="top">• <a href="#Bug-checklist" accesskey="1">Bug checklist</a></td><td> </td><td align="left" valign="top">What to include in a good bug report. </td></tr> -<tr><td align="left" valign="top">• <a href="#Mailing-lists" accesskey="2">Mailing lists</a>:</td><td> </td><td align="left" valign="top">Joining the bugs or announcements mailing lists. +<tr><td align="left" valign="top">• <a href="#Mailing-lists" accesskey="2">Mailing lists</a></td><td> </td><td align="left" valign="top">Joining the bugs or announcements mailing lists. </td></tr> -<tr><td align="left" valign="top">• <a href="#Debugging" accesskey="3">Debugging</a>:</td><td> </td><td align="left" valign="top">Analyzing runtime problems. +<tr><td align="left" valign="top">• <a href="#Debugging" accesskey="3">Debugging</a></td><td> </td><td align="left" valign="top">Analyzing runtime problems. </td></tr> -<tr><td align="left" valign="top">• <a href="#Logging" accesskey="4">Logging</a>:</td><td> </td><td align="left" valign="top">Recording searches. +<tr><td align="left" valign="top">• <a href="#Logging" accesskey="4">Logging</a></td><td> </td><td align="left" valign="top">Recording searches. </td></tr> -<tr><td align="left" valign="top">• <a href="#Common-problems" accesskey="5">Common problems</a>:</td><td> </td><td align="left" valign="top">When things go wrong. +<tr><td align="left" valign="top">• <a href="#Common-problems" accesskey="5">Common problems</a></td><td> </td><td align="left" valign="top">When things go wrong. </td></tr> </table> <hr> -<a name="Bug-checklist"></a> -<div class="header"> +<span id="Bug-checklist"></span><div class="header"> <p> Next: <a href="#Mailing-lists" accesskey="n" rel="next">Mailing lists</a>, Up: <a href="#Reporting-bugs" accesskey="u" rel="up">Reporting bugs</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Bug-checklist-1"></a> -<h3 class="section">8.1 Bug checklist</h3> +<span id="Bug-checklist-1"></span><h3 class="section">8.1 Bug checklist</h3> -<a name="index-checklist-for-bug-reports"></a> -<a name="index-bug-checklist"></a> +<span id="index-checklist-for-bug-reports"></span> +<span id="index-bug-checklist"></span> <p>Before reporting a bug, please check below to be sure it isn’t already known (see <a href="#Common-problems">Common problems</a>). @@ -3853,24 +3784,24 @@ information necessary for reproduction. Therefore, to enable investigation, your report should include the following: </p> <ul> -<li> <a name="index-version-numbers_002c-determining"></a> +<li> <span id="index-version-numbers_002c-determining"></span> The version number(s) of the program(s) involved, and of Kpathsea itself. You can get the former by giving a sole option ‘<samp>--version</samp>’ to the program, and the latter by running ‘<samp>kpsewhich --version</samp>’. The <samp>NEWS</samp> and <samp>ChangeLog</samp> files also contain the version number. -</li><li> <a name="index-uname"></a> +</li><li> <span id="index-uname"></span> The hardware, operating system (including version), compiler, and <code>make</code> program you are using (the output of <code>uname -a</code> is a start on the first two, though incomplete). -</li><li> <a name="index-config_002elog"></a> +</li><li> <span id="index-config_002elog"></span> Any options you gave to <code>configure</code>. This is recorded in the <samp>config.status</samp> files. -<a name="index-configuration-bugs"></a> -<a name="index-config_002estatus"></a> +<span id="index-configuration-bugs"></span> +<span id="index-config_002estatus"></span> <p>If you are reporting a bug in ‘<samp>configure</samp>’ 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. @@ -3896,20 +3827,20 @@ 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. -</li><li> <a name="index-context-diff"></a> -<a name="index-sending-patches"></a> -<a name="index-ChangeLog-entry"></a> +</li><li> <span id="index-context-diff"></span> +<span id="index-sending-patches"></span> +<span id="index-ChangeLog-entry"></span> If you are sending a patch (do so if you can!), please do so in the form of a context diff (‘<samp>diff -c</samp>’) 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 <samp>ChangeLog</samp> entry. -</li><li> <a name="index-stack-trace"></a> -<a name="index-debugger"></a> -<a name="index-crashes_002c-reporting"></a> -<a name="index-core-dumps_002c-reporting"></a> -<a name="index-null-pointers_002c-dereferencing"></a> -<a name="index-gdb_002c-recommended"></a> +</li><li> <span id="index-stack-trace"></span> +<span id="index-debugger"></span> +<span id="index-crashes_002c-reporting"></span> +<span id="index-core-dumps_002c-reporting"></span> +<span id="index-null-pointers_002c-dereferencing"></span> +<span id="index-gdb_002c-recommended"></span> 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 (<a href="http://www.gnu.org/software/gdb">http://www.gnu.org/software/gdb</a>). If the @@ -3926,19 +3857,17 @@ diagnosing, or fixing the bug. <hr> -<a name="Mailing-lists"></a> -<div class="header"> +<span id="Mailing-lists"></span><div class="header"> <p> Next: <a href="#Debugging" accesskey="n" rel="next">Debugging</a>, Previous: <a href="#Bug-checklist" accesskey="p" rel="prev">Bug checklist</a>, Up: <a href="#Reporting-bugs" accesskey="u" rel="up">Reporting bugs</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Mailing-lists-1"></a> -<h3 class="section">8.2 Mailing lists</h3> +<span id="Mailing-lists-1"></span><h3 class="section">8.2 Mailing lists</h3> -<a name="index-mailing-lists"></a> -<a name="index-bug-mailing-list"></a> -<a name="index-announcement-mailing-list"></a> +<span id="index-mailing-lists"></span> +<span id="index-bug-mailing-list"></span> +<span id="index-announcement-mailing-list"></span> -<a name="index-tex_002dk_0040tug_002eorg"></a> +<span id="index-tex_002dk_0040tug_002eorg"></span> <p>Web2c and Kpathsea in general are discussed on the mailing list <a href="mailto:tex-k@tug.org">tex-k@tug.org</a>. You can subscribe and peruse the archives on the web <a href="http://lists.tug.org/tex-k">http://lists.tug.org/tex-k</a>. @@ -3954,20 +3883,18 @@ full TeX system or how to use LaTeX, please see </p> <hr> -<a name="Debugging"></a> -<div class="header"> +<span id="Debugging"></span><div class="header"> <p> Next: <a href="#Logging" accesskey="n" rel="next">Logging</a>, Previous: <a href="#Mailing-lists" accesskey="p" rel="prev">Mailing lists</a>, Up: <a href="#Reporting-bugs" accesskey="u" rel="up">Reporting bugs</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Debugging-1"></a> -<h3 class="section">8.3 Debugging</h3> +<span id="Debugging-1"></span><h3 class="section">8.3 Debugging</h3> -<a name="index-debugging"></a> -<a name="index-runtime-debugging"></a> -<a name="index-options-for-debugging"></a> +<span id="index-debugging"></span> +<span id="index-runtime-debugging"></span> +<span id="index-options-for-debugging"></span> -<a name="index-kpse_002d_003edebug"></a> -<a name="index-debug_002eh"></a> +<span id="index-kpse_002d_003edebug"></span> +<span id="index-debug_002eh"></span> <p>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 @@ -3980,38 +3907,38 @@ than those below). It’s best to give the ‘<samp>-d</samp>’ (o first, for maximal output. Dvipsk and Xdvik have additional program-specific debugging options as well. </p> -<a name="index-KPATHSEA_005fDEBUG-1"></a> -<a name="index-kpse_002d_003edebug-1"></a> +<span id="index-KPATHSEA_005fDEBUG-1"></span> +<span id="index-kpse_002d_003edebug-1"></span> <p>You can also set the environment variable <code>KPATHSEA_DEBUG</code>; in this case, you should use the numbers below. If you run the program under a debugger and set the instance variable <code>kpse->debug</code>, also use the numbers below. </p> -<a name="index-_002d1-debugging-value"></a> +<span id="index-_002d1-debugging-value"></span> <p>In any case, by far the simplest value to use is ‘<samp>-1</samp>’, which will turn on all debugging output. This is usually better than guessing which particular values will yield the output you need. </p> -<a name="index-debugging-output"></a> -<a name="index-standard-error-and-debugging-output"></a> +<span id="index-debugging-output"></span> +<span id="index-standard-error-and-debugging-output"></span> <p>Debugging output always goes to standard error, so you can redirect it easily. For example, in Bourne-compatible shells: </p><div class="example"> <pre class="example">dvips -d -1 … 2>/tmp/debug </pre></div> -<a name="index-Kpsewhich_002c-and-debugging"></a> +<span id="index-Kpsewhich_002c-and-debugging"></span> <p>It is sometimes helpful to run the standalone Kpsewhich utility (see <a href="#Invoking-kpsewhich">Invoking kpsewhich</a>), instead of the original program. </p> -<a name="index-numeric-debugging-values"></a> +<span id="index-numeric-debugging-values"></span> <p>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 corresponding numbers. </p> <dl compact="compact"> <dt><code>KPSE_DEBUG_STAT <span class="roman">(1)</span></code> -<a name="index-KPSE_005fDEBUG_005fSTAT-_00281_0029"></a> +<span id="index-KPSE_005fDEBUG_005fSTAT-_00281_0029"></span> </dt> <dd><p>Report ‘<samp>stat</samp>’(2) calls. This is useful for verifying that your directory structure is not forcing Kpathsea to do many additional file @@ -4021,7 +3948,7 @@ nonexistent file that must exist is searched for. </p> </dd> <dt><code>KPSE_DEBUG_HASH <span class="roman">(2)</span></code> -<a name="index-KPSE_005fDEBUG_005fHASH-_00282_0029"></a> +<span id="index-KPSE_005fDEBUG_005fHASH-_00282_0029"></span> </dt> <dd><p>Report lookups in all hash tables: <samp>ls-R</samp> and <samp>aliases</samp> (see <a href="#Filename-database">Filename database</a>); font aliases (see <a href="#Fontmap">Fontmap</a>); and config @@ -4031,9 +3958,9 @@ using <samp>ls-R</samp>. </p> </dd> <dt><code>KPSE_DEBUG_FOPEN <span class="roman">(4)</span></code> -<a name="index-KPSE_005fDEBUG_005fFOPEN-_00284_0029"></a> +<span id="index-KPSE_005fDEBUG_005fFOPEN-_00284_0029"></span> </dt> -<dd><a name="index-fopen_002c-redefined"></a> +<dd><span id="index-fopen_002c-redefined"></span> <p>Report file openings and closings. Especially useful when your 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 @@ -4042,9 +3969,9 @@ redefining ‘<samp>fopen</samp>’ (‘<samp>fclose</samp>’) </p> </dd> <dt><code>KPSE_DEBUG_PATHS <span class="roman">(8)</span></code> -<a name="index-KPSE_005fDEBUG_005fPATHS-_00288_0029"></a> +<span id="index-KPSE_005fDEBUG_005fPATHS-_00288_0029"></span> </dt> -<dd><a name="index-kpse_005fformat_005finfo_005ftype"></a> +<dd><span id="index-kpse_005fformat_005finfo_005ftype"></span> <p>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 <samp>texmf.cnf</samp>, <samp>config.ps</samp>, @@ -4054,7 +3981,7 @@ contents of the <code>kpse_format_info_type</code> structure defined in </p> </dd> <dt><code>KPSE_DEBUG_EXPAND <span class="roman">(16)</span></code> -<a name="index-KPSE_005fDEBUG_005fEXPAND-_002816_0029"></a> +<span id="index-KPSE_005fDEBUG_005fEXPAND-_002816_0029"></span> </dt> <dd><p>Report the directory list corresponding to each path element Kpathsea searches. This is only relevant when Kpathsea searches the disk, since @@ -4062,7 +3989,7 @@ searches. This is only relevant when Kpathsea searches the disk, since </p> </dd> <dt><code>KPSE_DEBUG_SEARCH <span class="roman">(32)</span></code> -<a name="index-KPSE_005fDEBUG_005fSEARCH-_002832_0029"></a> +<span id="index-KPSE_005fDEBUG_005fSEARCH-_002832_0029"></span> </dt> <dd><p>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 @@ -4074,20 +4001,20 @@ what is in your input file. </p> </dd> <dt><code>KPSE_DEBUG_VARS <span class="roman">(64)</span></code> -<a name="index-KPSE_005fDEBUG_005fVARS-_002864_0029"></a> +<span id="index-KPSE_005fDEBUG_005fVARS-_002864_0029"></span> </dt> <dd><p>Report the value of each variable Kpathsea looks up. This is useful for verifying that variables do indeed obtain their correct values. </p> </dd> <dt><code>GSFTOPK_DEBUG <span class="roman">(128)</span></code> -<a name="index-GSFTOPK_005fDEBUG-_0028128_0029"></a> +<span id="index-GSFTOPK_005fDEBUG-_0028128_0029"></span> </dt> <dd><p>Activates debugging printout specific to <code>gsftopk</code> program. </p> </dd> <dt><code>MAKETEX_DEBUG <span class="roman">(512)</span></code> -<a name="index-MAKETEX_005fDEBUG-_0028512_0029"></a> +<span id="index-MAKETEX_005fDEBUG-_0028512_0029"></span> </dt> <dd><p>If you use the optional <code>mktex</code> programs instead of the traditional shell scripts, this will report the name of the site file @@ -4099,16 +4026,16 @@ parameters from <code>mktexnam</code>, filenames added by </p> </dd> <dt><code>MAKETEX_FINE_DEBUG <span class="roman">(1024)</span></code> -<a name="index-MAKETEX_005fFINE_005fDEBUG-_00281024_0029"></a> +<span id="index-MAKETEX_005fFINE_005fDEBUG-_00281024_0029"></span> </dt> <dd><p>When the optional <code>mktex</code> programs are used, this will print additional debugging info from functions internal to these programs. </p></dd> </dl> -<a name="index-kdebug_003a"></a> -<a name="index-hash_005fsummary_005fonly-variable-for-debugging"></a> -<a name="index-hash-table-buckets_002c-printing"></a> +<span id="index-kdebug_003a"></span> +<span id="index-hash_005fsummary_005fonly-variable-for-debugging"></span> +<span id="index-hash-table-buckets_002c-printing"></span> <p>Debugging output from Kpathsea is always written to standard error, and begins with the string ‘<samp>kdebug:</samp>’. (Except for hash table buckets, which just start with the number, but you can only get that output @@ -4117,33 +4044,31 @@ variable in <samp>kpathsea/db.c</samp>.) </p> <hr> -<a name="Logging"></a> -<div class="header"> +<span id="Logging"></span><div class="header"> <p> Next: <a href="#Common-problems" accesskey="n" rel="next">Common problems</a>, Previous: <a href="#Debugging" accesskey="p" rel="prev">Debugging</a>, Up: <a href="#Reporting-bugs" accesskey="u" rel="up">Reporting bugs</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Logging-1"></a> -<h3 class="section">8.4 Logging</h3> +<span id="Logging-1"></span><h3 class="section">8.4 Logging</h3> -<a name="index-log-file"></a> +<span id="index-log-file"></span> -<a name="index-logging-successful-searches"></a> -<a name="index-recording-successful-searches"></a> -<a name="index-usage-patterns_002c-finding"></a> -<a name="index-disk-usage_002c-reducing"></a> +<span id="index-logging-successful-searches"></span> +<span id="index-recording-successful-searches"></span> +<span id="index-usage-patterns_002c-finding"></span> +<span id="index-disk-usage_002c-reducing"></span> <p>Kpathsea can record the time and filename found for each successful search. This may be useful in finding good candidates for deletion when your filesystem is full, or in discovering usage patterns at your site. </p> -<a name="index-TEXMFLOG"></a> +<span id="index-TEXMFLOG"></span> <p>To do this, define the environment or config file variable <code>TEXMFLOG</code>. 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. </p> -<a name="index-epoch_002c-seconds-since"></a> -<a name="index-time-system-call"></a> +<span id="index-epoch_002c-seconds-since"></span> +<span id="index-time-system-call"></span> <p>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 @@ -4163,7 +4088,7 @@ call). The second word is the filename. 774455889 /usr/local/share/texmf/dvips/texc.pro </pre></div> -<a name="index-privacy_002c-semblance-of"></a> +<span id="index-privacy_002c-semblance-of"></span> <p>Only filenames that are absolute are recorded, to preserve some semblance of privacy. </p> @@ -4178,43 +4103,39 @@ else. </p> <hr> -<a name="Common-problems"></a> -<div class="header"> +<span id="Common-problems"></span><div class="header"> <p> Previous: <a href="#Logging" accesskey="p" rel="prev">Logging</a>, Up: <a href="#Reporting-bugs" accesskey="u" rel="up">Reporting bugs</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Common-problems-1"></a> -<h3 class="section">8.5 Common problems</h3> +<span id="Common-problems-1"></span><h3 class="section">8.5 Common problems</h3> -<a name="index-common-problems"></a> -<a name="index-problems_002c-common"></a> -<a name="index-FAQ_002c-Kpathsea"></a> +<span id="index-common-problems"></span> +<span id="index-problems_002c-common"></span> +<span id="index-FAQ_002c-Kpathsea"></span> <p>Here are some common problems with configuration, compilation, linking, execution, … </p> <table class="menu" border="0" cellspacing="0"> -<tr><td align="left" valign="top">• <a href="#Unable-to-find-files" accesskey="1">Unable to find files</a>:</td><td> </td><td align="left" valign="top">If your program can’t find fonts (or whatever). +<tr><td align="left" valign="top">• <a href="#Unable-to-find-files" accesskey="1">Unable to find files</a></td><td> </td><td align="left" valign="top">If your program can’t find fonts (or whatever). </td></tr> -<tr><td align="left" valign="top">• <a href="#Slow-path-searching" accesskey="2">Slow path searching</a>:</td><td> </td><td align="left" valign="top">If it takes forever to find anything. +<tr><td align="left" valign="top">• <a href="#Slow-path-searching" accesskey="2">Slow path searching</a></td><td> </td><td align="left" valign="top">If it takes forever to find anything. </td></tr> -<tr><td align="left" valign="top">• <a href="#Unable-to-generate-fonts" accesskey="3">Unable to generate fonts</a>:</td><td> </td><td align="left" valign="top">If mktexpk fails. +<tr><td align="left" valign="top">• <a href="#Unable-to-generate-fonts" accesskey="3">Unable to generate fonts</a></td><td> </td><td align="left" valign="top">If mktexpk fails. </td></tr> -<tr><td align="left" valign="top">• <a href="#TeX-or-Metafont-failing" accesskey="4">TeX or Metafont failing</a>:</td><td> </td><td align="left" valign="top">Likely compiler bugs. +<tr><td align="left" valign="top">• <a href="#TeX-or-Metafont-failing" accesskey="4">TeX or Metafont failing</a></td><td> </td><td align="left" valign="top">Likely compiler bugs. </td></tr> </table> <hr> -<a name="Unable-to-find-files"></a> -<div class="header"> +<span id="Unable-to-find-files"></span><div class="header"> <p> Next: <a href="#Slow-path-searching" accesskey="n" rel="next">Slow path searching</a>, Up: <a href="#Common-problems" accesskey="u" rel="up">Common problems</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Unable-to-find-files-1"></a> -<h4 class="subsection">8.5.1 Unable to find files</h4> +<span id="Unable-to-find-files-1"></span><h4 class="subsection">8.5.1 Unable to find files</h4> -<a name="index-unable-to-find-files"></a> -<a name="index-files_002c-unable-to-find"></a> +<span id="index-unable-to-find-files"></span> +<span id="index-files_002c-unable-to-find"></span> <p>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 @@ -4225,16 +4146,16 @@ debugging options helpful. See <a href="#Debugging">Debugging</a>. fonts and input files are distributed separately from the programs. See <a href="#unixtex_002eftp">unixtex.ftp</a>. -</li><li> <a name="index-_002fetc_002fprofile"></a> -<a name="index-environment-variables_002c-old"></a> +</li><li> <span id="index-_002fetc_002fprofile"></span> +<span id="index-environment-variables_002c-old"></span> 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 <samp>texmf.cnf</samp> (see <a href="#Supported-file-formats">Supported file formats</a>). System <samp>/etc/profile</samp> or other files such may be the culprit. -</li><li> <a name="index-symbolic-links-not-found"></a> -<a name="index-leaf-directories-wrongly-guessed"></a> +</li><li> <span id="index-symbolic-links-not-found"></span> +<span id="index-leaf-directories-wrongly-guessed"></span> Your files reside in a directory that is only pointed to via a symbolic link, in a leaf directory and is not listed in <samp>ls-R</samp>. @@ -4267,17 +4188,15 @@ fonts by hand with Metafont, or to grab them from a CTAN site <hr> -<a name="Slow-path-searching"></a> -<div class="header"> +<span id="Slow-path-searching"></span><div class="header"> <p> Next: <a href="#Unable-to-generate-fonts" accesskey="n" rel="next">Unable to generate fonts</a>, Previous: <a href="#Unable-to-find-files" accesskey="p" rel="prev">Unable to find files</a>, Up: <a href="#Common-problems" accesskey="u" rel="up">Common problems</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Slow-path-searching-1"></a> -<h4 class="subsection">8.5.2 Slow path searching</h4> +<span id="Slow-path-searching-1"></span><h4 class="subsection">8.5.2 Slow path searching</h4> -<a name="index-excessive-startup-time"></a> -<a name="index-slow-startup-time"></a> -<a name="index-startup-time_002c-excessive"></a> +<span id="index-excessive-startup-time"></span> +<span id="index-slow-startup-time"></span> +<span id="index-startup-time_002c-excessive"></span> <p>If your program takes an excessively long time to find fonts or other input files, but does eventually succeed, here are some possible culprits: @@ -4306,16 +4225,14 @@ precisely when the disk or network is being pounded. See <a href="#Debugging">D </p> <hr> -<a name="Unable-to-generate-fonts"></a> -<div class="header"> +<span id="Unable-to-generate-fonts"></span><div class="header"> <p> Next: <a href="#TeX-or-Metafont-failing" accesskey="n" rel="next">TeX or Metafont failing</a>, Previous: <a href="#Slow-path-searching" accesskey="p" rel="prev">Slow path searching</a>, Up: <a href="#Common-problems" accesskey="u" rel="up">Common problems</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Unable-to-generate-fonts-1"></a> -<h4 class="subsection">8.5.3 Unable to generate fonts</h4> +<span id="Unable-to-generate-fonts-1"></span><h4 class="subsection">8.5.3 Unable to generate fonts</h4> -<a name="index-unable-to-generate-fonts"></a> -<a name="index-font-generation-failures"></a> +<span id="index-unable-to-generate-fonts"></span> +<span id="index-font-generation-failures"></span> <p>Metafont outputs fonts in bitmap format, tuned for a particular device at a particular resolution, in order to allow for the @@ -4323,7 +4240,7 @@ highest-possible 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. </p> -<a name="index-mktexpk-can_0027t-guess-mode"></a> +<span id="index-mktexpk-can_0027t-guess-mode"></span> <p>If <code>mktexpk</code> runs, but fails with this error: </p><div class="example"> <pre class="example">mktexpk: Can't guess mode for <var>nnn</var> dpi devices. @@ -4333,7 +4250,7 @@ mktexpk: Use a config file to specify the mode, or update me. specifying the resolution, as in <code>-D 360</code>, is not enough. </p> <p>You can specify the mode name with the <code>-mode</code> option on the -Dvips command line, or in a Dvips configuration file (see <a href="http://tug.org/texinfohtml/dvips.html#Config-files">Config +Dvips command line, or in a Dvips configuration file (see <a href="https://tug.org/texinfohtml/dvips.html#Config-files">Config files</a> in <cite>Dvips</cite>), such as <samp>config.ps</samp> in your document directory, <samp>~/.dvipsrc</samp> in your home directory, or in a system directory (again named <samp>config.ps</samp>). (Other drivers use other @@ -4346,8 +4263,8 @@ a configuration file: M lqmed </pre></div> -<a name="index-Metafont-using-the-wrong-device"></a> -<a name="index-device_002c-wrong"></a> +<span id="index-Metafont-using-the-wrong-device"></span> +<span id="index-device_002c-wrong"></span> <p>If Metafont runs, but generates fonts at the wrong resolution or for the wrong device, most likely <code>mktexpk</code>’s built-in guess for the mode is wrong, and you should override it as above. @@ -4355,11 +4272,11 @@ mode is wrong, and you should override it as above. <p>See <a href="http://ctan.org/pkg/modes">http://ctan.org/pkg/modes</a> for a list of resolutions and mode names for most devices (additional submissions are welcome). </p> -<a name="index-_002e2602gf"></a> -<a name="index-2602gf"></a> -<a name="index-Metafont-making-too_002dlarge-fonts"></a> -<a name="index-proof-mode"></a> -<a name="index-online-Metafont-display_002c-spurious"></a> +<span id="index-_002e2602gf"></span> +<span id="index-2602gf"></span> +<span id="index-Metafont-making-too_002dlarge-fonts"></span> +<span id="index-proof-mode"></span> +<span id="index-online-Metafont-display_002c-spurious"></span> <p>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 @@ -4372,67 +4289,59 @@ a file <samp>modes.mf</samp>, run the following command (assuming Unix): <pre class="example">inimf "plain; input modes; dump" </pre></div> -<p><a name="index-plain_002ebase"></a> +<p><span id="index-plain_002ebase"></span> Then copy the <samp>plain.base</samp> file from the current directory to where the base files are stored on your system (<samp>/usr/local/share/texmf/web2c</samp> by default), and make a link (either hard or soft) from <samp>plain.base</samp> to <samp>mf.base</samp> in that directory. -See <a href="http://tug.org/texinfohtml/web2c.html#inimf-invocation">inimf invocation</a> in <cite>Web2c</cite>. +See <a href="https://tug.org/texinfohtml/web2c.html#inimf-invocation">inimf invocation</a> in <cite>Web2c</cite>. </p> -<a name="index-Metafont-installation"></a> +<span id="index-Metafont-installation"></span> <p>If <code>mf</code> is a command not found at all by <code>mktexpk</code>, then you need to install Metafont (see <a href="#unixtex_002eftp">unixtex.ftp</a>). </p> <hr> -<a name="TeX-or-Metafont-failing"></a> -<div class="header"> +<span id="TeX-or-Metafont-failing"></span><div class="header"> <p> Previous: <a href="#Unable-to-generate-fonts" accesskey="p" rel="prev">Unable to generate fonts</a>, Up: <a href="#Common-problems" accesskey="u" rel="up">Common problems</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="TeX-or-Metafont-failing-1"></a> -<h4 class="subsection">8.5.4 TeX or Metafont failing</h4> +<span id="TeX-or-Metafont-failing-1"></span><h4 class="subsection">8.5.4 TeX or Metafont failing</h4> -<a name="index-TeX-failures"></a> -<a name="index-Metafont-failures"></a> -<a name="index-compiler-bugs"></a> +<span id="index-TeX-failures"></span> +<span id="index-Metafont-failures"></span> +<span id="index-compiler-bugs"></span> <p>If TeX or Metafont get a segmentation fault or otherwise fail while running a normal input file, the problem is usually a compiler bug (unlikely as that may sound). Even if the trip and trap tests are passed, problems may lurk. Optimization occasionally causes trouble in programs other than TeX and Metafont themselves, too. </p> -<p>Insufficient swap space may also cause core dumps or other erratic -behavior. -</p> -<a name="index-optimization-caveat"></a> +<span id="index-optimization-caveat"></span> <p>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. </p> -<a name="index-GNU-C-compiler-bugs"></a> -<a name="index-system-C-compiler-bugs"></a> +<span id="index-GNU-C-compiler-bugs"></span> +<span id="index-system-C-compiler-bugs"></span> <p>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 also -recommend reporting a bug to the GCC mailing list; see <a href="http://gcc.gnu.org/onlinedocs/gcc/Bugs.html#Bugs">Bugs</a> in <cite>Using and Porting GNU CC</cite>. +recommend reporting a bug to the GCC mailing list; see <a href="https://gcc.gnu.org/onlinedocs/gcc/Bugs.html#Bugs">Bugs</a> in <cite>Using and Porting GNU CC</cite>. </p> -<a name="index-compiler-bugs_002c-finding"></a> +<span id="index-compiler-bugs_002c-finding"></span> <p>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. Things are -not helped by all-too-common bugs in the debugger itself. Good luck. +through TeX’s (or whatever program’s) data structures. Good luck. </p> <hr> -<a name="Index"></a> -<div class="header"> +<span id="Index"></span><div class="header"> <p> Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> [<a href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="#Index" title="Index" rel="index">Index</a>]</p> </div> -<a name="Index-1"></a> -<h2 class="unnumbered">Index</h2> +<span id="Index-1"></span><h2 class="unnumbered">Index</h2> <table><tr><th valign="top">Jump to: </th><td><a class="summary-letter" href="#Index_cp_symbol-1"><b>!</b></a> @@ -4509,13 +4418,13 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <table class="index-cp" border="0"> <tr><td></td><th align="left">Index Entry</th><td> </td><th align="left"> Section</th></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-1">!</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-1">!</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_0021_0021-in-path-specifications"><code>!! <span class="roman">in path specifications</span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-2">$</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-2">$</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_0024-expansion"><code>$ <span class="roman">expansion</span></code></a>:</td><td> </td><td valign="top"><a href="#Variable-expansion">Variable expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-3">-</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-3">-</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dall"><code>--all</code></a>:</td><td> </td><td valign="top"><a href="#Path-searching-options">Path searching options</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dcasefold_002dsearch"><code>--casefold-search</code></a>:</td><td> </td><td valign="top"><a href="#Path-searching-options">Path searching options</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dcolor_003dtty"><code>--color=tty</code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> @@ -4540,6 +4449,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-_002d_002dsafe_002dout_002dname_003dname"><code>--safe-out-name=<var>name</var></code></a>:</td><td> </td><td valign="top"><a href="#Auxiliary-tasks">Auxiliary tasks</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dshow_002dpath_003dname"><code>--show-path=<var>name</var></code></a>:</td><td> </td><td valign="top"><a href="#Auxiliary-tasks">Auxiliary tasks</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dsubdir_003dstring"><code>--subdir=<var>string</var></code></a>:</td><td> </td><td valign="top"><a href="#Path-searching-options">Path searching options</a></td></tr> +<tr><td></td><td valign="top"><a href="#index-_002d_002dvar_002dbrace_002dvalue_003dvariable"><code>--var-brace-value=<var>variable</var></code></a>:</td><td> </td><td valign="top"><a href="#Auxiliary-tasks">Auxiliary tasks</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dvar_002dvalue_003dvariable"><code>--var-value=<var>variable</var></code></a>:</td><td> </td><td valign="top"><a href="#Auxiliary-tasks">Auxiliary tasks</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dversion"><code>--version</code></a>:</td><td> </td><td valign="top"><a href="#Standard-options">Standard options</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002d_002dwith_002dmktextex_002ddefault"><code>--with-mktextex-default</code></a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> @@ -4555,7 +4465,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-_002diname_002c-find-predicate"><code>-iname<span class="roman">, find predicate</span></code></a>:</td><td> </td><td valign="top"><a href="#Casefolding-examples">Casefolding examples</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002dL-option-to-ls"><code>-L <span class="roman">option to <code>ls</code></span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-4">.</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-4">.</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_002e-directories_002c-ignored"><code>. <span class="roman">directories, ignored</span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002e-files"><code>. <span class="roman">files</span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002e2602gf"><code>.2602gf</code></a>:</td><td> </td><td valign="top"><a href="#Unable-to-generate-fonts">Unable to generate fonts</a></td></tr> @@ -4609,7 +4519,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-_002eweb"><code>.web</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002eweb-1"><code>.web</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-5">/</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-5">/</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_002f-may-not-be-_002f"><code>/ <span class="roman">may not be /</span></code></a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002f_002c-trailing-in-home-directory"><code>/<span class="roman">, trailing in home directory</span></code></a>:</td><td> </td><td valign="top"><a href="#Tilde-expansion">Tilde expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002f_002f"><code>//</code></a>:</td><td> </td><td valign="top"><a href="#Subdirectory-expansion">Subdirectory expansion</a></td></tr> @@ -4617,28 +4527,28 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-_002fetc_002fprofile-and-aliases"><code>/etc/profile <span class="roman">and aliases</span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_002fvar_002ftmp_002ftexfonts"><code>/var/tmp/texfonts</code></a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-6">2</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-6">2</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-2602gf"><code>2602gf</code></a>:</td><td> </td><td valign="top"><a href="#Unable-to-generate-fonts">Unable to generate fonts</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-7">8</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-7">8</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-8_002e3-filenames_002c-using">8.3 filenames, using</a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-8">:</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-8">:</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_003a-may-not-be-_003a"><code>: <span class="roman">may not be :</span></code></a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_003a_003a-expansion"><code>:: <span class="roman">expansion</span></code></a>:</td><td> </td><td valign="top"><a href="#Default-expansion">Default expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-9">\</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-9">\</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_005c_002c-line-continuation-in-texmf_002ecnf"><code>\<span class="roman">, line continuation in <samp>texmf.cnf</samp></span></code></a>:</td><td> </td><td valign="top"><a href="#Config-files">Config files</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_005copenin"><code>\openin</code></a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-_005cspecial_002c-suppressing-warnings-about"><code>\special<span class="roman">, suppressing warnings about</span></code></a>:</td><td> </td><td valign="top"><a href="#Suppressing-warnings">Suppressing warnings</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-10">{</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-10">{</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_007b-expansion"><code>{ <span class="roman">expansion</span></code></a>:</td><td> </td><td valign="top"><a href="#Brace-expansion">Brace expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_symbol-11">~</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_symbol-11">~</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-_007e-expansion"><code>~ <span class="roman">expansion</span></code></a>:</td><td> </td><td valign="top"><a href="#Tilde-expansion">Tilde expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-A">A</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-A">A</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-absolute-filenames">absolute filenames</a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-access-system-call"><code>access <span class="roman">system call</span></code></a>:</td><td> </td><td valign="top"><a href="#Casefolding-examples">Casefolding examples</a></td></tr> <tr><td></td><td valign="top"><a href="#index-access-warnings">access warnings</a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> @@ -4659,7 +4569,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-automounter_002c-and-ls_002dR">automounter, and <samp>ls-R</samp></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td></td><td valign="top"><a href="#index-auxiliary-tasks">auxiliary tasks</a>:</td><td> </td><td valign="top"><a href="#Auxiliary-tasks">Auxiliary tasks</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-B">B</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-B">B</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-Bach_002c-Johann-Sebastian">Bach, Johann Sebastian</a>:</td><td> </td><td valign="top"><a href="#Default-expansion">Default expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-backslash_002dnewline">backslash-newline</a>:</td><td> </td><td valign="top"><a href="#Config-files">Config files</a></td></tr> <tr><td></td><td valign="top"><a href="#index-basic-glyph-lookup">basic glyph lookup</a>:</td><td> </td><td valign="top"><a href="#Basic-glyph-lookup">Basic glyph lookup</a></td></tr> @@ -4677,7 +4587,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-bug-mailing-list">bug mailing list</a>:</td><td> </td><td valign="top"><a href="#Mailing-lists">Mailing lists</a></td></tr> <tr><td></td><td valign="top"><a href="#index-bugs_002c-reporting">bugs, reporting</a>:</td><td> </td><td valign="top"><a href="#Reporting-bugs">Reporting bugs</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-C">C</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-C">C</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-c_002d_002a_002eh"><code>c-*.h</code></a>:</td><td> </td><td valign="top"><a href="#Calling-sequence">Calling sequence</a></td></tr> <tr><td></td><td valign="top"><a href="#index-c_002dauto_002eh"><code>c-auto.h</code></a>:</td><td> </td><td valign="top"><a href="#Programming-overview">Programming overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-cache-of-fonts_002c-local">cache of fonts, local</a>:</td><td> </td><td valign="top"><a href="#Security">Security</a></td></tr> @@ -4724,7 +4634,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-crashes_002c-reporting">crashes, reporting</a>:</td><td> </td><td valign="top"><a href="#Bug-checklist">Bug checklist</a></td></tr> <tr><td></td><td valign="top"><a href="#index-CWEBINPUTS"><code>CWEBINPUTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-D">D</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-D">D</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-database-search">database search</a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-database_002c-for-filenames">database, for filenames</a>:</td><td> </td><td valign="top"><a href="#Filename-database">Filename database</a></td></tr> <tr><td></td><td valign="top"><a href="#index-database_002c-format-of">database, format of</a>:</td><td> </td><td valign="top"><a href="#Database-format">Database format</a></td></tr> @@ -4758,7 +4668,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-DVIPSSIZES"><code>DVIPSSIZES</code></a>:</td><td> </td><td valign="top"><a href="#Fallback-font">Fallback font</a></td></tr> <tr><td></td><td valign="top"><a href="#index-dynamic-creation-of-files">dynamic creation of files</a>:</td><td> </td><td valign="top"><a href="#mktex-scripts">mktex scripts</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-E">E</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-E">E</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-EC-fonts_002c-and-dynamic-source-creation">EC fonts, and dynamic source creation</a>:</td><td> </td><td valign="top"><a href="#mktex-scripts">mktex scripts</a></td></tr> <tr><td></td><td valign="top"><a href="#index-elt_002ddirs_002ec"><code>elt-dirs.c</code></a>:</td><td> </td><td valign="top"><a href="#Subdirectory-expansion">Subdirectory expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-elt_002ddirs_002ec-1"><code>elt-dirs.c</code></a>:</td><td> </td><td valign="top"><a href="#Subdirectory-expansion">Subdirectory expansion</a></td></tr> @@ -4786,7 +4696,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-externally_002dbuilt-filename-database">externally-built filename database</a>:</td><td> </td><td valign="top"><a href="#Filename-database">Filename database</a></td></tr> <tr><td></td><td valign="top"><a href="#index-extra-colons">extra colons</a>:</td><td> </td><td valign="top"><a href="#Default-expansion">Default expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-F">F</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-F">F</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-failed-mktex_2026-script-invocation">failed <code>mktex…</code> script invocation</a>:</td><td> </td><td valign="top"><a href="#mktex-script-names">mktex script names</a></td></tr> <tr><td></td><td valign="top"><a href="#index-fallback-font">fallback font</a>:</td><td> </td><td valign="top"><a href="#Fallback-font">Fallback font</a></td></tr> <tr><td></td><td valign="top"><a href="#index-fallback-resolutions">fallback resolutions</a>:</td><td> </td><td valign="top"><a href="#Fallback-font">Fallback font</a></td></tr> @@ -4826,7 +4736,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-ftp_002etug_002eorg"><code>ftp.tug.org</code></a>:</td><td> </td><td valign="top"><a href="#unixtex_002eftp">unixtex.ftp</a></td></tr> <tr><td></td><td valign="top"><a href="#index-fundamental-purpose-of-Kpathsea">fundamental purpose of Kpathsea</a>:</td><td> </td><td valign="top"><a href="#Introduction">Introduction</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-G">G</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-G">G</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-gdb_002c-recommended"><code>gdb<span class="roman">, recommended</span></code></a>:</td><td> </td><td valign="top"><a href="#Bug-checklist">Bug checklist</a></td></tr> <tr><td></td><td valign="top"><a href="#index-gf"><code>gf</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-GFFONTS"><code>GFFONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> @@ -4841,7 +4751,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-group_002dwritable-directories">group-writable directories</a>:</td><td> </td><td valign="top"><a href="#Security">Security</a></td></tr> <tr><td></td><td valign="top"><a href="#index-GSFTOPK_005fDEBUG-_0028128_0029"><code>GSFTOPK_DEBUG <span class="roman">(128)</span></code></a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-H">H</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-H">H</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-hash-table-buckets_002c-printing">hash table buckets, printing</a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> <tr><td></td><td valign="top"><a href="#index-hash-table-routines">hash table routines</a>:</td><td> </td><td valign="top"><a href="#Calling-sequence">Calling sequence</a></td></tr> <tr><td></td><td valign="top"><a href="#index-hash_005fsummary_005fonly-variable-for-debugging"><code>hash_summary_only <span class="roman">variable for debugging</span></code></a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> @@ -4850,7 +4760,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-home-directories-in-paths">home directories in paths</a>:</td><td> </td><td valign="top"><a href="#Tilde-expansion">Tilde expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-HOME_002c-as-_007e-expansion"><code>HOME<span class="roman">, as ~ expansion</span></code></a>:</td><td> </td><td valign="top"><a href="#Tilde-expansion">Tilde expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-I">I</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-I">I</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-identifiers_002c-characters-valid-in">identifiers, characters valid in</a>:</td><td> </td><td valign="top"><a href="#Config-files">Config files</a></td></tr> <tr><td></td><td valign="top"><a href="#index-include-fontmap-directive"><code>include <span class="roman">fontmap directive</span></code></a>:</td><td> </td><td valign="top"><a href="#Fontmap">Fontmap</a></td></tr> <tr><td></td><td valign="top"><a href="#index-INDEXSTYLE"><code>INDEXSTYLE</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> @@ -4859,7 +4769,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-interface_002c-not-frozen">interface, not frozen</a>:</td><td> </td><td valign="top"><a href="#Introduction">Introduction</a></td></tr> <tr><td></td><td valign="top"><a href="#index-introduction">introduction</a>:</td><td> </td><td valign="top"><a href="#Introduction">Introduction</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-K">K</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-K">K</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-kdebug_003a">‘<samp>kdebug:</samp>’</a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> <tr><td></td><td valign="top"><a href="#index-kdefault_002ec"><code>kdefault.c</code></a>:</td><td> </td><td valign="top"><a href="#Default-expansion">Default expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-Knuth_002c-Donald-E_002e">Knuth, Donald E.</a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> @@ -4902,7 +4812,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-KPSE_005fDOT-expansion"><code>KPSE_DOT <span class="roman">expansion</span></code></a>:</td><td> </td><td valign="top"><a href="#KPSE_005fDOT-expansion">KPSE_DOT expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-kpse_005fformat_005finfo_005ftype"><code>kpse_format_info_type</code></a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-L">L</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-L">L</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-last_002dresort-font">last-resort font</a>:</td><td> </td><td valign="top"><a href="#Fallback-font">Fallback font</a></td></tr> <tr><td></td><td valign="top"><a href="#index-lcircle10"><code>lcircle10</code></a>:</td><td> </td><td valign="top"><a href="#Fontmap">Fontmap</a></td></tr> <tr><td></td><td valign="top"><a href="#index-leading-colons">leading colons</a>:</td><td> </td><td valign="top"><a href="#Default-expansion">Default expansion</a></td></tr> @@ -4921,7 +4831,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-ls_002dR-database-file"><code>ls-R <span class="roman">database file</span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td></td><td valign="top"><a href="#index-ls_002dR_002c-simplest-build"><code>ls-R<span class="roman">, simplest build</span></code></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-M">M</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-M">M</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-Mac-filesystem_002c-case_002dinsensitive">Mac filesystem, case-insensitive</a>:</td><td> </td><td valign="top"><a href="#Casefolding-rationale">Casefolding rationale</a></td></tr> <tr><td></td><td valign="top"><a href="#index-MacKenzie_002c-David">MacKenzie, David</a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> <tr><td></td><td valign="top"><a href="#index-MacKenzie_002c-David-1">MacKenzie, David</a>:</td><td> </td><td valign="top"><a href="#Subdirectory-expansion">Subdirectory expansion</a></td></tr> @@ -4972,7 +4882,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-multiple-TeX-hierarchies">multiple TeX hierarchies</a>:</td><td> </td><td valign="top"><a href="#Brace-expansion">Brace expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-must-exist">must exist</a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-N">N</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-N">N</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-names-for-mktex-scripts">names for <samp>mktex</samp> scripts</a>:</td><td> </td><td valign="top"><a href="#mktex-script-names">mktex script names</a></td></tr> <tr><td></td><td valign="top"><a href="#index-Neumann_002c-Gustaf">Neumann, Gustaf</a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> <tr><td></td><td valign="top"><a href="#index-NFS-and-ls_002dR">NFS and <samp>ls-R</samp></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> @@ -4982,7 +4892,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-null-pointers_002c-dereferencing">null pointers, dereferencing</a>:</td><td> </td><td valign="top"><a href="#Bug-checklist">Bug checklist</a></td></tr> <tr><td></td><td valign="top"><a href="#index-numeric-debugging-values">numeric debugging values</a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-O">O</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-O">O</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-obtaining-TeX">obtaining TeX</a>:</td><td> </td><td valign="top"><a href="#unixtex_002eftp">unixtex.ftp</a></td></tr> <tr><td></td><td valign="top"><a href="#index-OCPINPUTS"><code>OCPINPUTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-OFMFONTS"><code>OFMFONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> @@ -4996,7 +4906,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-OVFFONTS"><code>OVFFONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-OVPFONTS"><code>OVPFONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-P">P</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-P">P</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-path-expansion">path expansion</a>:</td><td> </td><td valign="top"><a href="#Path-expansion">Path expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-path-searching">path searching</a>:</td><td> </td><td valign="top"><a href="#Path-searching">Path searching</a></td></tr> <tr><td></td><td valign="top"><a href="#index-path-searching-options">path searching options</a>:</td><td> </td><td valign="top"><a href="#Path-searching-options">Path searching options</a></td></tr> @@ -5026,10 +4936,10 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-PSHEADERS"><code>PSHEADERS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-pxp-Pascal-preprocessor"><code>pxp <span class="roman">Pascal preprocessor</span></code></a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-Q">Q</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-Q">Q</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-quoting-variable-values">quoting variable values</a>:</td><td> </td><td valign="top"><a href="#Variable-expansion">Variable expansion</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-R">R</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-R">R</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-rationale-for-casefolding-fallback">rationale for casefolding fallback</a>:</td><td> </td><td valign="top"><a href="#Casefolding-rationale">Casefolding rationale</a></td></tr> <tr><td></td><td valign="top"><a href="#index-re_002dentrant-API">re-entrant API</a>:</td><td> </td><td valign="top"><a href="#Programming-overview">Programming overview</a></td></tr> <tr><td></td><td valign="top"><a href="#index-readable"><code>readable</code></a>:</td><td> </td><td valign="top"><a href="#Suppressing-warnings">Suppressing warnings</a></td></tr> @@ -5048,7 +4958,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-runtime-configuration-files">runtime configuration files</a>:</td><td> </td><td valign="top"><a href="#Config-files">Config files</a></td></tr> <tr><td></td><td valign="top"><a href="#index-runtime-debugging">runtime debugging</a>:</td><td> </td><td valign="top"><a href="#Debugging">Debugging</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-S">S</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-S">S</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-Sauter-fonts_002c-and-dynamic-source-creation">Sauter fonts, and dynamic source creation</a>:</td><td> </td><td valign="top"><a href="#mktex-scripts">mktex scripts</a></td></tr> <tr><td></td><td valign="top"><a href="#index-scripts-for-file-creation">scripts for file creation</a>:</td><td> </td><td valign="top"><a href="#mktex-scripts">mktex scripts</a></td></tr> <tr><td></td><td valign="top"><a href="#index-search-path_002c-defined">search path, defined</a>:</td><td> </td><td valign="top"><a href="#Searching-overview">Searching overview</a></td></tr> @@ -5099,7 +5009,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-system-C-compiler-bugs">system C compiler bugs</a>:</td><td> </td><td valign="top"><a href="#TeX-or-Metafont-failing">TeX or Metafont failing</a></td></tr> <tr><td></td><td valign="top"><a href="#index-system_002ddependent-casefolding-behavior">system-dependent casefolding behavior</a>:</td><td> </td><td valign="top"><a href="#Casefolding-rationale">Casefolding rationale</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-T">T</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-T">T</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-T1FONTS"><code>T1FONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-T1INPUTS"><code>T1INPUTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-T42FONTS"><code>T42FONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> @@ -5177,7 +5087,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-typeface-directory_002c-omitting">typeface directory, omitting</a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td></td><td valign="top"><a href="#index-typeface-directory_002c-omitting-1">typeface directory, omitting</a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-U">U</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-U">U</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-unable-to-find-files">unable to find files</a>:</td><td> </td><td valign="top"><a href="#Unable-to-find-files">Unable to find files</a></td></tr> <tr><td></td><td valign="top"><a href="#index-unable-to-generate-fonts">unable to generate fonts</a>:</td><td> </td><td valign="top"><a href="#Unable-to-generate-fonts">Unable to generate fonts</a></td></tr> <tr><td></td><td valign="top"><a href="#index-uname"><code>uname</code></a>:</td><td> </td><td valign="top"><a href="#Bug-checklist">Bug checklist</a></td></tr> @@ -5191,7 +5101,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-USE_005fTEXMFVAR"><code>USE_TEXMFVAR</code></a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td></td><td valign="top"><a href="#index-USE_005fVARTEXFONTS"><code>USE_VARTEXFONTS</code></a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-V">V</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-V">V</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-varfonts"><code>varfonts</code></a>:</td><td> </td><td valign="top"><a href="#mktex-configuration">mktex configuration</a></td></tr> <tr><td></td><td valign="top"><a href="#index-variable-expansion">variable expansion</a>:</td><td> </td><td valign="top"><a href="#Variable-expansion">Variable expansion</a></td></tr> <tr><td></td><td valign="top"><a href="#index-variable_002ec"><code>variable.c</code></a>:</td><td> </td><td valign="top"><a href="#Variable-expansion">Variable expansion</a></td></tr> @@ -5203,7 +5113,7 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-VFFONTS"><code>VFFONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-Vojta_002c-Paul">Vojta, Paul</a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-W">W</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-W">W</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-Walsh_002c-Norman">Walsh, Norman</a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> <tr><td></td><td valign="top"><a href="#index-warning-about-unusable-ls_002dR">warning about unusable <samp>ls-R</samp></a>:</td><td> </td><td valign="top"><a href="#ls_002dR">ls-R</a></td></tr> <tr><td></td><td valign="top"><a href="#index-warning_002c-about-missing-texmf_002ecnf">warning, about missing <samp>texmf.cnf</samp></a>:</td><td> </td><td valign="top"><a href="#Config-files">Config files</a></td></tr> @@ -5217,13 +5127,13 @@ Previous: <a href="#Reporting-bugs" accesskey="p" rel="prev">Reporting bugs</a>, <tr><td></td><td valign="top"><a href="#index-Windows-and-casefolding">Windows and casefolding</a>:</td><td> </td><td valign="top"><a href="#Casefolding-rationale">Casefolding rationale</a></td></tr> <tr><td></td><td valign="top"><a href="#index-www_002etug_002eorg"><code>www.tug.org</code></a>:</td><td> </td><td valign="top"><a href="#unixtex_002eftp">unixtex.ftp</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-X">X</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-X">X</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-XDvi"><code>XDvi</code></a>:</td><td> </td><td valign="top"><a href="#Specially_002drecognized-files">Specially-recognized files</a></td></tr> <tr><td></td><td valign="top"><a href="#index-XDVIFONTS"><code>XDVIFONTS</code></a>:</td><td> </td><td valign="top"><a href="#Supported-file-formats">Supported file formats</a></td></tr> <tr><td></td><td valign="top"><a href="#index-XDVIMAKEPK"><code>XDVIMAKEPK</code></a>:</td><td> </td><td valign="top"><a href="#mktex-script-names">mktex script names</a></td></tr> <tr><td></td><td valign="top"><a href="#index-XDVISIZES"><code>XDVISIZES</code></a>:</td><td> </td><td valign="top"><a href="#Fallback-font">Fallback font</a></td></tr> <tr><td colspan="4"> <hr></td></tr> -<tr><th><a name="Index_cp_letter-Z">Z</a></th><td></td><td></td></tr> +<tr><th id="Index_cp_letter-Z">Z</th><td></td><td></td></tr> <tr><td></td><td valign="top"><a href="#index-zuhn_002c-david">zuhn, david</a>:</td><td> </td><td valign="top"><a href="#History">History</a></td></tr> <tr><td colspan="4"> <hr></td></tr> </table> |