Creating Language Copies for Assets

You're viewing help content for version:

6.2
Older Versions

The Language copy feature of Adobe Experience Manager (AEM) Assets lets you create translated binaries, metadata, and tags for assets and folders so they can be used in multilingual projects.

Note:

Asset binaries are translated only if the translation service provider that you choose for translation supports translation of binaries.

Automate the translation of assets to create and maintain multilingual projects. To automate translation workflows, you integrate translation service providers with AEM and create projects for translating assets into multiple locales. AEM supports human and machine translation workflows.

Human translation: Assets are sent to your translation provider and translated by professional translators. When complete, the translated assets are returned and imported into AEM. When your translation provider is integrated with AEM, assets are automatically sent between AEM and the translation provider.
Machine translation: The machine translation service immediately translates your assets.

If your translation service provider does not provide a connector for integration with AEM, use an alternative process.

To create a language copy, trigger one of the following language copy workflows available under the References rail in the Assets console:

DAM Create Language Copy

In this workflow, only a language copy is created. To translate the contents of the language copy, create a translation project manually, add assets to the project, and then trigger the translation job.

DAM Create and Translate Language Copy

This is an automatic translation workflow for a folder containing assets. In this workflow, the folder and its contents (including any underlying folder hierarchy) are copied to create a language copy. A translation project is created, and the folder contents are automatically added in the translation job for the translation project. You can then trigger the translation from the Projects console.

To orchestrate the translation of AEM assets, configure Translation Integration Framework that integrates with third-party translation services. These configurations include specifying translation method, translation provider, settings to use for translation, and authentication credentials for the translation provider.

Translation configuration

Translation configuration specifies translation project settings, including:

Which translation service provider to use.
Whether human or machine translation is to be performed.
Whether to translate other content that is associated with assets such as tags.
Whether to automatically trigger translation as soon as the translation job is created.

For Assets translation, specify these settings in the Assets tab of the Translation Configuration dialog.

Credential configuration

Credential configuration includes information required to connect with the translation provider, for example authentication credentials, project id, and so on. By default, AEM provides the capability to connect to Microsoft Translator.

For details, see Configuring the Translation Integration Framework.

This workflow provides the flexibility to create the translation project and trigger the translation workflow at your convenience because it creates a copy of the original folder or asset. You can add this copy to a translation project later.

In the Assets console, select the source folder for which you want to create a Language copy.

Click the References icon from the toolbar. The Reference pane displays the language copies that already exist for the folder under the Copies section.

Select Language Copies under Copies. The Language Copies section displays the translation copies that are currently available for the folder.

To create a language copy, click the Create option at the bottom.

From the Translation Workflow list, select DAM Create Language Copy.

From the Languages list, select the translation language.

Enter a title for the workflow.

Click Start. A language copy of the selected folder is created with the target language root as its name. If you set up a translation workflow in Italian for your source folder en containing assets with English metadata, the language copy is named it. This language copy appears under the Language Copies section in the References rail.

If the source folder has a different name, the target folder name includes the source folder name and the language root of the target locale separated by a hyphen. For example, if the name of the source folder is test, the name of the language copy folder created for Italian is test-it.

To navigate to the folder, select the language copy, and click Go to link.

When the workflow completes, a target language copy folder is created. Create a translation project and add the language copy to the translation project.

From the rail, go to the Projects console, and click the Create icon from the toolbar to create a translation project.

In the Create Project page, select Translation Project and then click Next.

In the Basic tab, enter a title for the project and an optional description.

Enter an optional due date for the project, and add members from the User list.

In the Advanced tab, select a translation language from the Target Language list.

Select Machine Translation as the translation method.

Select an appropriate translation provider and content category from the corresponding lists.

The available configurations for the selected translation provider are listed in the Cloud Config list depending on the configuration selected. Select the appropriate configuration, and then click Create.

Click Done to close the dialog. Alternatively, click Open Project to open the translation project.

From the project details page, click the ellipsis at the bottom of the Translation Job card.

Click the Add icon from the toolbar of the Translation Job page. Then, select the Language copy folder you created in step 8 of this procedure to add assets to the translation workflow.

