Oracle® Fusion Applications Extensibility Guide 11g Release 6 (11.1.6) Part Number E16691-08 |
|
|
PDF · Mobi · ePub |
This chapter describes how to localize the changes that you make to Oracle Fusion applications using Page Composer and CRM Application Composer. It also describes how to localize your navigator menu customizations and your descriptive flexfield and extensible flexfield configurations.
This chapter includes the following sections:
Section 16.2, "Translating Resource Bundles from an MDS Repository"
Section 16.3, "Translating Page Composer and CRM Application Composer Customizations"
Section 16.5, "Translating Flexfield and Value Set Configurations"
If your Oracle Fusion Applications are running in different locales, you can localize your customizations such that end users see the custom text in the language of their locale. End users set their locale when they log in. Users can also set their locale by choosing Set Preferences from the Personalization menu in the Oracle Fusion Applications global area.
Most user interface text is made available to applications through resource bundles. These resource bundles are stored in an Oracle Metadata Services (MDS) repository in XML localization interchange file format (XLIFF). To provide locale translations for your Page Composer, CRM Application Composer, and navigator menu changes, you export, edit, and import XLIFF documents. For flexfield and value set configurations, you provide locale translations using the appropriate maintenance tasks.
For information about XLIFF documents, see the "Manually Defining Resource Bundles and Locales" section in the Oracle Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition).
You use the Oracle WebLogic Scripting Tool (WLST) exportMetadata
command to obtain XLIFF documents and you use the WLST importMetadata
command to import XLIFF documents into an MDS repository. For information about MDS Repository and the exportMetadata
and importMetadata
commands, see the "Managing the Metadata Repository" chapter in the Oracle Fusion Middleware Administrator's Guide.
Tip:
You can also use Oracle Enterprise Manager Fusion Applications Control to import and export the XLIFF documents from an MDS repository. For more information, see the "Transferring Metadata Using Fusion Middleware Control" section in the Oracle Fusion Middleware Administrator's Guide. The referenced procedure describes using Fusion Middleware Control, but also applies to Fusion Applications Control.
For specific information about localizing Page Composer and CRM Application Composer customizations, see Section 16.3, "Translating Page Composer and CRM Application Composer Customizations." For specific information about localizing navigator menu customizations, see Section 16.4, "Translating Navigator Menu Customizations."
Task: Define Translations for the Custom Text in an MDS Repository
You define the translations for custom text by exporting XLIFF documents from an MDS repository, editing the documents to include the translated text, and importing the revised documents into the repository.
To localize the custom text:
Use the WLST exportMetadata
command shown in Example 16-1 to export XLIFF documents from the MDS repository to a directory of your choice.
Example 16-1 WLST exportMetadata Command
exportMetadata(application='application', server='server', toLocation='directory-path', docs='xlf-classpath', applicationVersion='version')
Set the docs
attribute to the class path for the XLIFF file. For example, use /oracle/apps/resourcebundles/xliffBundle/FusionAppsOverrideBundle.xlf
for the base file for Page Composer and CRM Application Composer custom text. Use /oracle/apps/menu/CustResourceBundle.xlf
for the base file for navigator menu custom text. Use the following format for the names of locale documents:
basename_language[_country].xlf
Replace language with the ISO 639 lowercase language code, such as fr
for France. When applicable, replace country with the ISO 3166 uppercase country code. Country codes are necessary when one language is used by more than one country. For example, use CustResourceBundle_zh_CN.xlf
for custom translations for Chinese in the People's Republic of China.
Because all Oracle Fusion applications use the same repository partition, you can use any Oracle Fusion application as an argument for the application
attribute when you export an XIFF file for text customizations.
Synchronize the entries in the XLIFF documents and provide the translated text in the <target>
tags, as shown in Example 16-2.
Use the WLST importMetadata
command shown in Example 16-2 to import the modified documents into the MDS repository.
Example 16-3 WLST importMetadata Command
importMetadata(application='application', server='server', fromLocation='directory-path', docs='xlf-classpath', applicationVersion='version')
Because all Oracle Fusion applications use the same repository partition, you can use any Oracle Fusion application as an argument for the application
attribute when you import an XIFF file for text customizations.
For more information about naming and editing XLIFF files, see the "Manually Defining Resource Bundles and Locales" section in the Oracle Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework (Oracle Fusion Applications Edition).
All Page Composer and CRM Application Composer customizations are stored in the customizations XLIFF document for the locale of the session in which you made the customizations. After you customize a page using Page Composer or CRM Application Composer, you might want to define translations for the custom text in the base customizations file as well as the customizations files for the other supported locales. For example, you might want to define French and Chinese translations of new prompts.
As shown in Figure 16-1, when an end user accesses the customized objects, the application loads the translated custom text for the locale's language and, if applicable, country. If the user's locale is for a language in a specific country and customized text is not available for that locale, the application loads the text for the locale's language. If no translated text is found, the application loads the text from the base customizations document.
Note that Figure 16-1 does not show a No path for the condition where the translation is not found in the base XLIFF document. If no entries exist in the locale and base documents, the text that is displayed varies. For example, for a field label, the application displays the attribute name. In other cases, no text is displayed.
To define translations for custom text, follow the steps in Task: Define Translations for the Custom Text in an MDS Repository in Section 16.2, "Translating Resource Bundles from an MDS Repository." Export the base document /oracle/apps/resourcebundles/xliffBundle/FusionAppsOverrideBundle.xlf
and the documents for all the locales for which you want to define translations. The locale XLIFF documents are named /oracle/apps/resourcebundles/xliffBundle/FusionAppsOverrideBundle_
language[_
country].xlf
. Replace language with the ISO 639 lowercase language code, such as fr
for France. When applicable, replace country with the ISO 3166 uppercase country code. Country codes are necessary when one language is used by more than one country. For example, use /oracle/apps/resourcebundles/xliffBundle/FusionAppsOverrideBundle_zh_CN.xlf
for custom translations for Chinese in the People's Republic of China.
Note:
The base document /oracle/apps/resourcebundles/xliffBundle/FusionAppsOverrideBundle.xlf
is automatically generated the first time that a string is inserted or customized using Page Composer or CRM Application Composer. Ensure that the bundle exists by inserting or customizing at least one string.
Copy the new and changed entries from the document for the locale with which you made the customizations into the base document and into the other locale documents. Provide the translations and import the modified documents into the MDS repository.
All navigator menu customizations are stored in the /oracle/apps/menu/CustResourceBundle.xlf
base XLIFF document regardless of your locale setting when you customized the menu. After you customize the navigator menu, you might want to define translations for your changes in the locales that you support, including the locale for the session in which you entered the custom text. For example, you might want to define French and Chinese translations of new menu items.
The process for retrieving translated text is the same as for Page Composer and CRM Application Composer, as shown in Figure 16-1, with the exception that if no entries exist in the locale and base documents, no text is displayed.
To create locale translations for your navigator menu changes, follow the steps in Task: Define Translations for the Custom Text in an MDS Repository in Section 16.2, "Translating Resource Bundles from an MDS Repository." Export the base document /oracle/apps/menu/CustResourceBundle.xlf
and export the documents for all the locales for which you want to define translations. The locale XLIFF documents are named /oracle/apps/menu/CustResourceBundle_
language[_
country].xlf
. Replace language with the ISO 639 lowercase language code, such as fr
for France. When applicable, replace country with the ISO 3166 uppercase country code. Country codes are necessary when one language is used by more than one country. For example, use /oracle/apps/menu/CustResourceBundle_zh_CN.xlf
for custom translations for Chinese in the People's Republic of China.
Copy the new and changed entries from the base document into the locale documents and provide the translations. Then import the modified locale documents into the MDS repository.
When you first configure a flexfield or segment, the translatable text that you enter, such as prompts and descriptions, is stored as the text for all installed locales. To translate the text for a particular locale, log in with that locale or use the Personalization menu in the global area to set the locale. Then, update the translatable text in the flexfield using the appropriate task, as described in Section 5.5.1, "Configuring Descriptive Flexfields" and Section 5.5.2, "Configuring Extensible Flexfields." Your modifications change the translated values only for the current session's locale.
After you complete the translations, deploy the flexfield as described in Section 5.7, "Deploying Flexfield Configurations."
You can define translations for a dependent value set or an independent value set, if it is of type Character with a subtype of Translated text. You define the translations by setting the current session to the locale for which you want to define the translation and using the Manage Value Sets task as described in Section 5.4, "Creating Custom Value Sets" to enter the translated values and descriptions for that locale.
For a table value set for which the underlying table supports multiple languages and for which the value set's value column is based on a translated attribute of the underlying table, you can define translated values using the maintenance task for the underlying table. For more information about enabling localization for table value sets, see Section 5.4, "Creating Custom Value Sets." For information about multilanguage support for tables, see the "Using Multi-Language Support Features" section in the Oracle Fusion Applications Developer's Guide.