It looks like part of the patch I recently sent in made it into
98.1p4 (the part with a bug in it), but not some other parts.
In process_ext_file(), my patch added a loop that ran over
$TEXINPUTS if the file had not already been found. The loop used
"break" to exit, and should have used "last". I can't find anything
about a break statement in the camel book (other than last), so I have
no idea why it didn't break with a syntax error.
Another part of the patch made deal_with_texinputs() absolutize the
parts of $TEXINPUTS; this is still needed but isn't in 98.1p4. I
still think this or some other path "math" needs to be done within
latex2html since it's changing directories. I am using the following
code in my init file to work around this:
------------------------------------------------------------------------
sub absolutize_path{
my $path = @_[0];
my $npath = '';
foreach $dir (split $envkey, $path) {
$npath .= make_directory_absolute($dir) . $envkey;
}
$npath =~ s/$envkey$//;
$npath;
}
# This is done because latex2html doesn't do this for us, but does change the
# directory out from under us.
if (defined $ENV{'TEXINPUTS'}) {
$ENV{'TEXINPUTS'} = absolutize_path($ENV{'TEXINPUTS'});
}
------------------------------------------------------------------------
The third part of my patch removed the getcwd() function from
Override.pm; this is still necessary. For now I have to use:
------------------------------------------------------------------------
package Override;
use Cwd qw(getcwd);
package main;
------------------------------------------------------------------------
at the top of my init file to get things to work. I asked if there
was any reason not to remove the version defined there and allow the
(already imported) version from Cwd take over. Since there wasn't any
response to my query, I'd like to ask again: is there any reason to
define getcwd() in Override.pm? The version defined there doesn't
work:
$ pwd
/home/fdrake/projects/python/Python-1-5/Doc
$ mkdir temp
$ perl -e 'print `pwd`; chdir('\''temp'\''); print `pwd`;'
/home/fdrake/projects/python/Python-1-5/Doc
/home/fdrake/projects/python/Python-1-5/Doc
I don't know how important it is for others here, but running a
released version of l2h is fairly important for me since I'm releasing
not only the formatted documents but also the process itself. I want
to be able to say "use latex2html 99.1, available at <url>". I have
to provide an initfile, but I don't like redefining a lot of stuff
from the main latex2html script there; the maintenance is
problematic. The file
http://cdc-server.cdc.informatik.tu-darmstadt.de/~latex2html/readme
indicates that there is some cooperative development going on and a
CVS repository is available; is sending a message to this list really
a good way to deal with latex2html problems? I'm presuming at least
Ross is one of the developers using the CVS repo; is it still active?
-Fred
--
Fred L. Drake, Jr.
[EMAIL PROTECTED]
Corporation for National Research Initiatives
1895 Preston White Drive Reston, VA 20191
