TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> Jackie says:
> I know that contractions shouldn't be used in tech writing, but
> I can't find where it says this.
And Rosie says...
> Well, darn it, I like contractions in technical writing, and as a lead
> I have blessed their use in our documentation.
> I read somewhere that there is a trend in tech writing away from such
> formal writing; however, I cannot remember where I read this!
> I imagine you will find this list polarized on this issue, with slightly
> more writers leaning towards the formal style.
> I also imagine that the audience and purpose of your document should
> figure into any style decisions that you make. If you are writing to a
> highly educated audience that you want to impress with your
> erudition, you may want to take a more formal tone.
> Otherwise, you may want to keep the writing light.
I too, use contractions in technical documents -- particularly
in end-user documentation. I believe it removes some (but not
all) of the intimidation factor from software documentation.
Just as passive voice used to be considered more "appropriate"
for formal writing and isn't considered so anymore, I think
that contractions will come into their own relatively quickly.
Anything that you can do to make technical information more
inviting, less intimidating, and easier to read can't be
a bad thing, now... Can it???
StarBase Corp, Irvine CA
sgallagher -at- starbasecorp -dot- com