Databases Reference
In-Depth Information
Figure 5-20.
Interactive report text translation
When the application runs in Czech (cs)—for example, if I change the Default Language to Czech
(cs)—the correct translation will appear in every interactive report within the application, as Figure 5-21
shows.
Figure 5-21. Interactive report action button in Czech
Keep in mind that these internal translations must be performed for every distinct primary
application. If multiple applications must to be created and translated, a base application with internal
messages translated could be created and a copy can be used for new application developments. When
exporting and importing an application, translated text messages and dynamic actions are also exported
and imported. Currently, in APEX 4, there are no views available to list the translated text messages for
an application.
Some of the internal messages use substitution variables making it important to reuse them in the
translated message text. For example,
FLOW.VALIDATION ERROR
message text includes the number of
errors that occurred: “%0 errors have occurred” could be translated to “%0 erreurs sur la page”.
For the complete list of translatable Internal Messages, please refer to the Application Builder User's
Guide, Chapter 16, “Managing Application Globalization, Translating Messages, Translating Messages
Used Internally by Oracle Application Express.”
This feature can also be used for other strings used in applications generated from PL/SQL stored
procedures, functions, triggers, packaged procedures, and functions. Simply define a new text message
and use the
APEX LANG.MESSAGE
function. This is the same function as the Dynamic Translation:
Ex : select APEX LANG.MESSAGE('MY MESSAGE')
This will display the text defined in the message text in the language in which the application is
running for
MY MESSAGE
.
There is a view called APEX_APPLICATION_TRANSLATIONS that lists all the text message
translations.
