Path: utzoo!utgpu!attcan!uunet!lll-winken!ames!mailrus!cornell!rochester!rit!cci632!ccicpg!felix!kehr
From: kehr@felix.UUCP (Shirley Kehr)
Newsgroups: comp.sys.mac
Subject: Re: Desktop Publishing on Mac - HELP
Keywords: word processing draw packages desktop publishing
Message-ID: <78627@felix.UUCP>
Date: 13 Jan 89 15:30:32 GMT
References: <Jan.10.22.44.46.1989.18184@seagulls.rutgers.edu> <932@thor.stolaf.edu>
Sender: daemon@felix.UUCP
Reply-To: kehr@felix.UUCP (Shirley Kehr)
Organization: FileNet Corp., Costa Mesa, CA
Lines: 23

In article <932@thor.stolaf.edu> sobiloff@thor.UUCP (CP^ZAZPPPYPYXU	zQYhBYPYoZO) writes:
<As far as your software goes, if you really need revision marks (?) and style
<sheets my best guess would be Word (real WYSIWYG supposedly coming w/ 4.0) or
<possibly Nisus (new from Paragon Concepts, Inc.).

Word doesn't do automatic revision marks like FullWrite, but I don't see
that as a disadvantage. If you let the computer do revision marks, you'll
get them for spelling corrections, style changes, etc. And this would 
happen even if you changed it back to the original. I can't see burdening
users with having to identify changes like that.

What you can do with word is put a bar to the left of an entire paragraph.
This isn't as accurate as identifying the specific lines in which changes
occurred, but would identify any paragraph you updated. But you would have
to remember to put them in manually. Personally, that would be my 
preference.

Luckily, we don't have to do change bars (yet). But the time may come
when we decide to send change pages instead of entire chapters. (The
problem isn't change bars - it's identifying the list of pages that
comprise an up-to-date manual.)

Shirley Kehr