Johannes Purer 

Hi Johannes,

You need to have precisely the right version of MultiTerm for the version of Studio that you are using, or term recognition may not work correctly.

The easiest way to achieve this is to have the most recent version of both.

You can download it from My account > Downloads

I hope this helps!

All the best,

Ali

 Johannes Purer 

I should also add that I don't know for sure if my suggestion will resolve your language variants issue, it's just that I noticed you don't have the correct version of MultiTerm.

Hi Ali,

thanks for your quick reply.

No, the Multiterm version is not the solution, it does not matter to have MT 2021 or 2022 next to Studio 2022. The result is the same.

Do only we experience this issue, I can't imagine we are the only ones with that problem?

Regards,

Johannes

Johannes Purer 

Hi Johannes,

My way of avoiding a term from another language variant being displayed would be to have separate termbases for each language variant.

However, you may find the following article in the Community Knowledge base helpful:

Managing sublanguages in a termbase in Multiterm

All the best,

Ali

 Johannes Purer 

the easiest way is you set up your termbase so that the variants are attributes and not actually sub-languages. This article refers:

https://multifarious.filkin.com/2014/04/08/yanks-versus-brits

Paul 

Brilliant, Paul, I knew you'd be able to help but didn't tag you because I know you're on holiday...

Thanks!

Ali

Hi Paul,

thanks a lot for your reply.

This procedure might make sense, when you start a termbase, but we already have several hundred terms in our database, with languages in various variants (English, Chinese, Portuguese, to name a few). I do not want to set up the termbase from scratch, as I am not sure if exporting and importing would work with all fields in that database smoothly.

Generally, what's the purpose of offering the variants in Multiterm, when Studio does not recognize them?

I select a variant, let's say PT-BR, in Studio, and I have that variant in Multiterm, why does it not just look up in PT-BR? Why does it then look up PT-PT terms? It just could be dealt with like another language, as for example FR-FR would be as well (those terms are not displayed).

I do not understand the concept, there might be a reason, which I have not realized yet.

Thanks,

Johannes

Hi Ali,

yes, that would be an option, but we have several multi-language projects, sometimes up to 30, so it's easier to handle, when all these languages are in one database, as that way cross-references between all these languages are possible.

Unfortunately I cannot see this article you are referring to.

Regards,

Johannes

 Johannes Purer 

Hi Johannes,

Here's the link again, hoping it works for you this time; make sure you're signed in first:

https://gateway.sdl.com/apex/communityknowledge?articleName=000001143

 Paul  is better than I, to advise you on this topic...

Also, Gerhard Kordmann  who created the wonderful 'Glossary Converter' app, may be able to advise. I frequently use Glossary Converter to export a termbase to Excel so that I can remove the languages that I don't want in the termbase, then I can import it back to a MultiTerm termbase or first remove duplicates for example. I've never come across the need to remove or export language variants.

As I said, Paul will be able to advise better than I.

All the best,

Ali