Resource Menu


You must pay attention to the files encoding using So6.

If you work with LibreSource, you have certainly notice that the server queue has a properties File Encoding. This property is used to configure the java web start So6 client. When you commit or update your workspace, you download a jnlp file. The property "file.encoding" is set as the corresponding file encoding value of the queue.

You can check this editing the jnlp file (here is the default value) :

(...)
<property name="file.encoding" value="ISO-8859-1"/>
(...)

With So6 in command line, the property is not set (java use the default value). But you can change this value with the following command (bash) :

$> export JAVA_OPTS="-Dfile.encoding=UTF-8"


JVM Property "file.encoding"

The java property "file.encoding" is used by the classes which make I/O operations (read or write files). See JDK 1.4.2 and JDK 1.5.0 supported encoding.

In order to have a good behaviour of So6, you must set the file.encoding to the same value that the text editor you use.

For example,

  • with emacs, you can set the Language environment ("Options > Mule > Set Language Environment") and the encoding of the buffer ("Options > Mule > Set Coding Systems > For Saving This Buffer").
  • with eclipse, go to "Window > Preferences", and then in "General > Editors" and set the text file encoding (default is UTF-8 with eclipse 3.1).
Thus, you can force the file encoding of your shared files.

If you get problems, in particular with accentuated characters (, , , etc...) and with exotic platform (for example, a windows os, with the chineese language), check the queue encoding in LibreSource and use the same encoding for all workaspaces.


Notes :

  • The default "file.encoding" value used by java is the file encoding of the system.


Last edited by Root at Aug 28, 2006 11:16 AM - Edit content - View source