Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!shelby!unix!quintus!pds
From: pds@quintus.UUCP (Peter Schachte)
Newsgroups: comp.sys.amiga
Subject: Re: Word Processors & PostScript
Message-ID: <1429@quintus.UUCP>
Date: 4 Oct 90 21:14:02 GMT
References: <895@h.cs.wvu.wvnet.edu> <558@macuni.mqcc.mq.oz>
Reply-To: pds@quintus.UUCP (Peter Schachte)
Organization: Quintus Computer Systems, Inc.
Lines: 36

In article <558@macuni.mqcc.mq.oz> ifarqhar@sunc.mqcc.mq.oz.au (Ian Farquhar) writes:
>In article <895@h.cs.wvu.wvnet.edu> parker@cs.wvu.wvnet.edu (James Parker) writes:

I've been using ProWrite 2.0 and ProScript.  I've been pretty happy with
them.

>> 2. True WYSIWYG. (Whatever that stands for!) I need to see how the margin
>What You See Is What You Get.  Which is usually not what you wanted anyway :-)

Yeah, but at least you know.  Better than not knowing until you print
the thing.

>> 4. Should be able to output PostScript to a file so as to be able to be
>>    printed from other platforms which are connected to PostScript printers.
>You have to be careful here....  Of particular note (for it's
>stupidity) is Excellence!, which just dumps a bitmap to the Postscript
>printer.

ProScript generates reasonable postscript, and provides Helvetica,
Times, Courier and Symbol fonts (the standard Laser Writer fonts) in a
variety of sizes.  I haven't tried anything with graphics, just straight
text.  This was for a 100 page document, which it handled well.

Well, I did have one problem.  Somehow ProWrite got some strange,
invisible character in the document, which caused ProScript to loop
forever trying to load the file, eventually consuming all my memory.  I
found the rascal by doing a binary split on the file, and finally
noticing that I had to hit a forward arrow twice to move from one
particular character to (what I thought was) the next.  Deleting the
mystery character fixed the problem.  After this, ProScript was able to
generate the .ps file for my 100 page document with no problem on my
A100 with 1.5 Meg.  ProWrite was able to edit it fine, too.
-- 
-Peter Schachte
pds@quintus.uucp
...!sun!quintus!pds