🚀 go-pugleaf

From: Allan Hetzel  <SYSAL%UKCC.BITNET@WISCVM.arpa>

The note posted to Laser-Lovers on Oct 28 by Joseph Goldstone of Symbolics
Cambridge Research Center was helpful but I didn't try his suggested fix
correctly and so I called Adobe.  They were very helpful (much more so than
Apple) and explained the problem and how to bypass it.

My apologies to Adobe if this not an accurate description of the problem.
The problem apparently is due to the PostScript interpreter getting confused
by what it thinks is an excess of white space characters.

The bypass is to place a special character (parenthesis, bracket, brace,
slash, etc.) to the right of some token, but without an intervening white
space character. As the PostScript scanner reads the token it also reads the
special character which acts as a delimiter. The scanner then has to back up
one character so that it can reprocess the special character after it has
processed the preceding token.  During this backing up process a number of
internal values are recalculated, including some pointer into the input buffer.
This causes the XON/XOFF protocol to work properly.  Doing this once per page
seems to keep everybody happy.

Each page in the PostScript file built by our word processing program is
surrounded by a "save restore" sequence. We changed the beginning save
sequence "/saveobj save def" to read "/saveobj save def() pop".
The "() pop" is effectively a no-op and we are assured that the necessary
recalculations are done on each page.  This seems to have corrected the problem
completely.

Allan Hetzel (sysal@ukcc.bitnet)