
Application Primary Language
Application Language Derived From
Document Direction
Application Primary Language
Application Language Derived From
Document Direction
Application Date Format
Application Date Time Format
Application Timestamp Format
Application Timestamp Time Zone Format
Character Value Comparison
Character Value Comparison Behavior
Automatic Time Zone
Automatic CSV Encoding
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.
APEX_UTIL.SET_PREFERENCE(
p_preference => 'FSP_LANGUAGE_PREFERENCE',
p_value => 'ar-eg');
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 Application Express to determine the appropriate language preference every time the user logs in.
:FSP_LANGUAGE_PREFERENCE := :P9999_LANGUAGE ;
Session
- Determines the translated application language from the session setting. The Application Express session language can be set via either the APEX_UTIL.SET_SESSION_LANG procedure or via the P_LANG parameter of the F procedure in the URL.
apex_util.set_session_lang('ar-eg');
Dynamic translations enable custom PL/SQL code to perform translations using the APEX_LANG.LANG function.
This table maps values from the primary language to another national language.
This Course describes how to translate an application built in App Builder.
Understanding Application Translation and Globalization Support
A single Oracle database instance and Oracle Application Express can support multiple database sessions customized to support different languages.
Specifying the Primary Language for an Application
Globalization attributes specify how the Application Express engine determines the primary language of an application.
About Apply Format Masks to Items
The Application Express engine applies globalization settings for each rendered page. This default behavior can impact the display of certain items such as numbers and dates.
About Translating Applications for Multibyte Languages
If your application must run in several languages simultaneously (such as Chinese and Japanese), consider configuring your database with a character set to support all of the languages.
Understanding the Translation Process
To translate an application developed in App Builder, you must map the primary and target language, seed and export text to a translation file, translate the text, apply the translation file, and publish the translated application.
Translating Messages
Learn when and how to translate messages is an Oracle Application Express application.
Translating Data That Supports List of Values
You create a dynamic translation to translate dynamic pieces of data. For example, you might use a dynamic translation on a list of values based on a database query.
Understanding Supported Globalization Codes
If you are building a multilingual application, it is important to understand how globalization codes affect the way in which your application runs. These codes are set automatically based on the application-level Globalization attributes you select.