
You can create proposals as exceptions in the proposal pool . An exception is a proposal that is only valid for a specific context within a domain, but not throughout the domain.
You should define translations as exceptions in the proposal pool if you only want to use them in the context of the object you are currently translating.
The following English translations of German source texts are examples of exceptions:
|
Source Text |
Usual Translation (System Standard) |
Exception |
|
Alter |
Age |
Old |
|
Belege |
Documents |
Vouchers |
|
Aktion |
Action |
Promotion |
|
Bild |
Screen |
Image |
Exceptions are domain-specific, and they are never the best proposal. You can use the system standard or application standard to translate the source text, depending on which of them is the best proposal , even if an exception exists for the domain in which you are currently translating.
If you translate a source text line with an exception , other source text lines that have already been translated with an application standard or system standard retain their translation status translated .
If you want to use the system standard to translate a source text line, but an application standard exists that differs from the system standard , you must create the translation already defined as a system standard as an additional exception for this domain.
The system standard for Auftrag is Order . The translation Request is the application standard for the domain Basis (BC).
This means that Request is the best proposal when you translate objects belonging to the domain BC. However, you may need to use Order as a translation of Auftrag in a few specific contexts in the domain BC.
Create Order as an exception for the domain BC. Request is still the best proposal for Auftrag in objects from the domain BC, but you can also save Order as a translation of these objects.
As a result, the status of translation lines changes to translated in objects assigned to domain BC, irrespective of whether you enter Request or Order as your translation of Auftrag. It also ensures that the existing translation Request remains valid, so the status is still translated .
Exceptions are never the best proposal, so they are not displayed in the short text editor . To see if exceptions exist for a specific source text, you need to branch to the proposal pool from the short text editor.
To use an exception as a translation for a short text, double-click the exception in the proposal pool. The system inserts the exception into your translation line and returns to the short text editor. The system displays the
icon in the status bar of a source text that has been translated with an exception.
Exceptions do not have a quality status . If you create an exception, you therefore do not have to assign a quality status to it.
You cannot create abbreviations for exceptions. If you need to create an abbreviated translation as an exception, you must create it as an additional exception for the domain in question.
You can create as many exceptions as you like for a domain. We recommend that you minimize the number of exceptions you create.
For more information on proposal pool concepts, see Proposal Pool , Proposal Pool Concepts and the subordinate documents.
For more information on creating, changing, and deleting proposals, and on accessing the entries in the proposal pool, see Proposal Pool Maintenance and the subordinate documents, as well as Transaction SLPP .