DocumentationAEM GuidesAEM Guides Documentation

Translate content id181GB0400UI

Last update: Fri Jun 07 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin

Automate the translation of page content, assets, and user-generated content to create and maintain multilingual websites. To automate translation workflows, you integrate translation service providers with AEM and create projects for translating content into multiple languages. AEM supports human and machine translation workflows.

  • Human translation: Content is sent to your translation provider and translated by professional translators. When complete, the translated content is returned and imported into AEM. When your translation provider is integrated with AEM, content is automatically exchanged between AEM and the translation provider

  • Machine translation: The machine translation service immediately translates your content

Translating content involves the following steps:

  1. Connect AEM with your translation service provider and create translation integration framework configurations.

  2. Associate the pages of your language master with the translation service and framework configurations.

  3. Identify the type of content to translate.

  4. Prepare the content for translation by authoring the language master and creating the root pages of language copies.

  5. Create translation projects to gather the content to translate and to prepare the translation process.

  6. Use the translation projects to manage the content translation process.

When your translation service provider does not provide a connector to integration with AEM, then AEM supports the manual export and import of translated content in XML format.

TIP
See the Translation section in the Best practices guide for best practices around translating content.

Configure the Translation tab on the DITA map dashboard

To hide the Translation tab on the DITA map dashboard, perform the following steps:

  1. Use the instructions given in Configuration overrides to create the configuration file.

  2. In the configuration file, provide the following (property) details to configure the translation tab on the map dashboard:

    table 0-row-3 1-row-3
    PID Property Key Property Value
    com.adobe.fmdita.config.ConfigManager tabs.translation Boolean ( true/ false).
    Default value: true
    note note
    NOTE
    This configuration is enabled by default and the translation tab is not available on the map dashboard.

Configure component-based translation workflow

If the connector for the translation vendor does not support DITA content, then the component-based translation workflow needs to be enabled. Once enabled, the translatable content is sent as asset metadata. However, the connector needs to support asset metadata translation for this workflow to work.

Based on the translation workflow used in your setup, the component-based translation workflow option should be configured. Use the instructions given in Configuration overrides to create the configuration file. In the configuration file, provide the following (property) details to configure component-based translation workflow:

PID
Property Key
Property Value
com.adobe.fmdita.config.ConfigManager
component.translation
Boolean:
- If you are using human translation, then Disable ( false) the Component-Based Translation Workflow option.
- If you are using machine translation, then Enable ( true) the Component-Based Translation Workflow option.

Configure the legacy translation workflow

It is recommended that you use the latest translation workflow, which provides enhanced performance. However, if you want to use the legacy translation workflow, you can configure it.

Use the instructions given in Configuration overrides to create the configuration file. In the configuration file, provide the following (property) details to configure the legacy translation workflow:

PID
Property Key
Property Value
com.adobe.fmdita.config.ConfigManager
translation.workflow.version.legacy
Boolean:
- If you use the latest translation workflow, then Disable ( false) the Run legacy translation workflow option. The latest translation workflow is enabled by default.
- If you use the legacy translation, then Enable ( true) the Run legacy translation workflow option.
NOTE
If you are using translation connector, then ensure that you have configured the connector as described in the Configuring the Translation Integration Framework topic in Adobe Experience Manager documentation.
IMPORTANT
After setting up the translation configurations, ensure that you set up the appropriate Cloud Configuration on the language folders.

Configure post-processing of temporary language copies

When you initiate the translation workflow, the system creates temporary language copies of the source content. You can choose to enable or disable the post-processing operation on these temporary files. In the post-processing operation, the incoming and outgoing references from the files are resolved, the document state is set, along with other operations. If you enable post-processing on these temporary files, the translation process could take longer time to complete. Therefore, it is recommended to keep post-processing option disabled.

Use the instructions given in Configuration overrides to create the configuration file. In the configuration file, provide the following (property) details to configure post-processing of temporary language copies:

PID
Property Key
Property Value
com.adobe.fmdita.config.ConfigManager
postprocess.temporary.langcopies
Boolean:
- If you do not want to run the post-processing operation on the temporary files, then Disable ( false) the Post-process language copies option.
- If you want to run the post-processing operation on the temporary files, then Enable ( true) the Post-process language copies option.
Default value: false
recommendation-more-help
11125c99-e1a1-4369-b5d7-fb3098b9b178