To view the latest 11.3.x version, see  PATROL Agent 11.3.02 .

Internationalization and localization requirements

This section lists the internationalization (I18N) and localization (I10N) requirements for a KM. This section presents the following topics:

Externalize message IDs and catalogs

KM messages (menu command strings, dialog messages, event catalogs, etc.) must be externalized in the form of message catalogs. For more information about message catalogs, see PATROL Script Language overview and functions.

Use complete messages in catalog files

KM message catalogs must contain complete messages to facilitate translation. Messages must not be broken into segments in the message catalogs.

Use vendor IDs for catalog files

The KM must use its unique vendor ID that uniquely identifies the vendor.

A vendor or group is allocated only one vendor ID that is used for all KMs created by that vendor or group.

For more information about catalog files, see PATROL Script Language overview and functions.

Use tool IDs for catalog files

The KM must use its unique tool ID.

A vendor or group is allocated a range of tool IDs that are used for all KMs created by that vendor or group.

For more information about catalog files, see PATROL Script Language overview and functions.

Support system locales

The KM must support the system locale and not make any assumptions as to the character size.

Use file paths in localized format

The KM must handle file paths, within the context of the monitored application, in the localized format correctly.

Perform codeset conversion

When the KM communicates with an external process with a compatible locale but a different codeset, the KM must perform the codeset conversion.

Support locale uniqueness

The KM must correctly translate the monetary, time, date, and demographic specific formats for supported locale.

Sort text correctly

The KM text sorting must operate based on the alphabetical order defined for supported locale.

Support multi-byte characters

The KM must not split multi-byte characters when reading or writing data files.

Provide locale translation

If localization is required, the KM menu commands, InfoBox items, window captions, graph titles, and units. must be translated into the supported locale and be displayed correctly.

Note

Local translation is driven by marketing requirements and may or may not apply to the KM.

Support language enablement

If language enablement is required, the KM must accept and display the characters of the required languages correctly.

Note

Language enablement is driven by marketing requirements and may or may not apply to the KM

Was this page helpful? Yes No Submitting... Thank you

Comments