Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!mailrus!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: <25354@tut.cis.ohio-state.edu>
Date: 21 Oct 88 16:09:38 GMT
References: <6937@orstcs.CS.ORST.EDU> <12908@oberon.USC.EDU> <6637@batcomputer.tn.cornell.edu>
Sender: news@tut.cis.ohio-state.edu
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 20

In article <6637@batcomputer.tn.cornell.edu> cloos@tcgould.tn.cornell.edu (James H. Cloos Jr.) writes:
>(BTW, as to why I think they wanted 100 dpi on the monitor:  converting 100
>to 300 or 400 is considerable easier than converting 94.3 to 300 or 400.
>Maybe they even run the monitor as if it were 100 dpi rather than the 94+-.)

The content of a PostScript-driven display is not represented
internally as a bitmap in screen resulution.  The image is maintained
in PostScript, then interpreted when the image needs to go to the
rendering medium.  The interpreter knows the resolution and other
properties (e.g. color, grayscale, spot shape, spot size, inter-spot
spacing) of the medium and applies antialiasing and other techniques
appropriately at display time.

In the case of the NeXT machine, the interpreter knows that the screen
has certain properties and the printer has certain other properties.
One internal representation is sufficient to generate the image on
either rendering engine.  Neither engine's rendering properties
matter, nor does the ratio between the two.
-=-
Zippy sez,								--Bob
How's it going in those MODULAR LOVE UNITS??