🚀 go-pugleaf

Our normal mode of operation is to produce text using troff,
with TransScript doing the troff to PostScript translation.
Output is produced on our DataProducts 2665 laser printer.
(This is a PostScript printer.) We produce graphics on the Mac
and paste them in mechanically.

We are trying to complete a test case here to show that
the drawings we have on the Mac can indeed be printed on
our DataProducts 2665 laser printer.  This test case will be
used to support our decision to purchase devps by Pipeline
Associates, which allows PostScript files to be sourced into
troff documents.  For us, this is a chance to finally do
electronic cut & paste.

Unfortunately, we can't seem to get the Mac-generated PostScript
files to do anything but *print* on the printer.  That is, the
printer looks at them as if they are something to print, not
something to *do*.

What we've done:

	Saved two versions of a MacDraw drawing, one with clover-F,
		one with clover-K.
	Uplinked these files to UNIX, using SmartCom II and
		xmodem.
	On UNIX, we translated ASCII carriage returns to newlines.

This gave us two files, one with the prologue, one without, both
of which were usable with the UNIX editors.  In the file with
the prologue, the vi editor says that one character is non-ASCII.
Haven't figured out the problem there yet.

In any case, we tried sending these files to the printer a few
different ways.  Queueing them through lpr -Pps (ps is our local
id for the printer) just gets them printed out like text.
We tried this one: cat filename > /dev/tty25 (the printer port)
with no success (no output at all).  We also tried cat-ing the
files and piping them to psif and pscomm, which are both low-level
filters used by TranScript.  This clocked up cpu time but never
produced output or terminated.

Next we tried some suggestions from folks like, for instance,
adding this line at the beginning of the files:
	serverdict begin 0 exitserver
And also adding the showpage command at the end.  Still nothing.

I tried to include all the pertinent details here.
Anyone have any other suggestions?  Remember, we are just trying
to show that we have all the pieces of the puzzle here already,
with the exception of devps to make life easy.

Thanks in advance...
-- 
=> Regards, Tom Cianflone @ Gould Computer Systems Division <=
=>   ...!{uunet,sun,pur-ee,brl-smoke}!gould!tcianflone      <=
=>    ...!ihnp4!{codas,allegra}!novavax!gould!tcianflone    <=
=> NOTE: Disregard header info. Email to above paths only.  <=