Dear all

For those of you wondering what this is about - my issues are listed below. In desperation, I tried another plugin download and installation method this minute, and stumbled across a solution that seems to work. However, this leaves me with the question:

Is it necessary to install the Language Weaver plugin to have a third party NMT plugin work properly?

This is how I came by this conclusion:

Current status:

• My Trados Studio is set to German as display language, so bear with me, if the name of the button or feature isn't quite right.
• I moved my Trados Studio 2024 Professional license in October 2024 from my PC to my new laptop by deactivating my 2024 license and reactivating it as instructed on the Trados Website.
• I downloaded the plugins for Language Weaver and DeepL from the RWS app store directly in Trados Studio 2024.
• DeepL is listed in the TM section.
  • In DeepL settings, the API key is entered correctly.
    • The API version is set to "V1 (DeepL Advanced or Ultimate subscription)" as I'm using it as a single user.
    • The language pair is selected as  De-EnUK.
    • No DeepL glossary has been added yet.
  • In the TM section, DeepL is activated, as is the "search" function.
• I don't have a support contract with Trados/RWS.

Issue - Language Weaver:

• However, the Language Weaver plugin will not access NMT in TM section.

Issue - DeepL Pro Advanced

• The DeepL plugin is working, however, only as a "pre-translate" batch task.
• During regular segment by segment translation, the TM view immediately jumps to concordance view indicating fuzzy matches and must be manually returned to TM matches view, which only shows NMT without fuzzy matches in the defined range to be considered first.
• In older projects, created with Trados Studio 2022, however, this issue does not occur when adding a new file for translation to the project. DeepL works both as a batch task as well as when translating segment by segment. Segment-by-segment translation shows all fuzzy matches and NMT matches in the TM result view rather than just in the Concordance view.

What I have done:

• I deinstalled Language Weaver and reinstalled it through Trados Studio AppStore access point.
  
  • Language Weaver can still not be added in TM selection view of the translation project.
• To work with DeepL only, I changed my TM search settings within a translation project to get Trados to show NMT and TM matches on the same tab by (de)activating "Look for fuzzy matches, even if a 100% match is found",  "Search project and main translation memory", and "Look for segments in MT, even if a TM match is found".
  • It makes no difference other than having the display bounce back and forth erratically a couple of times until it settles on the Concordance view.
• I changed my minimum match value from 70 to 80 both in the Translation and the Concordance section and lowered the number of maximum hits hoping to get better results by matching them.
  • It makes no difference.
• The Pretranslation batch task is set to "80%" minimum match and "Use NMT if no match is found".
  • Doesn't help outside of batch task.
• I changed the generic project settings similarly as far as possible without activating TMs.
  • It makes no difference either.

What I just did in a case of inspired desperation:

• I deinstalled Language Weaver Provider in the AppStore view in Trados Studio again.
• But this time, I downloaded the Plugin in the RWS AppStore Browser, NOT from Trados Studio.
• I added the plugged in  Language Weaver to the TMs as a cloud MT - I can't remember to have been given this option before.
• I activated Language Weaver as a TM in my translation project.
  • It works now.
• DeepL seems to work now too, whether Language Weaver is activated as an MT or not.
  • Without it, the issues remain as described above.

I'm confused.

Have a nice day

Susanne