Posted
about 1 month
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
about 1 month
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
about 1 month
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]
Posted
about 1 month
ago
Installation / Setup:: https://svn-de.nightlabs.org/svn/jfire-main/trunk/NightLabsConnection' doesn't exist
Hi,
I'm experiencing problem during the import of the project.
Even If I follow the steps, when starting the
... [More]
initialization I get the following error:
Quote:Initialize workspace failed
NightlyBuild failed:
Last Nightly Build error:
Build failed
org.nightlabs.nightlybuild.BuildException: Exception in nightly build
at org.nightlabs.nightlybuild.NightlyBuild.buildError(NightlyBuild.java:285)
at org.nightlabs.nightlybuild.NightlyBuild.run(NightlyBuild.java:189)
at org.nightlabs.nightlybuild.NightlyBuild.main(NightlyBuild.java:298)
Caused by: org.nightlabs.nightlybuild.PrerequisiteException: Error downloading or scanning prerequisites
at org.nightlabs.nightlybuild.BuildPrerequisites.scanNightlyBuildConfig(BuildPrerequisites.java:312)
at org.nightlabs.nightlybuild.BuildPrerequisites.scan(BuildPrerequisites.java:173)
at org.nightlabs.nightlybuild.NightlyBuild.run(NightlyBuild.java:138)
... 1 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: URL 'https://svn-de.nightlabs.org/svn/jfire-main/trunk/NightLabsConnection' doesn't exist
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:839)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:728)
at org.nightlabs.nightlybuild.download.DownloadWithSVN.checkout(DownloadWithSVN.java:209)
at org.nightlabs.nightlybuild.download.DownloadWithSVN.checkoutOrUpdateWithRetry(DownloadWithSVN.java:175)
at org.nightlabs.nightlybuild.download.DownloadWithSVN.download(DownloadWithSVN.java:146)
at org.nightlabs.nightlybuild.download.DownloadWithSVN.run(DownloadWithSVN.java:96)
at org.nightlabs.nightlybuild.download.Download.run(Download.java:115)
at org.nightlabs.nightlybuild.BuildPrerequisites.downloadNewSources(BuildPrerequisites.java:460)
at org.nightlabs.nightlybuild.BuildPrerequisites.scanNightlyBuildConfig(BuildPrerequisites.java:307)
... 3 more
Thanks for telling me how to solve this problem. [Less]
Posted
2 months
ago
Announcements:: Problems with ServerConfiguration
By changing the import handling of jks keystore and truststore (issue#1254) a small problem was introduced.
Now an explicit field is used to indicate that the keystore/truststore has been
... [More]
imported. Previously this was indicated by setting the truststoreURL to "". Since the ServerConfigurator-framework does an initial initialisation and is thereby setting the URLs to "", this approach doesn't work for the second initialisation because the ServerConfigurator considers the {key,trust}store to be imported, although it isn't.
To cut a long story short:
The addition of the new field will result in an error like "The URL pointing to the XXXstore to import is empty" which results from the old way of importing the keystores. There are two ways of fixing this:
Do a full server reset.
Just add the Boolean in the Config-org.nightlabs.jfire.servermanager.config.JFireServerConfigModule.xml
and set it to true:
Excerpt: ...
<void property="sslCf">
<object class="org.nightlabs.jfire.servermanager.config.SslCf">
<void property="jksStoresImported">
<boolean>true</boolean>
</void>
...
Note that this might result in problems once the ServerConfigurators are reset since the original URL for both the jks stores is not known anymore. It is of course possible to enter it manually into the same file.
Greetings
Marius [Less]
Posted
2 months
ago
Contribute:: Contribute to JFire
Contributor License Agreement
You and NightLabs hereby accept and agree to the following terms and conditions:
1. Your "Contributions" means all of your past, present and future
... [More]
contributions of object code, source code and documentation to a NightLabs project, however submitted to this project, excluding any submissions that are conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
2. You hereby grant to NightLabs a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to NightLabs in this paragraph, You reserve all right, title and interest in and to your Contributions. By contributing to a NightLabs project, you accept especially, but not exclusively, that the project's license is applied to your Contributions.
3. You represent that you are legally entitled to grant the above license. If your employer(s) have rights to intellectual property that you create, you represent that you have received permission to make the Contributions on behalf of that employer, or that your employer has waived such rights for your Contributions to a NightLabs project.
4. You represent that, except as disclosed in your Contribution submission(s), each of your Contributions is your original creation. You represent that your Contribution submission(s) include complete details of any license or other restriction (including, but not limited to, related patents[1] and trademarks) associated with any part of your Contribution(s) (including a copy of any applicable license agreement). You agree to notify NightLabs of any facts or circumstances of which you become aware that would make Your representations in this Agreement inaccurate in any respect.
5. You are not expected to provide support for your Contributions, except to the extent you desire to provide support. You may provide support for free, for a fee, or not at all. Your Contributions are provided as-is, with all faults defects and errors, and without warranty of any kind (either expressed or implied) including, without limitation, any implied warranty of merchantability and fitness for a particular purpose and any warranty of non-infringement.
Your Name: _mano saelao_____________________________
Your eMail: vince at guinaree dot com
Your Country: ______thailand__________________________
Your SourceForge User ID: _____vinnyvince_____________ [Less]
