Progress
Report Builder
User’s Guide


Using a Translated Version of Report Builder or Report Engine

Report Builder and Report Engine use many text fields, dialog control labels, and other character strings. Many of these strings have been translated into languages other than English. Report Builder and Report Engine can use these translated strings as easily as they can use the English versions of these strings. This means that many users can run Report Builder and Report Engine and see the dialog boxes, menus, and layout window in their native language. Although Report Builder and Report Engine are translated, reports themselves are not translated.

The character strings for a particular language are stored in a resource file called the RBRES32 file. Each RBRES32 file contains strings in one language (such as English), but different files can use different languages. In other words, each language has its own RBRES32 file. There is only

one PRORB32.EXE executable and one PRORE32.EXE executable, but they both work with any valid RBRES32 file. At startup, each executable attaches an RBRES32 file and pulls character strings out of the RBRES32 file. This is what determines the language Report Builder appears in.

When Report Builder and Report Engine look for the RBRES32 file, they first check to see if the RBLNG environment variable has been defined. If so, they expect it to point directly to the RBRES32 file that they should use. Therefore, one way to choose a language for Report Builder and Report Engine is to set RBLNG to point to the RBRES32 file that corresponds to that language.

Each RBRES32 file is actually a DLL file, and the value of RBLNG must include a .DLL extension. It can be either a complete pathname or a relative filename. For example, it can be \RBAPP\RBGER32.DLL or RBGER32.DLL. If the value of RBLNG is a relative filename, Report Builder and Report Engine interpret it as relative to the directory containing the Report Builder or Report Engine executable.

NOTE: Report Builder does not look for a value of the RBLNG environment variable in the registry or PROGRESS.INI file (unlike other environment variables). This means that setting RBLNG has no effect. The only way to use RBLNG is to set it as a genuine DOS environment variable. This limitation is due to technical details of Report Builder. See the "Environment Variables" section later in this chapter for information about setting RBLNG.

If the RBLNG variable is not set to anything, Report Builder and Report Engine look for an RBRES32 file explicitly named “RBRES32.DLL”. They will look for RBRES32.DLL in the following places, in the order specified:

  1. Current working directory
  2. Windows directory (containing WIN.COM)
  3. Windows system directory (containing files such as GDI.EXE)
  4. Directory containing the Report Builder executable
  5. Directories listed in the PATH environment variable

If you do not set the RBLNG environment variable, you can also choose the language in which Report Builder and Report Engine work by copying the corresponding RBRES32 file into one of these locations (using the name RBRES32.DLL), so that Report Builder and Report Engine find it there.

The database engine, which Report Builder and Report Engine call, also uses the PROMSGS file to obtain error and warning messages. Therefore, if you want to run Report Builder and Report Engine in a certain language, make sure that the database engine can find the PROMSGS file that corresponds to that language. The database engine uses the same rules for finding the PROMSGS file as regular Progress clients. For more information, see the Progress Client Deployment Guide. For example, you can set the PROMSGS environment variable to indicate the correct manual file.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095