Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!umeecs!msi.umn.edu!cs.umn.edu!sialis!orbit!incstar!lhotka
From: lhotka@incstar.uucp (Glamdring)
Newsgroups: comp.windows.ms
Subject: Re: WfW and ATM - not quite WYSIWYG
Message-ID: <2405@incstar.uucp>
Date: 21 Jan 91 14:19:15 GMT
References: <69220012@hpl-opus.hpl.hp.com> <1991Jan16.125135.23096@watserv1.waterloo.edu>
Organization: INCSTAR Corp, Stillwater MN
Lines: 24

In article <1991Jan16.125135.23096@watserv1.waterloo.edu>, tom@mims-iris.waterloo.edu (Tom Haapanen) writes:
> Tom Knotts <knotts@hpl-opus.hpl.hp.com> writes:
>> I am running WFW with ATM and postscript. When I have WFW in standard
>> viewing mode (not Page and not Draft), the text is not quite WYSIWYG.
>> The text looks correct in shape and style, but the line breaks are not
>> the same as they will be when printed. To get the line breaks to show
>> correctly, I must switch the viewing mode to Page. [...]
>> I thought that ATM was suppose to deliver accurate screen fonts to
>> within a pixel. It seems that it is only accurate to @ 5%.
> 
> FaceLift behaves the same way.  I find it rather annoying, but I'll put up
> with it for now.  I'm hoping that when TrueType finally comes out, it'll
> be really WYSIWYG...

We had similar problems with just W4W - nothing else running.  It turned
out that the driver for our monitor was almost but not quite correct
for Win30...  Once we switched vendors and got a different monitor with
a working driver all was well.
 ______________________________________________________________________
/ Rockford Lhotka				INCSTAR Corp	       \
| Applications Project Leader			1990 Industrial Blvd   |
| incstar!lhotka@uunet.uu.net         		PO Box 285             |
\ 612/779-1701					Stillwater, MN 55082   /
 -------------Amiga - The computer for the creative mind.--------------