Event Text Translation

When the CAISDI/els interface opens a ticket for a product, it can translate the text of some or all events into another language.
Required roles: systems programmer
Using our earlier example, to translate L0Y001EN into another language, create a member name that begins with 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)
For example, to translate L0Y001EN into German, create a member that is named L0Y001DE. Only the contents of the summary and description sections should be translated.
To select an alternate language for processing, use one of the following options:
  • Include the LANG parameter on the DEFINE command for the product in the ELSSTART CAI.CAW0OPTN member. If you want the LANG parameter to apply to all products, code it in the DEFAULTS command.
  • 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 in the DEFINE command.
For this example, include LANG=DE on the control statement.
Structure the text in text fragments to minimize the amount of ECSA that is required to store it. If the same clause appears more than once across all events for a given product, specify that clause on a line by itself. Doing so causes that clause to be stored once, and all events reference that one clause. If you translate the text, be mindful of the ECSA storage that is occupied while the CAISDI/els interface is active.
If you translate only some events, CASIDI/els substitutes the English version for the events that you do not translate.