Packaging the output for a specific language

After the views and data are localized, you can create packages with language-specific views and data.

To package the output for a specific language

1. Export the form views for the language.
   InDeveloper Studio, select File > Export to export the view definitions to a definition file. For more information, see Exporting-object-definitions-views-and-applications.
   Make sure the definition file includes all of the forms that were included in the localization package definition.
   Optionally, you can create a script to perform this step.
2. Export the language-specific data.
   1. Create an AR System report (with a browser), which includes the fields containing the localized data generated from the forms that were included in the localization package definition and that include the Locale field.
   2. From this report, create a data file. If you have attachment fields, you might create more than one data file.
      For more information, see Configuring-the-mid-tier.
      As part of localization, all English messages in the active link and filter Message actions are translated, and the localized entries are generated in the AR System Message Catalog form. So, export the data for the specific language from this form; otherwise, the workflow messages will appear in English at runtime.
      Optionally, you can create a script to export the language-specific data.
3. Create a zip file of the definition file and data file for the language.
4. Deliver the zip file to your customers, and instruct them to:
   1. Unzip the file.
   2. Import the .def file by using Developer Studio. For more information, see Setting-up-the-Object-List.

   3. Import the data files AR System Data Import or from the command line. For more information, see Running-a-data-import.

      Important

      On Chinese UNIX systems, CSV and ASCII files cannot be imported if they contain Date/Time fields. When using the AR System Data Import utility on Japanese UNIX systems, convert the data and .arm mapping files to EUC format before the files are moved to the UNIX server. (The .arx and .xml data files are already in EUC format when they are generated in the client tool, but the .csv file is not. Therefore, the .arm and .csv files must be converted.) Make sure that all of the data file names and mapping file names are in English.