Manage Site Translation Jobs

When you select a site for translation, a translation job is created. You can then download the files for translation, translate them, and then import the translated files.

To create a translation job, see Translate a Site.

The Translation Jobs page lists all translation jobs and their status:
  • Ready status icon (Ready) - The .zip file of site files is ready to be downloaded.
  • In progress status icon (In Progress) - The .zip file has been downloaded. The status will remain in progress until all translations for all targeted languages have been imported successfully.
  • Complete status icon (Complete) - The translations for all targeted languages for this job have been imported successfully.
  • Failed status icon (Failed) - The translation job failed. You should have seen a failure message above the banner about why the job failed. If you need to see the message again, you can Resubmit the translation job. Correct the problem, then Resubmit the job.

You can perform the following actions:

  • To view the details of a translation job, open it. The details include the source language and all the selected targeted languages, and the status of those translations.
  • To download the .zip file of site files, select the job, and click Download.
  • To delete a job, select the job and click Delete.
  • To import translations, click Import, then click Upload, select the .zip file of translated site files, 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 site pages and assets are included in the translation job, click the link in the dialog. When you're ready to import the translations, click Import.

Locales for Translation

When submitting an item for translation the target language is identified by a code so the language service provider knows what language to translate the item into and return. For example, fr represents French and de represents German.

These codes can be extended for more regional dialects. For example, de-LI is the code for German as it is spoken in Liechtenstein and de-LU is the code for German as it is spoken in Luxemburg. But if the language service provider doesn't support a regional dialect, then the code provided is truncated to the two character base language. For de-LI and de-LU the code would be truncated to de, for example.

If the language service provider supports one regional dialect but not all, it may substitute. For example, ms-BN is the code for Malay as spoken in Brunei, but if the language service provider doesn't support that dialect, it may switch to a dialect it does support, such as ms-MY, which is the code for Malay as it is spoken in Malaysia. If the language service provider doesn't make a distinction between dialects, for example en-BZ for English as spoken in Belize and en-JM for English as spoken in Jamaica, then it will truncate to the base language, in this case en for English.

Custom Locales for Translation

Custom locals may be created by a developer based on your organization's needs. Custom locale codes include the base language, any regional dialect code if applicable, an x to designate it is a custom locale, and whatever other identifying customization is required by your organization. For example, a custom local for English might look like en-JM-x-custom.

Because a custom locale is unique to your organization, custom locale codes are truncated when submitted for translation to the base language and the regional dialect if supported by the language service provider. In the example above, en-JM-x-custom would be truncated to en-JM, eliminating the portion of the code specific to the customization. Or if the language service provider does not support the regional dialect code for Jamaica (JM), it may be truncated to just the base language, en.

Set Locale Alias for URL Redirect

You can easily set an alias for locales that is used in a site URL at runtime and the runtime preview. This is especially useful if your organization makes use of custom locales that can be long and add complexity to a URL.

For example, you may have a custom locale defined as en-GB-x-cornish, which in the URL would look like this:
https://example.com/site/BlogSite/en-GB-x-cornish/home.html

By adding an alias, you can redirect to a simpler URL:

https://example.com/site/mysite/en/home.html
  1. Open a site for editing.

  2. Click Settings icon in the sidebar and then click Locales.

    A list of all locales used in your site is displayed next to corresponding URL Alias fields.

    Locales Settings

  3. Enter an alias next to each site locale you want an alias for, click Close, and then Save.

  4. To preview the alias used in the URL at runtime, clickthe Preview icon

  5. When you publish the update, the changes are published and put into use.