Mats Linder

Mats Linder said:

It seems that when I don't add a cloud-based termbase as a stand-alone resource, Studio says "No open termbase" even if the translation engine contains one. 

Correct.  This is a work in progress.  Translation Engines are not properly supported in Studio yet so you have to manually add the cloud termbase.  If you open the file for translation in Studio from the Language Cloud interface then you'll find that the termbase is added automatically, so even there this needs to happen for Studio to be able to use it.

Mats Linder said:

What I was trying to check is how hits in a termbase in an engine are presented. It seems they are not presented at all, unfortunately. (I've already discovered that hits in a TM which is contained in a translation engine are simply indicated by "NTM", so there is no way to differentiate between such hits and the hits in an MT engine also contained in the translation engine -- which is a pity.)

You're incorrect here Mats.  I did a small test using your post as the source and added a translation engine that contains the following:

• TM, populated a little
• DeepL (add-on in the cloud)
• SDL MT (from the cloud)
• Termbase, populated a little

This is what I see:

The numbers represent these:

1. TM result using the same context as Studio
2. DeepL result.  Unfortunately Studio doesn't see this as NMT which it should do.  This is a bug that needs fixing.
3. SDL MT result.
4. Terminology results
5. Fully translated file populated in the online editor by me

The other point to note here is that the translation details will tell you where thing came from:

This isn't very helpful as it doesn't tell you which MT engine was used or which translation memory.  It only tells you which translation engine provider, which I called MatsLinder.  I think this could (read as should) be improved by adding this information into the metadata of the TM in the translation results view as well as in these translation details (Luis Lopes Patrik Mazanek)

And it's further confused because the SDLXLIFF correctly contains this for DeepL where the result was inserted as NMT by Language Cloud in the Online Editor and the specific MT engine noted:

So no surprise you're confused.  We have a lot of inconsistency here that needs to be resolved between Language Cloud and Trados Studio.  Finally, hots from the termbase are not represented in the Translatin Results pane.  They are represented as shown above in 4.  You can see where the termbase came from here: