Ross Moore writes:
> Here is another of my mammoth emails.
Wow! For the moment, I'll just persue one topic from this post,
because I'm having problems with it today.
> At 5:42 PM -0400 4/24/98, Fred L. Drake wrote:
> > Is there a way to tell l2h that latex created it's temporary files
> >someplace other than the directory where l2h is run from?
> > What I want to do is this: I have a whole bunch of .tex files in a
> >directory, and then have the subdirs that l2h creates *and* separate
> >directories for running latex for both letter and a4 paper. If my
>
> You should be able to adjust the $TEXINPUTS variable to include
> the appropriate directories.
>
> > Is there a way to tell l2h "look over there" to get the *.aux files
> >and anything else it uses that latex creates? A command line switch
> >would be great.
>
> There is already the -external_file switch for this purpose;
> but it can only be used for one file.
This doesn't seem to be working. Here's what I have:
./*.tex a bunch of document source files
./perl/*.perl extra stuff for l2h
.texinputs/*.{cls,sty} extra stuff for latex
./paper-letter/*.??? stuff generated by latex,
including *.aux and friends.
./lib/ l2h output dir for lib.tex
If I call l2h like this (from ./):
TEXINPUTS=texinputs:paper-letter: latex2html \
-init_file ./perl/l2hinit.perl -external_file \
`TEXINPUTS=texinputs:paper-letter: kpsewhich lib.aux` \
lib.tex
or like this (again, from ./):
TEXINPUTS=texinputs:paper-letter: latex2html \
-init_file ./perl/l2hinit.perl lib.tex
I get the following error just before 'Translating ..':
Cannot open lib.aux No such file or directory
and this at the end:
The lib.aux file was not found, so sections will not be numbered
and cross-references will be shown as icons.
I wouldn't be surprised if I need to do something different, which
is fine as long as I can do it in a Makefile. ;-) Frankly, my
suspision is that a path is get searched at the wrong time;
`TEXINPUTS=texinputs:paper-letter: kpsewhich lib.aux` expands to
"paper-letter/lib.aux". If this isn't absolutized before l2h switches
to the output directory, I'd expect it not to be found. But it seems
like l2h should be responsible for absolutizing the path. (It also
seems like it should be a fatal error if -external_file is specified
on the command line and doesn't exist; the messages and continuation
of processing indicate that that's not the case.)
I'd really appreciate any assistance in this.
-Fred
--
Fred L. Drake, Jr.
[EMAIL PROTECTED]
Corporation for National Research Initiatives
1895 Preston White Drive Reston, VA 20191
