The Exceptions File: overview

ECCEZIONE SCHEDARIOEL ARCHIVO DE EXCEPCIONES

The Exception File consists of translation exceptions defined by the application designer. Most translations are defined via the Dictionary and Translations Files as described in previous sections. There are times, however, when the designer may wish to override the translation for a specific word, clause, or sentence. For example, a sentence might not have a translation defined for it but the Language Translator is able to translate its component words. While the translation is successful, it might result in grammatical nonsense that requires a more meaningful translation to provide a polished presentation. Exceptions might also be defined for sentences or text that the Language Translator can only translate in fragments, resulting in text that displays with only a partial translation.

Exceptions can be defined and maintained using these methods:

1. Via Exception File Input Processes found on the application’s Language Translation Menu

The preferred method when you have a number of exceptions to define and plan on dedicating a block of time to define them. This method provides for a means of sequentially accessing only the items for which exceptions can be made.

2. Directly from Application Design while in Data Dictionary Management or Process Management

This is the most efficient method when designing new applications that were not originally part of the application’s initial Dictionary File build and translation process. It is also recommended when defining exceptions for a limited number of items. For the bi- or multi-lingual designer, it is more efficient to define translations as exceptions on the fly while designing than to later add items into the Dictionary File and define translations in the Translations File.

Before learning how to make exceptions, it is first important to learn when (i.e. what design components) exceptions can be made. Take a look at the following chart: