Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!usc!hacgate!gryphon!richard
From: richard@gryphon.COM (Richard Sexton)
Newsgroups: comp.sys.amiga
Subject: Re: Stupid Wishes
Keywords: ... and the bad news is that the OTHER Kent is back too...
Message-ID: <16615@gryphon.COM>
Date: 9 Jun 89 22:20:27 GMT
Reply-To: richard@gryphon.COM (Richard Sexton)
Distribution: na
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 54

In article <17222@swrinde.nde.swri.edu> kent@swrinde.UUCP (Kent D. Polk) writes:
>
>Yes, I know about the hardware limitation, but considering Amiga owner
>discontent over 640*400 interlaced & the number of sales lost to the ST
>because of it's hires mode availability,

Wait a minute, is this the Atari 620x200 noninterlaced "hires",
the same thing that apple calls super-hi-res on the GS.

Hrmph. Sounds like low res to me.

>I must say that when I first saw 640 * 400 interlaced mode, I almost
>gagged.

1) Turn the brightnes down.

2) Get a Sony monitor.

The perception of flicker is dependent on many things, but brightness
of the tube, and the amount and kind of light are the two greatest
contributing factors to an undesirable amount of flicker.

I used hi-res exclusivly, and barly notice any flicker. Of course
I did 1) and 2) above.

>What I want is to make more information available to the printer
>drivers and to make it easier for applications programs to output to
>the printer. Now maybe this isn't the proper way to do it, but it was a
>suggestion as opposed to simply griping about the poor support provided
>for printers. I just felt that a different tack than filter hacks was
>needed. It seems kinda silly to me that to get things like Postscript
>output, one has to use a separate filter & can't even use prt:.  Not
>consistent.
>
>If this info was available, couldn't one make a 'simple' Postscript
>printer driver (not easy maybe, but doable)? Exactly how could one get
>font names for text (imbedded in the file)? Seems like IFF Text would
>be the way to do this. It has such info available (and without
>resorting to graphics output). This way one could print directly from
>something like ProWrite to a Postscript printer without having to save
>the file & bring up ProScript. One could also just 'type' the ProWrite
>IFF Text file to prt:. Much more convenient.  Now, for fancy page
>positioning & such, a separate program would be the advisable method.

This sounds great. I have a Postscript printer too, and while I 
havn't really had any problems in this area, what you describe
might be moderately useful.

Let me know when you're done.


-- 
       ``The who's who of Milwaukee only eats Ugandan pineapples''
richard@gryphon.COM  decwrl!gryphon!richard   gryphon!richard@elroy.jpl.NASA.GOV