To translate resource files

Resource files contain language-dependent content of LN homepages and query-based reports. Each resource file belongs to a particular homepage or query-based report. For example:

  • A resource file linked to a homepage, contains the homepage's title and the titles of the panes used in the homepage.
  • A resource file linked to a query-based report contains the report title, column headings, chart titles, and other static labels used in the report. For more information, refer to Query-based Reporting.

Some extra notes:

  • Resource files do not contain language dependent LN content such as label and message descriptions.
  • Each resource file contains data for only one language. The homepages and reports developed by Infor are delivered with English resource files. To run these homepages and reports in other languages, you must translate the corresponding resource files.
  • When a user opens a homepage or report, Web UI automatically downloads the corresponding resource file from the LN server. Web UI automatically selects the resource file that corresponds to the user's language, as defined in the User Data (ttaad2500m000) session, so that the homepage or report is displayed in the user's own language. If there is no resource file for the user's language, Web UI downloads the original (English) resource file delivered with the homepage.

To translate a resource file:

Step 1. Export resource files
  1. Start the Export Resource Files (ttadv8913m000) session.
  2. Enter the required settings and export the resource files to a directory on the LN server. The session generates an ASCII file for each exported resource file.
Step 2. Rename ASCII files

The names of the generated ASCII files have this structure:

<filename>_<ISO 639 language code>_<ISO 3166 country code>.properties

Note

  • The country code is optional and used for only a few languages.
  • The language code of a report's resource file must be identical to the language code of the resource file of the homepage to which the report is linked. For details, refer to the Infor Enterprise Server Web UI - Installation and Configuration Guide.

Rename the ASCII files so they match the target language code and optionally the target country code. Ensure you use the correct ISO codes, because otherwise the Web UI cannot read the resource file at runtime.

For example, the Export Resource Files (ttadv8913m000) session has generated this ASCII file: bwhwmdwarehousemanagerhomepage_en.properties.

  • To translate the file into German, rename the file to bwhwmdwarehousemanagerhomepage_ de.properties.
  • To translate the file into French, rename the file to bwhwmdwarehousemanagerhomepage_ fr.properties.
  • To translate the file into Dutch, rename the file to bwhwmdwarehousemanagerhomepage_ nl.properties.
Step 3. Translate content of ASCII files

The ASCII files consist of lines with the following structure: resource ID=resource description. For example, the bwhwmdwarehousemanagerhomepage_en.properties file contains these lines:

warehousemanagerhomepage.whinh2400m000=Warehouse Orders
warehousemanagerhomepage.whinh2100m000=Warehouse Orders
warehousemanagerhomepage.whinh4130m000=Create Shipments
warehousemanagerhomepage.workload=Warehouse Manager Tasks
warehousemanagerhomepage.Warehouse_Orders=Warehouse Orders
warehousemanagerhomepage.whinr1400m000=Inventory Transactions
warehousemanagerhomepage.whina1210m000=Inventory Valuation

Translate the resource descriptions in the ASCII files (the text behind the "=" in each line) to the target language.

Step 4. Import resource files
  1. Start the Import Resource Files (ttadv8923m000) session.
  2. Enter the required settings and import the translated ASCII files into a VRC in the LN environment.

Related topics