Neils Walet wrote:
>I have pinned down the problem a bit more -- it occurs in latex2html.config.
>I have set Web2C to 0 (I do have Web2C, but the kpsewhich command
>doesn't work this way on my machine). The offending lines are
>
>if ($Web2C) {
> chop ($TEXINPUTS =
> `kpsewhich -progname=latex -expand-var \\\$TEXINPUTS`);
>} else {
># $TEXINPUTS = "${dd}";
> $TEXINPUTS = ":";
>}
OK. I can explain the problem completely now.
I've changed the default use of $TEXINPUTS
and $ENV{'TEXINPUTS'} (which is the environment variable).
You are supposed to set $TEXINPUTS in an -init file,
rather than set TEXINPUTS for the environment.
Alternatively if you have input directories that you use frequently,
in both LaTeX and LaTeX2HTML then you might set *BOTH* the $TEXINPUTS
in latex2html.config *and* TEXINPUTS for your environment.
The point is that TEXINPUTS is for LaTeX inputs, some of which may be
quite incompatible with LaTeX2HTML , which must use $TEXINPUTS .
Of course you are free to live dangerously by setting $TEXINPUTS from
$ENV{'TEXINPUTS'} in the .config file, if you wish.
The default is no longer to search $ENV{'TEXINPUTS'} automatically.
In particular the Web2C option, using kpsewhich is dangerous, IMHO,
since it may cause weird input files to be used, pulled from totally
inappropriate places in the texmf tree.
e.g.
if you mis-spell the name of an input, asking for say example.tex
when you really meant example1.tex ,
then you could get any one of several example.tex documents
from within the texmf hierarchy, describing some totally unrelated
feature of a LaTeX package or BiBTeX or dvips or something else.
I don't think this is sensible behaviour.
The inconvenience of having to set 2 variables, if that is the way
you choose to work, is minor in comparison to the utter confusion
that could occur when a document contains completely the wrong input.
Surely it is best for LaTeX2HTML to stop and complain that it couldn't
find the right one.
(If you didn't check the HTML output thoroughly, you might not even
notice that it had happened. )
># This line helps LaTeX2HTML to recognize your adaption everywhere.
>$ENV{'TEXINPUTS'} = $TEXINPUTS unless defined $ENV{'TEXINPUTS'};
>
>which set $TEXINPUT to ":" rather than my value! Using web2c
>and my (tetex 0.4) kpsexpand in the chop line:
> `kpsexpand \\\$TEXINPUTS`);
>seems to solve the problem.
It may well do --- nevertheless I'd prefer you set $TEXINPUTS
within .latex2html-init for the local working directory,
than to use 'TEXINPUTS' this way.
Hope this helps,
Ross Moore
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ross Moore email: [EMAIL PROTECTED]
Mathematics Department phone: +612 9850 8955
Macquarie University fax: +612 9850 8114
Sydney, NSW 2109 office: E7A-419
Australia WWW: http://www-math.mpce.mq.edu.au/~ross/
***************************
for the best in (La)TeX-nical typesetting and Web page production
join the TeX Users Group (TUG) --- browse at http://www.tug.org
<[EMAIL PROTECTED]>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
