Using localized strings with a Java report application

Localized strings can be used to implement internationalization in your application or to use site-specific text (for example, when business terms change based on territory).

The Localized Strings feature allows:

  • the captions (titles of report objects) to be customized.
  • The translation of the Text property to be customized.

You could have multiple external string files, each containing the translated string in a different language. The runtime system searches the files in order to assign text in the report definition. The localized text replaces the captions and other specified text at runtime, choosing the correct string file based on entries in the fglprofile file.

The Source String file

A text file, with a str extension, defines the string to be displayed for the report object captions or the specified Word Box or WordWrap Box text. You can check the Text property of the report object to determine the exact string to be replaced.

"identifier" = "string"


  • identifier is the value of the Text property of the caption or label that you want to localize
  • string is the text that you want to be displayed instead

The backslash "\" is accepted as the escape character, to define non-printable characters.

Example file captions_en.str:
"Userid" = "Client ID"
"Shipcity" = "City"

At runtime, the text 'Userid" or "Shipcity" displays in the report as "Client ID" and "City".

In the Projects view, add the source string file to the application node for your report program, so it can be compiled when the application is built.

Using the translate function

Entries in the source string file can also be used by the translate PXML function to replace text in an expression that sets a property value. For example, if you set the text of a Word Box to this value:
"hello "+"world".translate() 
and you have this entry in the str file:
"world" = "universe"

then the final text displayed on your Word Box is “hello universe”.

Entries in fglprofile

You can specify the compiled string file, or a list of these files, with entries in an fglprofile configuration file. For example:
fglrun.localization.warnKeyNotFound= false     -- don't display warnings on errors
fglrun.localization.file.count = 1             -- number of string files = "captions_en.42s" -- name of the string file

Use the FGLPROFILE environment variable to specify the path to your fglprofile configuration file.