Show Menu
TOPICS×

Create translation projects

To create a language copy, trigger one of the following language copy workflows available under the References rail in the Experience Manager user interface.
  • 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 : 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 and Adobe InDesign files, their subassets or renditions (if any) are not submitted for translation.

Create and translate workflow

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.

Create structure only

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.
  1. In the Assets interface, select the source folder for which you want to create a structure in the target language root.
  2. Open the References pane and click Language Copies under Copies .
  3. Click Create & Translate at the bottom.
  4. From the Target Languages list, select the language for which you want to create a folder structure.
  5. From the Project list, choose Create structure only .
  6. Click Create . The new structure for the target language is listed under Language Copies .
  7. Click the structure from the list, and then click Reveal in Assets to navigate to the folder structure within the target language.

Create a new translation project

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.
  1. In the Assets UI, select the source folder for which you want to create a Language copy.
  2. Open the References pane and click Language Copies under Copies .
  3. Click Create & Translate at the bottom.
  4. From the Target Languages list, select the language(s) for which you want to create a folder structure.
  5. From the Project list, select Create a new translation project .
  6. In the Project Title field, enter a title for the project.
  7. Click Create . Assets from the source folder are copied to the target folders for the locales you selected in step 4.
  8. To navigate to the folder, select the language copy, and click Reveal in Assets .
  9. Navigate to the Projects console. The translation folder is copied to the Projects console.
  10. Open the folder to view the translation project.
  11. Click the project to open the details page.
  12. 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 .
  13. Navigate to the Assets UI, and open the Properties page for each of the translated assets to view the translated metadata.
    Figure: Translated metadata in the asset properties page.
    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.

Add to existing translation project

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.
  1. In the Assets UI, navigate to the source folder that contains untranslated assets.
  2. 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.
  3. Click Language Copies under Copies . A list of available translation copies is displayed.
  4. Click Create & Translate at the bottom.
  5. From the Target Languages list, select the language(s) for which you want to create a folder structure.
  6. 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.
  7. From the Existing translation project list, select a project to add the asset for translation.
  8. Click Create . The assets to be translated are added to the target folder. The updated folder is listed under the Language Copies section.
  9. Navigate to the Projects console, and open the existing translation project you added to.
  10. Click the translation project view the project details page.
  11. Click 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.
    If you delete the entry for tags or metadata, no tags or metadata are translated for any of the assets.
    If you use Machine Translation, asset binaries aren't translated.
    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.
  12. To start the translation for the assets, click the arrow on the Translation Job tile and select Start from the list.
    A message notifies the commencement of the translation job.
  13. To view the status of the translation job, click the ellipsis at the bottom of the Translation Job tile.
  14. 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.

Update language copies

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

Create a new 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.
  1. From the Assets UI, select the source folder where you added an asset.
  2. Open the References pane, and click Language Copies under Copies to display the list of language copies.
  3. Select the check box before Language Copies , and then select the target folder corresponding to the appropriate locale.
  4. Click Update language copies at the bottom.
  5. From the Project list, choose Create a new translation project .
  6. In the Project Title field, enter a title for the project.
  7. Click Start .
  8. Navigate to the Projects console. The translation folder is copied to the Projects console.
  9. Open the folder to view the translation project.
  10. Click the project to open the details page.
  11. To start the translation for the assets, click the arrow on the Translation Job tile and select Start from the list.
    A message notifies the commencement of the translation job.
  12. 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 .
  13. Navigate to the Assets UI, and open the Properties page for each of the translated assets to view the translated metadata.

Add to existing translation project

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.
  1. From the Assets UI, select the source folder where you added an asset folder.
  2. Open the References pane , and click Language Copies under Copies to display the list of language copies.
  3. Select the check box before Language Copies , which selects all language copies. Unselect other copies except the language copy (copies) corresponding to the locale(s) to which you want to translate.
  4. Click Update language copies at the bottom.
  5. From the Project list, choose Add to existing translation project .
  6. From the Existing translation project list, select a project to add the asset for translation.
  7. Click Start .
  8. See steps 9-14 of Add to existing translation project to complete the rest of the procedure.

Create temporary language copies

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). Adobe Experience Manager 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.
  1. Click the source root folder under Language Copies for which you already created a language copy, and then click Reveal in Assets to open the folder in Experience Manager Assets.
  2. From the Assets interface, select an asset you already translated and click the Edit icon from the toolbar to open the asset in edit mode.
  3. Edit the asset and then save the changes.
  4. Perform steps 2-14 of the Add to existing translation project procedure to update the language copy.
  5. Click 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.
  6. Select the checkbox next to Title .
  7. From the toolbar, click Accept Translation and then click 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 Reject Translation to retain the originally translated version of the asset in the target locale root and reject the edited version.
  8. To view the translated metadata, navigate to the Assets console and open the Properties page for each of the translated assets.