skip to main content
OpenEdge Development: Translation Manager
Preparing Data for Translation : Using third-party tools
Using third-party tools
You can use the Translation Manager tool in conjunction with third-party tools such as spell checkers by exporting the contents of the Data tab to the tool, using the tool, and then importing the material back into the Data Tab.
Exporting data strings
To prepare a Translation Manager project for export to a third-party tool, you must load and extract procedures, define filters, load strings, and create a glossary as you would for any project.
Note: The Export and Import menu choices are only available if there are strings in the project.
To export data to a third-party tool:
1. From the Data tab folder, choose FileExport. The Export dialog box appears:
2. Enter the name of the file to which you want to export the data. Use the file extension of .csu for all your export files. If you use this convention, you will later find it easier to distinguish data files from other types.
3. Check the Replace If Exists box if you want to replace an existing file with another file of the same name.
4. Specify the code page for the translation entries you want to export. If you need help determining the code page, contact the Project Manager.
5. Specify the name and language of the glossary.
6. Specify the target language of the strings that you want to export.
7. Specify the source language of the strings you want to export.
8. Optionally, specify which strings you want to export:
*All strings
*Translated strings only
*Untranslated strings only
You can now export the project to a third-party tool.
Importing data strings
When you have completed your work using the third-party tool, you can import the strings into the Data tab.
To import data strings into the data tab:
1. From the File menu, choose Import. The Import dialog box appears:
2. Enter the name of the text file that contains the data you want to add to the project. Select a file, then choose OK.
3. Specify the name of the glossary that you want to import. Activate the Update Glossary toggle box to update the glossary.
4. Choose one of the following options for reconciliation:
*Always Keep Newer Translations — The Translation Manager adds all the translations for all source phrases from the import text file, even if the project database already has a translation. If you activated the Update Glossary toggle box, the Translation Manager adds all new (custom) entries. If the translator modified any default entries, the Translation Manager adds the modified entry and retains the existing default entry.
*Always Keep Older Translations — If the project database already has a translation for a source phrase, the Translation Manager does not overwrite it with the translation from the import text file. The Translation Manager only includes a translation from the import text file if the project database does not already have one. If you activated the Update Glossary toggle box, the Translation Manager adds all new (custom) entries but keeps all existing default entries.
*Ask About Each Conflict — For each source phrase that has a different translation in the project database from that in the import text file, the Resolve Conflict dialog box appears and lets you decide which translation to save in the project database. This option does not affect the glossary.
5. Specify whether the text file that contains the translation entries you want to import separates the data phrases with a space (Space Delimited) or a comma (Comma Delimited).
Once you have imported your project back into Translation Manager, you are ready to proceed with the translation project.