Termbase Viewer in Studio 2017 shows terms but "No results available" in Term Recognition window and terms are not redlined in source

Question

Hi there 
 Someone else had this problem a few weeks ago. Paul asked the poster to send files to him but no solution has been posted. 
 I can't get Studio 2017 to show redlined terms that exist in the termbases, even though I can see the terms in the Termbase Viewer. The Term Recognition window shows "No results available" 
 I've looked at the article in the Knowledge Base about this problem and I reorganized the termbases in Multiterm as suggested. This did not solve the problem. 
 I do not have a problem connecting to the termbases and both Studio 2017 and Multiterm are up to date. 
 Thanks for any help or suggestions! 
 Zakiya

Paul Filkin · Accepted Answer

Aramazd Ghalamkaryan 
 Just an update on this. The product management team have confirmed this won't be fixed. It's been known since 2015 and we have still not been able to resolve it because it's so embedded into the way MultiTerm works. The focus today is on the next generation of terminology solutions which are provided by Language Cloud. 
 I tested your termbase in Language Cloud and it works in there.. for example: 
 
 So the solutions you, and anyone else working from languages not supported properly like this, are these: 
 - Language Cloud terminology 
 - TermExcelerator plugin from the appstore 
 - also worth testing other 3rd party plugins from the appstore that may work too

Paul Filkin · Answer

Hi Aramazd Ghalamkaryan 
 It looks as though there is a long standing problem that affects some unicode languages and Armenian is one of them. So this is going to require a resolution from the core development team and I don't have a timescale for this. 
 However, I do have a workaround for you which is to use the Excel Terminology Provider . This allows you to use a spreadsheet as the termbase with no conversion at all, such as the attached: 
 ARM (ARM) - ENG (US).xlsx 
 You then get this for example: 
 
 You can do everything you can with MultiTerm apart from use Term verification, so this might be a good way forward for you. 
 Regards 
 Paul

Paul Filkin · Answer

Maybe you just need to lower the match value for terms? It's hard for me to see but it doesn't look as though you have an exact match in this segment for the one you are showing in the termbase viewer.

Paul Filkin · Answer

Could it also be related to you having an en(US) project but an en(GB) termbase? Did you create the termbase with the very specific en(GB) rather than just EN? Try recreating your termbase without specifying the variants of English and see if this gives you better results?

Paul Filkin · Answer

Hi Aramazd Ghalamkaryan , 
 
Can you send me a termbase and some sample text that reflects this problem so I can look at it properly? If you can do this on small files it would be helpful. 
 
Thank you 
 
Paul

Paul Filkin · Answer

Thanks Aramazd Ghalamkaryan , the good news is I can reproduce the problem with your files. I thought at first it was due to all the tags in the source, but I removed these and still have the problem so I'll have to come back to you in due course. 
 
Thank you for the test files though, this is very helpful. 
 
Regards 
 
Paul

Paul Filkin · Answer

Dear Aramazd Ghalamkaryan , you are correct and this is because 2014 does not have the ability to use custom terminology providers. You can read about it here if you're interested: 
 
 multifarious.filkin.com/.../ 
 
Regards 
 
Paul

Paul Filkin · Answer

Hi Frank Jensen , 
 
Sounds like you need to disable lookahead: 
 
 gateway.sdl.com/.../communityknowledge 
 
That may help with your problem. 
 
Regards 
 
Paul

Trados Studio > 1. Trados Studio

Termbase Viewer in Studio 2017 shows terms but "No results available" in Term Recognition window and terms are not redlined in source

Top Replies