Naming Convention [ Message Catalogs:Programmer's Guide ] MPE/iX 5.0 Documentation
Message Catalogs:Programmer's Guide
Naming Convention
Before a source file is formatted by the GENCAT utility, you must decide
how you are going to name your formatted catalog. Catalogs that are not
going to be localized may use any valid MPE XL file name. Catalogs that
are going to be localized should take some guidelines into consideration.
An application that has been localized into more than one language will
typically have a separate message catalog for each language. A naming
convention facilitates using different localized versions of files
required by an application program.
Each native language supported by Native Language Support (NLS) has a
three-digit language ID number. This ID number can be used as the last
three characters of each catalog file name to identify each localized
catalog. This convention is used when the NLAPPEND intrinsic selects the
message catalog for the local language at run-time.
The NLAPPEND intrinsic is called to concatenate the language ID number
and a generic five-digit catalog file name to form the name of the
catalog that is opened.
For example, an original unlocalized message catalog is APCAT000. The
message catalog in German would be APCAT008 because the language ID for
German is 8. NLAPPEND concatenates 008 to APCAT to create the name of
the catalog that is opened with CATOPEN.
Refer to the Native Language Programmer's Guide (32650-90022) for a
complete list of native languages and their corresponding language ID
numbers. Run the NLUTIL utility to see the languages that are available
on your system.
MPE/iX 5.0 Documentation