Marion Hartmann 

To date, what file type are you using?

The nature of how Studio works is you will always have source replicated under each target language.

But if you use the Multilingual XML FileType Studio will 

Marion Hartmann said:

matches the source files to the different target languages using the data in the file

In essence this means you have 1 XML to support 9 languages. You will still have 1 project but come to completing the project you will get back 1 fully localised XML file.

I can perhaps give you a more complete answer once I know if you have any experience with the Multilingual XML FileType 

Lyds

Hi Lydia, thanks for your reply. As I stated in my question, we are using XML files.

Multilingual XML Files are not an option for us. Our future PIM system will create one single file per target language (for example filename_de-de_fr-fr.xml to be translated from German into French), not a multilingual XML file. And even if we had a multilingual XML file, that would mean we would only be able to generate the target file once all languages are complete. This also does not suit our workflow as my translators independently have to create their target files.

Do I understand you correctly that there currently is no option available in Trados to have a file, which should only be translated into one of the target languages of a project, replicated into only said target language? Thanks again for clarifying. This would sadly mean that our company might have to look into other CAT solutions.

Marion Hartmann 

What if you took any one of these files and translated it into your nine languages? Do the files actually differ, apart from the name?

Daniel

Yes, the files are different - they not only differ in name but also in content:
They have designated target locales for import.
They also might not contain the identical source content - for example, you have three snippets to be localized, but already have the translation for one of the three snippets in French. The French file will then only contain two snippets, whereas the other files will contain all three snippets.

An obvious workaround would be to create separate Trados projects but this would create an additional management workload.

 Marion Hartmann 

You could upload all nine versions and delete from the target languages the files that don't apply to that language. Depends a bit on whether that PIM is producing a large number of files or just one per job. It's more work than before, but less work than migrating to another software!

EDIT: The Manager view does not allow you to delete files, but once that's done it does allow you to see all target languages on one screen:

Hi Daniel! Yes, that seems to be the easiest workaround. It, of course, takes more time than I'd like but if it's the way Studio works (and this won't change), then I just have to roll with it.

Thanks everyone!

Hi Daniel! Yes, that seems to be the easiest workaround. It, of course, takes more time than I'd like but if it's the way Studio works (and this won't change), then I just have to roll with it.

Thanks everyone!