skip to main content
OpenEdge Development: Translation Manager
Managing Projects : Creating a project
Creating a project
Before you create a project, make sure the root directory of the source code you want to translate is in your PROPATH. See Chapter 3, “Getting Started,” for information about PROPATH.
To create a new project:
1. Choose the New button or choose FileNew. The New Project dialog box appears:
2. Type the name of the project database. You can use a maximum of eleven characters. (Do not use blank spaces.)
Note: Use the convention of starting all the names of your projects with the characters “p–.” This naming convention allows you to quickly distinguish a project database from a kit database or an application.
3. Type a description of the project.
4. You can specify a revision number. The Translation Manager tool does not use this information; it is for your records only.
5. If the new project database has the same name as an existing database, and you want to overwrite the old database, activate the Replace If Exists toggle box.
6. Enter the name of the directory where you want to save the project database in the Project fill‑in field. This directory will also contain the kit databases and the resource files. By default, the Translation Manager uses your current working directory.
7. Select the root directory that contains all the source code you want to translate.
Note: The Source Directory combo box lists only the directories in your PROPATH.
8. Choose Options to expand the New Project dialog box:
9. Specify whether to create a copy of an existing project database. If you have multiple projects you can use the same database for more than one project.
10. Select the privileges you want to give to all the translators for the project:
*Must Use Glossary For Translations — When you activate this option, the translators can use only the default glossary you supply with the translation kits. They cannot import their own glossary into the kit nor can they use their own words when the default glossary contains a translation. However, if the glossary does not contain a target phrase for the selected source phrase, translators can enter their own target phrase.
*Can Modify Default Glossary Entries — When you activate this option, the translators can override the pairings suggested by the default glossary you provide and modify existing translations. They can also import their own glossary into the kit.
All the language kits within a single project have the translator privileges you specify in this dialog box. If you want different translators to have different privileges, you must create several copies of the project.
You can only specify translator privileges when you create a new project. The only way to change translator privileges for an existing project is to create a new project with a new name, copy the files from the existing project, and specify new privileges.
11. Choose OK to create the project database in the working directory. The Translation Manager displays the Procedures tab folder.
For a description of how to create a list of source procedures for the project, see the“Selecting source procedures” section.