skip to main content
OpenEdge Development: Translation Manager
Translation Manager Interface Reference : Tab folders
 
Tab folders
The main interface component of the Translation Manager tool is the tab folder. When you select one of the tabs shown below, the Translation Manager displays the corresponding folder:
 
The tabs allow you to view the following folders:
*Procedures — Lets you specify the source files you want translated. You can specify entire directories or individual files. Also, it lets you peruse and edit source procedures.
*Data — Lets you extract text phrases from the source procedures you selected in the Procedures folder, specify filters, and load the extracted text phrases through the filters into the project database. Lets you create resource procedures—the user‑interface procedures that the translators will use to translate text phrases and user‑interface objects in context. Also, it lets you import and export data strings to a third‑party translation tool.
*Glossary — Lets you create and maintain glossaries with the option of using Microsoft Glossaries provided with the Translation Manager tool. Also, you can import and export glossary data.
*Kits — Lets you create a language kit for each translator. Each kit, when zipped (compressed), includes a database that contains text phrases to be translated and a glossary, resource procedures, image files, and an environment (progress.ini) file for the resource procedures. Also, you can consolidate a translated kit into the project database.
*Statistics — Lets you view various statistics for the current project including the date you created the project, the size of the project, the code page, the number of procedures and text phrases, and the number of words. You can also generate a hardcopy of the statistics report or save the report to a text file.
Procedures tab folder
Use the Procedures tab folder to create a list of the source procedures you want to translate. Chapter 4, “Managing Projects,” describes how to use this folder. Figure A–1 shows the Procedures tab folder.
 
Figure A–1: Procedures Tab folder
The Procedures tab folder contains the following user‑interface elements:
*Source Directory — Displays the pathname of the root directory for the source procedures.
*Directories — Displays the subdirectories within the source directory that contain the source procedures.
*Browse Viewer:
*File Name — Displays the name of the source procedure (.p or .w) file.
*File Size — Displays the size of the source procedure, in bytes.
*Last Updated — Specifies the date and time the source procedure was last changed by a developer.
*Status of Last Kit — Specifies the number of translated text phrases and the total number of text phrases in the kit that you last consolidated into the project database.
*Resources Generated? — Indicates whether you have generated a resource procedure (.rc) file from the source procedure.
*Comments — Lets you enter comments about the procedure for the translator.
*Action Buttons:
*Add — Displays the Add Procedures dialog box, which lets you add the names of the source procedures you want to translate to the project database.
*Remove — Removes the selected procedure or directory from the list of procedures in the project database. Note that you can only remove a directory after deleting all the procedures it contains.
*Scan — Displays the File Scan dialog box, which lets you compare the source procedures in the project database list to the source procedures in the source code directory and internally marks files so you can extract them separately.
*Edit — Opens a Procedure Editor window in which you view and edit the selected source procedure.
Data tab folder
Use the Data tab folder to extract text phrases from the source procedures, set filters, load text phrases into the project database, generate resource procedures, and view or edit the source procedures. Chapter 5, “Preparing Data for Translation,”discusses how to use this folder. Figure A–2 shows the Data tab folder.
 
