[507] in Release_7.7_team
Re: sun4 8.0A: I can't preview or print from ez
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Apr 25 12:20:49 1996
Date: Thu, 25 Apr 1996 12:20:37 -0400
From: Greg Hudson <ghudson@MIT.EDU>
To: "Albert Dvornik" <bert@MIT.EDU>
Cc: Bill Cattey <wdc@MIT.EDU>, sol24@MIT.EDU, Carla Fermann
<carla@MIT.EDU>,
release-team@MIT.EDU, irix53@MIT.EDU
In-Reply-To: "[486] in Release_7.7_team"
> (5) There are some strange bugs under IRIX in some of the programs
> that were added between Transcript 2.1 and 4.1. We could fail
> to install them on the packs with no user impact, but they are
> sort of neat, so fixing would be better.
> See next piece of mail for details.
All of your tests for pslpr, psdraft, and psnup use as input the
result of "psroff -t -man man/psdraft.1p". If I take the output of
psroff -t -man man/psdraft.1p on an SGI and then run, say, psdraft on
it on a Sun, I get the same (bad) output as if I run psdraft on an
SGI.
That is to say, the problem appears to be in the psroff output on the
SGIs. psroff uses troff, so it appears to be a problem with the SGI
troff output. Both the Sun and SGI troff output use currentmatrix and
setmatrix; I'm guessing that the SGI troff output uses them in an
unethical manner (read: not conforming with the Adobe Document
Structuring Conventions).
When I played with psdraft and psnup on other postscript files, they
worked fine on an SGI.
Although it's bothersome that the SGI troff doesn't seem to produce
DSC-compliant output, I don't think it needs to affect our release
plans.