Re: How do you handle revisions for translation?

Subject: Re: How do you handle revisions for translation?
From: "Sharon Burton-Hardin" <sharonburton -at- earthlink -dot- net>
To: "Krista Van Laan" <KVanlaan -at- verisign -dot- com>, "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 11 Jan 2000 14:16:17 -0800

When I needed to do this - and I tell my writers to do this now - Keep an
Excel spreadsheet or a table that has 3 columns marked Page, Was, Is or
something like that. Then when they make a change, they mark in the table
the page of the change, paste the text before the change and paste the new

Once a week, the table is sent to the localization company, along with the
new files. Everyone seems very happy with this arrangement.


Sharon Burton-Hardin
President of the Inland Empire chapter of the STC
Anthrobytes Consulting
Check out!

----- Original Message -----
From: Krista Van Laan <KVanlaan -at- verisign -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Tuesday, 11 January, 2000 2:05 PM
Subject: How do you handle revisions for translation?

| 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
| 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
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| Sponsored by Weisner Associates Inc., Online Information Services
| Training & consulting for RoboHELP, Dreamweaver, HTML, and HTML-Based
| More info at or mailto:training -at- weisner -dot- com -dot-
| Sponsored by, Language Translation Simplified. Instant
| on line quotations and free samples available for technical documentation.
| Any File...Any Language...Anytime
| ---
| You are currently subscribed to techwr-l as: sharonburton -at- earthlink -dot- net
| To unsubscribe send a blank email to
leave-techwr-l-18328T -at- lists -dot- raycomm -dot- com
| Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
| for more resources and info.

Previous by Author: Re: Are you debating the elimination of printed docs? (An idea.. .)
Next by Author: Re: customizable documentation
Previous by Thread: RE: How do you handle revisions for translation?
Next by Thread: RE: How do you handle revisions for translation?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads