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: Editing for Non-Native Speakers of English From:Lyda Woods <lyda -at- pacbell -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sun, 31 Mar 2002 11:03:53 -0800
Please send me a copy of your research paper when finished. I'm most
interested in this topic.
As a teacher of English to Speakers of Other Languages and as a technical
writer, I think your topic is an important one.
Here are some of my observations that may be useful:
When editing for non-native speakers of English:
-be aware of the language transfer issues between your readers' native
language(s) and English (see Ann Raimes "Keys for Writers" for information
in this area).
-try not to use phrasal verbs such as "go over" meaning "to review"
-offer comprehension worksheet sections with the answers in the back - this
allows readers to privately check their comprehension and to go over parts
that they may have missed or misread (this may be especially important for
functional specifications docs which require in-depth comprehension before
technical specs are crafted). I've seen SW designed by non-native speakers
that was based primarily on the screen shots in the functional specs but did
NOT include the details and additions mentioned in the written text on the
very same page of the spec?! I saw this problem, however, as an area of
improvement mainly for Product Management which apparently did not develop
ways to build and evaluate comprehension of the functional spec materials.
-find other ways to develop comprehension skills such as discussion times
with the author or other key figures who can talk about the document and the
assumptions it is built upon
-interview non-native speakers where you work to find out directly from them
what kinds of language issues they have
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
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.