Skip to main content

Install language packs for standard pages

To install Bravura Security Fabric language pack:

  1. Obtain the necessary <lang>-<locale>.<version>.zip file from Bravura Security .

  2. Place the <lang>-<locale>.<version>.zip file in the \<instance>\ directory and unzip it.

    Verify that language pack source files are correctly placed in the \<instance>\design\src\common\ directory.

    In a replicated environment , install on the primary node.

  3. Generate and install the new skin files for the language.

    From the \<instance>\design\ directory, run the following command:

    make.bat default <lang>-<locale>
make.bat install default <lang>-<locale>

    The language skin files are installed to their own <lang>-<locale> directory within the \<instance>\skin\ directory.

  4. Generate and install the default American English skin to complete installation of the language pack.

    make.bat default en-us
make.bat install default en-us

    Close browsers if you have them open and then re-open them to test the changes.

    If you do not see changes as expected, try clearing the browser cache before re-opening the browser.

    You must run the two default skin commands (as in step above) in addition to any previous commands any time any language or errmsg kvg file is touched.

    When the new skins are generated, the en-us language tags are used as a set of defaults to fall back on. If a tag exists in the en-us language file and is missing or undefined in the foreign language files, the value of the corresponding en-us language tag is used instead.

You can now use the translator interface or edit KVG files to alter text if required.

Replication

If you have Bravura Security Fabric installed on multiple nodes, install the language pack on the primary node. Any language files are automatically propagated to secondary nodes when auto discovery runs the updinst program , towards the end of the process. You can also propagate the files manually with the following command from the util directory:

updinst.exe -syncfile

The time this takes depends on the number of files you have to propagate, but is faster than running auto discovery.

See the File Synchronization for a more detailed explanation.

In this section: