Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!tut.cis.ohio-state.edu!allosaur.cis.ohio-state.edu!bob
From: bob@allosaur.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: comp.sys.next
Subject: Re: WYSIWYG
Keywords: WYSIWYG
Message-ID: <25540@tut.cis.ohio-state.edu>
Date: 24 Oct 88 18:27:45 GMT
References: <6937@orstcs.CS.ORST.EDU> <12908@oberon.USC.EDU> <25354@tut.cis.ohio-state.edu> <588@optilink.UUCP>
Sender: news@tut.cis.ohio-state.edu
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 26

In article <588@optilink.UUCP> cramer@optilink.UUCP (Clayton Cramer) writes:
>So how much hassle is it going to be for someone with a NeXT machine
>to connect up a 1270 dpi PostScript typesetter and make it work?

If our experiences with various PostScript printers are any guide,
you'll have more trouble getting the serial line flow control to work
right.  Once that calms down, you can use the standard Berkeley remote
line printer daemon stuff to drive any PostScript printer, just like
when you run TranScript on a networkful of other machines with only
one PS printer around.

>Will the NeXT machine have enough smarts to output true PostScript
>without knowledge of the rendering engine?  (I sure hope so -- or my
>opinion of NeXT will tkae a nose dive).

Surely you can find plenty of better reasons to lower your opinion of
NeXT!  Jobs' nose is too big, etc... :-)

To print to a PostScript device that's not attached on the custom
interface, you'll just ship the PostScript off across the net.  Then
the engine in the printer (e.g. Apple LaserWriter, DataProducts 2665,
whatever) will worry about its own device's rendering attributes.  At
that point, it's not NeXT's problem.
-=-
Zippy sez,								--Bob
Can I have an IMPULSE ITEM instead?