Sending project packages to multiple translators

Question

Hi all 
 We have a project where we receive translations requests which have to then be translated to 6 languages. The project has grown to around 30 brief requests every day to be translated to all 6 languages. Up to now, we have been sending them out one by one, but now the volume has grown it means that we have to create around 180 project packages every day (30 for each translator). 
 Is there any way that we can send a project package to all 6 translators at the same time instead of sending 6 individual requests? 
 Thanks so much for your help. 
 David

Greta Magyar · Answer

Hello David Wright , 
 
A quick question first: do you have a separate project for each new file received for translation (into 6 languages)? 
 
The reason I'm asking is that in Studio as you know you can only create packages by projects - that is, you can create a package for each language in the project together, but it only works on individual projects. 
 
What could be a solution in this situation is to add all files received in a day into a single project, or at least create projects in batches, containing more files. 
So for example if you have 15 of the 30 files to translate in one project, you can create 6 packages (one for each language) together at once. 
 
Do you think this could help you? Provided of course that you have a little time to wait and to handle the files in batches rather than to dispatch each individually. 
 
Hoping to hear from you. 
 
Best wishes, 
 
Greta Magyar 
Customer Success Representative - SDL

Paul Filkin · Answer

David Wright said: Is there any way that we can send a project package to all 6 translators at the same time instead of sending 6 individual requests? 
 Hi David Wright 
 This is possible of course, but it means sending every language to each translator and you would then have to carefully manage the returns which might be more time consuming. 
 Some workarounds I know people use might be to send out the sdlxliff files and not the packages so that you just replace the sdlxliff files in each target language when you get them back. This may also require some work as you'd need to zip each on in a language annotated folder so each translator knew which one was for them. It also means your QA settings and any other requirements/assets you might have for the project will be ignored. 
 Another workaround is to send out the sdlxliff from the source language folder as this has not been given a target language yet. I know some project managers do this as well, but this carries more risk as it means the preparation of the correct target language will be down to the translator and you might have problems when you get the files back. You could experiment with this approach though as it might work for you. 
 Perhaps the best solution is to use SDL GroupShare and then the process is simpler as you don't have to manage packages for the work... you could even make use of the online editor.

Trados Studio > 1. Trados Studio

Sending project packages to multiple translators