NLS message catalogs

With NLS message catalogs you can output the message texts in different languages irrespective of the linked message module. The message texts are then taken from the appropriate message catalog by the program at run time on a language-specific basis. The language is defined on Unix, Linux and Windows systems by evaluating the user’s
%LANG% environment variable.

NLS message catalogs contain only the message texts and no information on message destinations or message attributes. For evaluating the inserts, message destinations and message attributes and in response to an error, openUTM uses the standard message module or a user-defined message module, if one exists.

A UTM application can also be run without NLS message catalogs. For these reasons the UTM message module (supplied in the library utmpath/sys/libwork.* or, under Windows systems, in the library utmpath\sys\libwork.lib) must be linked into the application. In addition, a user-defined, modified message module can be linked in.

The NLS message catalogs can be ignored when the application is generated and when the application program is linked.

NLS standard message catalogs in German and English are supplied with openUTM and are stored in the following diretories, where lang is the language identifier:

• Unix and Linux systems: utmpath/nls/msg/lang

• Window systems: utmpath\nls\msg\lang

The message catalogs under .../lang and ...\lang have the following names:

Unix and Linux systems	Windows systems	Contents
utmsys.cat	utmsys.dll	K and P messages of the system
utmutil.cat	utmutil.dll	K messages of the utility programs
utmxprog.cat	utmxprog.dll	U messages

Application-specific message catalogs, i.e. message catalogs under filebase, are evaluated only for messages of the SYS function unit (message catalog name utmsys.cat or utmsys.dll) and the XPROG function unit (message catalog name utmxprog.cat or utmxprog.dll), see section “Evaluation of message texts”.