When you export content items for translation, a translation job is created. You can then download the files for translation, translate them, and then import the translated files.
Before you can manage a translation job, you need to export assets. See Localize Content Items.
(Ready) - The .zip file of exported assets is ready to be downloaded.
(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) - The translations for all targeted languages for this job have been imported successfully.
(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, all the selected targeted languages, any additional data fields included in the translation, and the status of those translations.
- To download the .zip file of exported assets for a job, 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 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. 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.
Create Custom Locales for Translation
If you are a developer for your organization, you can create custom locales for translation.
Click Content in the Administration section of the side navigation menu.
Select Localization Policies from the banner menu.
Click Languages in the banner.
Select the base language code with whatever regional dialect code you want to use for your custom locale.
Enter the custom locale tokens in the field next to the base code. Custom local tokens cannot be more than 8 characters, but any number of tokens can be entered when separated by a dash. Only alphanumeric characters (A-Z and 0-9) are valid.
Enter an optional description. If no description is entered, the default is to display the base language code description.
For example, if you select Portuguese (Brazil) (pt-BR) as your base code and dialect, you can enter custom-south-america as your tokens. The resulting custom locale displayed in the Language Code list would be pt-BR-x-custom-south-america. If no description was entered, then the description for the custom locale would be Portuguese (Brazil). If a description of Portuguese South America was entered, then that would be displayed as the description.
Click Add. The custom locale is now available when creating localization policies.
To delete a custom locale, click next to the custom local type in the Language Code list.