From what I understand, in such situation both terms shall be in "German" and then you can add a field to differ the sublanguage. Otherwise German Germany and German Switzerland ARE two different languages.

Dear Jerzy, thank you very much. Your reply confirms what I feared, and which I see as a bad shortcoming in MultiTerm. I wouldn't say that German as spoken in Germany and as spoken in Switzerland are 2 separate languages from a linguistical point of view.

Well, it really depends how your TB is organized. If you create a TB with just German, English, Portuguese and so on and then add a field for example at the index level, making it a picklist, you'll be simply able to add the extra information on sublanguage where necessary, while keeping the TB simple.

For example Auto or Schraube will be the same in all German languages, so there is no need to enter this in three different sublanguages.

Well, it really depends how your TB is organized. If you create a TB with just German, English, Portuguese and so on and then add a field for example at the index level, making it a picklist, you'll be simply able to add the extra information on sublanguage where necessary, while keeping the TB simple.

For example Auto or Schraube will be the same in all German languages, so there is no need to enter this in three different sublanguages.

Yes, this is a practical and clever workaround. Of course I never meant to have DE-DE=Auto and DE-CH=Auto in the same concept-entry, althought this is apparently what Multiterm (and Studio) would like to see.

I am not a linguist, just a mechanical engineer, working as a translator. For me, terminology has just one purpose: to serve me to translate easier, faster and better. For this reason I tend to see it very simple. This is why I never would create a TB for EN-GB and EN-UK separately, but would have put both together. Things are certainly different if you are a terminologist. But in that situation I cannot help, as I have no concept how to achieve what you request.