Language support


It is possible to design forms in many different languages and scripts. If your language has non-roman characters, you should make sure your database must be set-up to handle the storage of your character set. UTF8 seems to work for many languages.

By default, openXdata has character encoding set to UTF-8. But you may want a different character encoding like latin or UTF-36.

To enable support for other en-conding formats, the file has to be changed to reflect the desired encoding format the user wishes to use. Lets take an example of say UTF-36 is the desired encoding format.

The file, found under your webapp directory, can be changed like this.

  • hibernate.connection.url=jdbc:mysql://localhost:3306/openxdata?autoReconnect=true&useUnicode=true&characterEncoding=UTF36
  • hibernate.connection.createdb.url=jdbc:mysql://localhost:3306/?autoReconnect=true&useUnicode=true&characterEncoding=UTF36

Please note that we are appending/changing these two parameters in each URL:

  • &useUnicode=true
  • &characterEncoding=UTF8

That will enable the system to run with the specified character encoding.

Important to Note

Some MySQL database versions might not be able to support the specified encoding format. Be sure to cross check that the version of MySQL supports the encoding format specified or else the system will not start.

CAVEAT you cannot upload!

However, although many Nokia phones will accept text entry in a local language such as Arabic or Urdu, openXdata currently does is not able to upload non-roman characters. However, a wide-range of very effective forms can be designed with just numbers, single-select, multiple-select, and multimedia etc.

Mobile client

It is also possible to translate the mobile client using the text file. This has been tested in spanish and found to work, but did not work when briefly tested in Urdu (similar to the Arabic character script).

Previous Page: Running multiple openXdata servers Table of Contents Next Page: Adding a new form