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.
Hi all. I'm hoping someone out there has some experience with this issue.
We are working on our first project which involves translation. Our current
doc set is several thousand pages, with commensurate screen shots. The plan
for doc translation is that we (the documentation team) will be provided
with the translated GUI, and, using our current user docs as a guide, will
replace all screen shots in the English doc with the translated shots by
stepping through the foreign language GUI. The language for this first
go-round is Spanish, and so the assumption has been made that "everything in
the GUI will be in the exact same place", so that lack of knowledge of the
target language should (theoretically) not be a problem. Future customers
may not be using Roman alphabets, which may be an issue in that "just count
three items over on the menu bar, then count down two on the drop-down menu"
may not be an option, especially as it concerns data entry and keyboard
mapping.
I understand that it will be less costly than having our translation vendor
perform the task; however, since most of the documentation group doesn't
know the target language, I do have a few questions about the process.
My questions to you are:
1. Has anyone here undertaken such a project? How did it work out?
2. How do you account for the lack of knowledge of the target language? Was
this an issue?
3. We don't have the luxury of using a side-by-side computer approach (one
in English, one in Spanish). Presumably this will prove to be a usability
test of our English docs, since we'll have to step through the instructions.
Comments?
Thanks very much for any information you can give us.
Laurah
--
Laurah Limbrick
Instructional Designer
Open Systems Technical Information Development
CSG Systems, Inc.
303.200.3364
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See http://www.infomap.com or 800-463-6627 for more about our solutions.
---
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.