Forum archive 2000-2006

Zbigniew Fiedorowicz - trouble updating latex2html

Zbigniew Fiedorowicz - trouble updating latex2html

by Arnold Pizer -
Number of replies: 0
inactiveTopictrouble updating latex2html topic started 6/21/2001; 7:13:49 PM
last post 6/22/2001; 12:53:48 PM
userZbigniew Fiedorowicz - trouble updating latex2html  blueArrow
6/21/2001; 7:13:49 PM (reads: 1109, responses: 2)
Our system administrator installed a new version of latex2html, v2000 beta something on our server (running Linux 6.2). Unfortunately it doesn't work, even when invoked manually. No image files are produced. The first error message comes from pnmcrop -- something about an illegal seek. Unfortunately the debug option doesn't seem to work either: we can't save the temporary postscript files.

Has anyone run into this problem?

Zig Fiedorowicz

<| Post or View Comments |>

userThomas R. Shemanske - Re: trouble updating latex2html  blueArrow
6/22/2001; 10:26:17 AM (reads: 1321, responses: 0)
I have installed LaTeX2HTML Version 2K.1beta (1.48) on our WeBWorK server.

There were a number of problems I had to resolve. One of the first is that somewhere along the line I was forced to use pngs instead of gifs. I believe this was due to a change in the netpbm package.

See the latex2html.config file option @IMAGE_TYPES = qw(png gif); $IMAGE_TYPE = $IMAGE_TYPES[0];

Then once latex2html runs, there will be an issue with black borders on the images, but Pizer has posted how to patch the pstoimg file used by latex2html to correct this defect.

Other than that, it might help to have the versions of latex2html and netpbm

Good Luck


<| Post or View Comments |>

userArnold K. Pizer - Re: trouble updating latex2html  blueArrow
6/22/2001; 12:53:48 PM (reads: 1340, responses: 0)
For general information on LaTeX2HTML try

There is a mail list-serve devoted to LaTeX2HTML ( which is archived at . This may be the best place to look for help.

If you have LaTeX2HTML running from the command line and it is still not working with WeBWorK, check the WeBWorK error log (.../webwork/system/logs/error_log) and also possibly Apache's error log for information.

If necessary you can follow the following advice from the readme.install file.

For debugging errors in output (postscript,latex2html, etc), you can set $debugON=1 in .../cgi/cgiscripts/ and $debug=1 in ../courseScripts/ Doing so will save intermediate temporary files (log files, TeX files, etc) that may help in finding the error. Don't leave these set to 1. If you do, you will find your file system filling up.

<| Post or View Comments |>