Ross:

   Thanks for the reply. I have tried the same file on my machine
at work and it wors fine. The only difference is I use 98beta6
at work instead of beta8, and the debian tetex instead of the 
TUG CDROM LIve 3 version of tex used at home. I don't think
these are possible causes, because I have tried to change
to other versions of latex2html without success. The configuration
I have at home does not appear to produce any math images at all
for any .tex files. I tried latex the images.tex and it went without
a hitch and the images and there. Somewhere in the process of conversion
from .ps to .gif the problem seems to crop up. 

   What more diagnostics should I do?

Thanks and best regards.

Sebastian

Sebastian Canagaratna,
Department of Chemistry
Ohio NOrthern University
Ada, OH 45810.


> > 
> >  Hi: This is a folllow up to an earlier post. I have
> >      narrowed down my problem.
> > 
> >      latex2html runs without any complaint, but netscape does
> > now show any image. The .ps images are formed correctly, since
> > I can view them. Running with -debug gives
> >  
> >    in one of the lines:
> > 
> >    pnmcrop: EOF/ read error reading magic number.
>  
> This happens when the image fed to  pnmcrop  is too small
> in one of its dimensions;
>  e.g. 0 x 0   pnmcrop  hates this.
>       1 x <num>
>      <num> x 1  
>   
>  in fact  X x Y  where either X or Y is less than 4 , I think.
> 
> Since pnmcrop can be called several times, to remove the 
> 'cropping bars' it is possible to crop away an image completely
> and feed an empty (or very thin) image to the next call
>  --- hence the error message.
> 
> 
> > This is a recent problem. I have had this working fine before.
> > I am using latex2html98.2beta8 and gs-aladdin, netpbm 1994, 
> > installation was done with install-test , and there were
> > no complaings. 
> > 
> >   Has anybody come across this problem before? Is this a latex2html
> > problem or is the problem somewhere else?
> 
> You say the images are all created -- good.
> After using  -debug  have a look at  images.dvi 
> using xdvi or some other dvi-viewer.
> 
> Are all the images correctly surrounded by cropping-bars ?
> (i.e. a L-shaped structure partially framing the contents.)
> 
> Is the image always located with the top-left corner
> at the top-left of the page (roughly an inch in and down).
> 
> If not, are you using 'twoside' for alternate margins ?
> 
> Are any images blank ?
> (This will really upset things with 'twoside'.)
> Does images.log give any clue as to where images may have
> got out of synchronisation ?
> 
>  
> Hope this helps,
> 
>       Ross Moore
> 
> 
> 
> 

Reply via email to