Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!violet.berkeley.edu!steve
From: steve@violet.berkeley.edu (Steve Goldfield)
Newsgroups: comp.sys.next
Subject: Re: WYSIWYG
Keywords: WYSI*A*WYG
Message-ID: <15757@agate.BERKELEY.EDU>
Date: 20 Oct 88 16:30:32 GMT
References: <6937@orstcs.CS.ORST.EDU> <12908@oberon.USC.EDU> <2482@silver.bacs.indiana.edu>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 34

In article <2482@silver.bacs.indiana.edu> chiaravi@silver.UUCP (Lucius Chiaraviglio) writes:

About resolution in displaying screen vs. print images.
I appreciated the information you posted. However, as I posted
to comp.sys.mac yesterday, not all the discrepancies between
screen and printer can be ascribed to resolution. I gave two
examples in PageMaker. In one case, I drew a jagged line
across the screen and tried to put bullets on the nodes.
[Please don't tell me that I could have bought software like
MacFlow to do this. That isn't the point.] One of the bullets
printed about half an inch away from the node it was supposed
to be coincident with and which it was coincident with on the
screen. I phoned Aldus at the time, and they admitted that
such things could happen. [I admit that I don't know if this
is just a bug or laziness on their part or an inherent problem
as Aldus claimed.] In a second example, which has happened to
me twice, my screen showed a box, but the laser printer failed
to print one of its corners. In that case, I copied everything
into MacDraw which printed the box in its entirety.
[Incidentally, I always use the Aldus driver with PageMaker
because the Apple driver doesn't seem to handle reversed fonts.]

If the problem is only the inferiority of PageMaker, it isn't
worth discussing here except to warn people away from it. But
if something more fundamental in the interaction between
applications and the Mac screen and laser printer is going on,
then I for one would be interested in knowing what it is and
what real limitations it imposes on application programmers.
And for this news group, I'd be interested in knowing if the
problem is eliminated on the NeXT.

It seems quid pro quo to raise this here since the NeXT got so
much discussion in comp.sys.mac.

Steve Goldfield