Figure A–2: Data tab folder
The Data tab folder contains the following user‑interface elements:
*Language Combo Box — Displays the name of the current target language.
*Browse Viewer:
*Source Phrase — Displays the text phrase in the original, source language.
*Target Phrase — Displays the text phrase in the current target language.
*Procedure Name — Displays the name of the procedure file that contains the text phrase.
*# Occurs — Displays the number of times the text phrase occurs in the procedure file.
*Line Number — Indicates the line numbers on which the text phrase occurs in the procedure file or its associated include (.i) file. Displays the unknown value (?) if the text phrase occurs on more than one line number in the procedure file.
*Justification — Provides the justification format for the text phrase in the user interface: Center, Right, Left, or Trim.
*Length — Provides the number of characters allocated for the text phrase.
*Object Name — Indicates the type of user‑interface object that contains the text phrase.
*Statement — Indicates the 4GL statement associated with the text phrase.
*Item — Provides a 4GL keyword that clarifies the Progress4GL statement.
*Comments — Lets you enter comments about the text phrase for your own use. The translators will not see these comments; they can only view the comments you write in the Procedures tab folder.
Note: You can double‑click on any field to display the Long String Translator dialog box. You can view the source string text in the Source String viewer. You can view and edit target string text in the Target String viewer.
*Action Buttons:
*Extract — Displays the Extract dialog box, which lets you extract text phrases from the source procedures into a temporary STRING-XREF file.
*Filters — Displays the Filter Wizard, which lets you specify filters where you load the text phrases from the STRING-XREF file to the project database. The Filter Wizard contains fourteen panels. The first ten let you specify the 4GL text phrases you want to include. Panels eleven, twelve, and thirteen let you specify words you want to exclude. The final panel provides a summary of the filters you specified.
*Load — Displays the Load dialog box, which lets you load the text phrases from the STRING-XREF file, through the filters, into the project database.
*Resources — Displays the Resources dialog box, which lets you generate resource procedures that the translators will use to visualize the application as they translate the text phrases.
Glossary tab folder
Use the Glossary tab folder to add glossaries to the project database. See Chapter 6, “Adding Glossaries,” for instructions on using this tab folder. Figure A–3 shows the Glossary tab folder.
 
Figure A–3: Glossary tab folder
The Glossary tab folder contains the following user‑interface elements:
*Glossary combo box — Displays the name of the current glossary.
*All radio‑set button — Displays all the glossary entries.
*Default radio‑set button — Displays only the glossary entries you entered with the Translation Manager tool.
*Custom radio‑set button — Displays only the glossary entries entered by the translator with the Visual Translator tool.
*Browse Viewer:
*Source Phrase — Displays the text phrase in the original, source language. You can edit this field.
*Target Phrase — Displays the text phrase in the current target language. You can edit this field.
*Modified by Translator? — Displays yes if the translator altered a default glossary entry or if the translator added the entry; displays no if the translator did not alter the glossary entry.
*Type — Displays D (for default) if the entry was added with the Translation Manager tool; displays C (for custom) if the entry was added with the Visual Translator tool.
Note: You can double‑click on any field to display the Long String Translator dialog box. You can view the source string text in the Source String viewer. You can view and edit translation text in the Target String viewer.
*Action Buttons:
*Add — Displays the Add Glossary dialog box and lets you add a glossary table to the project database.
*Remove — Deletes the entire selected glossary table from the project database.
Kits tab folder
Use the Kits tab folder to create kit databases and zip files. Also use it to unzip a kit you receive from the translators. Chapter 7, “Preparing a Kit,” and Chapter 8, “Incorporating a Translated Kit into the Project,” discuss how to use this folder. Figure A–4 shows the Kits tab folder.
 
Figure A–4: Kits tab folder
The Kits tab folder contains the following user‑interface elements:
*Browse Viewer:
*Kit Name — Displays the name of the current kit.
*Language Name — Displays the name of the current target language.
*Glossary Name — Displays the name of the current glossary.
*Create Date — Indicates the date you created the kit database.
*Zipped? — Indicates whether you created a zip file for the kit.
*Consolidated? — Indicates whether the kit has come back from the translator and you have consolidated it into the project database.
*Phrases Translated? — Indicates the total number of phrases translated in the kit.
*Percent Translated — Indicates the percentage of text phrases translated in the kit.
*Action Buttons:
*Add — Displays the Add Kit dialog box and lets you add a kit to the project database.
*Remove — Deletes the selected kit name from the project database. Also lets you delete the corresponding kit database.
*Consolidate — Displays the Consolidate dialog box and lets you consolidate the translated text phrases and custom glossary entries into the project database.
*Create Zip file — Displays the Create Zip File dialog box and lets you compress the kit into a zip file.
*Install Zip file — Displays the Install Zip File dialog box and lets you decompress a kit zip file returned from the translator.
Statistics tab folder
Use the Statistics tab folder to view the statistics for the current project database. Figure A–5 shows the Statistics tab folder.
 
Figure A–5: Statistics tab folder
The Statistics tab folder contains information divided into sections for the current project, the kits in the current project, and any glossaries in the current project that are not part of a kit. You can generate a hard‑copy report or send the report to a text file. For more information on the Statistics report, see Chapter 9, “Updating a Project.”