The short text editor enables you to enter a translation in the translation line of each source text in a short text object. Each translation that you enter must match a valid proposal in the proposal pool. This means that if there is no proposal for your translation, or if you do not want to use an existing proposal, you must create a new proposal. You can also decide to accept the best proposal. For some examples, see the graphic below. The translation of a source text is available in the system after you have saved it in the short text editor.
Once a translation and a proposal exist for a source text, the text line has the status translated. Once all of the texts in the short text object have been translated, you can proceed to the next short text object you need to translate. If you cannot translate all of the texts in the short text object immediately, you can return to the object later.
Creating entries in the proposal pool while translating objects in the short text editor is not a prerequisite for ensuring that the objects can be displayed in your target language when you log on to the system in that language. If you do not maintain the proposal pool, you cannot reuse translations because you have no best proposals, and therefore no automatic distribution.
For more information on the translation status, see Translation Status.
In the ABAP environment, short text objects are translated in the short text editor.
These objects consist of one or several separate lines of text.
To access the short text editor and translate short texts, you can:
· Perform sequential processing in a personal worklist
· Double-click a specific object in your personal worklist
For more information on these two options, see Translating Objects via a Personal Worklist.
· Access an object directly from the initial screen of transaction SE63
To do this, choose Translation → ABAP Objects → Short Texts. This takes you to a dialog box that enables you to select the required object type. In the dialog box that is now displayed, enter the technical name of the object and, depending on the object type, additional technical information and choose Edit. The short text editor is opened. If you know the shortcut for the object type, you can enter it directly in the command field and access the object this way instead. (See Translating Objects Directly).
In the non-ABAP environment, interface texts are translated in the short text editor. There are two different types of interface text: fragments (X types) and sentences (Y types). Fragments are texts that are not sentences in their own right. They cannot exceed 255 characters. Examples include the names of pushbuttons or fields. Sentences are complete sentences. They cannot exceed 16,384 characters. The individual elements within a sentence cannot have their own formatting, such as bold type or italics. Only fragments are translated in the short text editor. Sentences have their own editor. For direct access, choose Translation → Non-ABAP Objects -> Interface Texts (Fragments). Alternatively, enter x in the command field. If you know the object type, you can also access the object by entering its shortcut in the command field.
For more information on how to translate non-ABAP objects, see the appropriate documentation.
The title of the short text editor displays the following information:
· Object type that you are currently translating
You can recognize the object type by its four-character ID.
· Domain to which the object belongs.
The domain to which a text belongs is derived from its collection. If you create an application standard or exception in the proposal pool while translating the text, they are assigned to this domain. The best proposal concept takes this domain into account.
If a single character is displayed in the title (like J for example), ask your translation coordinator to refresh the translation hierarchy. For more information, see Refreshing the Translation Hierarchy.
· Source language and target language combination
For example, if you are translating from German to French, the system displays From deDE to frFR in the title bar.
· Technical name of the object
Depending on the object type, short text objects are broken down into several lines. For example, data elements can consist of up to five lines that are offered for translation in five separate lines. A short text is limited to 255 characters in one line.
The individual lines to be translated are displayed as follows:
· Status bar
The status bar contains an area whose color indicates the translation status of the line. If this area is red, the translation status is new. If it is yellow, the translation status is modified. A green area indicates that the translation status is translated.
The system also displays the following technical information in the status bar:
¡ Type of source text, such as menu entry or quick info
¡ Number of proposals that exist of the same type as the best proposal.
¡ Type of proposal in the proposal pool that matches the entry in the translation line (system standard, application standard, or exception.)
¡ Quality status of the proposal pool entry that matches the translation in the translation line.
¡ Type of proposal in the proposal pool that is the best proposal (system standard or application standard)
¡ Quality status of the proposal pool entry that is the best proposal.
¡ Maximum input length
· Source text line
· Translation line
This is where you need to enter your translation, or where the system displays the existing translation. The length of the translation line indicates how much space is available for your translation.
· Best proposal
If the source text has been translated before, the best proposal is displayed beneath the translation line.
For more information on the icons in the short text editor, see Functions in the Short Text Editor.
The graphic below contains the following three examples of texts in the short text editor:
· In the case of the first line to be translated, the area in the status bar is red. The text line has status new. You can see that the translation line below the source text line is empty. No proposal exists for this source text in the proposal pool, as nothing is displayed in the line that usually contains the best proposal.
¡ Enter a translation in the translation line, choose Save, and then branch to the proposal pool to create your translation as a proposal.
· In the case of the second line to be translated, the area in the status bar is yellow. The text line has status modified. That is because there is no valid proposal for the translation in the translation line.
¡ You have the following two options:
§ Replace the current translation in the translation line with the best proposal. To do this, simply double-click the best proposal and choose Save.
§ Continue to use the current translation. To do this, branch to the proposal pool and create the translation as a proposal. For more information, see Creating Proposals in the Proposal Pool.
· In the case of the third line to be translated, the area in the status bar is green. The text line has status translated. You can see that the translation line contains a translation that matches the best proposal displayed beneath the translation line.
For more information on working with the short text editor, see the following topics:
The editor’s standard settings are intended for ordinary translation processes. You can change these settings according to your specific requirements.
These topics explain the three translation statuses new, modified, and translated in more detail.
These topics provide you with information on the icons and pushbuttons in the short text editor.