HP-UX Event ManagerProgrammer's Guide

NOTE: The evmwatch command does not return the templates of any events for which you
do not have access authorization. Hence, you must log in as superuser to view your templates.
Establishing Translations for Event Text (I18N)
The objective of event internationalization (I18N) is to enable an event's format data item, and
the values of any string variables contained in the event, to be converted to another language
for display. If you are developing a product that is used internationally, you can include support
for translation of any or all of these items.
Different users may want to view the same stored event in different languages. Language
interpretation must be performed at the same time when the event is formatted for presentation,
not when it is posted. It is impractical for an event to carry the text in all possible languages.
Hence, its associated message catalog must be available when the event is formatted. Product
developers are responsible for providing message catalogs and for including them during
installation along with their products. In case the catalog is not available, an internationalized
event can carry a default native-language string.
The following data items support internationalization of events:
• I18N message catalog name
• I18N message set identifier (optional)
• I18N message identifier for the format data item
• Separate I18N message identifier for each internationalized string variable
• Default native-language strings for any or all of the previous items in this list
All message identifiers for the event must relate to the same message catalog, and they must all
belong to the same message set (1, by default).
In general, the catalog ID, set ID, and message ID for the event format string must be supplied
in the event template, because the format string is usually fixed. If events contain string-type
variables, the variables are likely to refer to items such as device names or application names,
which usually are not translated, regardless of the language for display. Hence, in most cases, it
is not necessary to supply a message ID. In rare cases, where the value of a string variable needs
to be translated, the poster must supply the message ID.
Table 2-6 lists some examples of internationalized values for an example event.
Table 2-6 Example Data Item Values for an Internationalized Event
Message IDValueEvent Data Item
n/a
acme.prod.env.temp
Name
n/a
acme_prod.cat
Message catalog
541Temperature of sensor $sensor is
$temperature
Format string
n/a
S27
String variable “sensor”
542high
String variable “temperature”
English and French versions of temperature.cat contain:
• English
— 541:Temperature of sensor $sensor is $temperature
— 542:high
— 543:low
• French
28 Event Manager Events