We have to translate several documents into 25+ languages. Based on past experience, we know, for sure, that there will be updates and changes during the exact time that the documents are being translated. It's also not impossible that there will be updates to the updates (... highly regulated industry with new rules coming out all the time). You get the idea.
Does anyone have any insights or experiences to share? I'm particularly interested to know how I can attempt to manage the injection of streams of updates into an in-progress translation effort across multiple languages.
many thanks in advance from cloudy England.
Clive Harris.
Managing updates in large translation project
Re: Managing updates in large translation project
This is a very common issue, and it's present in most technical environments. It's also easy to solve.
Assuming you use a versioning system, I suggest creating a branch version of the project you sent out for translation. In practice, this would mean a backup copy that was sent out and existed on a given date. When you get the translations back, you'll also receive the Translation Memory database (TM), which is a database of all strings in a source-target pairing, and a snapshot of your original translation.
The first translation will take a while, and your corrections in this time will be a smaller amount of content.
At some point, you decide you want a publishable version. That day, create a second branch (copy) of the most recent projects, and deliver the new project to the translator along with the TM you received from the 1st bulk project. He'll run the TM through the new version, and Lingo will show him where he needs to add/correct the changed information. He'll do that in a short time, return your new project and updated TM, and you can publish.
Every time you repeat this process, the amount of correction and update is smaller (because the translator project turns around faster), until you get to a manageable level of micro-corrections which can be done about as fast as the changes you apply to your documentation.
Assuming you use a versioning system, I suggest creating a branch version of the project you sent out for translation. In practice, this would mean a backup copy that was sent out and existed on a given date. When you get the translations back, you'll also receive the Translation Memory database (TM), which is a database of all strings in a source-target pairing, and a snapshot of your original translation.
The first translation will take a while, and your corrections in this time will be a smaller amount of content.
At some point, you decide you want a publishable version. That day, create a second branch (copy) of the most recent projects, and deliver the new project to the translator along with the TM you received from the 1st bulk project. He'll run the TM through the new version, and Lingo will show him where he needs to add/correct the changed information. He'll do that in a short time, return your new project and updated TM, and you can publish.
Every time you repeat this process, the amount of correction and update is smaller (because the translator project turns around faster), until you get to a manageable level of micro-corrections which can be done about as fast as the changes you apply to your documentation.
Re: Managing updates in large translation project
Thanks. This sounds like an excellent arrangement.Fedja wrote:This is a very common issue, and it's present in most technical environments. It's also easy to solve...<snip>