Here are some curable symptoms:
#!/usr/local/bin/perl
to
: # *-*-perl-*-*
eval 'exec perl -S $0 "$@"'
if $running_under_some_shell;
Also, make sure that the files pstogif, texexpand and latex2html are executable, and if necessary use the Unix chmod command to make them executable.
$DONT_INCLUDE = "$DONT_INCLUDE" . ":<style file name>"; 1; # This must be the last line
Another reason why LaTeX2HTML might stop is that the LaTeX source file itself contains raw TeX commands. In this case you may put such commands inside a latexonly environment.
You can check which version of Perl you are using by invoking Perl with the -v option.
While you wait for your technical support people to upgrade Perl you could try invoking Perl from within LaTeX2HTML with the -d (debug) option. Then, when LaTeX2HTML starts, it will immediately fall into the Perl debugger. To continue just press c <CR>.
As a last resort you may consider increasing the virtual memory (swap space) of your machine. As an indication of what you might be able to do on your machine, a very long book (about 1000 printed pages) required about 24MB of RAM and over 150MB of swap space to convert on a local Sun Sparc ELC running SunOS 4.1.3.
\~{}.
Alternatively it is possible to use something like
\htmladdnormallink{mylink}
{
or
\htmladdnormallink{mylink}
{http://host/\%7Eme/path/file.html}
Warning: Some browsers may not be able to interpret the %7E
as a ``tilde'' character.
In general the macro handling mechanism is inefficient and very fragile. Avoid using macros if possible.
\item[{[nested [angle [brackets] are ok]]}]
If you notice any strange side-effects from previous runs of LaTeX2HTML try using the option -no_reuse and choose (d) when prompted. This will clear any intermediate files generated during previous runs. Note that this option will disable to image reuse mechanism.
\begin{figure}
\epsffile{<postscript file name>}
\end{figure}
Another reason why this might happen is that your shell
environment variable
TEXINPUTS is undefined. This is not always
fatal but if you have problems you can use full
pathnames for included postscript files (even when the postscript
files are in the same directory as the LaTeX source file).
Alternatively try setting TEXINPUTS to ".::".
With some TeX and LaTeX installations setting TEXINPUTS to
".::" may cause problems in the normal operation of LaTeX.
If you get errors such as LaTeX complaining that it can no longer find
any style files then you must set TEXINPUTS to
"<path to your LaTeX installation>:."
if you want to use both LaTeX and LaTeX2HTML.
Another reason why this may happen is that by default the dvips program
reverses the postscript pages it generates. If your dvips
program
behaves in this way try changing the line
$DVIPS = "dvips";
to
$DVIPS = "dvips -r0";
in the file latex2html.config.
1; # This is the last lineThis is a Perl quirk...
Of course you also have to make sure that LaTeX knows where the html.sty
file is, either by putting it in the same place as the other style files on
your system, or by changing your TEXINPUTS shell environment variable
.
\tt fixed-width font.
\begin{something}
nothing here
\end{something}
default font.
When processed by LaTeX, the effect of the tt command is
delimited
by the beginning of the environment ``something'' so that ``default font'' will
appear in the default font. But LaTeX2HTML will not recognize
``something'' as a delimiter and ``default font'' will appear in the
wrong
font.
To avoid this problem until it is fixed you may delimit the scope of
some
commands explicitly using {}'s i.e.
{\tt fixed-width font}.
\begin{something}
nothing here
\end{something}
default font.
With earlier versions of LaTeX2HTML you can fix it by
replacing the file pstoppm.ps in the
LaTeX2HTML directory with a newer one that accompanies
Ghostscript 3.X. Alterhatively you can avoid using
pstoppm.ps
by changing the way GS is invoked in the file pstogif,
using something like
open (GS, "|$GS -q -sDEVICE=ppmraw -sOutputFile=$base.ppm $base.ps");
% image-test.tex
\documentstyle{article}
\begin{document}
Some text followed by \fbox{some more text in a box}.
\end{document}
You should see something like:
This is LaTeX2HTML Version (Wed Dec 1 1993) by Nikos Drakos, Computer Based Learning Unit, University of Leeds. OPENING /usr/cblelca/nikos/scripts/tex2html/tests/image-test.tex Reading .... Translating ...0/1.....1/1...... Generating images using latex ... This is TeX, C Version 3.14t3 (12222_images.tex LaTeX Version 2.09 <7 Dec 1989> Generating postscript images using dvips ... This is dvips 5.521 Copyright 1986, 1993 Radical Eye Software
' TeX output 1993.12.03:1050' -> 12222_image (-> 12222_image001) <tex.pro>[1] Initializing... done. Ghostscript 2.6.1 (5/28/93) Copyright (C) 1990-1993 Aladdin Enterprises, Menlo Park, CA. All rights reserved. Ghostscript comes with NO WARRANTY: see the file COPYING for details. GS>GS>Writing 12222_image001.ppm GS>pnmcrop: cropping 119 rows off the top pnmcrop: cropping 961 rows off the bottom pnmcrop: cropping 208 cols off the left pnmcrop: cropping 484 cols off the right Doing section links ..... Done.
If there is a problem somewhere during the conversion from postscript to GIF you can try to do it manually so that you can find out where the problem is. Here is one way to do it (Please use the pstoppm3.ps file instead of pstoppm.ps if your version of ghostscript is later than 3.0):
cblelca% latex image-test.tex This is TeX, C Version 3.14t3 (image-test.tex LaTeX Version 2.09 <7 Dec 1989> (/usr/TeX/tex.lib/inputs//paper.sty Document Style `paper' <28 Nov 89>. (/usr/TeX/tex.lib/inputs//pap11.sty) (/usr/TeX/tex.lib/inputs//doublespace.sty) (/usr/TeX/tex.lib/inputs//smaller.sty)) (/usr/TeX/tex.lib/inputs//psfig.sty psfig/tex 1.9 ) No file image-test.aux. [1] (image-test.aux) ) Output written on image-test.dvi (1 page, 652 bytes). Transcript written on image-test.log. cblelca% dvips -o image-test.ps image-test.dvi
This is dvips 5.519 Copyright 1986, 1993 Radical Eye Software ' TeX output 1993.11.12:1412' -> image-test.ps <tex.pro>. [1] cblelca% gs -dNODISPLAY pstoppm.ps Initializing... done. Ghostscript 2.6.1 (5/28/93) Copyright (C) 1990-1993 Aladdin Enterprises, Menlo Park, CA. All rights reserved. Ghostscript comes with NO WARRANTY: see the file COPYING for details. GS>(image-test) ppm1run Writing image-test.ppm GS>quit cblelca% pnmcrop image-test.ppm >image-test.crop.ppm pnmcrop: cropping 61 rows off the top pnmcrop: cropping 110 rows off the bottom pnmcrop: cropping 72 cols off the left pnmcrop: cropping 72 cols off the right cblelca% ppmtogif image-test.crop.ppm >image-test.gif
If you get into a mess try running LaTeX2HTML with the options -no_reuse and -no_images eg
cblipca% latex2html -no_reuse -no_images test.tex This is LaTeX2HTML Version 95.1 (Tue Nov 29 1994) by Nikos Drakos, Computer Based Learning Unit, University of Leeds. OPENING /tmp_mnt/home/cblelca/nikos/tmp/test.tex Cannot create directory /usr/cblelca/nikos/tmp/test: File exists (r) Reuse the images in the old directory OR (d) *** DELETE *** /usr/cblelca/nikos/tmp/test AND ITS CONTENTS OR (q) Quit ? :d Reading ... Processing macros ....+. Reading test.aux ...................... Translating ...0/1........1/1..... Writing image file ... Doing section links ..... *********** WARNINGS *********** If you are having problems displaying the correct images with Mosaic, try selecting "Flush Image Cache" from "Options" in the menu-bar and then reload the HTML file. Done.
Then try to have a look in the file images.tex (as described earlier) and perhaps fix it. Once you are happy that images.tex is OK run LaTeX2HTML again with the option -images_only.
The options no_reuse, no_images and images_only are available with LaTeX2HTML version 0.7 or later.
Some problems in displaying the correct inlined images, may be due to the image caching mechanisms of your browser. With some browsers a simple ``Reload Current Document'' will be enough to refresh the images but with others (eg Mosaic) you may need to request for the cache to be refreshed. With Mosaic try selecting "Flush Image Cache" from "Options" in the menu-bar and then reload the HTML file.