home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.software
- Path: sparky!uunet!stanford.edu!leland.Stanford.EDU!leland.Stanford.EDU!kocks
- From: kocks@leland.Stanford.EDU (Peter Kocks)
- Subject: Re: NeXT Word Processors - Junk, garbage, and more junk...
- Message-ID: <1992Dec14.201322.6826@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: DSG, Stanford University, CA 94305, USA
- References: <Bz137t.2Io@news.cso.uiuc.edu> <5393@disuns2.epfl.ch> <1get2pINN6l7@phakt.usc.edu> <1geub7INN6r5@phakt.usc.edu>
- Date: Mon, 14 Dec 92 20:13:22 GMT
- Lines: 22
-
- Could someone please explain what is meant when someone says,
-
- "NeXT needs a *REAL* wordprocessor".
-
- What is a *REAL* wordprocessor and what does it do that one of FrameMaker, WP,
- or WriteNow does not do? (add TeX to that list).
-
- I'm really curious. I understand that NeXT does not have a native MS-WORD port
- (although you can run it through executor if you want). I also understand
- that some people just love MS-WORD and have essentially grown-up on it.
- While it is very nice, it is IMHO far from perfect.
-
- Moreover, on a NeXT, any of the exisiting wordprocessors use DPS so you
- truly get what you see (much better than WORD, for example). Also, the
- NeXT mail makes working on complex documents over a network relatively
- easy compared to most other machines. You CAN do similar things on other
- platforms, but it usually requires a lot of configuration work and additional
- products. Everyone who has a NeXT has NeXTMail.
-
- --Peter Kocks
- kocks@chemistry.stanford.edu
-
-