You're viewing help content for version:
- 6.4
- 6.3
- 6.2
- Older Versions
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.
Note:
Asset binaries are translated only if the translation service provider supports the translation of binaries.
Note:
If you launch a translation workflow for complex assets, such as PDFs and 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:
- Create structure only
- Create a new translation project
- Add to existing translation project
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.
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.
-
To view the status of the translation job, click the ellipsis at the bottom of the Translation Job tile.
For more details around job statuses, see Monitoring the Status of a Translation Job.
-
Navigate to the Assets UI, 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.
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.
-
From the Project list, select Add to existing translation project to run the translation workflow on the folder.
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. Otherwise, a new project is created.
-
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.
Note:
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 includes subassets, select the subassets and remove them for the translation to proceed without any glitches.
-
To view the status of the translation job, click/tap the ellipsis at the bottom of the Translation Job tile.
For more details, see Monitoring the Status of a Translation Job.
Run this workflow to translate any additional set of assets and include it in a lanugage 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:
- Create a new translation project
- Add to existing translation project
If you use this option, a translation project is created for the set of assets for which you want to update a language copy.
-
To view the status of the translation job, click/tap the ellipsis at the bottom of the Translation Job tile.
For more details around job statuses, see Monitoring the Status of a Translation Job.
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). AEM 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.
-
Perform steps 2-14 of the Add to existing translation project procedure to update the language copy.
-
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.
Note:
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.
For tips on translating metadata for assets efficiently, see 5 Steps for Efficiently Translating Metadata.