How to Implement CAISDI › Configure CAISDI/elmds › Configure the CAISDI/els Interface for Each CA Product › Notes on Translating Event Text

Notes on Translating Event Text

You may want to translate the text of some or all events into another language. Using our earlier example, if you want to translate L0Y001EN into another language, simply create a new member name that begins L0Y001 and use one of the following language codes:

• DA (Danish)
• DE (German)
• ES (Spanish)
• FI (Finnish)
• FR (French)
• IT (Italian)
• NO (Norwegian)
• PT (Portuguese)
• SV (Swedish)

If, for example, you translated L0Y001EN into German, you would create the member named L0Y001DE. Only the contents of the summary and description sections should be translated.

To select an alternate language for processing, you have two options:

• Include the LANG parameter on the DEFINE command for the product in the ELSSTART CAI.CAW0OPTN member. (You can code the LANG parameter in the DEFAULTS command if you want it to apply to all products.)
• Include the LANG parameter on the SETUP command in the Product Control Member. The LANG setting in the Product Control member overrides the LANG setting from the DEFINE command.

For this example, you would include LANG=DE on the control statement.

As mentioned previously, the text should be structured in text fragments to minimize the amount of ECSA required to store it. If the same clause appears more than once across all of the events for a given product, that clause should always be specified on a line by itself. This causes that clause to be stored once and all events will reference that one clause. If you translate the text, you must be mindful of the ECSA storage that is occupied while the CAISDI/els interface is active.

If you translate some, but not all events, CASIDI/els will substitute the English version for those you did not translate.