Users do not always need full internationalization support and ability to switch the user interface to different languages. Your administration determines if only one language (which matches the user’s login language) is implemented, or a subset of installed languages is installed.
To allow the user to install additional translations files and custom versions of ini files, the files can be placed in an ad hoc folder (“CustomFiles”) along with the installer package (for example workspace\zeroadmin\component\Insight\CustomFiles), and relative path to which it must be transferred to in the installer. Three methods are available for transferring files to the user machine.
First, the administrator can transfer files into the Interactive Reporting Web Client home directory (for example, c:\program files\internet explorer\plugins\hyperion). In this case, files are placed corresponding to the relative path in which they stored in the “CustomFiles” folder. For example if briottbl.txt file is placed in the :CustomFiles\9.3\Translations\Latin folder on the server, it is transferred to c:\program files\internet explorer\plugins\hyperion\9.0.2\Translations\Latin\briottbl.txt. This reduces the changes to the subfolder name corresponding to Interactive Reporting Web Client version for each new version of the installer (for example, changing the \9.0.2\Translations to \9.1\Translations). To simplify the maintenance of custom installations, a special folder name “PluginFolder” is supported. If briottbl.txt is placed in the CustomFiles\PluginFolder\Translations\Latin folder on the server, it is transferred to the folder corresponding to the version of the installed Interactive Reporting Web Client (for example. \9.0.2\Translations\Latin\briottbl.txt, \9.1\Translations\Latin\briottbl.txt etc.).
In the second case, the files can be transferred into the Windows system directory. This option is supported only for updating existing Interactive Reporting Web Client, .ini files (brioqplg_ev.ini etc.) and it is not possible to transfer any other file to the Windows system directory.
The third option enables you to transfer *.ttf font files. These files can be transferred to the Windows Fonts folder and properly registered. The registration requires that font name be made available to the installer (the administrator might write a script to retrieve the font names).