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:How do you handle revisions for translation? From:Krista Van Laan <KVanlaan -at- verisign -dot- com> To:"'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 11 Jan 2000 14:05:07 -0800
I've got a question for those of you who work with translators.
What do you do when a document is revised and updated? Change bars
don't seem to be an answer because we are still doing a lot of
rewriting and updating as we develop the product. We do frequent revisions,
too.
We keep track of changes by listing them, but this is very broad, so it
might say something like "Updated installation procedure" rather than
itemizing each change within the installation procedure.
I'm thinking that the right way to handle this is to keep the list of
changes, but make it more detailed. Before I make a decision about this,
I'd appreciate some ideas from people who have done it. Up until now,
I've been giving the translator the entire new document with the
list of broad changes, but that isn't good enough.
Krista
==========================================================
Krista Van Laan VeriSign, Inc.
Documentation Manager 1350 Charleston Road
kvanlaan -at- verisign -dot- com Mountain View, CA 94043
tel: (650) 429-5158 fax: (650) 961-7300
