Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!itsgw!steinmetz!uunet!rlgvax!smadi
From: smadi@rlgvax.UUCP (Smadi Paradise)
Newsgroups: comp.sources.d
Subject: pps (was: v17i080:  PostScript pretty-printers...)
Summary: problems + fixes
Keywords: flex spooler iamgen error yacc
Message-ID: <1113@rlgvax.UUCP>
Date: 15 Feb 89 06:23:50 GMT
References: <1470@fig.bbn.com>
Reply-To: smadi@rlgvax.UUCP (On Paradise)
Organization: a guest of Computer Consoles Inc, Reston VA 22091
Lines: 42

Here is a summary of some common problems people had with pps.

1. Flex
	I am told that flex (a faster lex) would not accept two Kleen
	stars in the same regular expression if one of them is in right
	context.
Cure: use lex(1), or alternatively modify the source to ``gulp'' the
	left context and then yyless() it.
Effects: *.l

2. Spooler
	Some spoolers expect %%Page comments in their PostScript input.
	Mea culpe -- pps produces none, as it does not _know_ about
	page breaks.
Cure: remove the ``PS-Adobe 1.0'' from the first line, leaving %! alone.
	This tells the spooler that pps does not strictly follow 1.0 .
Effects: *.sh

3. Imagen
	I am told that some Imagen printers have smaller usable
	bounding box than bbox returns. When printing outside this box,
	paper may stick to the seperating mechanism.
Cure: increase margins to about 72 points.
Effects: *.pro

4. Usenet (?)
	Some sites complain about transmission errors in pps.pro
Cure: drop me a line and I shall mail it.

5. Yacc
	The language-sensitive front-end for yacc(1) was not incuded
	in the orignal posting (it has never been beta-sited).
Cure: if there is enough interest I shall post it here.

Thanks to
	Dave Platt <coherent!dplatt>
	Dave Curry <riacs!davy>
	Kevin B. Kenny [the Arch-Traitor] <m.cs.uiuc.edu!kenny>
	Blair MacIntyre <watdragon.waterloo.edu!bmacintyre>
for sharing these problems and solutions.
-- 
On (a guest of uunet!rlgvax!smadi) Paradise