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.

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.