The system standard is a translation stored in the proposal pool. The system standard is valid across all domains in which no application standard exists.
Many source texts are not domain-specific, which means they do not require a domain-specific translation. In such cases, you should define your translation of the source text as a system standard.
The following German source texts and their English translations are examples of system standards:
German Source Text |
English System Standard |
Sichern |
Save |
Beenden |
Exit |
Springen |
Goto |
If you define a single system standard for a source text, you ensure consistent translations throughout the system. This is particularly important for basic command texts that have the same meaning in all domains.
System standards enable you to translate source texts that appear multiple times.
When you translate a short text line, the system standard is offered as the best proposal when the following criteria are met:
· A system standard exists in the proposal pool for the source text.
· No application standard exists for the source text in the domain of the object to which the text belongs.
· The system standard fits into the space available in the translation line.
To insert the system standard into the translation line, double-click it. When you save, this short text line has the status translated.
When you create a system standard, the system prompts you to assign a quality status to it. Your translator profile determines the quality statuses that you can assign.
You can create abbreviations for system standards. They are used when the translation line is too short for the full translation. For more information, see Abbreviation.
Sometimes, more than one system standard exists for a source text. For more information, see Creating Multiple System / Application Standards.
Creating Proposals in the Proposal Pool