Preface
Purpose
Audience
Organization
Using this manual
Typographical conventions
Examples of syntax descriptions
OpenEdge messages
Preparing Your Application for Translation
Advantages of planning ahead
4GL considerations
Defining text as untranslatable
Defining alignment and space
Defining accelerator keys
Using default buttons
Screen layout considerations
Explicitly sizing and positioning widgets
Planning for text expansion
Creating adjustable text on rectangles
Length and width of text phrases
Creating message statements
Adjusting database field justification
Where to go for more information
Overview
Overview of the translation process
Tasks for the project manager
Tasks for the translator
Getting Started
Organizing a directory structure for the source code
Setting the PROPATH
Creating and storing environment (.ini) files
Starting the Translation Manager
Connecting to the application databases
Managing Projects
What is a project?
Determining the number of projects to create for an application
Creating a project
Opening a project
Selecting the current project
Closing a project
Selecting source procedures
Adding files to the procedures list
Removing files from the procedures list
Viewing and editing a file in the procedures list
Preparing Data for Translation
Extracting text phrases from source procedures
Specifying filters
Exporting and importing filters
Loading text phrases into the project database
Generating resource procedures
Working on subsequent iterations of a project
Procedure subsets and supersets
Using procedure subsets
Preparing text from a character application
Using third-party tools
Exporting data strings
Importing data strings
Adding Glossaries
Creating a glossary
Importing a glossary
Exporting a glossary
Tracking glossary entries
Preparing a Kit
What is a kit?
Building a kit
Deleting a kit
Pretranslation
Changing a kit's source language
Sending a kit to the translator
Incorporating a Translated Kit into the Project
Receiving the kit from the translator
Consolidating the translated kit into the project database
Compiling the source code with the translated phrases
Text segment expansion
Running the compiled code in a target language
Running code from the command line
Updating a Project
Printing a statistics report
Editing translations and glossary entries
Browsing through the tab folders
Sorting rows and ordering columns
Inserting and deleting rows
Cutting, copying, and pasting text
Scanning for changed source files
Tutorial
Preparing to use this tutorial
Creating a new Translation Manager project
The Procedures folder: adding files
The Data tab folder
Extracting text phrases
Specifying filters
Loading text phrases
Creating resource procedures
The Glossary folder
The Kits folder
Creating a kit
Creating a zip file
Installing a zip file and consolidating a kit received from the translator
Compiling source code with the translated phrases
Troubleshooting
Why can’t I start the Translation Manager?
Why do I receive error messages when I try to extract text phrases?
Why do I receive a “cannot find a file” error message?
Why do I receive an “open database table is full” error message when creating a kit?
How do I include the text phrases in SmartObjects?
Why can’t the tool display resource procedures?
Why does the Visual Translator tool display the text phrases in an undesired font in the resource procedures?
How do I avoid common errors and warnings in the Compiler’s log file?
Why do I receive error messages at run time?
Translation Manager Interface Reference
Tab folders
Procedures tab folder
Data tab folder
Glossary tab folder
Kits tab folder
Statistics tab folder
Menu bar
Toolbar
OpenEdge Development:Translation Manager
Toolbar