How to translate OpenJUMP into another language - Revision history

Ma15569 at 07:29, 20 November 2019

2019-11-20T07:29:39Z

Edso: /* The steps on how to translate OpenJUMP */

2013-02-15T17:59:23Z

The steps on how to translate OpenJUMP

Edso: /* The steps on how to translate OpenJUMP */

2013-02-15T17:56:53Z

The steps on how to translate OpenJUMP

Edso: /* The steps on how to translate OpenJUMP */

2013-02-13T09:35:02Z

The steps on how to translate OpenJUMP

Edso: /* The steps on how to translate OpenJUMP */

2013-02-13T09:34:34Z

The steps on how to translate OpenJUMP

Edso: /* The steps on how to translate OpenJUMP */

2013-02-13T09:33:46Z

The steps on how to translate OpenJUMP

Edso: /* Translation of non latin languages like Chinese, Vietnamese, Japanese etc. */

2012-04-12T08:52:23Z

Translation of non latin languages like Chinese, Vietnamese, Japanese etc.

Michaudm at 21:42, 21 January 2012

2012-01-21T21:42:11Z

Edso: /* Translation process */

2011-11-13T22:14:23Z

Translation process

Edso: /* The steps on how to translate OpenJUMP */

2011-11-13T22:11:27Z

The steps on how to translate OpenJUMP

← Older revision		Revision as of 07:29, 20 November 2019
Line 1:		Line 1:
		+	'''back to''' [[Index]] page
	== '''The steps on how to translate OpenJUMP''' ==		== '''The steps on how to translate OpenJUMP''' ==

@@ Line 9: / Line 9: @@
 :<span style="color:#FF0000">It's crucial that you use the latest snapshot. '''Only snapshots''' are packaged with the language files exposed in the ''/language'' folder.</span>
-=== Translation process ===
+=== '''Translation process''' ===
 # download
 #* the most recent development snapshot from the [[Downloading OpenJUMP#Snapshots|snapshot repository]]
@@ Line 48: / Line 48: @@
 #: You should verify your changes by running OpenJUMP now as described in the next step.
-=== Formatting message ===
+=== '''Formatting message''' ===
 Messages can use variables. For example :
 #: <pre>openjump.error = The layer {0} contains invalid features.</pre>
@@ Line 54: / Line 54: @@
 #: <pre>openjump.error = L''attribut {0} existe déjà!</pre>
+=== '''Verification''' ===
 # start openjump with the start script for your platform
 # check the translated strings
-=== Release ===
+=== '''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

@@ Line 20: / Line 20: @@
 #: C:\OJfolder\readme.txt</tt>
 # set the language
-#; SKIP
+#;<span style="color:#FF0000"> SKIP
-#: if your operating system is configured to use the language you want to translate OJ to you can skip this step (e.g. your Windows is portuguese and you want to edit OJ's portuguese translation)
+#:<span style="color:#FF0000"> if your operating system is configured to use the language you want to translate OJ to you can skip this step (e.g. your Windows is portuguese and you want to edit OJ's portuguese translation)
 #* 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
@@ Line 30: / Line 30: @@
 #: <pre> set JAVA_OPTS=%JAVA_OPTS% -Duser.language=pt -Duser.country=BR </pre>
 # extract the language files
-#; SKIP
+#;<span style="color:#FF0000"> SKIP
-#: if using a current snapshots as they distribute the ''language/'' folder already as described below. Be aware that this is not the case for stable releases, but they are not suggested for translation work anyway because they are probably missing changes of the development tree.
+#:<span style="color:#FF0000"> if using a current snapshots as they distribute the ''language/'' folder already as described below. Be aware that this is not the case for stable releases, but they are not suggested for translation work anyway because they are probably missing changes of the development tree.
 #* extract from 'OJfolder\lib\openjump-core-*.jar' (where * are nightly built specific name) only the folder '''language''' into 'OJfolder' resulting in a folder structure like
 #: <tt>C:\OJfolder\bin\

@@ Line 7: / Line 7: @@
 ;<span style="color:#FF0000">ATTENTION
-:<span style="color:#FF0000">It's crucial that you use the latest snapshot. '''Only''' snapshots are packaged with the language files exposed in the ''/language'' folder.</span>
+:<span style="color:#FF0000">It's crucial that you use the latest snapshot. '''Only snapshots''' are packaged with the language files exposed in the ''/language'' folder.</span>
 === Translation process ===

@@ Line 7: / Line 7: @@
 ;<span style="color:#FF0000">ATTENTION
-:<span style="color:#FF0000">It's crucial that you use the latest snapshot. '''Only''' they are packaged with the language files exposed in the ''/language'' folder.</span>
+:<span style="color:#FF0000">It's crucial that you use the latest snapshot. '''Only''' snapshots are packaged with the language files exposed in the ''/language'' folder.</span>
 === Translation process ===

@@ Line 3: / Line 3: @@
 This in an ''example for'' translation into ''Brazilian Portuguese''.
-'''NOTE''' The steps below show the translation on the operating system windows. The steps however are pretty much generally the same for every operating system.
+;NOTE
 === Translation process ===
 # download
-#* the most recent development snapshot, an archive named similar to OpenJUMP-20111111-r2527-CORE.zip (the CORE edition should suffice)
+#* the most recent development snapshot from the [[Downloading OpenJUMP#Snapshots|snapshot repository]]
 # extract
 #* it contains a folder named like 'OpenJUMP-DATE-rREV-CORE' (called '''OJfolder''' in the further steps)

@@ Line 68: / Line 68: @@
 * put the properties file into '''language''' folder
-== '''Translation of non latin languages like Chinese, Vietnamese, Japanese etc.''' ==
+== '''Problems with "special" characters''' (e.g. translation of asian languages or european accented characters)==
-# Use an '''UTF-8''' capable editor (notepad, notepad++, jEdit ...) to do the translation and save a '''UTF-8''' text file as '''jump_zh_HK-utf8.properties'''.
+Use an '''UTF-8''' capable editor (notepad, notepad++, jEdit ...) to do the translation and save a '''UTF-8''' text file eg. as '''jump_zh_HK-utf8.properties'''.
-# 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
-#:<pre>native2ascii.exe -encoding utf8 jump_zh_HK-utf8.properties jump_zh_HK.properties </pre>
+In a second step convert the whole file
-: '''ATTENTION''' characters such as chinese may not be shown properly in the splash image.
+: Convert the utf-8 to unicode literals using native2ascii.exe (part of the java development kit, e.g. C:\Program Files\Java\jdk<version>\bin\native2ascii.exe
 == '''Useful tools''' ==

@@ Line 44: / Line 44: @@
 #; NOTE
 #: You should verify your changes by running OpenJUMP now as described in the next step.
 === Verification ===
@@ Line 91: / Line 98: @@
 * get it at
 ** http://www.jedit.org/

@@ Line 41: / Line 41: @@
 #: '''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
+#; NOTE
 === Verification ===