Cannot run verification on projects which reference DeepLMTProvider

Some of my colleagues (working for an LSP) are having trouble with projects which have the DeepL Translation Provider plugin listed as one of the translation providers.

What usually happens is that the project goes out to the freelancer translators, who can complete the work apparently without any problems. Then it is returned to us for finalisation. When the verification process is run, some colleagues find that the verification progress bar goes up to about 10%, then Trados Studio 2019 freezes.

The only way out of this is to kill Trados (via Task Manager) restart and proceed without any verification.

This happens whether or not the user has the DeepL translation provider installed - they shouldn't need the translation provider available for verification, should they?

Has anyone else encountered the same or similar problems?

Parents
  • Hello ,

    please clarify what you mean by...

    Some of my colleagues (working for an LSP) are having trouble with projects which have the DeepL Translation Provider plugin listed as one of the translation providers.

    ... have you not added the DeepL as a translation provider yourself? Was this already attached to the project (template) when you received it?

    If you have added the provider, then its essential to check the exact versions everyone has installed and remove any older versions from the plugin folder.

    As...

    some colleagues find that the verification progress bar goes up to about 10%, then Trados Studio 2019 freezes

    ...this would suggest this is a local issue as it is seemingly irrelevant whether you have the app installed or not.

    I think we need more information here- maybe you could attach Window log files- this often gives an insight to where the problem lies.

     

    Oana Nagy | Developer Experience | QA Engineer | RWS Group

  • Hi Steven,

    have you not added the DeepL as a translation provider yourself?

    Yes I did, but I didn't encounter the same problem even though I opened and verified the same project.

    Was this already attached to the project (template) when you received it?

    Yes, though as we're the LSP it was us who attached the DeepL translation provider.

    To clarify, one of my colleagues prepares the project and then sends it to a (freelance) translator; the translator then sends it back to another colleague who sometimes sends it to a (freelance) proofreader or sometimes proofreads it themselves. It is this second colleague who then attempts the QA verification and encounters the problem, though it is the first colleague (who prepared the project) who typically has the DeepL translation provider installed.

    I think I can obtain the Windows log files - is it the Application log file you'd like to see?

Reply
  • Hi Steven,

    have you not added the DeepL as a translation provider yourself?

    Yes I did, but I didn't encounter the same problem even though I opened and verified the same project.

    Was this already attached to the project (template) when you received it?

    Yes, though as we're the LSP it was us who attached the DeepL translation provider.

    To clarify, one of my colleagues prepares the project and then sends it to a (freelance) translator; the translator then sends it back to another colleague who sometimes sends it to a (freelance) proofreader or sometimes proofreads it themselves. It is this second colleague who then attempts the QA verification and encounters the problem, though it is the first colleague (who prepared the project) who typically has the DeepL translation provider installed.

    I think I can obtain the Windows log files - is it the Application log file you'd like to see?

Children
No Data