Deepl Translator

New in 1.9.0 Glossary management !

Please report any issue using the Github repo https://github.com/brunobaudry/moodle-local_deepler/issues. DO NOT use the messaging tool bellow as we cannot manage the statuses and histrory.

Deepler is developed for those who want to translate a course all on one page without having to navigate to each module and update translations. Translation workflow being the following:

1. Set the main source language by selecting Moodle's Language (user profile menu)
2. Select the source and target languages.
3. Fine tune your ©Deepl's settings (select a Glossary for your institution jargon).
4. Choose all your course's activity text fields to translate. 
5. If needed, select a different source language for each field, should your course have multilingual content.
6. Click Send to ©Deepl.
7. Review and or amend/edit the result of the automated translations. 
8. Save translations to Moodle's DB individuallay or by batch in one click.

API Token mapping to user attributes.

Depending on you DeepL API account (Pro or Free) you can generate and use several tokens to map them to any of Moodle's user attributes, so that you can create pool's of translators to manage usage, cost control and restrict Glossaries visibility.

1. Create several tokens while logged to you DeepL API account.
2. In Moodle paste it and select a user attibute filter.

Glossaries:

• Are synched with DeepL.com
• Have different level of visibilty : Public, Pool and Private.
• Uploadable in XLS, XLSX, ODS, CSV, TSV.
• Saved with the course's language pair.
• Admin can make glossaries Private, Public or Pool (it will be shared with all translator sharing the same API token)
• Translator can set own Glossaries as Private or share with own Pool.

Multi-Language Content (v2) is a dependency of this plugin and will not work without it, as well as a FREE or PRO ©DeeplAPI account.

files are currently not yet sent to DeepL for document translation, only activities and questions' text fields.