Newsgroups: comp.sys.apple2
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!dodo.cis.ohio-state.edu!meekins
From: meekins@dodo.cis.ohio-state.edu (Tim Meekins)
Subject: Re: POSTSCRIPT
Message-ID: <1991Jun22.161913.18825@cis.ohio-state.edu>
Sender: news@cis.ohio-state.edu (NETnews        )
Organization: The Ohio State University, Department of Computer and Information Science
References: <1991Jun22.151814.13318@clark.edu>
Date: Sat, 22 Jun 1991 16:19:13 GMT
Lines: 21

In article <1991Jun22.151814.13318@clark.edu> andy@pro-palmtree.cts.com (Andy Stein) writes:

>    Why can't the Apple IIGS just print directly to the PostScript printer,
>instead of having to save a PostScript file to a disk, and then
>transferring it to a Mac, which prints the file to the PostScript printer?
>Is there some inherent limitation in the GS, or did Apple deliberately
>cripple the GS so it would compete with the Mac, by not making a real
>PostScript LaserWriter driver?

? The GS *does* send directly to a postcript printer. It's a feature of
the GS that we can *also* create Postscript files. The discussions ongoing
about created PS files is important becuase *most* of don't own a PS
printer to connected to the GS, but *do* have access to printere elsewhere.
I am one of those people. I cannot possibly afford a laserwrite, but my
school has about 20 of them sitting around in all the labs. All I have to
to on my GS is *redirect* my output to a text file, take it to school (or
upload it there) then print it on the printer there.

The actually problem with this scenario is that the GS actually *assumes*
it is connected to a printer, so some extra garbage is left in the postscript
file which *must* be removed before printing.