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: What to do??? From:"M Page" <mpage -at- csl -dot- co -dot- uk> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 28 Oct 2003 09:58:36 -0000
(Sorry - to chip in late - it's 1st thing in the morning on this side of the
Atlantic.)
I too have worked with enginneers whose technical expertise far exceeds
their grasp of English. I tried to take the role of high priest or shaman
interpretting the cryptic utterances of the gods, which seemed to work
pretty well, though - yes - it can do your head in after a while.
Some suggestions:
*Explain to your boss it takes time, and why: grammer exists in part to lock
out ambiuguities. To correct the grammer you have to first comprehend what
you're reading, which is hard if the grammer is so mutilated as to make
comprehension doubtful. The task is analogous to debugging comment-free code
which has been randomly re-arranged by a five year old.
*Get the engineers to write as little as possible, using numbering, bullets
and arrows - whatever - to convey flow and sequence. That way, they write
less (making them happy, cost-effective, engineers), and you spend less time
wrestling with strange constructions (making you a happy, cost-effective
techwriter).
*Cycle each completed document back to the engineers in editable form,
ostensibly for approval, but actually so they can:
-Use them as a basis for similar output - this will be easier for the
engineers than generic boilerplate because they'll be familiar with the
subject matter.
-Learn by example - but don't tell them that's the idea!
*Keep a file of really amusing errors so you can share the best ones with
your friends...
It all sounds very... anecdotal...
Take care
M
"Wade Courtney" <courtney -at- hsq -dot- com> wrote in message news:217815 -at- techwr-l -dot- -dot- -dot-
>
> Thanks for all of the words of encouragement, wisdom, and support. I
> will try some of the suggestions that I have read about. By the way, I
> forgot to mention that I am not only editing it, but also making the
> corrections.
>
> Wade
>
>
>
>
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
---
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.