The Nesstar server comes pre-installed with English, Norwegian and French language support files. These can be viewed and edited in a tree style browser. Each pack consists of a .properties file which is created and used by the server and it's counterpart .ansi file which is edited by the user and used to create the .properties file. The .properties file must be encoded in ISO-8859-1 (also known as Latin 1). The .ansi file must be encoded in the native encoding of the country, e.g. Cp1252 under Windows in the United Kingdom.
Customising an Existing Language File
[Customisation -> Edit Translations]
This will open ‘Language Pack Editor’. To customise an existing language file simply select the file from the tree on the left side frame and type into the panel which will be populated on the right side frame. Click on Save when you have finished or Undo to set the text back to the last saved version. The original language files are stored in ./config/instdata/config/languages for easy restoring.
Creating a New Language Pack
To create a new language pack you must first copy all of the existing en properties files over to your required country code, e.g. for a German pack copy files ending in _en.properties to _de.properties. These files are located in ./config/languages (server related) and ./jboss/server/default/deploy/webview.war/WEB-INF/classes/nesstar/webclient/translation (web client related). See ISO 639-2 to help determine your local 2 or 3 character country code. Then simply change the value of the first property from 'encoding = ISO-8859-1' to the encoding that you will be using to edit the file. Remove the entire line if you are not sure and the editor will use the local system's encoding. To start using the new pack you must now close and re-launch the Language Editor. The counterpart .ansi file containing your new language pack country code will be created automatically.
You can now edit the text directly in your chosen language using the Language tree Editor. Alternatively you may pass the .ansi files to a translator for translation. When editing the .ansi files externally please ensure that the editor supports the encoding that you have specified. In the same country, this is usually the system's default encoding anyway, so no change is needed. For example Greek uses an encoding of ISO-8859-7. Your system's locale can be viewed or modified in the Windows Control Panel under Regional and Language Options.
The list of available languages in webview is a combination of all the languages the server
has got data available in + the list of languages webview has been translated into.
Language customization is split/spread-over into different files to segregate them as per functionality. Please find the details below:
1. Server, configuration tool & error messages :
2. Webview display :
3. Published study, cube & resource labels :
When adding a webview translation language (ex. German),
you must follow the below steps:
( For server,configuration tool and error message translations)
1. Check if the language properties file is present in
2. If not present then copy the messages_en.properties file
3. Edit the message_de.properties file
4. Copy the message_de.properties file to the following folders
( For webview display translations)
5. Check if the language properties file is present in
6. If not present then copy the messages_en.properties file which in folder ./jboss/server/default/deploy/webview.war/WEB-INF/classes/nesstar/webclient/translation/
7. Edit the message_de.properties file
(For published study, cubes & resource labels translations)
8. Check if the language properties file is present in ./jboss/server/default/deploy/webview.war/WEB-INF/classes/nesstar/webclient/translation/ddi/
9. Copy the alias_en.properties file which is in the folder ./jboss/server/default/deploy/webview.war/WEB-INF/classes/nesstar/webclient/translation/ddi/ as alias_de.properties into the same folder.
10. Edit the alias_de.properties
(Making translations available)
11. The user-visible list of languages in webview is a sum of the ui-translations available (the ones listed in customise.properties) and the translations the server says it has for the data.
Add ( or remove) the language code to ( from) available.languages entry in
customise.properties which can be found at jboss/server/default/deploy/webview.war/WEB-INF/classes/config/customise.properties