22.1 Understanding Application Translation and Globalization Support
Learn about developing APEX applications that can run concurrently in different languages.
A single Oracle database instance and Oracle APEX can support multiple database sessions customized to support different languages.
- About the Translation Process
Learn about translating an application built in App Builder. - About Language Identification
Learn how the APEX engine determines the application language. - About the Rules for Translating Applications
Learn about rules for translating applications. - How Translated Applications Are Rendered
Learn about how APEX renders translated applications. - Making Application Attributes Translatable
Learn about best practices to make application attributes within your application translatable.
Parent topic: Managing Application Globalization
22.1.1 About the Translation Process
Learn about translating an application built in App Builder.
In general, translating an application built in App Builder involves the following steps:
-
Step 1: Define Application Languages - Create a mapping which identifies the target primary and target application language.
-
Step 2: Seed and Download to a Translation File - Seed the translation table and then export the translation text to a translation file. Seeding the translation copies all translatable text into the Translation Text repository. After you specify the language and seed the Translation Text, you generate and export an XLIFF file for translation.
-
Step 3: Translate the XLIFF File - Download the XLIFF files for translation or manually edit the translation repository.
-
Step 4: Upload and Apply a Translated XLIFF Document - Upload XLIFF files with translated text and apply translations to the Translation Text repository.
-
Step 5: Publish the Application - Make the translated application available to users.
Tip:
To learn more, see the translations steps described in Understanding the Translation Process.22.1.2 About Language Identification
Learn how the APEX engine determines the application language.
After you create an application, you specify a language preference by editing the Application Primary Language attribute. Globalization attributes control how the how the APEX engine determines the application language. The application primary language can be static, derived from the Web browser language, or determined from a user preference or item.
Tip:
To learn more, see Specifying the Primary Language for an Application22.1.3 About the Rules for Translating Applications
Learn about rules for translating applications.
Use the following rules to determine which translated version to use:
-
Look for an exact match between the user language preference and the language code of the translated application.
-
Look for a truncated match. That is, see if the language and locale exist. For example, if the user language preference is
en-us
and the translated version ofen-us
does not exist, look for a translated application that has the language codeen
. -
Use the primary application language.
For example, suppose you create an application with the primary language of German, de
, and you create a translated version of the application with a language code of en-us
. Users accessing this application with a browser language of en-us
execute the English en-us
version of the application. Users accessing the application with a browser language of en-gb
view the application in the application's primary language, that is, in German. For this example, you should create the translated English version using language code en
to encompass all variations of en
.
22.1.4 How Translated Applications Are Rendered
Learn about how APEX renders translated applications.
After APEX determines the language for an application, the APEX engine alters the database language for a specific page request. It then looks for a translated application in the appropriate language. If the APEX engine finds that language, it renders the application using that definition. Otherwise, it renders the application in the base (or primary) application language.
Note that the text that displays within an application is not translated on the fly. APEX dynamically collects page attributes from either a base language application definition or an alternative application definition.
22.1.5 Making Application Attributes Translatable
Learn about best practices to make application attributes within your application translatable.
When you build an application in App Builder, you define a large number of declarative attributes such as field labels, region headings, page header text, and so on.
- About Shortcuts that Support Translatable Messages
Learn about shortcuts that support translatable messages. - About Messages
Learn about messages. - About Dynamic Translation Text Strings
Learn about dynamic translation text strings. - Marking a Region as Not Translatable
Learn about marking a region as not translatable. - Identifying a Template as Translatable
Learn how to identify a template as translatable.
22.1.5.1 About Shortcuts that Support Translatable Messages
Learn about shortcuts that support translatable messages.
App Builder includes two shortcut types that enable you to reference translatable messages:
-
Message. Use this shortcut to reference a translatable message at runtime. Note that the name of the shortcut must match the corresponding message name. At runtime, the name of the shortcut expands to the text of the translatable message for the current language.
-
Message with JavaScript Escaped Single Quotes. Use this shortcut to reference a shortcut inside of a JavaScript literal string and reference a translatable message at runtime. This shortcut defines a text string. When the shortcut is referenced, it escapes the single quotation marks required for JavaScript.
See Also:
Parent topic: Making Application Attributes Translatable
22.1.5.2 About Messages
Learn about messages.
If your application includes PL/SQL regions or PL/SQL processes, you must translate any generated HTML or text. You may also need to translate messages used in reports if your application uses a language that is not one of the ten languages into which APEX is translated.
See Also:
Parent topic: Making Application Attributes Translatable
22.1.5.3 About Dynamic Translation Text Strings
Learn about dynamic translation text strings.
Dynamic translations are used for database data that must be translated at runtime. For example, you might use a dynamic translation to translate a list of values based on a database query. A dynamic translation consists of a translate-from language string, a language code, and a translate-to string. You can also use the APEX_LANG.LANG
API to retrieve dynamic translations programmatically.
Parent topic: Making Application Attributes Translatable
22.1.5.4 Marking a Region as Not Translatable
Learn about marking a region as not translatable.
By default, page region titles are included in the generated translation file. However, you can mark a region title as not translatable.
To mark a region title as not translatable:
Parent topic: Making Application Attributes Translatable
22.1.5.5 Identifying a Template as Translatable
Learn how to identify a template as translatable.
To identify a template as translatable:
See Also:
Parent topic: Making Application Attributes Translatable