Multilingual assets means assets with binaries, metadata, and tags in multiple languages. Generally, binaries, metadata, and tags for assets exist in one language, which are then translated to other languages for use in multilingual projects. Adobe Experience Manager Assets lets you automate translation workflows on assets (including binaries, metadata, and tags) to generate assets in other languages for use in multilingual projects.
To automate translation workflows, you integrate translation service providers with Experience Manager and create projects for translating assets into multiple languages. Experience Manager supports human and machine translation workflows.
Human translation: The translated assets are returned and imported into Experience Manager. When your translation provider is integrated with Experience Manager, assets are automatically sent between Experience Manager and the translation provider.
Machine translation: The machine translation service immediately translates the metadata and tags for assets.
Multilingual assets means assets with binaries, metadata, and tags in multiple languages. Generally, binaries, metadata, and tags for assets exist in one language, which are then translated to other languages for use in multilingual projects.
In Adobe Experience Manager Assets, multilingual assets are included in folders, where each folder contains the assets in a different language.
Each language folder is called a language copy. The root folder of a language copy, known as the language root, identifies the language of the content in the language copy. For example,
/content/dam/it is the Italian language root for the Italian language copy. Language copies must use a correctly-configured language root so that the correct language is targeted when translations of source assets are performed.
The language copy for which you originally add assets is the language primary. The language primary is the source that is translated into other languages. A sample folder hierarchy includes several language roots:
/content /- dam |- en |- fr |- de |- es |- it |- ja |- zh
Perform the following steps to prepare your assets for translation:
Create the language root of your language primary. For example, the language root of the English language copy in the sample folder hierarchy is
/content/dam/en. Ensure that the language root is correctly configured according to the information in Create a language root.
Add assets to your language primary.
Create the language root of each target language for which you require a language copy.
To create the language root, you create a folder and use an ISO language code as the value for the Name property. After you create the language root, you can create a language copy at any level within the language root.
For example, the root page of the Italian language copy of the sample hierarchy has
it as the Name property. The Name property is used as the name of the asset node in the repository, and therefore determines the path of the assets. (<server>:<port>/assets.html/content/dam/it/)
The touch-optimized UI provides a References panel that shows a list of language roots that have been created within Assets.
If you use this option, assets to be translated are copied to the language root of the language to which you want to translate. Depending upon the options you choose, a translation project is created for the assets in the Projects console. Depending on the settings, the translation project can be started manually or runs automatically as soon as the translation project is created.
This feature is available both for assets and folders. When an asset is selected instead of a folder, the entire hierarchy of folders up to the language root is copied to create a language copy for the asset.
If you use this option, the translation workflow runs for assets that you add to the source folder after running a previous translation workflow. Only the newly-added assets are copied to the target folder that contains previously-translated assets. No new translation project is created in this case.
In the Assets UI, navigate to the source folder that contains untranslated assets.
Select an asset you want to translate, and open the Reference pane. The Language Copies section displays the number of translation copies that are currently available.
Click/tap Language Copies under Copies. A list of available translation copies is displayed.
Click/tap Create & Translate at the bottom.
From the Target Languages list, select the language(s) for which you want to create a folder structure.
From the Project list, select Add to existing translation project to run the translation workflow on the folder.
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. Otherwise, a new project is created.
From the Existing translation project list, select a project to add the asset for translation.
Click/tap Create. The assets to be translated are added to the target folder. The updated folder is listed under the Language Copies section.
Navigate to the Projects console, and open the existing translation project you added to.
Click/tap the translation project view the project details page.
Click/tap the ellipsis at the bottom of the Translation Job tile 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.
To start the translation for the assets, click/tap the arrow on the Translation Job tile and select Start from the list. A message notifies the commencement of the translation job.
To view the status of the translation job, click/tap the ellipsis at the bottom of the Translation Job tile.
After the translation completes, the status changes to Ready to Review. Navigate to the Assets UI, and open the Properties page for each of the translated assets to view the translated metadata.
Run this workflow to translate any additional set of assets and include it in a language copy for a particular locale. In this case, the translated assets are added to the target folder that already contains previously-translated assets. Depending upon the choice of options, a translation project is created or an existing translation project is updated for the new assets. The Update language copies workflow includes the following options:
If you use this option, the set of assets are added to an existing translation project to update the language copy for the locale you choose.
When you run a translation workflow to update a language copy with edited versions of original assets, the existing language copy is preserved until you approve the translated asset(s). Assets stores the newly-translated asset(s) at a temporary location and updates the existing language copy after you explicitly approve the asset(s). If you reject the asset(s), the language copy remains unchanged.
Click/tap the source root folder under Language Copies for which you already created a language copy, and then click/tap Reveal in Assets to open the folder in Assets.
From the Assets UI, select an asset you already translated and click/tap the Edit icon from the toolbar to open the asset in edit mode.
Edit the asset and then save the changes.
Perform steps 2-14 of the Add to existing translation project procedure to update the language copy.
Click/tap the ellipsis at the bottom of the Translation Job tile. From the list of assets in the Translation Job page, you can clearly view the temporary location where the translated version of the asset is stored.
Select the checkbox next to Title.
From the toolbar, click/tap Accept Translation and then click/tap Accept in the dialog to overwrite the translated asset in the target folder with the translated version of the edited asset.
To enable the translation workflow to update the destination asset(s), accept both the asset and metadata.
Click/tap Reject Translation to retain the originally translated version of the asset in the target locale root and reject the edited version.
Navigate to the Assets console, and open the Properties page for each of the translated assets to view the translated metadata.
To create a language copy, trigger one of the following language copy workflows available under the References rail in the Assets UI:
Create and translate
In this workflow, assets to be translated are copied to the language root of the language to which you want to translate. In addition, depending upon the options you choose, a translation project is created for the assets in the Projects console. Depending on the settings, the translation project can be started manually or allowed to run automatically as soon as the translation project is created.
Update language copies
You run this workflow to translate an additional group of assets and include it in a language copy for a particular locale. In this case, the translated assets are added to the target folder that already contains previously-translated assets.
Asset binaries are translated only if the translation service provider supports the translation of binaries.
If you launch a translation workflow for complex assets, such as PDF files and Adobe InDesign files, their subassets or renditions (if any) are not submitted for translation.
You use the create and translate workflow to generate language copies for a particular language for the first time. The workflow provides the following options:
Use the Create structure only option to create a target folder hierarchy within the target language root to match the hierarchy of the source folder within the source language root. In this case, source assets are copied to the destination folder. However, no translation project is generated.
Adobe Experience Manager lets you avail cloud-based translation services from the translation provider of your choice to ensure your assets are translated based on your requirements.
You can apply the translation cloud service directly to your asset folder so they can be utilized during translation workflows.
Applying translation cloud services directly to your asset folder eliminates the need to configure translation services when you create or update translation workflows.
From the Assets user interface, select the folder to which you want to apply translation services.
From the toolbar, click/tap the Properties icon to display the Folder Properties page.
Navigate to the Cloud Services tab.
From the Cloud Service Configurations list, choose the desired translation provider. For example, if you want to avail translation services from Microsoft, choose Microsoft Translator.
Choose the connector for the translation provider.
From the toolbar, click/tap Save, and then click OK to close the dialog.The translation service is applied to the folder.
If you want to apply a custom connector for the translation services you want to use in translation workflows. To apply a custom connector, first install the connector from Package Manager. Then, configure the connector from the Cloud Services console. After you configure the connector, it is available in the list of connectors in the Cloud Services tab described in Applying the translation services. After you apply the custom connector and run translation workflows, the Translation Summary tile of the translation project displays the connector details under the heads Provider and Method.
Install the connector from Package Manager.
Click/tap the Experience Manager logo, and navigate to Tools > Deployment > Cloud Services.
Locate the connector you installed under Third Party Services in the Cloud Services page.
Click/tap the Configure now link to open the Create Configuration dialog.
Specify a title and a name for the connector, and then click/tap Create. The custom connector is available in the list of connectors in the Cloud Services tab described in step 5 of Applying the translation services.
Run any translation workflow described in creating translation projects after you apply the custom connector. Verify the details of the connector in the Translation Summary tile of the translation project in the Projects console.