Hello,

Yes, there is a quicker way to enable or disable term recognition in the editor view without going into the project settings. Here are the steps:

Step 1: Open your document in the Editor view.

Step 2: Go to the "Termbase Search" view. If it's not visible, you can enable it by going to the "View" tab and selecting "Termbase Search".

Step 3: In the "Termbase Search" view, you will see a list of your termbases.

Step 4: To disable a termbase, simply uncheck the box next to it. To enable it again, check the box.

This way, you can quickly enable or disable term recognition as needed without having to go into the project settings each time.

I hope this helps! If you have any other questions, feel free to ask.

Best regards,

TradosAI

It's about the same as going to the "project settings". I wanted to know if there was some way to enable/disable term recognition in one click (like one box to tick in the editor view..).

It's about the same as going to the "project settings". I wanted to know if there was some way to enable/disable term recognition in one click (like one box to tick in the editor view..).

 Olivier 

There is no "one click" option but what I would suggest is the following:

1. Keep your termbase well maintained which means lots of different things
   1. Splitting it
   2. keeping it well maintained by reorganising it

Other things to conciser: Cloud terminology may prove more sustainable given the size of your termase 

Alternatively dont use integrated terminology for random lookups

MultiTerm Widget will give your term lookups outside of your project

Lyds 

Olivier 

Taking Lydia's idea a bit further, you could

a) not add your termbase as a project resource, no lookups, better performance

b) Write a little AHK script that when you select a word in the source segment and press a hotkey you define, MultiTerm is activated and performs the search.

That's quite simple. Maybe it helps solve your termbase-related issues.

But do give the cloud termbase a try.

 Daniel Hug
Your script idea is what the Widget would do so either way - the ideal would actually would be to have term lookups via the term viewer pane WITHOUT active term recognition .

Lydia Simplicio TBH, my TB makes this widget crash. I would love to use it esp. for colleagues who use Word to write copy, but it just does not work for us. Look and Feel is a bit like Windows 95… I liked it when I first used it in 2018, but as I said, it's not working for me any more.

I did find a sweet way to look up a term with one keystroke. You mark a term in source or target segment, then press:

CTRL C

ALT V

T

3

Shift Pos1

CTRL V

Enter

I programmed the macro into my Microsoft Natural Keyboard onto the"Search" key, works sweetly. You can surely do it in AHK, put it on a mouse button or in 1000 other ways as well. Total execution time is slightly under 1 second.

Daniel

Hi Daniel,

That's a great idea! That would compensate for the keyboard shortcut called "Termbase Search" (Ctrl+Alt+I), which doesn't work (see  Termbase lookup : only display a source term when I click on it and https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/39249/shortcut-to-search-within-tb).

I will try you key combination with AHK and let you know.

Have a nice day!

Olivier

Love it Daniel Hug  and Olivier 

I tried this is AHK

^!::  ; CRTL + l
Send ^c
Send !v
Send t
Send 3
Send {End}
Send +{Home}
Send {Del}
Send ^v
Send {enter}
return

And when pressing "CTRL L", the highlighted word is searched in the termbase panel. Excellent! (I'll try something more direct, like pressing both mouse buttons at the same time or pressing the wheel...).

In my release there's an "error sound" playing though. I'll have to tweak this a little, but basically it does the job. 

Thanks again.

Olivier 

Often the requirements of translators can be extremely specific so that no standard solution can meet them all. I think many users found that AHK is a very useful tool to create amazing functionality very quickly. My experience with AHK is that you need to build in delays (Sleep, 100 or Sleep, 250) basically between each keystroke. Otherwise, the keystrokes are so fast that the UI stumbles and does not register this or that keystroke. That can even be for ^c or the like. If you run into problems with that, you might have to say explicitly “Press CTRL, wait, then press c, wait, then release CTRL”.

You might also want to restrict this macro to running only in Studio and to never have more than one active instance.

Thank you Daniel.

Interesting. I'm going to try the delays to give the editor some time between commands. This will help, as my AHK macro doesn't always work. It probably needs some tweaking.

Well the current AHK macro (for "CRTL !") looks like this.

If no word is selected, the word under the cursor is searched in the TB, otherwise the selected word(s) is/are searched.

The macro makes sure that the focus is in Studio when it is run.

#SingleInstance Force
#IfWinActive, ahk_exe SDLTradosStudio.exe  ; Only active when TRADOS is active

^!::  ; CRTL + !

Suspend, On

clipboard := ""  ; Start off empty to allow ClipWait to detect when the text has arrived.
Send ^c ; Try to copy to the clipboard
Sleep 200

; If nothing was copied to the clipboard, select the current word and copy it to the clipboard
If (clipboard = "")
{
	;Clipboard does not contains data
	Clipboard := ""
	Send ^{Left}^+{Right} ; select current word
	Sleep 100
	Send ^c               ; copy selection to the clipboard
	Sleep 250
}

Send !v ; ALT V
Sleep 150
Send t  ; T
Sleep 150
Send 3  ; 3
Sleep 150

; we are in the Termbase Search panel
; Clear the content of the search box
Send {End}
Sleep 100
Send +{Home}
Sleep 100
Send {Del}
Sleep 100

; copy what's stored in the clipboard
Send ^v

; execute search
Send {enter}

Suspend, Off

return