Length Variant 

Definition

For technical reasons, it is often not possible to write a translation out to its full length. This might be due to:

The translation must therefore be abbreviated. If the text appears in several places in the system, this might result in several different abbreviations of the same text, called length variants.

You can also create length variants for texts that have the same length but which differ with regard to upper-case and lower-case text. A length variant should, however, never be a different translation.

Use

In the proposal pool, all length variants of one and the same translation are stored in the same position of the hierarchy. They are thus all valid in the same application context.

If you need to create length variants of a target text, one of these variants must be marked as the Node Text. Normally, this is the longest (full length of text) length variant (otherwise, the longest abbreviation). The first standard translation will automatically become the node text. This can be changed later on, if necessary.

You can only create length variants for system standards and application standards, not for exceptions.

Integration

The graphic below illustrates the different kinds of length variant that are possible.