Virginia Seggiaro 

If you want to work that way with a separate termbase for each language rather than use a multilingual termbase (which is probably better), then don't use All Language Pairs.  Use specific language pairs for each language pair.

Hi Paul 

If I use specific language pairs for each language as shown in the screenshot below and upload the termbase in the "Termbases" section, the result remains the same—the first termbase I upload becomes the default one.

Would the best option be to create a separate project for each language rather than one for all languages together? Up until now, I’ve been creating a single project and then generating different packages from it.

Also, I have another question: I’ve created a unilingual glossary with the following fields: Language, Clarifications, and Screenshot. The Language field contains the source language (English). When creating projects for different target languages, I’d like to add both this unilingual glossary and the second termbase I’m asking about above. What would be the best way to handle this in Trados Studio?

Thank you,

Virginia Seggiaro 

Virginia Seggiaro said:

Would the best option be to create a separate project for each language rather than one for all languages together? Up until now, I’ve been creating a single project and then generating different packages from it.

The best option would be for you, as the agency, to use a cloud solution where you can provide access to a multilingual termbase that all your translators can access.

But if you can't do that, then the next best option would be to create a single multilingual termbase and share that to each one in the packages.

But if you really want to send them their own bilingual termbase then either send the termbases separately with the packages, or create separate projects as you suggested.

Virginia Seggiaro said:

Also, I have another question: I’ve created a unilingual glossary with the following fields: Language, Clarifications, and Screenshot. The Language field contains the source language (English). When creating projects for different target languages, I’d like to add both this unilingual glossary and the second termbase I’m asking about above. What would be the best way to handle this in Trados Studio?

Just add the one termbase so all translators get it.

You seem to be doing some weird stuff here!

Virginia Seggiaro 

Virginia Seggiaro said:

Would the best option be to create a separate project for each language rather than one for all languages together? Up until now, I’ve been creating a single project and then generating different packages from it.

The best option would be for you, as the agency, to use a cloud solution where you can provide access to a multilingual termbase that all your translators can access.

But if you can't do that, then the next best option would be to create a single multilingual termbase and share that to each one in the packages.

But if you really want to send them their own bilingual termbase then either send the termbases separately with the packages, or create separate projects as you suggested.

Virginia Seggiaro said:

Also, I have another question: I’ve created a unilingual glossary with the following fields: Language, Clarifications, and Screenshot. The Language field contains the source language (English). When creating projects for different target languages, I’d like to add both this unilingual glossary and the second termbase I’m asking about above. What would be the best way to handle this in Trados Studio?

Just add the one termbase so all translators get it.

You seem to be doing some weird stuff here!