Translating the ACT! supplemental files

There are a number of ACT! supplemental files, such as layouts and reports, that you translate during the localization process. The Translation User uses the ACT! application to translate ACT! supplemental files. The following sections contain steps for translating these files.

Translating ACT! layouts

A person with an understanding of database concepts and is knowledgeable in using the ACT! Layout Designer should perform layout translation.

To translate ACT! layouts

1. Open each of the English layouts from the most current English ACT! version in the ACT! Layout Designer of the localized ACT! product.

The database fields should pre-populate correctly for the localized language given that the database schema is localized.

2. Edit each label or tab name as preferred for dialect and/or language.

Language dependent resizing and rearranging of labels and fields may be necessary due to length of strings and preferred address format.

3. Set the tab stops and enter stops as desired.
4. Save the layout.
5. Test the layout to assure correct data and complete labels appear.
6. If any field data is incorrect, delete and then replace the field.

Translating reports

A person who is knowledgeable in basic reporting principles, database concepts, and XML should perform report translation.

To translate reports

1. Open each of the English reports from the most current ACT! English version in the ACT! Report Designer of the localized ACT! product.

The database fields should pre-populate correctly for the localized language given that the database schema is localized.

2. Edit each label as preferred for dialect and/or language.

Language dependent resizing and rearranging of labels and fields may be necessary due to length of strings and preferred address format.

3. Save the report.
4. Test the report to assure correct data and complete labels are displayed

Note: To test properly, you must enter all variations of data in the ACT! application for Contacts, Groups, Companies, Activities, Opportunities, History, and Notes.

5. If any field names are incorrect, delete and then replace the field.
6. Custom Visual Basic scripting may be required to optimize appearance of address and footer formats.
7. Certain field names included in custom scripting need to be translated directly from the report script using a UTF-8 text editor (Examples: True/False, Open, Close-Won, Closed-Lost).

Translating other supplemental files

To translate other supplemental files

1. In the ACT! desktop application, open the localized ACT! database.
2. Translate each supplemental file as needed.

For help using the ACT! desktop application, see the online Help.

The next step in the localization process is to translate any additional files with a text or XML editor.