Elena Mazzetto

What happens if you put this termbase locally and not on an external drive?

Hi Paul,

If I move the TB to Trados' default folder and use it into the project from its new position, nothing changes.

I'm sure there's something wrong with the TB itself, but I don't know what to check on MultiTerm.

I'm going to ask a very obvious question... Is it possible the client has unticked any or all of the following boxes in Project settings before sesnding you the 3rd batch? I believe that the settings of the project on your system would be overwritten by any project settings they changed before sending you the next batch:

If the above screenprints look different to your version, it's because I've taken them from Studio 2015 as I don't have 2017 and the most recent versions/' screens would probably look more different.

I hope this is the solution...

All the best,

Ali 

Thank you Alison, now I'm a step forward to understand what is the issue with this termbase 

All the boxes in yellow in your screenshots were checked.

I tried checking the "Show recognized terms with no available translation" option as well, I rebooted Trados and now it recognizes the terms but... with no translation available 

In the termbase viewer everything looks fine, so I really don't know.

Hi again Elena Mazzetto 

If you open one of the files in the first two batches that worked OK before, is term recognition still working properly there?

All the best,

Ali

Elena Mazzetto

Does your TB contain the right target language? What are you translating from, what into, and which languages are in your TB?

Daniel

Hi Elena Mazzetto

Daniel Hug is right, if the PM sent you the wrong language pair that would cause issues. This could happen if your language pair is one of a couple or more if the job's being translated into more than one language.

Also, did you check that the Match Value and the Search Depth hadn't been adjusted incorrectly?:

Sorry this is a 2021 screenshot, to save me opening 2015... If the minimum match value slider had somehow been dragged up to 100% or the Depth dragged to 10, ah, and the repetition threshold dragged down to 2, it would give inconsistent results but not NO results...

I would recommend that you try recreating the termbase. Did you use Glossary Converter for this, if so it's not a lengthy process.

As this is an old version of Studio it could be being affected by more recent software somehow... If your Windows environment is the latest version for example.

The answer to this would be to run a Windows Repair on all the SDL components, as follows:

1. Close all SDL applications.
2. Open the Control Panel:
   • Windows Vista/7: Start > Control Panel > Programs > Programs and Features.
   • Windows 8: Right-click on the screen at bottom-left corner and choose Control Panel > Uninstall a Program.
   • Windows 10: Right-click on Start > Control Panel > Select View by: Small Icons > Programs and Features
   • - or type 'Control Panel' in the search line on your bottom Windows toolbar.
3. Click/highlight the relevant SDL product from the list (e.g. SDL Trados Studio 2017 SR1) and click 'Repair' or 'Uninstall/Change' (then Yes then Repair) either on the top toolbar or on the right-click dropdown menu.
4. Restart Studio/MultiTerm.

This iwll take longer for Studio than for the MultiTerm - I don't recall whether MultiTerm was still just one entry in the Programs list with 2017 or whether it had become 'Desktop', Core and 'Convert' in which case you only have to do these 3 and not the 'Remove suite...' entry.

See if that sorts things out for you...

All the best,

Ali

Hi Elena Mazzetto

Daniel Hug is right, if the PM sent you the wrong language pair that would cause issues. This could happen if your language pair is one of a couple or more if the job's being translated into more than one language.

Also, did you check that the Match Value and the Search Depth hadn't been adjusted incorrectly?:

Sorry this is a 2021 screenshot, to save me opening 2015... If the minimum match value slider had somehow been dragged up to 100% or the Depth dragged to 10, ah, and the repetition threshold dragged down to 2, it would give inconsistent results but not NO results...

I would recommend that you try recreating the termbase. Did you use Glossary Converter for this, if so it's not a lengthy process.

As this is an old version of Studio it could be being affected by more recent software somehow... If your Windows environment is the latest version for example.

The answer to this would be to run a Windows Repair on all the SDL components, as follows:

1. Close all SDL applications.
2. Open the Control Panel:
   • Windows Vista/7: Start > Control Panel > Programs > Programs and Features.
   • Windows 8: Right-click on the screen at bottom-left corner and choose Control Panel > Uninstall a Program.
   • Windows 10: Right-click on Start > Control Panel > Select View by: Small Icons > Programs and Features
   • - or type 'Control Panel' in the search line on your bottom Windows toolbar.
3. Click/highlight the relevant SDL product from the list (e.g. SDL Trados Studio 2017 SR1) and click 'Repair' or 'Uninstall/Change' (then Yes then Repair) either on the top toolbar or on the right-click dropdown menu.
4. Restart Studio/MultiTerm.

This iwll take longer for Studio than for the MultiTerm - I don't recall whether MultiTerm was still just one entry in the Programs list with 2017 or whether it had become 'Desktop', Core and 'Convert' in which case you only have to do these 3 and not the 'Remove suite...' entry.

See if that sorts things out for you...

All the best,

Ali

Alison Field You and Daniel Hug were both correct.

It was a language pair issue. I solved recreating the termbase from scratch (aka from the excel file I used in the first place).

Thank you all for your assistance!

Hi Elena Mazzetto, Daniel Hug and Paul Filkin!

Phew! That's a relief, I'm glad you've found the solution!

Well done to all the brains involved!

Enjoy the rest of your evening,

Ali