Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!marque!studsys!jetzer
From: jetzer@studsys.mu.edu (jetzer)
Newsgroups: comp.sys.apple
Subject: Re: Good Word Processors
Message-ID: <460@studsys.mu.edu>
Date: 7 Mar 89 14:43:19 GMT
References: <8903051558.AA00969@tcgould.TN.CORNELL.EDU> <4594@charon.unm.edu>
Organization: Marquette University - Milwaukee, Wisconsin
Lines: 32

In article <4594@charon.unm.edu>, cs1552ao@charon.unm.edu (Lazlo Nibble) writes:
> >If the Timeout AWP TO TEXT route is chosen, rather than the one built into
> >AppleWorks, saving WP files as text files is not painful, and the files do
> >not have the troublesome LF-CR at the end of each line.

> ...Meaning I have to buy TimeOut as well as AppleWorks, and still be retricted
> to 55k or so (less, with TimeOut installed) by the limited amount of memory in
> my machine.  Yuck.


With all the discussion about converting AppleWorks word processing files to
text, might I direct your attention to the March issue of NIBBLE Magazine?

There's a nice little program called Works Processor (written by little ol' me)
that will convert AWP files to text in several formats:  Carriage returns only
where there's a hard CR, carriage returns after each line, or CR/LF combination
at the end of each line.

While it is a separate program that you have to run, it is MUCH faster at
converting AWP files to TXT files than AppleWorks is -- in one test, a file
took only 9% of the time to convert (actual conversion time; of course you
must leave AppleWorks to run this program).

I've been avoiding plugging my own program, but could no longer resist.
(BTW, NIBBLE introduced a couple of bugs into my program from the time I
sent them the final version to publication time.  I could post the fixes
if anyone wants them.  Of course, I can't post the actual program, because
they bought the rights to it.)

-- 
Mike Jetzer
"Hack first, ask questions later."