atw: Re: AND, BUT, or OR as the first word of a sentence

Petra, Re-read both our statements. We agree much more than we disagree.
We both agree that readability is the aim.=20
I am professing simple, elegant use of language to convey technical
information not 'technical language'.
Most technical communication has to use a corporate voice so the
author's own style is not used.
By the way:
"<Topic Name> for Dummies" is designed in a chatty format. It works
well. It is an applied style.=20
The authors are not using their own voice but are applying an editorial
style.


John Murphy
Documentation
Dilithium Networks



> We follow conventions because it assists us in technical=20
> communication. We wear a suit and tie to certain functions not because

> it is a rule but because, by doing so, we convey a certain formality,=20
> stability and dignity to our attendance which opens the door to=20
> further forms of communication. In the same way, we use formal English

> in technical documents to relax the viewer, to assure them that the=20
> documentation they are reading will not shock them, confront them or=20
> task them. This is why technical writers are encouraged to be=20
> conservative in their use of English. Their readership is not arty=20
> farty or highly literate. Use of simple, elegant English allows the=20
> content to shine through rather than the personality of the writer.=20
> The opposite is often true for creative writing. And the earth moved.=20
> And the sun rose. And most novelists have fragile egos.
>
> John Murphy
> Documentation
> Dilithium Networks

John,

I'm afraid I totally disagree. I have been working on insurance
documents for the past few months and with only one exception have found
them all pretty deadly - not that I expect them not to be. The one that
wasn't deadly was written in a chatty style, with the occasional corny
joke and yet it was extremely informative, provided historical examples
which helped me understand terms I'd seen explained several times
already in "technical language" but hadn't quite got a handle on and was
generally very readable. The writer's personality came through and as
far as I'm concerned that was not an unwelcome thing. I'm not suggesting
that all technical documents be written like this and most people
(including myself) wouldn't have the aptitude for it. However, apart
from providing the information required in a well-structured way, when
you're writing a long document surely readability is what you aim for -
people have to get through the thing. In the hands of a good writer a
certain "style" enhances the reader's understanding rather than reduces
it.

Petra

**************************************************
To post a message to austechwriter, send the message to
austechwriter@xxxxxxxxxxxxxx

To subscribe to austechwriter, send a message to
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject
field.

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx
with "unsubscribe" in the Subject field.

To search the austechwriter archives, go to
www.freelists.org/archives/austechwriter

To contact the list administrator, send a message to
austechwriter-admins@xxxxxxxxxxxxx
**************************************************
**************************************************
To post a message to austechwriter, send the message to 
austechwriter@xxxxxxxxxxxxxx

To subscribe to austechwriter, send a message to 
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with 
"unsubscribe" in the Subject field.

To search the austechwriter archives, go to 
www.freelists.org/archives/austechwriter

To contact the list administrator, send a message to 
austechwriter-admins@xxxxxxxxxxxxx
**************************************************

Other related posts: