Localize client-side literals

You can localize client-side literals by running the JavaScript bundle collector utility.

About this task

To localize the client-side literals, you must run the JavaScript bundle collector utility by performing the following steps:

Procedure

  1. If you are localizing Business Intelligence, you must generate the bundle-index.properties file. Therefore, run the following script from the <INSTALL_DIR>/bin folder to extract the client-side literals in the bundle-index.properties file:

    ant -f jsUtil.xml bundle.index -Dsourcedir=<INSTALL_DIR>/repository/eardata/sbi/war -Dindexdir=<INSTALL_DIR>/repository/eardata/sbi/localization_index

    where -Dindexdir is the output directory.

    A new folder, localization_index, containing the following files is created:

    • opts
    • context-index
    • bundle-index.properties
  2. Send the bundle-index.properties file for translation.
  3. After localization, save the localized bundle-index.properties file as bundle-index_<language_code>_<locale>.properties based on the locale in the <INSTALL_DIR>/repository/eardata/sbi/localization_index folder.

    For example, if you want to localize the application for France in French language, save the localized bundle-index.properties as bundle-index_fr_FR.properties.

    Note: If you have not localized the Web UI Framework client-side literals already, you must localize the Web UI Framework client-side literals by running the JavaScript bundle collector utility.
  4. Perform the postlocalization tasks on the client side. For more information about the postlocalization tasks, refer to the topic Recreating the Enterprise ARchive (EAR) package post localization.