Who is this article for?

Administrators who want to make the application available in other languages.

Admin permissions are required.

Language Packs are additional content that can be loaded into the Internal Audit database and provide various levels of translation capabilities. This article outlines the packs available and how to implement them in your system.

1. Downloading Language Packs
2. Importing Language Packs
3. Using Language Packs
4. Limitations
5. Demo

1. Downloading Language Packs

There are two types of Language Packs available for download.

• Full Language Packs contain translations of the user interface and a spell check dictionary. These change the field labels, button names, and messages to the target language, and add a spell check for the target language.
• Dictionary-only Language Packs contain a spell check dictionary.  These do not change the field labels, button names, or messages (they will remain in English), but they do add a spell check for the target language.

Language packs are available from the main download site and are files with names ending in .PAK.

The naming convention is:

• Full Language Pack - version_[language code]_lang.pak
• Dictionary-only Language Pack - [language code]_lang.pak

When a Language Pack is added to a system, each user is able to select which of the available languages they use, and Administrators can set a default language pack for each user.

2. Importing Language Packs

As this is a data import, ensure that:

• Nobody is using the system.
• You have backed up the database and the backup is valid.

After the backup is complete:

1. Go to the application server.
2. Open App Manager.
3. Select the correct instance.
4. Switch to the "Import Export" tab.
5. Click the Import Language Packs button.
6. Select the .PAK file to import.
7. Click Execute and wait for the process to complete.

After adding the language pack, the local database will need to be updated:

1. Open App Manager again.
2. Switch to the "Config" tab.
3. Choose Rebuild Local DB.

If you are using ClickOnce, this should cause clients to download the new file. If not, you will need to distribute the updated local database file via your normal method.

3. Using Language Packs

Once imported, users can change their application language by clicking the Logo button and selecting the desired language from the menu.

After selecting a language, they will need to restart the application.

Administrators can set a user's default language via their Staff or Contacts record.

4. Limitations

There are a couple of limitations to be aware of when using Language Packs.

When a system is upgraded to a new version (e.g.: v5.4 to v6), new functions will appear with English labels.  It is therefore necessary to apply an updated language pack alongside an upgrade.

Aspects of the WebUI aren't translated, for example:

• Text box labels on the Login and Password Management pages remain in English.
• Some error messages are hardcoded and can't be translated.

5. Demo

You can find a walkthrough of the installation and functionality in the video below.

https://app.screendesk.io/recordings/5bdb5feb-ffcd-4a74-b35e-eeb0e53634f1