Importing Your Language Templates

Tip: You only need to read this section when the ProMatrix Corporation releases a new Language Templates for a language that is not already included in VPME.

When ProMatrix Corporation releases a new Language Template, you need to import the Language Templates into VPM Enterprise so that the translations in the Language Template will be available for inclusion in new or existing projects.

A VPME Multilingual Language Template contains two table files and their accompanying .cdx and .fpt files:

·       Message Translations: Contains translations of the messages in a VPME starter application. The table name is SVPMMessageTranslations_LanguageName.dbf, where LanguageName is the name of the language for which the table contains message translations.

·       String Translations: Contains translations of the strings in a VPME starter application. Strings include interface text such as property values, menu prompts, report labels and Data Builder values. The table name is SVPMStringTranslations_LanguageName.dbf, where LanguageName is the name of the language for which the table contains string translations.

Importing your Language Templates is done by adding the records in the Language Template tables to the VPME Multilingual New Project Message and String Translation tables.You import the Language Template files using the New Project Language Builder form, which you access on the PM-Admin/ProMatrix Setup menu.

Ø To import a Language Template

1.   Language Template Files: Make sure that you have unzipped the Language Template files into a folder on your computer or readily accessible to your computer.

2.   New Project Language Builder: Select New Project Language Builder on the PM-Admin/ProMatrix Setup menu in Visual ProMatrix. VPME displays the New Project Language Builder form.

    

3.   Create Language Record: Click the New button on the Form Toolbar to create a Language record for the language whose Language Template you are importing.

4.   Enter Language ID: In the ID field enter a language ID for the Language Template you are importing. You may enter up to three characters. For example, for Dutch you might enter “DUT”.

5.   Enter Language Description: In the Description field enter a description for the Language Template you are importing.

6.   Enter Comments: If you wish, enter comments in the Comments box.

7.   Properties: Before you use the new Language and translations in a project, you will want to visit the Properties page on the New Project Language Builder form to set up the language properties appropriately. For now, we’ll skip the Properties page.

8.   Save: Click the Save button on the Form Toolbar to save your new Language record. After you save the record, the buttons at the bottom of the Language page are enabled.

    

9.   Import Message Translations: Click the Import Message Translations button. VPME displays the Open dialog. Find the Message Translations table for the Language Template you are importing.

   The name of the Message Translations table you are looking for begins with “SVPMMessageTranslations_” and ends with the language name (for example, “russian”). Find the table and click Select. After you click Select, VPME imports the message translations into its New Project Message Translations table.

10. Import String Translations: Click the Import String Translations button. VPME displays the Open dialog. Find the String Translations table for the Language Template you are importing. The name of the String Translations table you are looking for begins with “SVPMStringTranslations_” and ends with the language name (for example, “dutch”). Find the table and click Select. After you click Select, VPME imports the string translations into its New Project String Translations table.

11. Check the Imports: Make sure that you imported the correct Message and String Translation tables. Click the Message Translations and String Translations buttons on the New Project Language Builder form to see the message and string records that you just imported. Scroll through the Message and String Translations records to make sure that they belong to the language you are setting up.

Tip: If you find that you accidentally imported the wrong table for a language, the easiest way to fix it at this point is to delete the Language record that you have just created on the New Project Language Builder form and start over from Step 3 above. Deleting the Language record will also remove the translations you imported from the Message and String Translations tables.

12. Import Additional Templates: If you have another Language Template to import, repeat Steps 3 through 11.

Set Up Language Properties

Don’t forget to visit the Properties page on the New Project Language Builder form to set up the language properties for the languages you have added while importing your Language Templates.

More:

Where to Go from Here