What is the best work flow for commissioning follow-on translation of docs with changes?

We need the help of the experienced in what must be a fairly common need that arises after an initial translation has been done... handling revisions.

I am about to send our Studio-using translator a significant number of help file topics that have changed since his initial translation, EN > JPN. 

Some of these changes are small (typos, rewording). Some of them are significant -- additions & changes in self-help steps, large areas of additional instruction or explanation, and the like.

Plus, since it is a help file and the subject software is still under development, there are some significant changes in how the software works, as well as changes in the user interface.

As I send the changes to our translator:

  • Does the translation management side of Studio automatically spot these changes? (I can't see how that would be possible). 
  • Do we somehow indicate where all the changes have occurred? If so, what are the best practices for listing or indicating these changes?
  • Do we just start over?

(If it matters, we are working with Help + Manual, a second-tier help authoring application that uses standard XML for storing topic and table of contents verbiage.)

If you have pointers to tutorials or articles, please pass them along. I've been through a lot of the Trados materials, but I'm still at the stage where I'm overwhelmed with what appears to be thousands of details about Studio...

Any help is much appreciated, believe me.

Parents
  • Hi Dave,

    If there's a TM from the previous round of translations, then all you would need to do is create a project with the new files and the old TM, run the Prepare without project TM batch task and send the translator a package with the new, revised documents and the TM (or the separate SDLXLIFF files and the TM). When an existing TM is used to prepare and translate new documents, Studio will do the following:

    1. For segments that are identical in the old and new documents, Studio will populate the segment and mark it either as a CM (context match) or 100% match.

    2. For segments that have been revised, Studio will offer the fuzzy match if the changes cause the segment to fall within the fuzzy match threshold. The translation results window will show the changes between the old and the new segment in tracked changes.

    3. For segments that are completely new or have been heavily revised and now fall below the fuzzy match threshold, Studio will offer no translation results, and the translator will need to translate them from scratch.

    I hope that helps, but if anything is unclear, please don't hesitate to ask, I know how overwhelming it can be when one first starts working with Studio.

Reply
  • Hi Dave,

    If there's a TM from the previous round of translations, then all you would need to do is create a project with the new files and the old TM, run the Prepare without project TM batch task and send the translator a package with the new, revised documents and the TM (or the separate SDLXLIFF files and the TM). When an existing TM is used to prepare and translate new documents, Studio will do the following:

    1. For segments that are identical in the old and new documents, Studio will populate the segment and mark it either as a CM (context match) or 100% match.

    2. For segments that have been revised, Studio will offer the fuzzy match if the changes cause the segment to fall within the fuzzy match threshold. The translation results window will show the changes between the old and the new segment in tracked changes.

    3. For segments that are completely new or have been heavily revised and now fall below the fuzzy match threshold, Studio will offer no translation results, and the translator will need to translate them from scratch.

    I hope that helps, but if anything is unclear, please don't hesitate to ask, I know how overwhelming it can be when one first starts working with Studio.

Children
No Data