You are currently working on UAT 

Dividing a single document between three or more translators

Dear all,

I have a productivity question regarding working between several translators with the same file. The team usually deals with single files divided between two translators. In such situations, one of them creates a project and then a translation project package for the second translator. Both work on the same file (for instance, translator A from segment 1 to 500 and translator B from segment 501 to 1000). Then, translator B send the return package to translator A who opens in and can see the whole translation. Then, translator A does a QA and delivers the final translation.

However, lately, this team has been facing situations in which three or more translators have to work with the same file. So, translator A does not create two or more translation packages for translators B and C, and so on, but imports TMXs from the other translators once they've finished the translation. This process proves to be a bit complicated, but does work.

My question is: is there a way of dividing a single document for three or more translators by using the project packages option? In my tests, when trying to import back the return packages from more than one translator, the translation gets replaced. That is, if I import a translation package from translator C after having imported the return package from translator B, the translation from translator B gets replaced by blank segments because the segments that translator B had to do were not assigned, obviously, to translator C.

I hope I have been clear enough and you can help me improve productivity in these situations.

Note: the team is using all SDL Trados Studio Professional licenses.

Thanks in advance!

Damián

Parents
  • Damián Santilli said:
    In my tests, when trying to import back the return packages from more than one translator, the translation gets replaced. That is, if I import a translation package from translator C after having imported the return package from translator B, the translation from translator B gets replaced by blank segments because the segments that translator B had to do were not assigned, obviously, to translator C.

    Instead of importing the package, just extract the SDLXLIFF from the package (I assume you know it's just a ZIP file...) and "Apply PerfectMatch" to your main file using this partially translated SDLXLIFF - the translations will be transferred right there where they should be. And if you use the "Use original translation origin and status" option, you even get the segment statuses exactly as they are in the partially translated SDLXLIFF.

Reply
  • Damián Santilli said:
    In my tests, when trying to import back the return packages from more than one translator, the translation gets replaced. That is, if I import a translation package from translator C after having imported the return package from translator B, the translation from translator B gets replaced by blank segments because the segments that translator B had to do were not assigned, obviously, to translator C.

    Instead of importing the package, just extract the SDLXLIFF from the package (I assume you know it's just a ZIP file...) and "Apply PerfectMatch" to your main file using this partially translated SDLXLIFF - the translations will be transferred right there where they should be. And if you use the "Use original translation origin and status" option, you even get the segment statuses exactly as they are in the partially translated SDLXLIFF.

Children