grops and BeginBinary

[Michael Selway]

I've been trying to include an EPS file into a groff document
using .PSPIC.  The eps file was made by quark express on a
macintosh.  The quark express file includes an image.  I'm getting
the diagnostic "bad %%EndBinary line".  I think there are two
faults in grops which cause this:

- resource_manager::do_begin_binary() has an "ungetc(c, fp)"
  call, which should be "ungetc(cc, fp)".

- The Quark Express data has a terminating carriage return before
  the %%EndBinary line.  grops is expecting the %%EndBinary to be
  right up against the end of the binary data, and doesn't
  tolerate the carriage return.  I don't know if grops or quark is
  violating the standard, from the look of grops's *output*, I
  think it's grops that's at fault.

I've fixed the first by editing the code; patch is attached.  I've
worked-around the 2nd problem by manually removing the carriage
return from my eps export.

I've also had problems with (one of) microsoft's postscript
drivers which seems to think 256-character lines are fine, but
grops won't tolerate more than 255.  The patch below makes grops
much more tolerant by upping the limit to (an arbitrary) 1000.

HTH,
Michael.
------------------ stuff you asked for in BUG-REPORT:
I'm using redhat 7.2's default build of groff, groff-1.17.2-3.i386.rpm.

version is 1.17.2; machine is a pentium PC; OS is linux 2.4.9;
compiler is gcc 2.96; I can't send you the quark express export,
but I could perhaps make one if you need one; I'm using ".PSPIC
filename.ps" in a document which uses the mm macros; command line
is "grops" (called out of gxditview).
------------------

grops.patch
Description: Binary data