Disclaimer

©2024 Deutsche Boerse AG - All rights reserved. The information contained in this document is confidential or protected by law. Any unauthorized copying of this document or part of it or unauthorized distribution of the information contained herein is prohibited. All materials provided by DB in this context are and remain the intellectual property of DB and all rights therein are reserved.

1 Introduction

1.1 About this Document

This document contains a description of how to change the language setting used in the ComTrader application provided by Deutsche Börse AG (DBAG). It is intended as a manual for customers to initiate the process of the translation. Together with this document DBAG also provides resource files which can be translated to desired language and subsequently sent back to DBAG, which will integrate them into the standard ComTrader (frontend) and M7 (backend) configuration.

2 Resource files

To change the language in ComTrader, the provided resource files need to be translated. The resource file is a text document which is encoded in UTF-8 (presence of byte order mark (BOM) is not necessary) with only two columns separated by an equals sign (i.e. =) separator. The first column contains the resource keys used in ComTrader or in the M7 backend (these resource keys must remain unchanged). The second column contains the resource values which relate to the corresponding resource keys in the first column (these resource values are to be translated). The resource values are also separated into groups according to their similar meaning (e.g. actions, ask, bid, etc. or messages and particular group of errors).

The number sign (i.e. #) denotes an informative note which doesn’t have to be translated. A block of notes is initiated by the following signs /* and subsequently ended by the */ signs. Notes can be arbitrarily added to the resource file. Blank lines in the file have no meaning. Notes and blank lines are skipped by the resource parser.

Note that new resource keys and resource values shouldn’t be created, and existing ones must not be deleted. Parameters in the resource values indicated by the curly brackets (e.g. member and traderId in the login resource key) should not be translated.

2.1 Frontend resource file

The following picture describes the content of the provided frontend resource file. This file contains the resource keys representing the ComTrader interface as well as messages and errors generated directly by ComTrader (for more details please refer to DFS200 - Messages).

The following picture describes the same resource file as shown above, but the English resource values in the second column are now translated to Chinese.

2.2 Backend resource file

The following picture describes the content of the provided backend resource file. The resource file contains both the messages and errors that are broadcasted by backend. The Error Response is sent whenever the backend system determines an exception based on wrong entries in the request. Errors are sent with corresponding codes indicating the specific reason. The complete list of messages and errors along with the corresponding error codes can be found in DFS200 – Messages.

The following picture describes the same resource file as shown above, but the English resource values in the second column are now translated to Chinese.

3 Loading the resource file to ComTrader

The language used in ComTrader can be chosen in the ComTrader Settings window. The Settings window can be opened by selecting the option "Settings" from the "General" menu of the Trading or Login windows. All of the settings are stored on a profile server.

The following picture describes the first tab of the ComTrader Settings window.

The first "General" tab contains several options including the field "Language ", which allows the user to change the language in the GUI. If the required language is not included in this field, a user can click on the "Load Custom Localisation" label. This action opens a browser window to select the translated resource file with the suffix *.properties. This underlying resource file must be a UTF-8 byte order mark text document.

Note that the presence of the Load Custom Localisation button is limited to testing/development purposes and depends on the specific environment.

After the translated resource file (see Resource files chapter) is loaded, the "Language" field is automatically changed to the "custom" value. When the "Ok" button is clicked, the custom localisation is used and the user profile is saved. When the "Apply" button is clicked, the change is applied without closing the Settings window.

The following picture describes the same "General" tab of the Settings window but with the loaded Chinese localisation.

Note that some resource values are not included in the provided resource file (e.g. Languages, Date format, colour theme and others), thus they cannot be translated.