Scanning for a Specific Source / Target Text
String
Use
You can perform a scan to find the following:
● A specific source text string.
For example, you want to check all instances of a specific source text string to verify that it has been translated correctly and consistently.
● A specific target text string
For example, you want to find all instances where a specific translation has been used, regardless of what the source text is.
● A specific source text and target text string
For example, you only want to find instances where a specific source text string has been translated in a particular way.
You can perform this scan in two different ways:
● Scan the objects in a specific object list for a specific source and/or target text string.
● Scan the entire proposal pool (or a domain in the proposal pool) for a specific language combination for a specific source and/or target text string.
Prerequisites
See the Prerequisites section in DEMS Objects for Quality Assurance.
Procedure
1. Call up transaction LXE_MASTER.
2. Choose Environment → DEMS Objects.
○ To scan for text strings in the objects in a specific object list, choose the Object List pushbutton, next to Text Search.
○ To scan for text strings in the entire proposal pool, choose the Proposal Pool pushbutton, next to Text Search.
3. Enter your selection criteria for the scan as follows:
Name of DEMS objects |
In the NAME field, enter a text string that will help you recognize the DEMS objects when you call them up in transaction SE63. |
Description |
You can enter a description of up to 40 characters in the DESCRIPT field to document how you created the DEMS objects, for example. |
Source language |
In the S_LANG field, enter the required source language for the text scan. |
Target language |
In the T_LANG field, enter the target language for the text scan. |
Object list (Only available if you perform the Object List scan) |
Choose F4 on the OBJLIST field, and select the object list that contains the objects for which you want to perform the text scan. |
Source text |
In the S_TEXT field, enter the source text string that you want to find. To search generically, ensure that you enter a * at the start and end of the string. If you do not want to scan according to source text, ensure that this field contains the default value *. |
Target text |
In the T_TEXT field, enter the target text string that you want to find. To search generically, ensure that you enter a * at the start and end of the string. If you do not want to scan according to target text, ensure that this field contains the default value *. |
Case-sensitive source text scan |
We recommend that you leave the S_NO_CASE field blank in order to perform a case-sensitive scan, which is less performance-intensive. You can still search in a case-sensitive manner, by leaving this field blank and entering the source text minus its first letter in the S_LANG field. For example *uftrag* would enable you to find all source texts that contain either the string Auftrag or the string auftrag. Similarly, *rder* would enable you to find all source texts that contained either the string Order or the string order. |
Case-sensitive target text scan |
We recommend that you leave the T_NO_CASE field blank in order to perform a case-sensitive scan, which is less performance-intensive. You can still search in a case-sensitive manner, by leaving this field blank and entering the target text minus its first letter in the T_LANG field. For example *uftrag* would enable you to find all target texts that have a proposal containing either the string Auftrag or the string auftrag. Similarly, *rder* would enable you to find all target texts that have a proposal containing either the string Order or the string order. |
Maximum number of source texts |
In the NUMBER field, you can specify a limit to how many source texts are contained in the DEMS objects produced by the scan. If you want the scan to find all source texts with proposals that match your selection criteria, enter a suitably high number here. |
Create object list |
If you enter the value X in the MAKE_OL field, the system creates an object list that contains the DEMS objects created in the run. This enables you to create worklists for the top texts by evaluating this object list. To do this, you first need to create a graph for collection $TMP and then activate it for the target language that will process the DEMS objects. |
Domain to be scanned (Only available if you perform the Proposal Pool scan) |
If you scan the proposal pool, you can restrict the scan to search only in the application standards and/or exceptions created in a specific domain. To do this, make sure the field DOMATYP contains the value *, choose F4 on the DOMANAM field, and double-click the domain in which you want to scan. To search in all domains of the proposal pool, make sure the fields DOMATYP and DOMANAM both contain the value *. |
Types of proposals (Only available if you perform the Proposal Pool scan) |
You can exclude exceptions from your scan, or scan exceptions only. ● To exclude exceptions from the scan, make sure the NORMAL field contains the value X and the EXCEPT field is blank ● To scan exceptions only, make sure the NORMAL field is blank and the EXCEPT field contains the value X |
Schedule top text job in the background |
Ensure the BATCH field contains the value X so that the job to create the top texts runs in the background. |
4. Choose Execute (F8) and schedule the job to run in the background.
Result
Depending on the scan method, the system scans the objects in the object list specified by you, or the proposal pool, and creates DEMS objects in accordance with your selection criteria.
You can now trigger processing of these DEMS objects. For more information, see Processing DEMS Objects for Quality Assurance.
Example
You have found out that since the start of the translation project, the German text Vertrag has been incorrectly translated into English as contract. In the context of your development, the correct English translation is policy. You want to clean up the entire proposal pool so that this problem is solved once and for all. The first step is to find all German source texts containing the string Vertrag or vertrag that have a proposal containing the string Contract or contract.
...
1. Call up transaction LXE_MASTER.
2. Choose Environment → DEMS Objects.
3. Choose the Proposal Pool pushbutton, next to Text Search.
4. Enter your selection criteria for the scan as follows:
Field |
Input |
NAME |
CONTRACT_EN |
DESCRIPT |
DE *ertrag* EN *ontract* |
S_LANG |
deDE |
T_LANG |
enUS |
S_TEXT |
*ertr* Why only *ertr* as the search string and not *ertrag*? Don’t forget that the plural of Vertrag is Verträge! A suitable example in English would be criterion and criteria. |
T_TEXT |
*ontract* |
S_NO_CASE |
Leave blank |
T_NO_CASE |
Leave blank |
NUMBER |
Enter a suitably high value to ensure that all instances are included in the DEMS objects |
DOMATYP |
* |
DOMANAM |
* |
NORMAL |
X |
EXCEPT |
X |
CREA_OL |
X |
BATCH |
X |
5. Choose Execute (F8) and schedule the job to run in the background.