>
> index.tex -> index.html
> jtpack.tex -> jtpack.html
> emacs.tex -> emacs.html
No problem. Simply prepend a prefix using -prefix <prefix>
Look at how the LaTeX2HTML manual uses 6 (or more) separate prefixes,
one for each chapter.
Here is what the v97.1 manual says:
-prefix <filename-prefix>
Same as setting: $PREFIX = "<filename-prefix>";
The <filename-prefix> will be prepended to all .gif, .pl and
.html files produced, except for the top-level .html file; it may
include a (relative) directory path. This will enable multiple products of
LATEX2HTML to peacefully coexist in the same directory. However, do
not attempt to simultaneously run multiple instances of LATEX2HTML
using the same output directory, else various temporary files will
overwrite each other.
e.g. with -prefix P :
Nodes come out as Pnode1.html, Pnode2.html
Images become: Pimg001.gif, Pimg002.html, etc.
Similarly all the .pl files use the prefix.
> What I'm worried about are clashes with things like labels.pl and
> internals.pl (not even sure what the latter is for) since i'm using
> -no_subdir. Right now I think only one of the .tex files uses a \ref,
> so it's not a problem, but what if several of them did?
> If the answer is simply "don't do that", that's fine. Just thought
> I'd check.
Run with it. ;-)
In your other message you asked about something like Format dumps,
using LaTeX2HTML. In principle this should be possible, since Perl
allows the current state of a job to be *dump*'d.
I've often thought about this. It would allow LaTeX2HTML to start
*much* faster.
The difficulty is in choosing the correct place within the code to
perform the dump, and being able to start a new job from that point.
This really means reorganising the internal code
to maximise the usefulness of such a feature.
This is a difficult problem, since handles to open files cannot
be preserved within a dump.
With the current strategy, I think there is little to gain,
since texexpand is called early. Only after this is it known
which packages and styles are to be used.
But texexpand has also written files specific to the job.
So you can't have a dump *after* texexpand, but having one *before*
won't catch the information you want to include.
I'd love to supervise a student to research this aspect of Perl
with LaTeX2HTML.
Hope this helps,
Ross Moore
