🚀 go-pugleaf

Etiquette, pt. 2:
2.      Writing style
Use short sentences and simple English.  Avoid rambling running
prose with complex syntax and a multitude of co-ordinate and
subordinate clauses.
 
3.       Spacing
Neat, meaningful spacing can ease mental processing. For
examples:
a.   Have short paragraphs separated by a blank line rather 
     than long paragraphs with a tab indent for the first line.
b.   Put questions on separate lines rather than stringing them 
     altogether in one paragraph. This makes it easier for people
     to annotate or answer them.
 
4.       Numbered items
Ideas, arguments, etc. are clearer if presented in point form,
and if they are numbered as well, it will make cross referencing
even easier.
 
5.       Annotation
a. Do not reproduce the entire original, extract only the parts
     that you wish to comment on.
b. If your local software does not allow  annotation, then
     paraphrase or summarize the original au that readers who
     have not read the original message can still understand the
     background and follow the argument.
 
6.       Upper case
The upper case is often used among networkers to denote emphasis,
but using too much of it can produce what is know as the "BANG"
effect. Words in upper case shout at you and generate a "noisy"
reading environment.
 
7.       Subject  line
If  you use the "reply" command to respond to a message on the
Internet, in most cases, that will automatically generate a RE
before the subject line of the original. Now if your response is
then read and replied by a third person who reacts to some side
issues that you raised,  his message by then will no longer be a
true reply to the first message and the old subject line can then
be very misleading. In such an instance, it  would be better if
the third person could refresh the subject line and put in
something appropriate to reflect the content of her message.



--  
uucp: uunet!m2xenix!puddle!23.0!Nancy.Petersen
Internet: Nancy.Petersen@p0.f23.n105.z1.fidonet.org