Posted
23 days
ago
The new and fully integrated Eclipse workspace setup was made available for public today.
Posted
27 days
ago
General:: Jfire Lacalization process
Just wanted to add one important note: Unfortunately, the *.properties-files must be encoded in ISO-8859-1.
In order to write non-western characters into a properties file, they have to be encoded
... [More]
using \uHHHH where HHHH is the hexadecimal unicode character number. Writing this manually is - of course - no fun.
Thus, I recommend using the said Resource Bundle Editor, which automatically performs the de- and encoding. [Less]
Posted
27 days
ago
General:: JFIRE Language Support
Hi Khaled,
JFire consistently uses unicode and therefore supports all languages existing in this world.
Concerning Arabic, there is, of course, the additional challenge that its writing is
... [More]
right-to-left instead of left-to-right, but AFAIK that's no problem for Java or Eclipse-RCP and thus should work fine with JFire. I haven't tested this, yet, though. Please give us feed-back, after you tried!
Note that you have to configure your MySQL server to use UTF-8!!! You should do this before creating any JFire-database! The default setting of MySQL is latin1 and thus Arabic characters are not supported without the following settings in your /etc/mysql/my.cnf:
[mysqld]
## Switch to UTF-8:
character_sets_dir = /usr/share/mysql/charsets
character_set_server = utf8
default_character_set = utf8
## We need many connections:
max_connections = 500
The max_connections doesn't have anything to do with UTF-8, but is always required by JFire.
Languages are automatically registered in the JFire server. You simply have to start your JFire client with your desired language (by default that's your operating system's language) and then login. If you have sufficient privileges, the JFire client automatically registers your language in the server and you'll have it in the language-selection-UI of all multi-lingual text fields.
To tell the client a specific language (and thus not use the operating system's default) you can pass the parameter "-nl LOCALE". For example, the following command starts JFire with Tunisian Arabic:
Linux: ./jfire -nl ar_TN
Windows: jfire.exe -nl ar_TN
Concerning the localisation of the application itself, please read this forum post.
Best regards, Marco [Less]
Posted
29 days
ago
Contribute:: Jfire Lacalization process
Dear Anousak,
yes, it is possible to localise JFire and there exist localisation files for English and German at the moment.
Unfortunately, there is AFAIK no document in the wiki about
... [More]
this topic, but localisation is pretty simple and straight-forward:
Every client-plug-in as well as some server-plug-ins contain a file named messages.properties (simply search for them in your IDE). This is the default (fallback) localisation which is always used when there is no localisation for the current language. In JFire, this default is always English (GB).
If you want to provide localisation for - say - Thai, you create a file named messages_th.properties, using the ISO-639-1-code of the language as suffix. This file must be located in the same directory.
Here is an example of a messages.properties with its corresponding messages_de.properties.
As you see, the file's structure is very simple: Every line is one message used by the application. It is identified by a key, followed by the equals-sign "=" and then the localisation.
Besides the messages.properties there exist files named plugin.properties which serve the same purpose but are used for localising messages that are registered in an RCP plug-in's plugin.xml. Besides the different name, they work exactly the same as messages.properties.
More information can be found in this Sun document.
For localisation, I recommend you install the Resource Bundle Editor (copy the plug-in com.essiembre.eclipse.i18n.resourcebundle from your JFire client into your IDE's dropins-directory).
Best regards, Marco [Less]
