Preparing your application to be localized

To be ready for localization, your server must be configured for localization. Additionally, applications must have the correct localization properties set for forms, their associated views, and fields.

By default, all forms, views, and fields are configured to be localized, so you should not have to manually set each property. Conversely, if you have specific forms, views, or fields that you do not want localized, set the property accordingly.

If you purchased your applications from BMC or from a third-party vendor, the localization properties might be set correctly already. Check with your sales representative.

If you have backend forms that contain configuration data for your applications, you must prepare that data for localization. For example, you might have a form used to drive menus; the form contains the data corresponding to those menus. See To prepare your application's configuration data to be localized.

In summary, to prepare your application for localization, you must prepare the:

• Server
• Application's forms, views, and fields
• Configuration data

To prepare your server for localization

1. To indicate that default AR System messages should be overridden:
   1. In a browser, open the AR System Administration: Server Information form.
   2. Click the Advanced tab.
   3. Select the Localize Server check box.
       This enables such tasks as searching entries in localized forms and using the AR System Message Catalog to load system messages.

 To prepare your application's forms, views, and fields to be localized

1. Set the properties for each form.
   1. Open the form in Developer Studio.
   2. Click the Definitions tab.
   3. Expand the Other Definitions panel and then the Basic panel.
   4. To localize form views, select the Localize Form Views check box. Then, select one of the following options:
      • All — The form is localized when you run the localization toolkit. The view properties and field properties are used to identify what to localize.
        By default, the Localize Forms Views check box and the All option are selected.
      • Only for Selection Field Aliases — Only selection (enumerated) fields are localized when you run the localization toolkit. Usually, this option is used for back-end forms.
2. Set the properties for the views for each form.
   1. Open the view of the form.
   2. In the Properties tab, set the Localize property. The options are True and False.
       By default, Localize is set to True, and the view is localized when you run the localization toolkit.
3. Set the properties for the fields on each view of each form.
   1. Select the field.
   2. In the Properties tab, set the Localize Label property. The options are True and False.
       By default, Localize Label is set to True, and the field is localized when you run the localization toolkit.

 To prepare your application's configuration data to be localized

1. For each form that contains configuration data:
   1. Make sure that the form contains a Locale field (field ID 160).
       The entry should contain the locale from which you are translating (for example, if you are translating from English data, then each data record must to have en as the locale value).
   2. Make sure that at least one of the following conditions is met:
      • A GUID field (field ID 179) is defined.
      • At least one unique index is defined with the Locale field (field ID 160) included in it.
   3. Open the form in Remedy Developer Studio.
   4. Click the Definitions tab.
   5. Expand the Other Definitions panel and then the Basic panel.
   6. Select the Localize Form Data check box.
       By default, this check box is not selected.
2. For each field in each view of forms with configuration data, change the Localize Data field property to True.
    When data is processed, for each record that has the matching source locale, a new record is created for each of the target locales defined in the localization package definition. The only data that is translated is the data in the fields that are tagged for data localization.
3. To localize templates, on the AR System Resource Definitions form, make sure that the Application field contains the application's name in each entry.
    This step ensures that the localization toolkit can identify the templates to extract and which application folder to place the files. For more information about where template files are stored for localization, see Extracting-the-strings-for-localization.