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: Fog Index, take II From:eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 31 May 2002 12:23:05 -0400
Eloquently put Geoff.
However, I do take issue with "Keep it simple". Should it not be "Write to the
level of the audience and task."? Simple to one person is rocket science to
another. Make it too simple for the intended audience and you'll lose all
credibility.
In identifying writing approaches, I think we have to be wary of who the 'rules'
are being devised by and for. Simpleton readers or simpleton writers. If a
guideline can help readers understand material and avoid confusion great. If the
rule is designed to be used without a writer and/or editor using their talents
and brain then it's worthless and all efforts possible should be put into
dispelling it.
Simplified English (at least in the aeronautical industry application) is a
useful tool to ensure consistent and accurate documentation and understanding.
Simplified (or controlled) English correctly implemented can help experienced
writers write clear documentation and helps any level of reader understand the
instructions. Any arguments about "corruption" of the language are ridiculous
(we're not writing prose). Additionally, I'd prefer to think of writing to a
style guide/accepted vocabulary as writing up to the level of the user.
Fog index, 7+/-2, blind adherence to the MS (or other) style guide, and many
others all fall into the category of aiding simpleton writers think they are
producing good documentation or help simpleton project managers easily
reject/accept publications. While many debate the validity of such rules, the
debate is always misplaced. There should be no debate. All these 'pseudo-rules'
are indeed relevant for particular instances and circumstances. Unfortunately
the adoption of these 'rules' without an understanding of the instances and
circumstances is just trying to avoid thinking/learning.
Eric L. Dunn
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
Free copy of ARTS PDF Tools when you register for the PDF
Conference by May 15. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
