Difference between revisions of "How to translate OpenJUMP into another language"
Jump to navigation
Jump to search
(Created page with ' A - The steps on how to translate OpenJUMP This in an *example for* translation into *Brazilian Portugese*. People interests in creating a new language file my read part B (bel…') |
|||
| Line 1: | Line 1: | ||
| − | + | == A - The steps on how to translate OpenJUMP == | |
| − | This in an | + | This in an ''example for'' translation into ''Brazilian Portugese''. |
People interests in creating a new language file my read part B (below) as well | People interests in creating a new language file my read part B (below) as well | ||
| − | * 1) download the last nightly built | + | * 1) download the last nightly built from http://jump-pilot.sourceforge.net/download/nightlybuild/ |
| − | http:// | ||
* 2) unpack it | * 2) unpack it | ||
* 3) if you work on Windows: | * 3) if you work on Windows: | ||
| − | ** set in the file YOUR_openjump_folder\bin\openjump.bat | + | ** set in the file YOUR_openjump_folder\bin\openjump.bat the i18n option to portugese language in the "start javaw" line: |
| − | + | ** eg. start javaw -Dlog4j.configuration=file:./log4j.xml -Xms256M -Xmx256M -cp | |
| − | ** eg. | + | %CLASSPATH% com.vividsolutions.jump.workbench.JUMPWorkbench -properties workbench-properties.xml -i18n pt_BR -plug-in-directory %LIB%/ext |
| − | start javaw -Dlog4j.configuration=file:./log4j.xml -Xms256M -Xmx256M -cp | ||
| − | %CLASSPATH% com.vividsolutions.jump.workbench.JUMPWorkbench -properties | ||
| − | workbench-properties.xml -i18n pt_BR -plug-in-directory %LIB%/ext | ||
** otherwise modify the appropriate .sh file | ** otherwise modify the appropriate .sh file | ||
| − | * 4) go to the file: | + | * 4) go to the file: YOUR_openjump_folder\lib\jump-workbench-2007XXXX-XXXX.jar (where xxx are nightly built specific number) |
| − | YOUR_openjump_folder\lib\jump-workbench-2007XXXX-XXXX.jar (where xxx are | ||
| − | nightly built specific number) | ||
* 5) for safety reasons make a copy of the file to some other place | * 5) for safety reasons make a copy of the file to some other place | ||
* 6) rename the .jar file to .zip | * 6) rename the .jar file to .zip | ||
* 7) unpack it somewhere | * 7) unpack it somewhere | ||
| − | * 8) look in the unpacked files for folder called "language" and a file | + | * 8) look in the unpacked files for folder called "language" and a file called "jump_pt_BR.properties" |
| − | called "jump_pt_BR.properties" | ||
* 9) open the file with your favorite editor and translate the strings: | * 9) open the file with your favorite editor and translate the strings: | ||
| − | ** you will see that on left side is an identifier string while on the | + | ** you will see that on left side is an identifier string while on the side of the "=" equal sign is the translated text |
| − | side of the "=" equal sign is the translated text | ||
** a hint: new strings have a date line just before like [sstein 7 march 2007] | ** a hint: new strings have a date line just before like [sstein 7 march 2007] | ||
* 10) after you have translated, safe the jump_pt_BR.properties file | * 10) after you have translated, safe the jump_pt_BR.properties file | ||
| − | |||
note: the following steps are useful if you want to check your | note: the following steps are useful if you want to check your | ||
translation in OpenJUMP; | translation in OpenJUMP; | ||
| Line 38: | Line 29: | ||
* 14) start openjump with the openjump.bat file and check your translation | * 14) start openjump with the openjump.bat file and check your translation | ||
| − | + | if you dont want to test: | |
| − | * 15) if you finished your translation send me the jump_pt_BR.properties file | + | * 15) if you finished your translation send me the jump_pt_BR.properties file (sstein@geo....) and i will add it to our sourcecode repository. |
| − | (sstein@geo....) and i will add it to our sourcecode repository. | ||
| − | After adding it, the nightly built of the next day should include your Portugese translation. | + | After adding it, the nightly built of the next day should include your Portugese translation. I hope that is detailed enough :o) If questions appear please don't hesitate to contact me (Stefan/sstein) |
| − | I hope that is detailed enough :o) | ||
| − | If questions appear please don't hesitate to contact me (Stefan/sstein) | ||
| − | + | == B - On new translations == | |
| − | * please simply make a copy of the file jump_en.properties file and | + | * please simply make a copy of the file jump_en.properties file and rename the copy to your language abbreviation (e.g. the swedish one should be like: jump_se.properties) |
| − | rename the copy to your language abbreviation (e.g. the swedish one should be like: jump_se.properties) | ||
* translate everything | * translate everything | ||
* put it as additional file in the zip as describe above | * put it as additional file in the zip as describe above | ||
| − | + | == C - Useful tools == | |
| − | * some of the developers use the prb-editor for translatiion | + | * some of the developers use the prb-editor for translatiion http://prbeditor.dev.java.net/ |
Revision as of 05:37, 5 October 2009
A - The steps on how to translate OpenJUMP
This in an example for translation into Brazilian Portugese. People interests in creating a new language file my read part B (below) as well
- 1) download the last nightly built from http://jump-pilot.sourceforge.net/download/nightlybuild/
- 2) unpack it
- 3) if you work on Windows:
- set in the file YOUR_openjump_folder\bin\openjump.bat the i18n option to portugese language in the "start javaw" line:
- eg. start javaw -Dlog4j.configuration=file:./log4j.xml -Xms256M -Xmx256M -cp
%CLASSPATH% com.vividsolutions.jump.workbench.JUMPWorkbench -properties workbench-properties.xml -i18n pt_BR -plug-in-directory %LIB%/ext
- otherwise modify the appropriate .sh file
- 4) go to the file: YOUR_openjump_folder\lib\jump-workbench-2007XXXX-XXXX.jar (where xxx are nightly built specific number)
- 5) for safety reasons make a copy of the file to some other place
- 6) rename the .jar file to .zip
- 7) unpack it somewhere
- 8) look in the unpacked files for folder called "language" and a file called "jump_pt_BR.properties"
- 9) open the file with your favorite editor and translate the strings:
- you will see that on left side is an identifier string while on the side of the "=" equal sign is the translated text
- a hint: new strings have a date line just before like [sstein 7 march 2007]
- 10) after you have translated, safe the jump_pt_BR.properties file
note: the following steps are useful if you want to check your translation in OpenJUMP;
- 11) pack all the stuff of the previously extracted zip file to a new .zip which has the same name as the old
- 12) rename the just packed file .zip to .jar
- 13) copy it in the same location as the old .jar (means the \lib\ folder)
- 14) start openjump with the openjump.bat file and check your translation
if you dont want to test:
- 15) if you finished your translation send me the jump_pt_BR.properties file (sstein@geo....) and i will add it to our sourcecode repository.
After adding it, the nightly built of the next day should include your Portugese translation. I hope that is detailed enough :o) If questions appear please don't hesitate to contact me (Stefan/sstein)
B - On new translations
- please simply make a copy of the file jump_en.properties file and rename the copy to your language abbreviation (e.g. the swedish one should be like: jump_se.properties)
- translate everything
- put it as additional file in the zip as describe above
C - Useful tools
- some of the developers use the prb-editor for translatiion http://prbeditor.dev.java.net/