A project is the main unit of information for the Translation Manager tool, and it consists of:
An OpenEdge database (stored in the project directory) that contains:
A list of the source procedures you want to translate
Filter settings
Text phrases to translate (and eventually the translations of the text phrases)
A glossary for each target language
A list of the kits in the project
Resource procedures (stored in the project directory)
An environment (.ini) file (used to specify font settings)
Image files (used with the resource procedures)
Each project has only one source language. The source language is the language (not necessarily English) in which the text phrases in the source procedures were written. A target language is the language to which you want to translate.
You can translate the source text phrases into many target languages. The target languages do not have to be national languages. You could define a language as Technical (contains software terminology), colloquial (contains informal expressions), or industry specific (contains manufacturing terminology). That way you can have translation variations of your product such that one version uses terminology appropriate for a specific industry, another uses more informal language that better suits ends users, and a third version uses vocabulary that meets the needs of a more technical audience. An application for small businesses with inexperienced computer users might require more general terms than the same application running in the Systems Operations department of a large multinational department. For example, an application for vehicle rental might have three variations—one that uses the term “vehicle” and allows you to lease both cars and trucks, one that allows you to lease cars, and one that allows you to lease trucks where “vehicle” is replaced with “car” or “truck,” as appropriate.
An OpenEdge database (stored in the project directory) that contains:
A list of the source procedures you want to translate