Xref: utzoo comp.windows.news:388 comp.text:1715
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!think!bloom-beacon!mit-eddie!uw-beaver!ssc-vax!benoni
From: benoni@ssc-vax.UUCP (Charles L Ditzel)
Newsgroups: comp.windows.news,comp.text
Subject: Re: Adobe flagellating PostScript trademark
Message-ID: <1803@ssc-vax.UUCP>
Date: 26 Mar 88 10:03:20 GMT
References: <4237@hoptoad.uucp>
Organization: Boeing Aerospace Corp., Seattle WA
Lines: 24
Summary: y

In article <4237@hoptoad.uucp>, gnu@hoptoad.uucp (John Gilmore) writes:
> According to the above definition, either the Apple LaserWriter or the
> LaserWriter Plus does not contain a PostScript interpreter, since they
> have different sets of language commands, and Adobe thinks
> sub/supersets are not PostScript.  Also, the PostScript interpreter in
> my original LaserWriter has, I suspect, at least as many bugs as NeWS,
> as far as meeting the specs in the PostScript language reference
> manual.  It is clear to me that if Adobe's products don't pass the test of
> what is really "PostScript", the test is worthless and cannot be used to
> judge whether NeWS is PostScript.

Agreed!  At NCGA where they were demoing Display Postscript, some people
asked about window management and how to do it using Display Postscript
...the Adobe rep stated correctly that you had to do it from the native
window system.  I mentioned NeWS.  The Adobe rep stated quite smugly
that *it* was *not* postscript.  To his horror, I responded that he was
right, NeWS was better since not only did it understand standard Postscript
but you could do window management, color, etc.  Immediately people wanted
to know where they could see *it*.  I told them to look at the Raster
Technologies, Sun and Silicon Graphics booths.

As I left the booth I heard the click and bang of a make-believe gun.

--------------
Naturally my opinions are my own and not my employers.