This documentation supports the 23.3 version of BMC Helix Innovation Suite (AR System and BMC Helix Innovation Studio).

To view an earlier version, select the version from the Product version menu.

Extracting the strings for localization

After you create a localization package definition, you can extract the strings for localization into the localization database (l10n.db in the root folder).

To extract the strings for localization

  1. Close any objects that you want to process in the localization toolkit.
  2. In Developer Studio, open the localization package definition.
  3. In the Localize section, click Extract Strings.
  4. To check the status or modify what is translated, click Translation Status in the Localization Status section.
    For more information, see Reviewing the translations.

Extracted attachment files and other external files

When you extract items for translation, separate folders are created for:

  • Attachment files
  • Template files on the AR System Resource Definitions form linked to an application
  • External help files
  • About box image files
  • External report files linked to the Open Window active link actions

The folders are organized in the root l10n folder as follows:

  • Folders for attachment files—For forms inside an application, the attachment files are saved in a hierarchy of folders. The name for the first folder under l10n contains the application's name. A subfolder under this folder is created for each attachment field and locale. The subfolder names include the form name, the attachment field ID, and the locale.
    The path to the attachment fields looks like this:


    For example:


    Attachment fields for independent forms have folders saved directly in the l10n folder. The naming scheme for the attachment field's folder is the same; it includes the form name, the attachment field ID, and the locale.

  • Template_Filesfolder—The Template_Files folder contains template files from the Resource Definition form linked to the application. A separate locale folder is created for each application and locale, for example:


    For example:

  • Help_Filesfolder—The Help_Files folder contains the About box image and external help files in the application. A separate folder is created for each locale, for example:


    If more than one file is linked, only the first file is extracted (or updated) because the catalog form can have only one such entry.

  • Support_Filesfolder—The Support_Files folder contains the external report files linked to the Open Window active link actions. A separate folder is created for each locale, for example:


    The translation processors cannot distinguish whether the file present is the original or localized version. The processors only verify the presence of the named file and pick it up.


    When you import the translated definition file, you must replace the file with the translated version, and the name and extension must exactly match the original file. For more information, see Importing the translated strings.

Was this page helpful? Yes No Submitting... Thank you