Translation Manager facilitates the process of translating 4GL applications, but it does not eliminate the need for planning ahead. To successfully create a multi‑lingual product, developers must design and create applications with translation in mind. For more information on preparing a project for translation, be sure to read Chapter 1, “Preparing Your Application for Translation,” and OpenEdge Development: Internationalizing Applications.
The translation management system consists of two tools designed to work together—the Translation Manager and the Visual Translator. Together, these tools facilitate and manage the entire process of translating the text phrases in an application into one or more languages. This book describes how to use the Translation Manager tool. For information on how to use the Visual Translator, see OpenEdge Development: Visual Translator.
The translation project manager uses the Translation Manager tool to prepare code for translation and then sends a kit to the translator, who uses the Visual Translator tool to translate the text phrases. The translator then sends the translated kit back to the project manager, who uses Translation Manager to consolidate the kit and produce the final translated application.
As the translation project manager—the person in your company who oversees the entire process of translating your company’s software applications—you are responsible for:
Determining the source code to translate. Note that if you use third‑party applications or components, such as an ActiveX control, you must verify that the application is localized. A localized application is an application that is customized for a specific region. Do not assume that you can translate the third‑party software.
Developing the application with the appearance of the translated application in mind. Note that you must plan for text expansion and differences in layout that result from translation.
Working with developers to prepare the source code for translation. Note that there might be behavioral differences and varying filter requirements as a result of translation.
Defining the types of text phrases to translate.
Estimating the volume of translation to be done.
Providing the necessary information (such as text phrases and glossaries) to the translators, in a form that is usable to them.
Reviewing the translated text phrases received from the translators.
Incorporating the translated text phrases into the application.
Compiling the source code with the translated text phrases to create a multi‑lingual product.
The Translation Manager tool helps you, the project manager, complete these tasks.
The translator—the person who translates words and phrases from one language into another—uses the Visual Translator to translate an application’s text phrases. The Visual Translator presents the translator with views of the text phrases as they actually appear in an application so that the translator can ensure that the translation’s meaning is appropriate for the context and so that the translator can fit the translation into space allowed by the application’s interface.
Figure 2–1 illustrates the technical concepts involved in translating the text phrases in a 4GL application.
Figure 2–1: Overview of translating an application
Figure 2–2 illustrates the steps the project manager follows with the Translation Manager tool and the interaction between the Translation Manager tool and the Visual Translator.
Figure 2–2: The Translation Manager translation process
Determining the source code to translate. Note that if you use third‑party applications or components, such as an ActiveX control, you must verify that the application is localized. A localized application is an application that is customized for a specific region. Do not assume that you can translate the third‑party software.
