Autotranslator

Use Case

The management of multilingual metadata is essential for a successful marketing campaign and a personalized customer approach. You therefore create, save and manage numerous assets in different languages. However, the manual effort is enormous, especially if you want to manage many languages.
The Autotranslator extension offers a suitable solution for the automatic translation of metadata from assets and nodes into different languages. The differences between Autotranslator for Microsoft Azure and Deepl are limited to the translation service used, with the actual translation mechanism being identical.

If a text is entered in an information field of the type "localized text", the entries for the other languages are automatically translated if this was not previously the case.

Initially, the preferred languages are checked in a fixed order. If an information field with text content is found, this text in the corresponding language is used as the source for the translations. Otherwise, the default language will be applied.

Use
AT en 1

Automatic translation for information fields

  1. Open the context menu on the asset to edit the metadata.
  2. Maintain the main language and save the changes.
  3. Refresh the page so that the automatically translated text fields appear.
AT en 2

Automatic translation when creating a node

  1. Create a new node using the context menu.
  2. Maintain the metadata in the CELUM default language (mandatory).
  3. The node has been translated into all available languages

Adjust translated values afterwards

If necessary, translated values can be subsequently adjusted by the user after automatic translation. There will be no new automatic translation. If a completely new translation of an information field is to be made, the contents for the respective languages can be deleted. Afterwards it is possible to enter the required translations.

Initial translation

An administrator can start an initial translation via the system task.

Configuration

Mandatory data:

  • Set which translation service – Microsoft or Deepl – you want to use.
  • Specify the URL of the translation service.
  • Connect the subscription or API key.
  • Set the region where the translation subscription was created (Microsoft only).

For more details see Installation for Microsoft, Deepl or in Properties.

Permission

The authorization is done via a separate user group of the extension.

Optimize your translation workflow

Use the ability to seamlessly translate asset metadata