Translate Toolkit & Pootle

Tools to help you make your software local

User Tools

Software >> OpenProj


OpenProj is a project management program. It is written in Java. The company making OpenProj also has a non-opensource variant which they run as a web-based service..

Author: Projity Incorporated

Language file information (overview)

  • Number of strings: 1451
  • Number of words: 4230
  • Original file format: Java .properties

Actually there are more words in the file, but not all of it must be translated.


The language file of OpenProj on Pootle was uploaded in October 2009.

* Which version is the latest version of FreeMind? See here (todo).

To see how far OpenProj has been translated into various languages, take a look at their statistics on our Pootle server. Not all languages listed on Pootle are being translated by our translators -- some language files were uploaded for reference purposes only (see “Second-language feature” below).

Procedure for translating OpenProj

If you want to translate OpenProj or parts of OpenProj using our Pootle server, here's the procedure to follow:

1. Check if your language has already been translated. You can find the existing translations here, here and here. Also check the OpenProj forums at Sourceforge if mention of your language has ever been made.

2.1 If your language is already translated or being translated, contact the existing translator (and contact us, if you want us to facilitate the use of Pootle for the existing language).

2.2 If your language is a new language, or if your language needs an update and you can't make contact with the current translator or if the current translator doesn't want to continue translating, announce your intention to help translate OpenProj on the OpenProj forum. Tell him that you would like to use for translation, and get some response from them:

3. Please understand that the files hosted on must be processed before the translation can be shared with the OpenProj people.

The OpenProj project uses Java .properties files, but Pootle uses PO files. The translations from the PO files have to be merged back into the Java .properties files. This is fairly simple to do, but you don't have to do it yourself -- you can ask me to do it for you.

Remember to also send the Decathlon project leader an e-mail of your intention or willingness to help translate OpenProj (keep me in the loop!).

Tips for translators

There is additional information you must read before starting on the OpenProj translation. Each of the original English OpenProj .properties files have instructions at the top of the file, which may be useful to read. The original files are here, here and here.

Second-language feature

If your English isn't that good, and you wish to translate from another language, or if you want to use a second language as a reference while translating, our Pootle server has the second-language feature enabled. You can view the German, Spanish, French, Japanese, Continental Portuguese, Russian and Simplified Chinese strings while you translate from English.

These eight languages are available on the server in read-only format. If you want to help translate them, contact their official translators.

To activate a second source language in Pootle, go to your profile page and select the second language under Alternative Source Language.

Sources for research and stuff

Technical stuff (not really for translators)

Converting the OpenProj .properties files to PO is a bit of a task. However, it has all already been done by me, so you don't have to do it unless you really want to and you enjoy experimenting with different formats.

1. The Translate Toolkit doesn't seem to accept Latin1 as an input encoding for prop2po, so you'll have to convert the .properties files to UTF8 first. For Windows users, I suggest resaving with BabelPad. Remember to save without BOM.

2. The file contain many strings that should not be translated. The tool prop2po does not have the ability to discriminate between strings, but you can use pogrep. Here is a program that will help (if you are using Windows): openprojjer

3. To convert properties to PO:
python prop2po openproj_prop_old openproj_new.po

4. To merge translations back:
python po2prop -t openproj_prop_old openproj_new.po openproj_prop_new

5. The only method of escaping supported by OpenProj is Unicode entities. This is also the default of prop2po and po2prop, so you don't need to specify additional arguments. Files must be delivered to OpenProj in ISO8859-1.

You can test your translation in an installed instance of OpenProj, but remember that you need to have .properties files to do this. Creating the .properties files are described above. You'll need copies of the latest OpenProj English .properties files… they are here, here and here.

OpenProj official l10n info

Already being translated into: cs, da, de, es, fa, fi, fr, gl, it, ja, ko, nl, pt, ro, ru, sk, sv, uk, zh_CN (including many partial translations).

OpenProj's official localisation guide -- not everything in this guide is relevant to Decathlon translators because Pootle takes care of many of the technical issues described in this guide.

Attribution for Decathlon translators

Translators' names and e-mail addresses are usually included in the translated files automatically. We also believe that translators should be given credit for their translations.

The following information reflects the situation between January 2008 and July 2009 (we don't keep statistics automatically). The “activity” column represents the number of lines translated or edited.

Name of translator E-mail address Activity
haytham abulela hammam 2815
Cindy Trinidad 795
Nahit Karatasli 422
Sergi Carrera 353
Richenel Ansano 303
Clytie Siddall 261
Samuel Murray 199
Adil Ait Hamd 190
Iman Zeid 58
Milena Nowotarska 51
Klean Xhelilaj 42
Ajsha Bajcinca 34
Urso Wieske 21
bousmaha habiba 18
F Wolff 14
Louis Kruger 14
Robert Buj 14