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.
Subject:Re: Usage of "that" From:Tim Altom <taltom -at- IQUEST -dot- NET> Date:Wed, 31 Jan 1996 09:29:00 EST
>I have a question regarding usage of the word "that." When is it
>appropriate
>and when is it just added fluff? To give you an idea of what I mean,
>here are
>some sample sentences:
>"This section lists related documentation *that* you may find helpful."
>"This guide assumes *that* you have a basic understanding of..."
>"Ensure *that* the hood is securely fastened."
>In these sentences, is the word "that" necessary? I prefer to leave it
>in
>because I think *that* it sounds better, but that is my own opinion.
This is only one of hundreds of such questions about usage that all teeter
on the question of reader anticipation. That is, if the reader isn't misled
by dropping the "that," then usual practice is to eliminate unnecessary
words. The hard part is anticipating the user expectations. Purists will
mumble and diagram the sentence to prove that you need the preposition. As
an English major, I see that point. As a writer, it's utter bosh. Usually
the "that" is implied and can be safely left off. But sometimes it can't,
just because its absence leaves a speed bump the reader feels as he passes
over the space. Here we're returning to the old and sorry but true phrase of
"know thy audience...and keep in touch." If you need a rule of thumb, I'm
personally of the "ultra-precise default" camp; when in doubt, add a word to
preserve clarity and precision. In my view, we're not in business for style,
but for meticulous transmission of concepts. And if you're heading for
translation, it's vitally important that you be clear, because many
translators aren't native English speakers and you're actually writing for
the translator, not the end user.
On another level, the overuse of "that" is often a sign of unnecessary
wording. For example, "This section assumes that you have a basic
understanding of..." isn't as easy to read as "You should have a basic
understanding of..." In strict terms, the section doesn't assume
anything...the writer does. Here at our company, we've used second person
extensively to overcome wordiness and it's usually acceptable to the client.
