• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 391 subscribers
  • Views 1500 views
  • Users 0 members are here
Options
Related

DeepL in Project Automation

Robert Bevington

Hi everyone,

we have a Project Creation tool that we use to automatically create SDL Studio projects. This works great. And we really appreciate that this sort of stuff is possible. We've recently been trying to include DeepL as part of the pre-translation process. Initially we thought all we had to do was add DeepL as translation provider to the project template. This works fine for manually created projects. However, when I run the project creation process via our tool, PerfectMatch and Pretranslate from TM run fine. But there are no DeepL (NMT) translations. If I then run Pretranslate manually on the project, then the DeepL works. So this proves that DeepL is properly configured in the project settings.

What are we missing? Is this a limitation in the DeepL versions? We have a DeepL Pro account and a DeepL API account. We are using the DeepL Pro account in the project template. Is it not possible to automate project creation and have DeepL run automatically as part of the pre-translation process?

Thanks for any help.

Rob 
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi Rob,

    I just recently dealt with something like this myself, so maybe I can help you out.

    Did you make sure to add the DeepL URI and your API Key to the credential store? You can do so by calling FileBasedProject.Credentials.AddCredential(Uri uri, string yourApiKey)

    The DeepL Plugin checks the credential store using some uri defined in the PlugIn resources. I believe the default uri is now "deepltranslationprovider:///".  In my case, the uri that we used when storing the credentials was wrong, but changing it to 'deepltranslationprovider:///' fixed the problem.

    Best

    Laurent
Reply
  • 0

    Hi Rob,

    I just recently dealt with something like this myself, so maybe I can help you out.

    Did you make sure to add the DeepL URI and your API Key to the credential store? You can do so by calling FileBasedProject.Credentials.AddCredential(Uri uri, string yourApiKey)

    The DeepL Plugin checks the credential store using some uri defined in the PlugIn resources. I believe the default uri is now "deepltranslationprovider:///".  In my case, the uri that we used when storing the credentials was wrong, but changing it to 'deepltranslationprovider:///' fixed the problem.

    Best

    Laurent
Children
No Data