🚀 go-pugleaf

In article <Brr3As.J8z@ux1.cso.uiuc.edu> hudson@ux1.cso.uiuc.edu (John Hudson) writes:

   When I include a large postscript file TeX (LaTeX) complains . . .

   Unable to read an entire line---bufsize=3000
   Please ask a wizard to enlarge me.

   What need to be done?  As the source was tossed after compilation, to rebuild
   I will need a new copy of the source.  Does the lastest version build with
   a larger buffer?  What's a reasonable size?

This type of problem typically has one of two root causes.  

The first is that the PS file was transferred between platforms WITHOUT using
end-of-line translation. Macintosh for example uses `return' as line
terminator, while PC's use `linefeed+return', while Unix uses `linefeed' etc
So your TeX macros looking for the BBoX comment try to read the whole file
in one gulp.  TeX implementations typically read input using fgets, which
stops only when it gets to a line-terminator.  Usually the input buffer
is 3000 bytes.  You can't fix this by making a `larger' TeX.  Just make sure
the PostScript file is broken into lines using whatever line terminator your
machine believes in...

The second common reason (well much less common actually) for this sort of
problem is that you have an EPSF file with a preview in PICT (Macintosh) or
TIFF (IBM PC) format.  These have binary headers, and if you are unlucky,
the TIFF image precedes the PostScript code, and if you are REALLY 
more unlucky, the header and the TIFF image do not contain a line terminator.
There isn't a whole lot you can do about this other than trying to force the
software that generates the EPSF file to put the TIFF preview AFTER the 
PostScript code.  Or going in and changing random bytes in the preview to
`return' or whatever is needed...


Berthold K.P. Horn
Cambridge, Massachusetts, USA