Localize Content Items From the Assets Page

You can localize a content item or a batch of content items when viewing the Assets page.

For information on adding a language to a content item, see Review and Add Languages to a Content Item.

To export an asset or assets for translation:

  1. Click Assets in the side navigation menu to see assets available to you. Select the repository of the asset or assets you are localizing.
  2. Select the asset or assets you want to export for translation. You can select individual assets from the Assets page, or a whole collection of assets from the Collections page.
  3. Click Translate. You may need to first click More and then select Translate.
  4. Enter information for the batch of assets you’re exporting — the translation job, and then click Create:
    1. Enter a name for the translation job.
    2. Select the source language.
    3. Select the target languages into which these assets will be translated.
    4. Choose whether to export the translation package for manual translation, or select a translation connector to translate the package.
    5. Click Create when done.
  5. If translating the content using a content connector, an import option is available when the translation job has finished. Click More Menu and select Translation Jobs to see a list of jobs, then right-click on the finished translation job and select Import.Translation Connector Import Option
  6. If manually translating the content, after the translation job has finished, download the .zip file of the exported assets. Click Translation Jobs in the banner, select the translation job, then click Download.

The export .zip contains job.json and a root folder containing a <asset_GUID><asset_name>.json file for each asset you exported, the source language file.

If manually translating the source language files:

  1. For each language you selected as a target language, create a folder in the .zip file, for example, de, es, and fr. If the translation job was created prior to December 2018, you must include a folder for each language you selected when creating the translation job. If the translation job was created after December 2018, you can translate a subset of the selected languages. For example, you could translate into German (de) now, and then translate into Spanish (es) and French (fr) at a later time.
  2. Copy all the <asset_GUID><asset_name>.json files from the root folder to each language folder.
  3. Translate the strings in all of the <asset_GUID><asset_name>.json files to the appropriate languages. Do not delete any strings from the .json files, and do not rename the files.
  4. Zip up the job.json, root, and all the language folders with the translated files.

After translating the assets, import the translations:

  1. On the Translation Jobs page, click Import.
  2. If the translation package was translated automatically using a translation connector, the validation process begins.
  3. If the translation package was translated manually, click Upload, select the .zip file of translated assets, then click OK.

    Oracle Content and Experience validates that all the translations that are defined in the job are available in the .zip file. If you want to see which assets are included in the translation job, click the link in the dialog.

  4. When you're ready to import the translations, click Import.

    The status of the import appears above the banner. You can view the details of the job by clicking Details.

See also Localize Content Items and Manage Asset Translation Jobs.