skip to main content
OpenEdge Development: Visual Translator
Translating : Pretranslation
 
Pretranslation
Before you start the translation process, you can perform a pretranslation on the text phrases in your kit. Pretranslation is a task you can perform that matches each text phrase with the first possible glossary entry. Visual Translator translates all text phrases at once. This task allows you to review and edit suggested translations before you start the manual translation process. To facilitate the review process, you can generate a hard-copy pretranslation exceptions report or print the information to a text file.
You can generate a pretranslation exceptions report that provides you with the following information about each string within a procedure file:
*Untranslated source strings
*Translated strings with no glossary match
*Translated strings that have more than one possible translation
The pretranslation exceptions report also provides the following summary information, by procedure and by project:
*Total number of translation strings
*Number of new translation strings
*Number of new translation strings that have more than one possible translation
*Number of previously translated strings
To pretranslate text phrases in a kit:
1. Choose ToolsTranMan UtilitiesPre-translation. The PreTranslation dialog box appears:
2. Select one of these options for pretranslating phrases:
*Translate case-sensitive matches — The Translation Manager translates only the text phrases that match a glossary entry exactly. For example, the Translation Manager will not translate “Customer Name” if the glossary entry is “customer name.” Although the text phrase is the same, the case does not match the glossary entry.
*Use case-insensitive match if necessary — The Translation Manager searches for an exact match with a glossary entry first. If there is no glossary entry that matches the text phrase exactly, the Translation Manager searches for a match regardless of case. You should select this button if you do not want leading and trailing blanks ignored.
*Use case-insensitive match and trim phrase if necessary — The Translation Manager first searches for exact matches with glossary entries, then it searches for a match regardless of case. Finally, it ignores leading and trailing blanks by trimming them from the phrase before looking for a match.
3. Activate the Exceptions Report toggle box if you want a hard-copy report (or to save the information to a text file).
4. Select your print options. If you select the Output To Printer radio-set button, you do not need to enter a filename. The default filename is pretrans.log. If you select the Output to A Text File radio-set button, you must either enter a filename or use the default filename, pretrans.log.
5. Choose OK. A pretranslation report prints:
 
Visual Translator PreTranslation Report                               Page 1
Project: GetStart1 02/21/97 10:32 pm
Procedure: TMsource\b-cuslkp.w
City Untranslated
Country Untranslated
Current record has been changed. Untranslated
Name Untranslated
Search On Customer Name Untranslated
State Untranslated
You must complete or cancel the update before leaving t... Untranslated
c:\progress\TMsource\b-cuslkp.w should only be RUN PERS... Untranslated
on-top Untranslated
SUMMARY:
10 Strings Total 100 %
0 Existing Translations 0 %
1 Strings Translated 10 %
9 Strings Untranslated 90 %
0 Strings with Multiple Translations 0 %Procedure:
TMsource\w-ordtrk.w
&Update Customer Untranslated
3,1 Untranslated
Customer Order Tracking Untranslated
Customer|Shipment|Order lines|Catalog Untranslated
SUMMARY:
4 Strings Total 100 %
0 Existing Translations 0 %
0 Strings Translated 0 %
4 Strings Untranslated 100 %
                        0 Strings with Multiple Translations 0 %
GRAND SUMMARY:
14 Strings Total 100 %
4 Existing Translations 8 %
1 Strings Translated 1 %
13 Strings Untranslated 91 %
                        0 Strings with Multiple Translations    0 %