Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!zaphod.mps.ohio-state.edu!uwm.edu!dogie.macc.wisc.edu!vms.macc.wisc.edu From: yahnke@vms.macc.wisc.edu (Ross Yahnke, MACC) Newsgroups: comp.sys.mac Subject: Re: Does anyone have comments on Nisus? Message-ID: <2941@dogie.macc.wisc.edu> Date: 8 Jan 90 14:14:30 GMT Sender: news@dogie.macc.wisc.edu Organization: University of Wisconsin Academic Computing Center Lines: 46 In article <422@skippy.UUCP>, ras@skippy.UUCP (Bob Surtees) writes... -I have seen a couple of reviews on Paragon's Word Processor Nisus and, as a -result of playing around with the demo version, am almost at the point of -purchasing a copy. - -Does anyone out there have any experience with this product for serious -word processing and had a chance to compare it to some of the other -*heavies* that are in common use? I currently use WordPerfect and was Nisus is an extremely well thought out product, with no where near the madness inherent in MS-Word's interface. (I've never used WP...). The search & replace facilities - based on GREP - are top notch, allowing s & r combinations just not possible in other packages. And combining that with the catalog window, allowing you to s & r thru all open files is incredibly useful. It's easy to learn but definitely a power-users app, you can really grow into it. On the downside, it keeps the whole document(s) being edited in RAM, thereby limiting document size, (esp. one w/a lot of graphics). With a 1 meg MF partition I started having memory-lo problems with around 20 pages of document. And when you start running low on RAM, watch out! I got into some bad situations where Nisus would refuse to save my document due to lo RAM. Not good, I lost several hours of work, even after trying all the suggestions in the manual. It did crash on a lo memory situation and also once when doing a Find operation, so there are still a few bugs to work out. The graphics integration is real nice, they've included basically a subset of MacDraw. How graphics get anchored to the document is some- what flaky tho, graphics tend to jump unpredictably from page to page when they're near a page border. Biggest strike against Nisus is their well written manual. The problem is that it comes with about FIFTY replacement pages that you have to insert, PLUS a HUGE list of erratas that make you have to go thru the manual page by page crossing out and adding text via ballpoint pen, PLUS (!!!) a read.me doc that has yet even MORE errata, even a page of text that you're s'posed to print out and insert in yur manual. Manual construction took me a good three hours, RIDICULOUS! Despite the glitches which I hope Paragon will iron out, I'll stick with Nisus over Word any day. >>> Internet: yahnke@macc.wisc.edu <<< >>> Mille voix chuchottent <> <<<