Localize client-side application literals

You can localize client-side application literals, but you must run the JavaScript bundle collector utility.

1. If you are localizing the Sterling™ Field Sales application, you must generate the bundle-index.properties file. Therefore, run the following script in <INSTALL_DIR>/bin to extract the client-side literals in the bundle-index.properties file:

   For Windows:

   sci_ant.cmd -f jsUtil.xml bundle.index -Dsourcedir=<INSTALL_DIR>/repository/eardata/sfs/war -Dindexdir=<INSTALL_DIR>/repository/eardata/sfs/localization_index

   where -Dindexdir is the output directory.

   For Linux/UNIX:

   ./sci_ant.sh -f jsUtil.xml bundle.index -Dsourcedir=<INSTALL_DIR>/repository/eardata/sfs/war -Dindexdir=<INSTALL_DIR>/repository/eardata/sfs/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>_<country or region or region_code>.properties based on the locale in the <INSTALL_DIR>/repository/eardata/sfs/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 post- localization tasks on the client side. For more information about the post- localization tasks, refer to ''Post-localization Tasks".