Release 10.1A: OpenEdge Development:
Visual Translator

> ## Preface

> This Preface contains the following sections:

> - Purpose

> - Audience

> - Organization

> - Using this manual

> - Typographical conventions

> - OpenEdge messages

> ### Purpose

> This manual describes how to use the OpenEdge™ Visual Translator tool to translate text phrases in Progress 4GL procedures.

> ### Audience

> This book is written for the translator-the person who translates the user-interface text phrases, such as labels and messages, from the source language to a target language. The translator must have some experience with personal computers and Microsoft Windows, but might have little or no experience with application development or the procedures in the translation project.

> ### Organization

> Chapter 1 "Overview"

> Describes the Visual Translator tool and provides an overview of how you can use the Visual Translator to translate the text phrases in a Progress 4GL application.

> Chapter 2 "Getting Started"

> Describes how to start the Visual Translator; use online help; load, open, and return a language kit; and import your own glossary.

> Chapter 3 "Translating"

> Describes how to translate text phrases with the Visual Translator tool. It provides an overview and step-by-step instructions on the two translation techniques: screen-by-screen translation and phrase-by-phrase translation.

> Chapter 4 "Tracking Your Work"

> Describes how to use the Visual Translator to check the status of translations, find untranslated text phrases, monitor glossaries, and print screen captures.

> Chapter 5 "Troubleshooting"

> Provides answers to some common questions.

> Appendix A, "Visual Translator Interface Reference"

> Provides reference information for the Visual Translator tool tab folders, menu bar, and tool bar for the main window and the Properties window.

> ### Using this manual

> This book is a guide to using the Visual Translator tool. Although you can use it as a reference, it is structured so that each chapter builds on the previous chapters. Therefore, you will learn the most if you start at Chapter 1 and read through until the end.

> Chapter 1 provides an overview of concepts and how the Visual Translator works with the Translation Manager tool. Subsequent chapters are task based-providing detailed instructions on how to use the Visual Translator tool. The Appendix contains reference information.

> ### Typographical conventions

> This manual uses the following typographical conventions:

> Convention | Description
> --- | ---
> Bold | Bold typeface indicates commands or characters the user types, or the names of user interface elements.
> Italic | Italic typeface indicates the title of a document, provides emphasis, or signifies new terms.
> SMALL, BOLD CAPITAL LETTERS | Small, bold capital letters indicate OpenEdge™ key functions and generic keyboard keys; for example, GET and CTRL.
> KEY1-KEY2 | A hyphen between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL-X.
> KEY1 KEY2 | A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
> Syntax:
>     Fixed width
> | A fixed-width font is used in syntax statements, code examples, and for system output and filenames.
> `Fixed-width italics` | Fixed-width italics indicate variables in syntax statements.
> `Fixed-width bold` | Fixed-width bold indicates variables with special emphasis.
>     UPPERCASE
>     fixed width
> | Uppercase words are Progress® 4GL language keywords. Although these always are shown in uppercase, you can type them in either uppercase or lowercase in a procedure.

> ### OpenEdge messages

> OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

> - Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.

> - Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.

> - Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

> After displaying a message, OpenEdge proceeds in one of several ways:

> - Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.

> - Returns to the OpenEdge Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.

> - Halts processing of a procedure and returns immediately to the Procedure Editor. This does not happen often.

> - Terminates the current session.

> OpenEdge messages end with a message number in parentheses. In this example, the message number is `200`:

>     ** Unknown table name table. (200)

> If you encounter an error that terminates OpenEdge, note the message number before restarting.

> #### Obtaining more information about OpenEdge messages

> On Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

> - Choose Help Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.

> - Choose Help Messages and then enter the message number to display a description of a specific OpenEdge message.

> - In the Procedure Editor, press the help key (F2 or CTRL-W).

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095