| Oracle® Application Express Application Builder User's Guide Release 3.2 Part Number E11947-01 |
|
|
View PDF |
| Oracle® Application Express Application Builder User's Guide Release 3.2 Part Number E11947-01 |
|
|
View PDF |
This section describes how to translate an application built in Application Builder.
This section contains the following topics:
See Also:
"Viewing Installed Translations" in Oracle Application Express Administration GuideYou can develop applications in Application Builder that can run concurrently in different languages. A single Oracle database instance and Oracle Application Express can support multiple database sessions customized to support different languages.
In general, translating an application built in Application Builder involves the following steps:
Map the primary and target application IDs
Seed and export the text to a file for translation
Translate the text in the file
Apply the translated file
Publish the translated file
See Also:
"Understanding the Translation Process"Topics in this section include:
After you create an application, you specify a language preference on the Edit Globalization Attributes page. Then you select a primary application language and determine how the Application Express engine determines the application language. You can specify to have the application language based on the user's browser language preference, an application preference, or an item preference.
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 of en-us does not exist, look for a translated application that has the language code en.
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.
After Oracle Application Express determines the language for an application, the Application Express engine alters the database language for a specific page request. It then looks for a translated application in the appropriate language. If the Application Express 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. Oracle Application Express dynamically collects page attributes from either a base language application definition or an alternative application definition.
When you build an application in Application Builder, you define a large number of declarative attributes such as field labels, region headings, page header text, and so on. Using the steps described in this section, you can make all the application definition attributes within your application translatable.
Application Builder includes two shortcut types that enable you to reference translatable messages:
Message. Use this shortcut to reference a translatable message at run time. Note that the name of the shortcut must match the corresponding message name. At run time, 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 run time. This shortcut defines a text string. When the shortcut is referenced, it escapes the single quotation marks required for JavaScript.
See Also:
"Using Shortcuts"If your application includes PL/SQL regions or PL/SQL processes, you may 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 Oracle Application Express is translated.
See Also:
"Translating Messages"Dynamic translations are used for database data that needs to be translated at run time. 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.
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:
Navigate to the Page Definition. See "Accessing a Page Definition".
On the Page Definition, select the region title.
The Edit Region page appears.
Select the exclude title from translation check box.
By default, templates are not translatable, and therefore are not included in the generated translation file. Generally, templates do not and should not contain translatable text. However, if you must mark a template as translatable, select the Translatable check box on the Edit Page Template page.
To identify a template as translatable:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
Under User Interface, select Templates.
The Templates page appears.
Locate the template you want to edit and select the template name.
Under Name, select Translatable.
You can include translatable text at the application-level by defining the translatable text using static substitution strings. Because application-level attributes are translated, any text defined as a static substitution string will be included in the generated translation file.
Globalization attributes specify how the Application Express engine determines the primary language of an application.
To edit globalization attributes:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Edit Attributes.
From Application Primary Language, select the language in which the application is being developed.
From Application Language Derived From, specify how the Application Express engine determines (or derives) the application language. Available options are described in Table 16-1.
Table 16-1 Application Language Derived From Options
| Option | Description |
|---|---|
|
No NLS (Application not translated) |
Select this option if the application will not be translated. |
|
Use Application Primary Language |
Determines the application's primary language based on the Application Primary Language attribute. (See step 5.) |
|
Browser (use browser language preference) |
Determines the application's primary language based on the user's browser language preference. |
|
Application Preference (use FSP_LANGUAGE_PREFERENCE) |
Determines the application's primary language based on a value defined using the See Also: "SET_PREFERENCE Procedure" in Oracle Application Express API Reference |
|
Item Preference (use item containing preference) |
Determines the application's primary language based on an application-level item called |
See Also:
"Configuring the Application Definition", "Configuring Globalization Attributes", and "About Supported Globalization Codes"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.
For example, suppose your application determines the application language based on the user's browser language preference. If the Application Express engine determines the users's browser language preference is French, it displays dates and numbers in a format that conforms to French standards. You can override this default behavior and explicitly control how items display by applying a format mask. You apply a format mask by making a selection from the Display As list:
When you create the item
After you create the item by editing the item attributes
The following procedure describes how to edit item attributes for items having the source type of Database Column.
To edit item attributes:
On the Workspace home page, click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
Under Items, select the item name.
The Edit Page Item page appears.
Under Name, make a selection from the Display As list.
Under source, select or enter a format mask.
If your application needs to run in several languages simultaneously (such as Chinese and Japanese), consider configuring your database with a character set to support all of the languages. The same character set has to be configured in the corresponding database access descriptor (DAD) in mod_plsql. UTF8 and AL32UTF8 are the character sets you can use to support almost all languages around the world.
To translate an application developed in Application 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.
Topics in this section include:
The first step in translating an application is to map the primary and target application language. The primary application is the application to be translated. The target application is the resulting translated application.
To map the primary and target application language:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
The Translate Application page appears.
Click Map your primary language application to a translated application.
The Application Mappings page appears.
Click Create.
On the Translation Application Mapping page:
Translation Application - Enter a numeric application ID to identify the target application. The translated application ID must be an integer and cannot end in zero.
Translation Application Language Code - Select the language into which you are translating.
Image Directory - Enter the directory where the images currently reside.
This attribute determines the virtual path for translated images. For example, if your primary language application had an image prefix of /i/, you could define additional virtual directories for other languages, such as /i/de/ for German or /i/es/ for Spanish.
Note that this language specific image directory is typically not needed for most translated applications.
Click Create.
The second step is to seed the translation table and then export the translation text to a translation file.
Topics in this section include:
Seeding the translation copies all translatable text into the Translation Text repository. After you specify the language and seed the Translation Text, you can then generate and export an XLIFF file for translation.
The seeding process keeps your primary language application synchronized with the Translation Text repository. You should run the seed process any time your primary language application changes.
To seed translatable text:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
The Translate Application page appears.
On the Translate Application page, select Seed and export the translation text of your application into a translation file.
From Language Mapping, select the appropriate primary and target application ID map.
Click Seed Translatable Text.
The XLIFF Export page appears.
Note:
XML Localization Interchange File Format (XLIFF) is an XML-based format for exchanging localization data. For information about the XLIFF or to view the XLIFF specification, see:http://www.xliff.org
After you have seeded translatable text, a status box displays at the top of the XLIFF Export page indicating the total number of attributes that may require translation, including the number of:
Existing updated attributes that may require translation
New attributes that may require translation
Purged attributes that no longer require translation
You can use this information to determine if you must export translatable text for an entire application or just a specific page.
The XLIFF Export page is divided into two sections. Use the upper section of the page to export translatable text for an entire application (that is, all pages, lists of values, messages, and so on). Use the lower section to export translatable text for a specific page.
To export translatable text for an entire application:
Seed the translatable text. See "Seeding Translatable Text".
Under Step 2, Export XLIFF:
From Application, select the appropriate primary and target application ID map.
Specify whether to include XLIFF target elements.
Under Export, specify what translation text is included in your XLIFF file.
Click Export XLIFF for Application.
Follow the on-screen instructions.
To export translatable text for a specific page:
Seed the translatable text as described in "Seeding Translatable Text".
Under Export XLIFF for specific Page:
From Application, select the appropriate primary and target application ID map.
Specify whether to include XLIFF target elements.
Under Export, specify what translation text is included in your XLIFF file.
Click Export XLIFF for Page.
Follow the on-screen instructions.
When Oracle Application Express generates an XLIFF document, each document contains multiple translation units. Each translation unit consists of a source element and a target element. The XLIFF document can be generated with both the source and target elements for each translation unit. You have the option of generating a file containing only source elements. The updated translations will be applied from the target elements of the translation units.
Use the options under Export to specify what translation text is included in your XLIFF file. Select All translatable elements to include all translation text for an application. In contrast, select Only those elements requiring translation to include only new elements that have not yet been translated. Only those elements requiring translation produces an XLIFF file containing new or modified translation units. Also, if translation units were intentionally not previously translated (that is, the source of the translation element equals the target of the translation element), those translation units will also be included in the file
After you export a translatable file to XLIFF format, you can translate it into the appropriate languages. Because XLIFF is an open standard XML file for exchanging translations, most translation vendors should support it. Oracle Application Express only supports XLIFF files encoded in UTF-8 character sets. In other words, it exports XLIFF files for translation in UTF-8 and assumes that the translated XLIFF files will be in the same character set.
Translation is a time-consuming task. Oracle Application Express supports incremental translation so that application development can be done in parallel with the translation. An XLIFF file can be translated and uploaded to Oracle Application Express even when only part of the XLIFF file is translated. For strings that have no translation in the corresponding translated application, Oracle Application Express uses the corresponding ones in the primary language.
See Also:
For more information about the XLIFF, or to view the XLIFF specification, see:http://www.xliff.org
After your XLIFF document has been translated, the next step is to upload and then apply it.
Topics in this section include:
To upload a translated XLIFF document:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
The Translate Application page appears.
Click Apply your translation file and publish.
Click Upload XLIFF.
On the XLIFF Upload page:
Specify a title.
Enter a description.
Click Browse and locate the file to be uploaded.
Click Upload XLIFF File.
The uploaded document appears in the XLIFF Files repository.
After you upload an XLIFF document, the next step is to apply the XLIFF document and then publish the translated application. When you apply an XLIFF document, the Application Express engine parses the file and then updates the translation tables with the new translatable text.
Publishing your application creates a copy of the base language application, substituting the translated text strings from your translations table. This published application can then be used to render your application in alternate languages.
Remember that in order to run an application in an alternative language, you must run it with globalization settings that will cause an alternative language version to display. For example, if the language is derived from the browser language, you must set the browser language to the same language as the translated application.
To apply a translated XLIFF document and publish the application:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
The Translate Application page appears.
Click Apply your translation file and publish.
In the XLIFF Files repository, click the View icon next to the document you want to publish.
From Apply to, select the appropriate primary and target application ID map.
Click Apply XLIFF Translation File.
Click Publish Application.
To delete an uploaded XLIFF document:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
The Translate Application page appears.
On the Translate Application page, select Apply your translation file and publish.
In the XLIFF Files repository, select the check box to the left of the document title.
Click Delete Checked.
You should verify the existence of the translated application after it is published. Translated applications do not display in the Available Applications list on the Application Builder home page. Instead, use the Application Navigate list on the left side of the page.
Note that in order for a translated application to appear in Application Builder, you must make sure that you have correctly configured the application Globalization attributes.
Once you have mapped the target language and seeded the translatable text, you manually edit a translation.
To manually edit a translation:
Map the target language. See "Step 1: Map the Target Language".
Seed the translatable text. See "Seeding Translatable Text".
Navigate to the Translatable Text page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
From the Translation Utilities list, click Manually Edit Translations.
The Translatable Text page appears. Use the Navigation bar at the top of the page to change the report display. Available options include:
Language Mappings - Select a language mapping and click Go.
Page - Enter a page number and click Go.
Translate - Enter a case insensitive query and click Go.
Display - Select the number of rows to display and click Go.
To edit translatable text, click the Edit icon.
The Translatable Text field appears.
Edit the appropriate text and click Apply Changes.
You may need to translate messages if your application:
Includes PL/SQL regions or PL/SQL processes or calls PL/SQL package, procedures, or function. If it does, you may need to translate the generated HTML.
Uses a language that is not one of the ten languages into which Oracle Application Express is translated. If it does, you may need to translate messages used in reports.
Topics in this section include:
If your application includes PL/SQL regions or PL/SQL processes or calls PL/SQL package, procedures, or functions, you may need to translate generated HTML. First, you define each message on the Translatable Messages page. Second, you use the APEX_LANG.MESSAGE API to translate the messages from PL/SQL stored procedures, functions, triggers, or packaged procedures and functions.
You create translatable messages on the Translate Messages page.
To define a new translation message:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Text Messages.
On the Translate Messages page, click Create.
On Identify Text Message, specify the following:
Name - Enter a name to identify the message.
Language - Select the language for which the message would be used.
Text - Enter the text to be returned when the text message is called.
For example, you could define the message GREETING_MSG in English as:
Good morning %0
Or, you could define the message GREETING_MSG in German as:
Guten Tag %0
Click Create.
Use the APEX_LANG.MESSAGE API to translate text strings (or messages) generated from PL/SQL stored procedures, functions, triggers, packaged procedures, and functions.
Syntax
APEX_LANG.MESSAGE (
p_name IN VARCHAR2 DEFAULT NULL,
p0 IN VARCHAR2 DEFAULT NULL,
p1 IN VARCHAR2 DEFAULT NULL,
p2 IN VARCHAR2 DEFAULT NULL,
...
p9 IN VARCHAR2 DEFAULT NULL,
p_lang IN VARCHAR2 DEFAULT NULL)
RETURN VARCHAR2;
Parameters
Table 16-2 describes the parameters available in the APEX_LANG.MESSAGE API.
Table 16-2 APEX_LANG.MESSAGE Parameters
| Parameter | Description |
|---|---|
|
|
Name of the message as defined in Oracle Application Express. |
|
...
|
Dynamic substitution value: |
|
|
Language code for the message to be retrieved. If not specified, Oracle Application Express uses the current language for the user as defined in the Application Language Derived From attribute. See Also: "Specifying the Primary Language for an Application" |
Example
The following example assumes you have defined a message called GREETING_MSG in your application in English as Good morning%0 and in German as Guten Tag%1. The following example demonstrates how you could invoke this message from PL/SQL:
BEGIN
--
-- Print the greeting
--
APEX_LANG.MESSAGE('GREETING_MSG', V('APP_USER'));
END;
How the p_lang attribute is defined depends on how the Application Express engine derives the Application Primary Language. For example, if you are running the application in German and the previous call is made to the APEX_LANG.MESSAGE API, the Application Express engine first looks for a message called GREETING_MSG with a LANG_CODE of de. If it does not find anything, then it will revert to the Application Primary Language attribute. If it still does not find anything, the Application Express engine looks for a message by this name with a language code of en-us.
See Also:
"Specifying the Primary Language for an Application" for information about the Application Primary Language attribute and APEX_LANG in the Oracle Application Express API ReferenceOracle Application Express is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. If your application uses a language that is not among the ten languages into which Oracle Application Express is translated, you must translate messages displayed by the Application Express reporting engine.
For example, if you develop a Russian application and want to include report messages, such as pagination, in Russian, you must translate the strings used in messages displayed in reports.
To translate messages:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Text Messages.
On the Translate Messages page, click Create.
On Identify Text Message, specify the following:
Name - Enter the name of each message that needs to be translated. See Table 16-3.
Language - Select the language for which the message would be used.
Text - Enter the text to be returned when the text message is called. If the English text message contains positional substitution values (for example, %0, %1), ensure that your defined message also contains the same named and number of positional substitution values.
Click Create.
Table 16-3 lists the internal messages that require translation.
Table 16-3 Internal Messages Requiring Translation
| Message Name | English Text |
|---|---|
|
|
1 error has occurred |
|
|
%0 errors have occurred |
|
|
Invalid Login Credentials |
|
|
Invalid set of rows requested, the source data of the report has been modified |
|
|
Next |
|
|
Next Set |
|
|
Previous |
|
|
Previous Set |
|
|
report total |
|
|
reset pagination |
|
|
%0 days ago |
|
|
%0 hours ago |
|
|
%0 minutes ago |
|
|
%0 months ago |
|
|
%0 seconds ago |
|
|
%0 weeks ago |
|
|
%0 years ago |
|
|
Total |
|
|
Calendar |
|
|
Close |
|
|
Ok |
|
|
Minimum row requested: %0, rows found but not displayed: %1 |
|
|
Sort by this column |
|
|
row(s) %0 - %1 of more than %2 |
|
|
row(s)%0 - %1 of %2 |
|
|
%0 - %1 of %2 |
Table 16-4 lists the internal messages that require translation.
Table 16-4 Interactive Report Messages Requiring Translation
| Message Name | English Text |
|---|---|
|
|
3D |
|
|
Actions Menu |
|
|
Add |
|
|
Aggregate |
|
|
Aggregates are displayed after each control break and at the end of the report. |
|
|
Aggregation |
|
|
Average |
|
|
Count |
|
|
Maximum |
|
|
Median |
|
|
Minimum |
|
|
Mode |
|
|
Sum |
|
|
All |
|
|
All Columns |
|
|
and |
|
|
Apply |
|
|
Ascending |
|
|
As of %0 |
|
|
between |
|
|
Background Color |
|
|
blue |
|
|
Bottom |
|
|
Calendar |
|
|
Cancel |
|
|
Category |
|
|
Cell |
|
|
Chart |
|
|
Initializing... |
|
|
Chart Type |
|
|
Choose report download format |
|
|
clear |
|
|
Column |
|
|
Columns |
|
|
Column Heading |
|
|
Column Heading Menu |
|
|
Column Information |
|
|
contains |
|
|
does not contain |
|
|
in |
|
|
is not in the last |
|
|
is not in the next |
|
|
is in the last |
|
|
is in the next |
|
|
is not null |
|
|
is null |
|
|
like |
|
|
not in |
|
|
not like |
|
|
matches regular expression |
|
|
Computation |
|
|
Create a computation using column aliases. |
|
|
(B+C)*100 |
|
|
INITCAP(B)||', '||INITCAP(C) |
|
|
CASE WHEN A = 10 THEN B + C ELSE B END |
|
|
Compute |
|
|
Control Break |
|
|
Control Breaks |
|
|
Report data as of %0 minutes ago. |
|
|
Date |
|
|
Default |
|
|
Delete |
|
|
Delete Checked |
|
|
Would you like to delete these report settings? |
|
|
Would you like to perform this delete action? |
|
|
Delete Report |
|
|
Descending |
|
|
Description |
|
|
Single Row View |
|
|
Direction |
|
|
Disable |
|
|
Disabled |
|
|
Display |
|
|
Displayed |
|
|
Displayed Columns |
|
|
Display in Report |
|
|
Down |
|
|
Download |
|
|
- Do not aggregate - |
|
|
Do Not Display |
|
|
Edit Chart Settings |
|
|
Edit Chart |
|
|
Edit Filter |
|
|
Edit Highlight |
|
|
Enable |
|
|
Enabled |
|
|
Enable/Disable |
|
|
Error |
|
|
Examples |
|
|
Examples: |
|
|
Exclude Null Values |
|
|
Expand/Collapse |
|
|
Expression |
|
|
Filter |
|
|
Filters |
|
|
Select columns to search |
|
|
Flashback |
|
|
A flashback query enables you to view the data as it existed at a previous point in time. |
|
|
Unable to perform flashback request |
|
|
Format Mask |
|
|
Function |
|
|
Functions |
|
|
Go |
|
|
green |
|
|
Horizontal Column |
|
|
Help |
|
|
An Interactive Report displays a predetermined set of columns. The report may be further customized with an initial filter clause, a default sort order, control breaks, highlighting, computations, aggregates and a chart. Each Interactive Report can then be further customized and the results can be viewed, or downloaded, and the report definition can be stored for later use. <p/> An Interactive Report can be customized in three ways: the search bar, actions menu and column heading menu. |
|
|
The actions menu is used to customize the display of your Interactive Report. |
|
|
Aggregates are mathematical computations performed against a column. Aggregates are displayed after each control break and at the end of the report within the column they are defined. <p/> <ul><li><b>Aggregation</b> allows you to select a previously defined aggregation to edit.</li> <li><b>Function</b> is the function to be performed (e.g. SUM, MIN).</li> <li><b>Column</b> is used to select the column to apply the mathematical function to. Only numeric columns will be displayed.</li></ul> |
|
|
Aggregates are mathematical computations performed against a column. Aggregates are displayed after each control break and at the end of the report within the column they are defined.<p/> <p/> <ul><li><b>Aggregation</b> allows you to select a previously defined aggregation to edit.</li> <li><b>Function</b> is the function to be performed (e.g. SUM, MIN).</li> <li><b>Column</b> is used to select the column to apply the mathematical function to. Only numeric columns will be displayed.</li></ul> |
|
|
You can include one chart per Interactive Report. Once defined, you can switch between the chart and report views using links below the search bar. <p/> <ul><li><b>Chart Type</b> identifies the chart type to include. Select from horizontal bar, vertical bar, pie or line.</li> <li><b>Label</b> allows you to select the column to be used as the label.</li> <li><b>Axis Title for Label</b> is the title that will display on the axis associated with the column selected for Label. This is not available for pie chart.</li> <li><b>Value</b> allows you to select the column to be used as the value. If your function is a COUNT, a Value does not need to be selected.</li> <li><b>Axis Title for Value</b> is the title that will display on the axis associated with the column selected for Value. This is not available for pie chart.</li> <li><b>Function</b> is an optional function to be performed on the column selected for Value.</li></ul> |
|
|
Clicking on any column heading exposes a column heading menu. <p/> <ul><li><b>Sort Ascending icon</b> sorts the report by the column in ascending order.</li> <li><b>Sort Descending icon</b> sorts the report by the column in descending order.</li> <li><b>Hide Column</b> hides the column.</li> <li><b>Break Column</b> creates a break group on the column. This pulls the column out of the report as a master record.</li> <li><b>Column Information</b> displays help text about the column, if available.</li> <li><b>Text Area</b> is used to enter case insensitive search criteria (no need for wild cards). Entering a value will reduce the list of values at the bottom of the menu. You can then select a value from the bottom and the selected value will be created as a filter using '=' (e.g. column = 'ABC'). Alternatively, you can click the flashlight icon and the entered value will be created as a filter with the 'LIKE' modifier (e.g. column LIKE '%ABC%').<li><b>List of Unique Values</b> contains the first 500 unique values that meet your filters. If the column is a date, a list of date ranges is displayed instead. If you select a value, a filter will be created using '=' (e.g. column = 'ABC').</li></ul> |
|
|
Computations allow you to add computed columns to your report. These can be mathematical computations (e.g. NBR_HOURS/24) or standard Oracle functions applied to existing columns (some have been displayed for example, others, like TO_DATE, can also be used). <p/> <ul><li><b>Computation</b> allows you to select a previously defined computation to edit.</li> <li><b>Column Heading</b> is the column heading for the new column.</li> <li><b>Format Mask</b> is an Oracle format mask to be applied against the column (e.g. S9999).</li> <li><b>Format Mask</b> is an Oracle format mask to be applied against the column (e.g. S9999).</li> <li><b>Computation</b> is the computation to be performed. Within the computation, columns are referenced using the aliases displayed.</li> </ul> <p/> Below computation, the columns in your query are displayed with their associated alias. Clicking on the column name or alias will write them into the Computation. Next to Columns is a Keypad. These are simply shortcuts of commonly used keys. On the far right are Functions. <p/> An example computation to display Total Compensation is: <p/> <pre>CASE WHEN A = 'SALES' THEN B + C ELSE B END</pre> (where A is ORGANIZATION, B is SALARY and C is COMMISSION) |
|
|
Used to create a break group on one or several columns. This pulls the columns out of the Interactive Report and displays them as a master record. |
|
|
To view the details of a single row at a time, click the single row view icon on the row you want to view. If available, the single row view will always be the first column. Depending on the customization of the Interactive Report, the single row view may be the standard view or a custom page that may allow update. |
|
|
Allows the current result set to be downloaded. The download formats will differ depending upon your installation and report definition but may include CSV, XLS, PDF, or RTF. |
|
|
Used to add or modify the where clause on the query. You first select a column (it does not need to be one that is displayed), select from a list of standard Oracle operators (=, !=, not in, between), and enter an expression to compare against. The expression is case sensitive and you can use % as a wild card (for example, STATE_NAME like A%). |
|
|
Performs a flashback query to allow you to view the data as it existed at a previous point in time. The default amount of time that you can flashback is 3 hours (or 180 minutes) but the actual amount will differ per database. |
|
|
Highlighting allows you to define a filter. The rows that meet the filter are highlighted using the characteristics associated with the filter. <p/> <ul><li><b>Name</b> is used only for display.</li> <li><b>Sequence</b> identifies the sequence in which the rules will be evaluated.</li> <li><b>Enabled</b> identifies if the rule is enabled or disabled.</li> <li><b>Highlight Type</b> identifies whether the Row or Cell should be highlighted. If Cell is selected, the column referenced in the Highlight Condition is highlighted.</li> <li><b>Background Color</b> is the new color for the background of the highlighted area.</li> <li><b>Text Color</b> is the new color for the text in the highlighted area.</li> <li><b>Highlight Condition</b> defines your filter condition.</li></ul> |
|
|
If you have customized your Interactive Report, the report settings will be displayed below the Search Bar and above the report. If you have saved customized reports, they will be shown as tabs. You can access your alternate views by clicking the tabs. Below the tabs are the report settings for the current report. This area can be collapsed and expanded using the icon on the left. <p/> For each report setting, you can: <ul><li><b>Edit</b> by clicking the name.</li> <li><b>Disable/Enable</b> by unchecking or checking the Enable/Disable check box. This is used to temporarily turn off and on the setting.</li> <li><b>Remove</b> by click the Remove icon. This permanently removes the setting.</li></ul> <p/> If you have created a chart, you can toggle between the report and chart using the Report View and Chart View links shown on the right. If you are viewing the chart, you can also use the Edit Chart link to edit the chart settings. |
|
|
Resets the report back to the default settings, removing any customizations that you have made. |
|
|
Saves the customized report for future use. You provide a name and an optional description. |
|
|
At the top of each report page is a search region. The region provides the following features: <p/> <ul><li><b>Select columns icon</b> allows you to identify which column to search (or all).</li> <li><b>Text area</b> allows for case insensitive search criteria (no need for wild cards).</li> <li><b>Rows</b> selects the number of records to display per page.</li> <li><b>[Go] button</b> executes the search.</li> <li><b>Actions Menu icon</b> displays the actions menu (discussed next).</li></ul> <p/> Please note that all features may not be available for each report. |
|
|
Used to modify the columns displayed. The columns on the right are displayed. The columns on the left are hidden. You can reorder the displayed columns using the arrows on the far right. Computed columns are prefixed with <b>**</b>. |
|
|
Used to change the column(s) to sort on and whether to sort ascending or descending. You can also specify how to handle nulls (use the default setting, always display them last or always display them first). The resulting sorting is displayed to the right of column headings in the report. |
|
|
Hide Column |
|
|
Highlight |
|
|
Highlights |
|
|
Highlight Condition |
|
|
Highlight Type |
|
|
Highlight When |
|
|
Interactive Report Help |
|
|
Invalid |
|
|
Invalid computation expression. %0 |
|
|
Keypad |
|
|
Label |
|
|
Axis Title for Label |
|
|
Last Day |
|
|
Last Hour |
|
|
Last Month |
|
|
Last Week |
|
|
Last %0 Days |
|
|
Last %0 Hours |
|
|
Last %0 Years |
|
|
Last Year |
|
|
Line |
|
|
The query is estimated to exceed the maximum allowed resources. Please modify your report settings and try again. |
|
|
This query returns more then %0 rows, please filter your data to ensure complete results. |
|
|
%0 minutes ago |
|
|
More Data |
|
|
Move |
|
|
Move All |
|
|
Name |
|
|
New Aggregation |
|
|
- New Category - |
|
|
New Computation |
|
|
> |
|
|
Next Day |
|
|
Next Hour |
|
|
Next Month |
|
|
Next Week |
|
|
Next %0 Days |
|
|
Next %0 Hours |
|
|
Next %0 Years |
|
|
Next Year |
|
|
No |
|
|
- None - |
|
|
No aggregation defined. |
|
|
No column information available. |
|
|
No computation defined. |
|
|
Nulls Always First |
|
|
Nulls Always First |
|
|
Nulls Always Last |
|
|
Null Sorting |
|
|
Flashback time must be numeric. |
|
|
Sequence must be numeric. |
|
|
Operator |
|
|
orange |
|
|
Other |
|
|
Pie |
|
|
< |
|
|
Public |
|
|
red |
|
|
Remove |
|
|
Remove Aggregate |
|
|
Remove All |
|
|
Remove Control Break |
|
|
Remove Filter |
|
|
Remove Flashback |
|
|
Remove Highlight |
|
|
Rename Report |
|
|
Report |
|
|
Report Settings |
|
|
< Report View |
|
|
Reset |
|
|
Restore report to the default settings. |
|
|
Row |
|
|
Rows |
|
|
Row %0 of %1 |
|
|
Row Order |
|
|
Row text contains |
|
|
Save |
|
|
Saved Report |
|
|
Saved Report = "%0" |
|
|
Save as Default |
|
|
The current report settings will be used as the default for all users. |
|
|
Save Report |
|
|
Search Bar |
|
|
- Select Category - |
|
|
- Select Column - |
|
|
Select Columns |
|
|
Computed columns are prefixed with **. |
|
|
- Select Function - |
|
|
Select Value |
|
|
Sequence |
|
|
Sort |
|
|
Sort Ascending |
|
|
Sort Descending |
|
|
space |
|
|
Status |
|
|
Text Color |
|
|
days |
|
|
hours |
|
|
minutes |
|
|
months |
|
|
weeks |
|
|
years |
|
|
Top |
|
|
Unauthorized |
|
|
Column Heading must be unique. |
|
|
Highlight Name must be unique. |
|
|
unsupported data type |
|
|
Up |
|
|
Please enter a valid color. |
|
|
Please enter a valid format mask. |
|
|
Value |
|
|
Axis Title for Value |
|
|
Value Required |
|
|
Vertical Column |
|
|
View Chart |
|
|
View Report |
|
|
Working Report |
|
|
yellow |
|
|
Yes |
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.
Dynamic translations differ from messages in that you query a specific string rather than a message name. You define dynamic translations on the Dynamic Translations page. You then use the APEX_LANG.LANG API to return the dynamic translation string identified by the p_primary_text_string parameter.
You define dynamic translations on the Dynamic Translations page. A dynamic translation consists of a translate-from language string, a language code, and a translate-to string.
To define a dynamic translation:
Navigate to the Translate Application page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, click Translate Application.
On the Translate Application page, select Optionally identify any data that needs to be dynamically translated to support SQL based lists of values.
On the Dynamic Translations page, click Create and specify the following:
Language - Select a target language.
Translate From Text - Enter the source text to be translated.
Translate To - Enter the translated text.
Click Create.
Syntax
APEX_LANG.LANG (
p_primary_text_string IN VARCHAR2 DEFAULT NULL,
p0 IN VARCHAR2 DEFAULT NULL,
p1 IN VARCHAR2 DEFAULT NULL,
p2 IN VARCHAR2 DEFAULT NULL,
...
p9 IN VARCHAR2 DEFAULT NULL,
p_primary_language IN VARCHAR2 DEFAULT NULL)
RETURN VARCHAR2;
Parameters
Table 16-5 describes the parameters available in the APEX_LANG.LANG API.
Table 16-5 APEX_LANG.LANG Parameters
| Parameter | Description |
|---|---|
|
|
Text string of the primary language. This will be the value of the Translate From Text in the dynamic translation. |
|
...
|
Dynamic substitution value: |
|
|
Language code for the message to be retrieved. If not specified, Oracle Application Express uses the current language for the user as defined in the Application Language Derived From attribute. See Also: "Specifying the Primary Language for an Application" |
Example
Suppose you have a table that defines all primary colors. You could define a dynamic message for each color and then apply the LANG function to the defined values in a query. For example:
SELECT APEX_LANG.LANG(color) FROM my_colors
If you were running the application in German, RED was a value for the color column in the my_colors table, and you defined the German word for red, the previous example would return ROT.
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.
NLS_LANGUAGE and NLS_TERRITORY determine the default presentation of numbers, dates, and currencies.
Table 16-6 describes the globalization codes in Oracle Application Express.
Table 16-6 Oracle Application Express Globalization Codes
| Language Name | Language Code | NLS_LANGUAGE | NLS_TERRITORY |
|---|---|---|---|
|
Afrikaans |
|
ENGLISH |
SOUTH AFRICA |
|
Arabic |
|
ARABIC |
UNITED ARAB EMIRATES |
|
Arabic (Algeria) |
|
ARABIC |
ALGERIA |
|
Arabic (Bahrain) |
|
ARABIC |
BAHRAIN |
|
Arabic (Egypt) |
|
EGYPTIAN |
EGYPT |
|
Arabic (Iraq) |
|
ARABIC |
IRAQ |
|
Arabic (Jordan) |
|
ARABIC |
JORDAN |
|
Arabic (Kuwait) |
|
ARABIC |
KUWAIT |
|
Arabic (Lebanon |
|
ARABIC |
LEBANNON |
|
Arabic (Libya) |
|
ARABIC |
LIBYA |
|
Arabic (Morocco) |
|
ARABIC |
MOROCCO |
|
Arabic (Oman) |
|
ARABIC |
OMAN |
|
Arabic (Qatar) |
|
ARABIC |
QATAR |
|
Arabic (Saudi Arabia) |
|
ARABIC |
SAUDI ARABIA |
|
Arabic (Syria) |
|
ARABIC |
SYRIA |
|
Arabic (Tunisia) |
|
ARABIC |
TUNISIA |
|
Arabic (U.A.E.) |
|
ARABIC |
UNITED ARAB EMIRATES |
|
Arabic (YEMEN) |
|
ARABIC |
YEMEN |
|
Assamese |
|
ASSAMESE |
INDIA |
|
Basque |
|
FRENCH |
FRANCE |
|
Belarusian |
|
RUSSIAN |
RUSSIA |
|
Bengali |
|
BANGLA |
BANGLADESH |
|
Bulgarian |
|
BULGARIAN |
BULGARIA |
|
Catalan |
|
CATALAN |
CATALONIA |
|
Chinese |
|
SIMPLIFIED CHINESE |
CHINA |
|
Chinese (China) |
|
SIMPLIFIED CHINESE |
CHINA |
|
Chinese (Hong Kong SAR) |
|
TRADITIONAL CHINESE |
HONG KONG |
|
Chinese (Macau SAR) |
|
TRADITIONAL CHINESE |
HONG KONG |
|
Chinese (Singapore) |
|
SIMPLIFIED CHINESE |
SINGAPORE |
|
Chinese (Taiwan) |
|
TRADITIONAL CHINESE |
TAIWAN |
|
Croatian |
|
CROATIAN |
CROATIA |
|
Czech |
|
CZECH |
CZECH REPUBLIC |
|
Danish |
|
DANISH |
DENMARK |
|
Dutch (Belgium) |
|
DUTCH |
BELGIUM |
|
Dutch (Netherlands) |
|
DUTCH |
THE NETHERLANDS |
|
English |
|
AMERICAN |
AMERICA |
|
English (Australia) |
|
ENGLISH |
AUSTRALIA |
|
English (Belize) |
|
ENGLISH |
UNITED KINGDOM |
|
English (Canada) |
|
ENGLISH |
CANADA |
|
English (Ireland) |
|
ENGLISH |
IRELAND |
|
English (Jamaica) |
|
ENGLISH |
UNITED KINGDOM |
|
English (New Zealand) |
|
ENGLISH |
NEW ZEALAND |
|
English (Philippines) |
|
ENGLISH |
PHILIPPINES |
|
English (South Africa) |
|
ENGLISH |
SOUTH AFRICA |
|
English (Trinidad) |
|
ENGLISH |
UNITED KINGDOM |
|
English (United Kingdom) |
|
ENGLISH |
UNITED KINGDOM |
|
English (United States) |
|
AMERICAN |
AMERICA |
|
English (Zimbabwe) |
|
ENGLISH |
UNITED KINGDOM |
|
Estonian |
|
ESTONIAN |
ESTONIA |
|
Faeroese |
|
ENGLISH |
UNITED KINGDOM |
|
Farsi |
|
ENGLISH |
UNITED KINGDOM |
|
Finnish |
|
FINNISH |
FINLAND |
|
French (Belgium) |
|
FRENCH |
BELGIUM |
|
French (Canada) |
|
CANADIAN FRENCH |
CANADA |
|
French (France) |
|
FRENCH |
FRANCE |
|
French (Luxembourg) |
|
FRENCH |
LUXEMBOURG |
|
French (Monaco) |
|
FRENCH |
FRANCE |
|
French (Switzerland) |
|
FRANCH |
SWITZERLAND |
|
FYRO Macedonian |
|
MACEDONIAN |
FYR MACEDONIA |
|
Gaelic |
|
ENGLISH |
UNITED KINGDOM |
|
Galician |
|
SPANISH |
SPAIN |
|
German (Austria) |
|
GERMAN |
AUSTRIA |
|
German (Germany) |
|
GERMAN |
GERMANY |
|
German (Liechtenstein) |
|
GERMAN |
GERMANY |
|
German (Luxemgourg) |
|
GERMAN |
LUXEMBOURG |
|
German (Switzerland) |
|
GERMAN |
SWITZERLAND |
|
Greek |
|
GREEK |
GREECE |
|
Gujarati |
|
GUJARATI |
INDIA |
|
Hebrew |
|
HEBREW |
ISRAEL |
|
Hindi |
|
HINDI |
INDIA |
|
Hungarian |
|
HUNGARIAN |
HUNGARY |
|
Icelandic |
|
ICELANDIC |
ICELAND |
|
Indonesian |
|
INDONESIAN |
INDONESIA |
|
Italian (Italy) |
|
ITALIAN |
ITALY |
|
Italian (Switzerland) |
|
ITALIAN |
SWITZERLAND |
|
Japanese |
|
JAPANESE |
JAPAN |
|
Kannada |
|
KANNADA |
INDIA |
|
Kazakh |
|
CYRILLIC KAZAKH |
KAZAKHSTAN |
|
Konkani |
|
KOREAN |
KOREA |
|
Korean |
|
KOREAN |
KOREA |
|
Kyrgyz |
|
RUSSIAN |
RUSSIA |
|
Latvian |
|
LATVIAN |
LATVIA |
|
Lithuanian |
|
LITHUANIAN |
LITHUANIANA |
|
Malay (Malaysia) |
|
MALAY |
MALAYSIA |
|
Malayalam |
|
MALAYALAM |
INDIA |
|
Maltese |
|
ENGLISH |
UNITED KINGDOM |
|
Marathi |
|
ENGLISH |
INDIA |
|
Nepali (India) |
|
ENGLISH |
UNITED KINGDOM |
|
Norwegian (Bokmal) |
|
NORWEGIAN |
NORWAY |
|
Norwegian (Bokmal) |
|
NORWEGIAN |
NORWAY |
|
Norwegian (Nynorsk) |
|
NORWEGIAN |
NORWAY |
|
Oriya |
|
ORIYA |
INDIA |
|
Polish |
|
POLISH |
POLAND |
|
Portuguese (Brazil) |
|
BRAZILIAN PORTUGUESE |
BRAZIL |
|
Portuguese (Portugal) |
|
PORTUGUESE |
PORTUGAL |
|
Punjabi |
|
PUNJABI |
INDIA |
|
Romanian |
|
ROMANIAN |
ROMANIA |
|
Russian |
|
RUSSIAN |
RUSSIA |
|
Russian (Moldova) |
|
RUSSIAN |
RUSSIA |
|
Serbia |
|
CYRILLIC SERBIAN |
SERBIA AND MONTENEGRO |
|
Slovak |
|
SLOVAK |
SLOVAKIA |
|
Slovenian |
|
SLOVENIAN |
SLOVENIA |
|
Spanish (Argentina) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
|
Spanish (Bolivia) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
|
Spanish (Chile) |
|
LATIN AMERICAN SPANISH |
CHILE |
|
Spanish (Columbia) |
|
LATIN AMERICAN SPANISH |
COLUMBIA |
|
Spanish (Costa Rica) |
|
LATIN AMERICAN SPANISH |
COSTA RICA |
|
Spanish (Dominican Republic) |
|
LATIN AMERICAN SPANISH |
PUERTO RICO |
|
Spanish (Ecuador) |
|
LATIN AMERICAN SPANISH |
ECUDOR |
|
Spanish (El Salvador) |
|
LATIN AMERICAN SPANISH |
EL SALVADOR |
|
Spanish (Guatemala) |
|
LATIN AMERICAN SPANISH |
GUATEMALA |
|
Spanish (Honduras) |
|
LATIN AMERICAN SPANISH |
GUATEMALA |
|
Spanish (Mexico) |
|
MEXICAN SPANISH |
MEXICO |
|
Spanish (Nicaragua) |
|
LATIN AMERICAN SPANISH |
Nicaragua |
|
Spanish (Panama) |
|
LATIN AMERICAN SPANISH |
Panama |
|
Spanish (Paraguay) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
|
Spanish (Peru) |
|
LATIN AMERICAN SPANISH |
PERU |
|
Spanish (Peurto Rico) |
|
LATIN AMERICAN SPANISH |
PEURTO RICO |
|
Spanish (Traditional Sort) |
|
LATIN AMERICAN SPANISH |
SPAIN |
|
Spanish (United States) |
|
LATIN AMERICAN SPANISH |
AMERICAN |
|
Spanish (Uruguay) |
|
LATIN AMERICAN SPANISH |
ARGENTINA |
|
Spanish (Venezuela) |
|
LATIN AMERICAN SPANISH |
VENEZUELA |
|
Swedish |
|
SWEDISH |
SWEDEN |
|
Swedish |
|
SWEDISH |
FINLAND |
|
Tamil |
|
TAMIL |
INDIA |
|
Telugu |
|
TELUGU |
INDIA |
|
Thai |
|
THAI |
THAILAND |
|
Turkish |
|
TURKISH |
TURKEY |
|
Ukrainian |
|
UKRAINIAN |
UKRAINE |
|
Urdu |
|
ENGLISH |
UNITED KINGDOM |
|
Uzbek |
|
LATIN UZBEK |
UZBEKISTAN |
|
Vietnamese |
|
VIETNAMESE |
VIETNAM |
|
Zulu |
|
ENGLISH |
UNITED KINGDOM |
|
 Copyright © 2003, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|