From e54beb75906e627b501ca07df9bc40432ee31a92 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Thu, 22 Apr 2010 16:21:31 +0000 Subject: avoid over/underfull boxes git-svn-id: svn://tug.org/texlive/trunk@17961 c570f23f-e606-0410-a88d-b1316a301751 --- Build/source/texk/kpathsea/ChangeLog | 5 ++ Build/source/texk/kpathsea/doc/bugs.texi | 3 +- Build/source/texk/kpathsea/doc/kpathsea.info | 104 +++++++++++++-------------- Build/source/texk/kpathsea/doc/kpathsea.texi | 24 +++---- 4 files changed, 71 insertions(+), 65 deletions(-) diff --git a/Build/source/texk/kpathsea/ChangeLog b/Build/source/texk/kpathsea/ChangeLog index fbace46ee67..f867e03d164 100644 --- a/Build/source/texk/kpathsea/ChangeLog +++ b/Build/source/texk/kpathsea/ChangeLog @@ -1,3 +1,8 @@ +2010-04-22 Karl Berry + + * doc/kpathsea.texi, + * doc/bugs.texi: Avoid over/underfull boxes. + 2010-04-19 Peter Breitenlohner * texmf.cnf (max_strings.pbibtex): New defn. diff --git a/Build/source/texk/kpathsea/doc/bugs.texi b/Build/source/texk/kpathsea/doc/bugs.texi index edbbb4285f1..43460f9d57b 100644 --- a/Build/source/texk/kpathsea/doc/bugs.texi +++ b/Build/source/texk/kpathsea/doc/bugs.texi @@ -617,7 +617,8 @@ which looks something like this: prompt$ ./configure @dots{} creating Makefile -sed: 1: "\\@@^ac_include make/pat ...": \ can not be used as a string delimiter +sed: 1: "\\@@^ac_include make/pat ...": \ can not + be used as a string delimiter @end example So far as I know, the bug here is in @code{/bin/sh} on these systems. I diff --git a/Build/source/texk/kpathsea/doc/kpathsea.info b/Build/source/texk/kpathsea/doc/kpathsea.info index 6c2a9885016..c8c68550638 100644 --- a/Build/source/texk/kpathsea/doc/kpathsea.info +++ b/Build/source/texk/kpathsea/doc/kpathsea.info @@ -1890,7 +1890,8 @@ looks something like this: prompt$ ./configure ... creating Makefile - sed: 1: "\\@^ac_include make/pat ...": \ can not be used as a string delimiter + sed: 1: "\\@^ac_include make/pat ...": \ can not + be used as a string delimiter So far as I know, the bug here is in `/bin/sh' on these systems. I don't have access to a machine running any of them, so if someone can @@ -2844,9 +2845,8 @@ filename, and returns the first file found. one you are interested in. We only match at the end because a site might happen to install TeX - in `/some/coincidental/pkg1/path/', and we wouldn't want - `texmf-dist/scripts/pkg2/' to match that when searching for - `/pkg1'. + in `/some/coincidental/pkg1/path/', and we wouldn't want to match + `texmf-dist/scripts/pkg2/' that when searching for `/pkg1'.  @@ -3171,7 +3171,7 @@ environment variables with an underscore, e.g., `TEXINPUTS_latex' `texmfscripts' (Architecture-independent executables distributed in the texmf - tree) `TEXMFSCRIPTS'. + trees) `TEXMFSCRIPTS'. `texpool' (TeX program strings, *note pooltype invocation: (web2c)pooltype @@ -3274,9 +3274,9 @@ tried; the difference is the order in which they are tried. *already* have an extension. A name without an extension (e.g., `tex story') will always have an extension added first. - This algorithm is implemented in the routine `kpathsea_find_file' in -`kpathsea/tex-file.c'. You can watch it in action with the debugging -options (*note Debugging::). + This algorithm is implemented in the function `kpathsea_find_file' +in the source file `kpathsea/tex-file.c'. You can watch it in action +with the debugging options (*note Debugging::).  File: kpathsea.info, Node: Glyph lookup, Next: Suppressing warnings, Prev: File lookup, Up: TeX support @@ -3668,12 +3668,12 @@ directories. The Standard TeX directory structure (*note Introduction: (tds)Top.), specifies that such files should go into a subdirectory named after the program, like `texmf/ttf2pk'. - Two special formats, `kpse_program_text_format' and -`kpse_program_binary_format' exist, which use `.:$TEXMF/PROGRAM//' as -their compiled-in search path. To override this default, you can use -the variable `PROGRAMINPUTS' in the environment and/or `texmf.cnf'. -That is to say, the name of the variable is constructed by converting -the name of the program to upper case, and appending `INPUTS'. + Two formats, `kpse_program_text_format' and +`kpse_program_binary_format', use `.:$TEXMF/PROGRAM//' as their +compiled-in search path. To override this default, you can use the +variable `PROGRAMINPUTS' in the environment and/or `texmf.cnf'. That +is to say, the name of the variable is constructed by converting the +name of the program to upper case, and appending `INPUTS'. The only difference between these two formats is whether `kpathsea_open_file' will open the files it finds in text or binary @@ -4899,43 +4899,43 @@ Node: Slow path searching73496 Node: Unable to generate fonts74873 Node: TeX or Metafont failing77382 Node: Empty Makefiles79261 -Node: XtStrings80491 -Node: dlopen81327 -Node: ShellWidgetClass82145 -Node: Pointer combination warnings83777 -Node: Path searching84166 -Node: Searching overview84813 -Node: Path sources88209 -Node: Config files89280 -Node: Path expansion92925 -Node: Default expansion93874 -Node: Variable expansion95944 -Node: Tilde expansion97347 -Node: Brace expansion98327 -Node: KPSE_DOT expansion99432 -Node: Subdirectory expansion99945 -Node: Filename database102296 -Node: ls-R103350 -Node: Filename aliases106244 -Node: Database format107422 -Node: Invoking kpsewhich108435 -Node: Path searching options109381 -Node: Specially-recognized files117550 -Node: Auxiliary tasks118906 -Node: Standard options120731 -Node: TeX support121087 -Node: Supported file formats122378 -Node: File lookup129894 -Node: Glyph lookup131626 -Node: Basic glyph lookup132750 -Node: Fontmap133629 -Node: Fallback font136246 -Node: Suppressing warnings137159 -Node: Programming138264 -Node: Programming overview138777 -Node: Calling sequence141471 -Node: Program-specific files147994 -Node: Programming with config files149036 -Node: Index150348 +Node: XtStrings80498 +Node: dlopen81334 +Node: ShellWidgetClass82152 +Node: Pointer combination warnings83784 +Node: Path searching84173 +Node: Searching overview84820 +Node: Path sources88216 +Node: Config files89287 +Node: Path expansion92932 +Node: Default expansion93881 +Node: Variable expansion95951 +Node: Tilde expansion97354 +Node: Brace expansion98334 +Node: KPSE_DOT expansion99439 +Node: Subdirectory expansion99952 +Node: Filename database102303 +Node: ls-R103357 +Node: Filename aliases106251 +Node: Database format107429 +Node: Invoking kpsewhich108442 +Node: Path searching options109388 +Node: Specially-recognized files117552 +Node: Auxiliary tasks118908 +Node: Standard options120733 +Node: TeX support121089 +Node: Supported file formats122380 +Node: File lookup129897 +Node: Glyph lookup131646 +Node: Basic glyph lookup132770 +Node: Fontmap133649 +Node: Fallback font136266 +Node: Suppressing warnings137179 +Node: Programming138284 +Node: Programming overview138797 +Node: Calling sequence141491 +Node: Program-specific files148014 +Node: Programming with config files149037 +Node: Index150349  End Tag Table diff --git a/Build/source/texk/kpathsea/doc/kpathsea.texi b/Build/source/texk/kpathsea/doc/kpathsea.texi index f19ca9ffcff..a386b5f7980 100644 --- a/Build/source/texk/kpathsea/doc/kpathsea.texi +++ b/Build/source/texk/kpathsea/doc/kpathsea.texi @@ -1313,9 +1313,8 @@ By specifying, say, @samp{--subdir=/pkg1}, you can be sure of getting the one you are interested in. We only match at the end because a site might happen to install @TeX{} -in @file{/some/coincidental/pkg1/path/}, and we wouldn't want -@file{texmf-dist/scripts/pkg2/} to match that when searching for -@samp{/pkg1}. +in @file{/some/coincidental/pkg1/path/}, and we wouldn't want to match +@file{texmf-dist/scripts/pkg2/} that when searching for @samp{/pkg1}. @end table @@ -1829,7 +1828,7 @@ dynamic creation program: @code{mktextex}. @item texmfscripts @vindex TEXMFSCRIPTS -(Architecture-independent executables distributed in the texmf tree) +(Architecture-independent executables distributed in the texmf trees) @code{TEXMFSCRIPTS}. @item texpool @@ -1990,7 +1989,8 @@ which *already* have an extension. A name without an extension (e.g., @flindex tex-file.c @findex kpathsea_find_file -This algorithm is implemented in the routine @code{kpathsea_find_file} in +This algorithm is implemented in the function +@code{kpathsea_find_file} in the source file @file{kpathsea/tex-file.c}. You can watch it in action with the debugging options (@pxref{Debugging}). @@ -2481,13 +2481,13 @@ Introduction, tds, A Directory Structure for @TeX{} files}), specifies that such files should go into a subdirectory named after the program, like @samp{texmf/ttf2pk}. -Two special formats, @samp{kpse_program_text_format} and -@samp{kpse_program_binary_format} exist, which use -@code{.:$TEXMF/@var{program}//} as their compiled-in search path. To -override this default, you can use the variable -@code{@var{PROGRAM}INPUTS} in the environment and/or @samp{texmf.cnf}. -That is to say, the name of the variable is constructed by converting -the name of the program to upper case, and appending @code{INPUTS}. +Two formats, @samp{kpse_program_text_format} and +@samp{kpse_program_binary_format}, use @code{.:$TEXMF/@var{program}//} +as their compiled-in search path. To override this default, you can +use the variable @code{@var{PROGRAM}INPUTS} in the environment and/or +@samp{texmf.cnf}. That is to say, the name of the variable is +constructed by converting the name of the program to upper case, and +appending @code{INPUTS}. The only difference between these two formats is whether @code{kpathsea_open_file} will open the files it finds in text or binary -- cgit v1.2.3