IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Implementing internationalization

About this task

The XML UI Engine supports multi-language, following the standardization of Eclipse. To support multi-language, do the following steps:

Procedure

  1. Change the message need to be internationalized to the form like “%messagekey” in the XML UI definition file. For example:
    <i18n.xui>
      <Composite bounds="14,15,723,452" id="test.i18n">
       <Label bounds="21,24,80,20" background="255,255,255"				text="%name.locale"/>
      </Composite>
    </i18n.xui>
  2. Create the default resource file for the message that defined in above step. The file name must be identical with the XML UI definition file and must be ended with .properties. And this file must be in the same place with the XML UI definition file. This file contains the message in the default locale, and it will be used when the XML UI Engine can’t find the resource file in required locale. For example: file I18n.properties, add code name.locale=name
  3. Translate the above property file to desired language. For example: in file I18n.tran.properties name.locale=名字
  4. Transfer the above locale property file to ascii with native2ascii of JDK. The name of the new file must be identical with the XML UI definition file and must be end with _LocalName.properties. And this file must be in the same place with the XML UI definition file. This file contains the message in the locale, and the XML UI Engine will find the resource file according to its locale. For example, the name of the file is native2ascii.exe I18n.tran.properties I18n_zh_CN.properties
  5. Define the default global resource file in the global settings of XML UI Engine
  6. Create the default resource file for global like in step 2. This file contains the message in the default locale, and it will be used when the XML UI Engine can’t find the global resource file in required locale and can’t find it in the resource file defined in above step 2.
  7. Translate the above global property file to desired language.
  8. Transfer the above global locale property file to ascii with native2ascii of JDK as step 4. This file contains the message in the locale, and the XML UI Engine will find the resource file according to its locale when XML UI Engine can’t find the resource file defined in above step 4.


Feedback