SourceForge.net Logo Support This Project

jMemorize

Translations

Jump to: navigation, search

Please see the FAQ on how to add/update the translations for jMemorize.

Contents

Using command line tools and Java tools to add a new translation

You can add your translation with the tools provided with Java at the console. This is a mostly platform neutral way of doing it, provided in the hope that it will be useful to someone doing their own translation.

NOTE: Commands like mkdir, mv, rm listed are the GNU/Linux versions, but similar commands are available on Microsoft Windows or Mac OS X. It is presumed that you know how to use your editor of choice.

Download jMemorize-x.y.z.jar. Create a new directory called “unpacked”

mkdir unpacked

Move the .jar file into unpacked

mv jMemorize-x.y.z.jar unpacked/

Extract the files from from JAR-archive

jar xvf unpacked/jMemorize-x.y.z.jar

Delete the JAR-file AFTER unpacking

rm unpacked/jMemorize-x.y.z.jar

Translate translation_en.properties with an editor

[Favourite editor] unpacked/resource/text/translation_en.properties

Save the file under a new name

[Favourite editor save as into] unpacked/resource/text/translation_no.properties

Encode native language properly

native2ascii -encoding UTF-8 unpacked/resource/text/translation_no.properties unpacked/resource/text/translation_no.properties

Add the language code to the language file, here “no” for Norwegian

[Favourite editor] unpacked/resource/text/langs.txt

Create a new JAR-file using the existing manifest-file

jar cmfv unpacked/META-INF/MANIFEST.MF jMemorize-1.2.3.jar -C unpacked/ .

Run the application and change to the new language under Preferences, then restart

java -jar jMemorize-1.2.3.jar

Send your translation to Riad Djemili

Send me (jmemorize at riad de) a copy of your translation so that it can be added to the next release of jMemorize!

NOTES

Most translations for jMemorize have been done on Microsoft Windows, using Microsoft Windows end of line characters. This should not be a problem, but if you experience odd behaviour, use

unix2dos translation_XX.properties

to change the end of line character to rule out that option.

Personal tools