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.
This post from translations.com was approved by Eric Ray,
and is in response to the "Translation Control" query
posted last week to TECHWR-L.
Please inform me straight away if there are any protocol questions or
issues:
translations.com is a TECHWR-L Silver Sponsor, actively participates in
industry events, and has been engaged in English content development and
localization since 1986.
Question: What is the easiest way to manage translations?
1. Limit the number of project "owners" on both the client and vendor side
to provide control.
2. Assume that there will be change during a project?-and build "managed
change" into the schedule.
3. Version control--ensure that all parties are working from the most recent
source content. This increases consistency and reduces confusion.
4. Use seasoned, experienced localization project managers, localization
engineers, and linguists.
5. Choose the simplest format that can be used for a given project (for
example, Word may be the appropriate tool for a simple document rather than
a more complex layout application such as In Design or Quark.
Question: What source files should you have (i.e. MSWord files, XML files,
HTML files)
1. See answer #5 above.
2. This is totally dependent on the nature of the project. If the project
involves documentation with a simple layout, Word or Frame are likely the
best source formats of choice. For the web (or browser-based help), HTML can
be simpler to work with, but if the site has database content or requires
greater utility than a simple, static site, XML is often the preferred
choice.
3. For marketing collateral, Quark or Illustrator or often the top choices
since such content requires expanded layout functionality.
4. The take home message here is that each project (and the intended
audience's needs) must be assessed to determine the most logical source
files.
Question: What process if any have any of you defined in managing the whole
translation process from start to finish?
1. Over the years, translations.com has developed and continually refined a
multi-page process document that answers this question. Our production teams
around the world follow this process with every project.
Please contact me directly for a copy of this document or to further discuss
any of your questions.
Best regards,
Mike
--------------------------
Mike McPherson
Director, Client Services
translations.com
541.766.1142
mmcpherson -at- translations -dot- com
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
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.
