> I think the first thing we need to settle is procedural: how are we going
> to go about editing these documents? I don't think the traditional method
> of dealing with source code (i.e., mailing "diff" output around) will work
> well for text. Anybody got any suggestions?
Since you've already provided a draft for us to work on, I would suggest
that any editing suggestions we make be marked down the left side with
the vertical bar. Like this:
| This is an example. Here is another one.
This isn't one.
And neither is this.
This draws attention to what the changes are, while still preserving
the flow of the prose. The issue of what to do if we disagree on
wording is a bit stickier, but I suspect that lots of "procedures"
won't help terribly with that. :-)
Beth E. Binde, Systems Programmer
Rutgers University Computing Services, Piscataway, NJ 08855-0879 USA
EMAIL: binde@noc.rutgers.edu VOICE: 908-932-5019
|
|
