Exporting labels and record data for translation

If IBM TRIRIGA does not include your required translations, you can create customized translations by using the Globalization Manager to export labels and record data. This method is the preferred method for translating additions that you make. The exported language packs can then be translated by you or a third party, and the customized files can be imported into IBM TRIRIGA.

Before you begin

If you choose to do a delta export, the TRIRIGA_version_Language_Packs.zip file must be in the <install directory>\userfiles\LanguagePacks folder on the IBM TRIRIGA Application Platform when you do the export. The file is on the Application Upgrade image in the IBM TRIRIGA application eAssembly on the IBM® Passport Advantage® website.

Procedure

  1. Select Tools > Administration > Globalization Manager and click Export.
  2. Optional: In the Product version info field, enter information about the IBM TRIRIGA version.
    This information appears in the product-version attribute in the exported XLIFF files.
  3. To export labels, ensure that the Label check box is selected and choose the scope of the labels to include.
  4. To export data, ensure that the Data check box is selected and choose the scope of the business objects to include.
  5. Select whether to do a full export or a delta export. A delta export affects only the labels and data that changed since the last export. If you select a delta export, you must also select the location of the reference files to which you want to compare the differences.
  6. Select the target language for the export. Select Internal Values to export labels and data from the main tables that are included with the product.
    You can change the language values in the List Manager.
  7. Click Export.

Export of database table indexes

In terms of globalization, the records that are created from certain Database Table Manager BOs, that is, triIndex, triSparseColumn, triTable, and triIndexedColumn, should not be translated. However, because their BO name mappings contain a list field, the platform automatically attempts to export the data for translation. To prevent this process, the records of these specific BOs are always excluded during data export.