After selecting the assets to add, click Confirm.

The assets in the language copy folder are added to the translation job. The translation job list also displays entries for asset metadata and tags. These entries indicate that the metadata and tags for the assets are also translated.

If you delete the entry for tags or metadata, no tags or metadata are translated for any of the assets.

Note:

If you use Machine Translation, asset binaries aren't translated.

Note:

If the asset you add to the translation job contains subassets, select the subassets and remove them for the translation to proceed without any glitches.

Navigate to the project details page, click the arrow on the Translation Job card, and select Start from the list to start the translation workflow.

To view the status of the translation job, click the ellipsis at the bottom of the Translation Job card.

For more details around job statuses, see Monitoring the Status of a Translation Job.

Navigate to the Assets console and open the Properties page for each of the translated assets to view the translated metadata.

Note:

This feature is available both for assets and folders. When an asset is selected instead of a folder, the entire hierarchy of folders upto the language root is copied to create a language copy for the asset.

In the Assets console, select the folder for which you want to create a Language copy.

Click the References icon from the toolbar. The Reference pane displays the Language copies that already exist for the folder under the Copies section.

Select Language Copies under Copies. The Language Copies section displays the translation copies that are currently available for the folder.

To create a translation copy, click the Create option at the bottom.

From the Translation Workflow list, select DAM Create and Translate Language Copy to run the translation workflow on the folder.

From the Translation Config list, select the translation configuration you want to associate with the translation project that gets created.

Depending upon the translation provider specified in the selected translation configuration, credential configurations for the translation provider are available in the Credential Config list. Select the credential configuration for the Microsoft Translator license.

Select the source language and the translation language from the Source Language and Target Language lists respectively. For example, select source language as English and the translation language as Italian.

To create a new translation project, select Create a new translation project from the Project list. If you want to reuse a pre-existing translation project, select Add to existing translation project.

Note:

If you choose the Add to existing translation project option, your translation project is added to a pre-existing project only if your project settings exactly match the settings of the pre-existing project. If the settings of your project is inconsistent with the settings of the pre-existing project in any way, a new project is created.

In the Project Title field, enter a title for the translation project. Also, enter a title for the translation workflow.

If the source folder has a different name, the target folder name includes the source folder name and the target language root separated by a hyphen. For example, if the name of the source folder is test, the name of the language copy folder created for Italian is test-it.

In addition to the language copy you created, a translation project with the same title is created under the Projects console. The assets in the language copy are added to the translation job in this project.

To navigate to the folder, select the language copy, and click Go to link.

From the rail, go to the Projects console to start or view the translation job.

Click the translation project to navigate to the project details page.

Click the ellipsis at the bottom of the Translation Job card to view the assets in the translation workflow. The translation job list also displays entries for asset metadata and tags. These entries indicate that the metadata and tags for the assets are also translated.

If you delete the entry for tags or metadata, no tags or metadata are translated for any of the assets.

Note:

If you use Machine Translation, asset binaries aren't translated.

Note:

If the asset you add to the translation job contains subassets, select the subassets and remove them for the translation to proceed without any glitches.

To start the translation for the assets, click the arrow on the Translation Job card and select Start from the list.

A message notifies the commencement of the translation job.

To view the status of the translation job, click the ellipsis at the bottom of the Tasks card.

For more details around job statuses, see Monitoring the Status of a Translation Job.

After the translation completes, the status changes to Ready to Review. Navigate to the Assets console and open the Properties page for each of the translated assets to view the translated metadata.

For more details around job statuses, see Monitoring the Status of a Translation Job.

Caution:

In cases where both the metadata and asset binary are required to be translated for a project, Adobe recommends that you submit the project for metadata translation only after the binary translation is complete.

If you do not follow this sequence, the metadata extracted from the binary may overwrite the metadata you submit through the translation framework.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices | Online Privacy Policy

Creating Language Copies for Assets

Creating translation configurations

DAM Create Language Copy workflow

DAM Create and Translate Language Copy workflow

Ask the Community

Contact Us