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:Effective use of language (was RE: Pet Peeves) From:Chris Borokowski <athloi -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 13 Mar 2007 09:28:06 -0700 (PDT)
This is a great list, and not only for non-native
English speakers. In our busy lives, as we pore over
mountains of documentation while computers and
blackberries and phones beep in the background, we
need simple clarity instead of flowery language. I've
distilled your list a mite further.
- Use short sentences where possible.
- Use present tense where possible.
- Use the simplest possible word where possible,
keeping in mind that oversimplifying loses the nuance
of some words (table versus ottoman).
- Avoid colloquialisms and references to media,
literature, art, sports, food and society. Even within
your native land, not everyone has experienced all of
these things or cares, so you will lose them.
- Avoid news references.
- Avoid humor where confusing. (I cannot become
humorless, and some things are absurd, but if it
detracts from meaning it must go)
- Define terms early in your
presentation/documentation and use them consistently.
- Use parallel structures where they reinforce
meaning.
- Speak clearly and slowly, enunciating carefully.
Great list. I hope someone puts it in an FAQ.
--- Jonathan West <jwest -at- mvps -dot- org> wrote:
> - Use short sentences.
> - Use present tense wherever possible.
> - Avoid long words except for defined technical
> terms.
> - Avoid colloquialisms.
> - Avoid literary references.
> - Avoid sporting metaphors.
> - Avoid topical references to news items in British
> newspapers.
> - Avoid humor. (Chatting in the coffee break is a
> different matter to formal
> communication.)
> - Where terms have already been defined in the
> standards, use the exact
> wording of the defined term.
> - Speak clearly and slowly, so that people whose
> first language isn't
> English can follow.
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-