- PHP 8.2+
- Moodle 4.2+
- Only supports 2 letter locale codes.
- Limited multilang ({mlang}) support. This filter will process your existing translations in mlang. See the Multilang Support section for more information.
- This filter only supports languages supported in DeepL.
- Unzip the plugin in the moodle .../filter/ directory.
This plugin is in an Alpha state and it is highly recommended that you backup your database before installing and enabling this plugin.
This autotranslation filter does not alter the original text of any of your content on Moodle. It stores all source and target text in a translation table. The filter works by retrieving the source text from the translation table after it has been saved for the first time. If in the event something goes arwy, disable the filter and all of your original text will be restored immediately.
You need to consider your database performance and size when using this plugin. It will effectively double the size of your database if every page of your Moodle site is visited because all source text is being saved as a reference.
This plugin provides limited support for multilang and multilang2. A custom parser has been written to find existing translations on your website and store those in the autotranslate table instead of fetching new translations from DeepL. You should enable the translator on each context where you have used multilang in the Autotranslate filter settings.
If you choose to leave the Multilang and Multilang 2 filters on, you need to do some database prepwork before enabling the Autotranslate filter. You should have a default site language set and know the 2 letter local code for that language. We will use en (English) as an example.
Navigate to /admin/tool/replace and perform a search and replace across your entire database for any {mlang en} tags and replace them with {mlang other}. It goes without saying that you should backup your database before performing this step. This can also be done via the CLI. This step is needed for the Autotranslate filter to work correctly. The other lang code is needed so that text can be referenced for pages without a translation.
This filter was developed against a production database where mlang had been wildly used. It is impossible to account for every variation of how someone might have used {mlang} tags and whether they used them properly. This filter requires that you have only used a single {mlang} tag per translation in your content using the following format:
{mlang other}Hello{mlang}
{mlang es}Hola{mlang}
{mlang fr}Bonjour{mlang}
This filter does not support the following structure:
Moodle
{mlang other}Hello{mlang}
{mlang es}Hola{mlang}
{mlang fr}Bonjour{mlang}
{mlang other}Goodbye{mlang}
The word Moodle would be stripped out from your translation and you would end up with the words Hola, Bonjour, Goodbye in the translation table. The first Hello would be lost because of the duplicate "other" key.
This plugin uses DeepL to autotranslate content on your Moodle site into any of the languages that DeepL supports. The source language is always your Moodle default site language. The target language are any of the languages that are not your default site language.
You can signup for a free or pro version key of DeepL's API. This plugin utilizes the official DeepL PHP client library for connecting to the API. You will need to enter your DeepL API key under the Autotranslate filter settings before this filter will work.
- Go to "Site Administration >> Plugins >> Filters >> Manage filters" and enable the plugin there.
- It is recommended that you position the Autotranslate Filter at the top of your filter list and enable it on headings and content.
There are two scheduled tasks that run every minute that can be configured in the Autotranslate Filter settings. The first task is an autotranslate job that translates any content loaded that is not your Moodle default site language. For example, if someone selects Spanish in the language switcher, and the default language of Moodle is in English, each line of text of the page visited will be queued for autotranslation. In the first minute after content on a page has been queued, the default site language will be served but after the autotranslate job has finished, the autotranslated version of the page will be served and become available for editing on the Autotranslation Management screen. By default, 200 strings are translated per minute using this scheduled task.
Running from the CLI:
php admin/cli/scheduled_task.php --execute='\filter_biblelinks\task\autotranslate_task'This filter provides a string management interface for translators to manually adjust autotranslations at /filter/autotranslate/manage.php. If the identical string shows up in multiple places on your Moodle site, you only need to translate the string once. This is useful for items like blocks, additional navigation, etc. You can select the different contexts you want to translate under the Autotranslate filter settings.
You can also find a link in each course to translate only the content found in the course under "More >> Manage Autotranslations."
The second scheduled task syncs a local copy of your Autotranslation glossary to DeepL for any language combinations supported by DeepL.. You can manage your glossaries at /filter/autotranslate/glossary.php. To create a sync job, you will need to click "Sync Glossary" on the Glossary Management page for the selected source and target language pair.
Running from the CLI:
php admin/cli/scheduled_task.php --execute='\filter_biblelinks\task\sync_glossaries_task'# checks that the requested translation has a source text available
php admin/cli/scheduled_task.php --execute='\filter_biblelinks\task\check_source_task'