22.4.1 Before You Begin: Configure Globalization Attributes

The first step in translating an application is to configure Globalization attributes and enable the Application Translation switch.

To enable application translation and configure attributes:

1. Navigate to the Globalization page:
   1. On the Workspace home page, click the App Builder icon.
   2. Select an application.
   3. On the Application home page, click Shared Components.
   4. Under Globalization, select Application Translation.
   5. Click Enable Translations.

   The Edit Globalization page appears.

2. Application Primary Language - Identifies the language in which an application is developed. This language is the base language from which all translations are made. For example, suppose application 100 was authored in English and then translated into French and published as application 101. The application ID would be transparent to the end user, thus all users regardless of language would access application 100.

   All modifications to an application should be made to the primary language specified here.

3. Translate Application - Turn on this switch to enable the application to support multiple languages.
4. Translate Method - Choose how translation works for your application. Options include:
   • Application-Based - Create a separate application for each language. Translatable text entered across application components will be implicitly translated. Translations are applied by creating a separate application for each language. To learn more, see Creating an Application-Based Translation.
   • Text Message-Based - Translatable text across application components is stored in Shared Components, Text Messages. You can reference Text Messages using &{TEXT_MESSAGE_NAME}. which enables a single application to support multiple languages. To learn more, see Creating a Text Message-Based Translation.
5. Application Language Derived From - Specify how the APEX engine determines (or derives) the application language. The application primary language can be static, derived from the Web browser language, or determined from a user preference or item.

   • No NLS (Application not translated) - Select this option if the application will not be translated.

   • Application Primary Language - Determines the translated application language based on the Application Primary Language attribute.

   • Browser (use browser language preference) - Determines the translated application language based on the user's Web browser language.

   • Application Preference (use FSP_LANGUAGE_PREFERENCE) - Determines the translated application language based on a value defined using the APEX_UTIL.SET_PREFERENCE API. This option can be used to maintain a user's language preference across multiple logins.

   • Item Preference (use item containing preference) - Determines the translated application language based on an application-level item called FSP_LANGUAGE_PREFERENCE. Using this option requires Oracle APEX to determine the appropriate language preference every time the user logs in.

   • Session - Determines the translated application language from the session setting. The Oracle APEX session language can be set using either the APEX_UTIL.SET_SESSION_LANG procedure or via the P_LANG parameter of the F procedure in the URL.

6. Configure other options as appropriate. To learn more about an attribute, see field-level Help or see Globalization Page.
7. Click Apply Changes.