Difference between revisions of "How to translate OpenJUMP into another language"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | === '''The steps on how to translate | + | === '''The steps on how to translate OpenJUMP''' === |
− | This in an ''example for'' translation into ''Brazilian | + | This in an ''example for'' translation into ''Brazilian Portuguese''. |
− | |||
− | + | '''NOTE:''' | |
− | + | * People interested in translating OpenJUMP to a new language should read part B (below) as well. | |
− | + | * The steps below show the translation on the operating system windows. The steps however are pretty much generally the same for every operating system. | |
− | * | ||
− | |||
− | * | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | ; Translation process | |
− | + | # download the last nightly built from http://jump-pilot.sourceforge.net/download/nightlybuild/ | |
+ | # unpack it e.g. to 'C:\OJfolder' (used in the subsequent steps) | ||
+ | # if your operating system is configured to use the language you want to translate you can skip this step | ||
+ | #* edit the start script for your platform | ||
+ | #* locate the following lines in the file '''OJfolder\bin\oj_windows.bat''', a similar line exists in '''oj_linux.sh''' for MacOS and Unix os's | ||
+ | #: <pre> rem --- uncomment and change your language/country here to overwrite OS locale setting ---</pre> | ||
+ | #: <pre> rem set JAVA_OPTS=%JAVA_OPTS% -Duser.language=de -Duser.country=DE</pre> | ||
+ | #* uncomment the line | ||
+ | #* add your language and optionally country code | ||
+ | #: <pre> set JAVA_OPTS=%JAVA_OPTS% -Duser.language=pt -Duser.country=BR </pre> | ||
+ | # extract the folder '''language''' from 'OJfolder\lib\openjump-core-*.jar' (where * are nightly built specific name) into 'OJfolder' resulting in 'OJfolder/language' containing lots of jump_*.properties files | ||
+ | # look in '''language''' folder for a file called "jump_pt_BR.properties". If it does not exist see [[#On new translations]] and come back here thereafter. | ||
+ | # open the file with your favorite editor and translate the strings | ||
+ | #: '''HINT''' if it appears like one line of text try an editor that supports unix line breaks e.g. wordpad | ||
+ | # you will see that on left side is an identifier string while on the right side of the "=" (equal sign) is the translated text | ||
+ | #: '''HINT''' new strings have a date line just before like [sstein 7 march 2007] | ||
+ | # when you are finished editing, save the file | ||
+ | :'''NOTE''' you should verify your changes by running OpenJUMP now and doublechecking your changes | ||
− | + | ; Verification | |
− | + | # start openjump with the start script for your platform | |
− | + | # check the translated strings | |
− | |||
− | + | ; Release | |
− | + | # send me the modified properties file to sstein@geo(....) or | |
+ | : to the development mailing list http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel or | ||
− | After adding it, the nightly built of the next day should include your | + | After adding it, the nightly built of the next day should include your Portuguese translation. I hope that is detailed enough :o) If questions appear please don't hesitate to contact me (Stefan/sstein) |
=== '''On new translations''' === | === '''On new translations''' === | ||
− | * please simply make a copy of the file | + | * please simply make a copy of the file jump.properties file and rename the copy to your language abbreviation (e.g. the swedish one should be like: jump_se.properties) |
* translate everything | * translate everything | ||
− | * put | + | * put the properties file into '''language''' folder |
=== '''Useful tools''' === | === '''Useful tools''' === | ||
− | * some of the developers use the prb-editor for | + | * some of the developers use the prb-editor for translation http://prbeditor.dev.java.net/ |
− | === '''Translation of | + | === '''Translation of non latin languages like Chinese, Vietnamese, Japanese etc.''' === |
− | + | # Use an editor (notepad or notepad++) to do the translation and save it as '''UTF-8''' format. | |
− | + | # Convert the utf-8 to unicode using native2ascii.exe (part of the java development kit, e.g. C:\Program Files\Java\jdk<version>\bin\native2ascii.exe | |
− | # Use an editor (notepad or notepad++) to do the translation and save it as | + | #:<pre>C:\>native2ascii -encoding utf8 c:\jump_zh_HK c:\jump_zh_HKe </pre> |
− | # Convert the utf-8 to unicode using native2ascii.exe, e.g. <pre>C:\>native2ascii -encoding utf8 c:\jump_zh_HK c:\jump_zh_HKe </pre> | + | : '''ATTENTION''' characters such as chinese may not be shown properly in the splash image. |
− | |||
− | |||
− |
Revision as of 20:28, 1 August 2011
The steps on how to translate OpenJUMP
This in an example for translation into Brazilian Portuguese.
NOTE:
- People interested in translating OpenJUMP to a new language should read part B (below) as well.
- The steps below show the translation on the operating system windows. The steps however are pretty much generally the same for every operating system.
- Translation process
- download the last nightly built from http://jump-pilot.sourceforge.net/download/nightlybuild/
- unpack it e.g. to 'C:\OJfolder' (used in the subsequent steps)
- if your operating system is configured to use the language you want to translate you can skip this step
- edit the start script for your platform
- locate the following lines in the file OJfolder\bin\oj_windows.bat, a similar line exists in oj_linux.sh for MacOS and Unix os's
rem --- uncomment and change your language/country here to overwrite OS locale setting ---
rem set JAVA_OPTS=%JAVA_OPTS% -Duser.language=de -Duser.country=DE
- uncomment the line
- add your language and optionally country code
set JAVA_OPTS=%JAVA_OPTS% -Duser.language=pt -Duser.country=BR
- extract the folder language from 'OJfolder\lib\openjump-core-*.jar' (where * are nightly built specific name) into 'OJfolder' resulting in 'OJfolder/language' containing lots of jump_*.properties files
- look in language folder for a file called "jump_pt_BR.properties". If it does not exist see #On new translations and come back here thereafter.
- open the file with your favorite editor and translate the strings
- HINT if it appears like one line of text try an editor that supports unix line breaks e.g. wordpad
- you will see that on left side is an identifier string while on the right side of the "=" (equal sign) is the translated text
- HINT new strings have a date line just before like [sstein 7 march 2007]
- when you are finished editing, save the file
- NOTE you should verify your changes by running OpenJUMP now and doublechecking your changes
- Verification
- start openjump with the start script for your platform
- check the translated strings
- Release
- send me the modified properties file to sstein@geo(....) or
- to the development mailing list http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel or
After adding it, the nightly built of the next day should include your Portuguese translation. I hope that is detailed enough :o) If questions appear please don't hesitate to contact me (Stefan/sstein)
On new translations
- please simply make a copy of the file jump.properties file and rename the copy to your language abbreviation (e.g. the swedish one should be like: jump_se.properties)
- translate everything
- put the properties file into language folder
Useful tools
- some of the developers use the prb-editor for translation http://prbeditor.dev.java.net/
Translation of non latin languages like Chinese, Vietnamese, Japanese etc.
- Use an editor (notepad or notepad++) to do the translation and save it as UTF-8 format.
- Convert the utf-8 to unicode using native2ascii.exe (part of the java development kit, e.g. C:\Program Files\Java\jdk<version>\bin\native2ascii.exe
C:\>native2ascii -encoding utf8 c:\jump_zh_HK c:\jump_zh_HKe
- ATTENTION characters such as chinese may not be shown properly in the splash image.