Term recognition problem: only the terms recognized in the first (default) termbase are shown in full

Question

Hi, please help if you could solve this problem: 
 Working environment: Windows 10 + Office 365 + SDL Trados Studio 2015 (with multiple termbases). 
 Problem: Term Recognition window within Studio (Edit) only shows full term recognition results (source + translation) from the first (default) termbase, while for the second/third termbase, the same terms are still recognized, but it shows only the source term (without translation). 
 Note: The problem remains after (1) reorganizing the termbases, and/or (2) using new termbases. 
 
 Picture below:

Pengfei Niu · Answer

Hi Yejun, This issue occurs since SR2. The previous version has no such issues. I tested myself. One workaround is that ensure the language pairs of the termbases are "exactly the same" Ivan

Paul · Answer

Hi Evzen, 
 Can you share a project and termbases for me to look at? I just quickly created this scenario and don't have any problem so I think we need to see what you have set up that I don't and then we can investigate more:

Paul · Answer

Hi Evzen, 
 
Got your project and can obviously repro in 2015 and also 2017. Will look at this with support/development as appropriate and come back to you. 
 
Thank you for sharing this project.

Paul · Answer

Hi Evzen, 
 
We raised an enhancement request, CRQ-4205, for this problem you have shown. It's a slightly unusual situation because you are using as a default termbase one that doesn't have the target language in the project. So the pair is EN-DE but you use the EN-CZ bilingual termbase as default. In a way this makes no sense since you can't add terms to that termbase anyway, but as we take termbases at All language Pairs level you don't have a lot of choice other than to change the default so we should at least show the correct results from the non-default termbase. 
 
So an easy workaround, and probably one reason we don't see this reported a lot is because it's a strange thing to do... use as default a non-matching termbase. 
 
Regards 
 
Paul

Paul · Answer

Hi Evzen, 
 
I don't disagree with you about the design... I guess one way to resolve this is use one termbase which might be acceptable given the emphasis you place on making things easy for the translator and the skills of the localization engineer. The Glossary Converter would make light work of all your excels into one multilingual termbase and then you wouldn't have this problem. 
 
Generally there is no need to lecture me, I get it. But really, given you can't even add terms to the termbase the way round you have this is it really such a bad workaround to change the default? You have to work with what you have. If you want something else don't waste your energy in here, post it into the ideas site and rally some support. 
 
Regards 
 
Paul

Trados Studio > 3. MultiTerm

Term recognition problem: only the terms recognized in the first (default) termbase are shown in full