JUpload is used by people talking/reading lots of languages. Internationalization is native in the core JUpload package. These translations may be total or partial, depending on when the contributor sent his/her contribution. You are, of course, welcome to complete the existing translations or create a new translation.
In order to contribute:
For all translaters:
Please also check/translate the Coppermine part, even if you don't use it. This part is not relative to the core applet, but translating it will allow the plugin to be used by more and more people.
For developpers (that is if you may commit in the JUpload SVN repository), just update the relevant ./src/translation/xxx file, and commit it. You'll then have to execute the translation plugin, to get the modified translation be properly taken into account in the applet. See below, Compile JUpload with an updated translation.
//TODO SVN ref to give
For non developper people, you should start from the files available in SVN, at this URL: translations (on SVN) as they are more up to date than the files referenced in the project site, behind the ./available_translations.html page. Then, you can submit the new or updated translation by submitting a patch in the Sourceforge Patch tracker. It's the best way. Any JUpoad developper can then commit this translation in the sf SVN. You can also mail me, at this address: etienne_sf at users.sourceforge.net.
JUpload is used for two main open source developpements:
So the translation part also contains two parts:
property = the translated text
$lang_jupload_php = array_merge ( $lang_jupload_php, array( 'link_comment' => 'Upload files to the gallery, with the help of an applet', ... ) );
The translation files are stored in these folders :
This part is useless for translation contributors. It explains how to compile the applet with modified translation file(s). This is done by using the maven-translation-plugin, given in the JUpload package.
There are to ways to do this:
Once the plugin is installed, you can use it. To do this, you'll have to build the JUpload applet, with the jupload.translation property defined as true. For instance, you can type one of the following commands, in the jupload folder:
Once you typed one of the two above commands, all translations file are generated, and you don't need any more to use the -Djupload.translation=true parameter in maven build ... until you change again your translation.