Siebel Reports Administration Guide > Developing Multilingual Reports >
Designing Multilingual Reports
Designing a multilingual report is essentially the same as that of any standard report. The only additional step is to externalize the user interface elements for localization in the desired languages. The same report executable obtains the language-specific strings from the localized text files based on user's specification. The following instructions will describe the details of the additional step for localization of user interface strings.
To design multilingual reports
- Design a report in the default language first; for example, ENU (English).
If your installation uses a non-English version of Siebel eBusiness Applications, you do not have an \ENU folder. Instead, you have a folder in the appropriate language code for your installation, such as \DEU for Germany.
See Global Deployment Guide for a list of three-letter International Standards Organization (ISO) language extensions.
This part of the design is the same as already discussed in using Siebel Tools to create the ROL file and using Actuate e.Report Designer Professional to create the ROD and ROX files. For more information, see Creating a Simple List Report.
- Run the report in Design mode to externalize user interface strings and data properties to an external file.
- Set gExportUI to 1 in the beginning of the Start method of ssReport in sscustom.rol.
- Compile and run by setting ssLanguage to the default language; for example, ENU (English).
The report executable and the user interface file are generated; for example, CUACCSVC.rox and CUACCSVC.txt.
NOTE: This executable is for design time use only.
- Localize the contents of cuaccsvc.txt into separate language specific files.
- Generate cuaccsvc.txt file specific to each language.
- Place each of the language specific TXT file in
LANGUAGE = the Siebel code for the language the report will use; for example, ENU for U.S. English.
- Run the report in Deployment mode to verify localization.
- Set gExportUI to 0 in the beginning of the Start method of ssReport in sscustom.rol.
- Recompile to create the report executable for the runtime deployment by setting ssLanguage to FRA (French), DEU (German), JPN (Japanese) and so forth as needed.
- Verify that the language specific labels are displayed in the Actuate e.Report Designer Professional for each user specified language parameter.
NOTE: After testing a multilingual report, make sure that the report executable is created in the Deployment mode; for example, set gExportUI to 0 at the beginning of the Start Method in ssReport in sscustom.rol.