Product \ internationalisation


The practice of creating user-interfaces which can be reused in a different language.

Internationalisation (or i18n for short) generally makes sure the texts that are put on screen are translated before they are shown by using per-language translation files. Showing right-to-left user-interfaces is handled per component, for example in NaturalLayout.

The concepts of i18n have been described by Sun in some tutorials (here), the tutorials don't provide a workflow that is as simple as it can be; UICollection provides mechanisms to make it easier and more robust.
Notice that the Translator class provided in UICollection builds on top of proven concepts but intends to make them easier to use and more accessable for the whole Java programming audience.

The UICollection package provides a class called Translate which is easy to use, yet as powerfull as can be. The class can be used without any other components of UICollection, for those that want to swim without getting wet. Please go to the tutorial where the usage is explained.

All Java Swing user interfaces created using the UICollection's designer technology will automatically contain the translate() method and all widgets will use the translation methods to place their content on screen.
In practice this means that no code will have to be written when you use UICollection.

Using UICollection generated UIs Internationalisation will work after you:

  1. write properties files for all the languages you wish to support.
  2. Divide your application in different 'contexts' by overriding the translate() method in your extending class and providing a different argument to the instanciation of the Translate class.
  3. Optionally set the locale on the Translator (via setLocale()) if you wish to override the machine's locale.

We hope you will create lots of easily translated user interfaces.