Software >> OpenProj

• OpenProj's official site
• OpenProj on Wikipedia

• OpenProj's Pootle page at Locamotion.org

• Customised Google search for OpenProj terminology

• OpenProj glossary for Pootle

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

The language file of OpenProj on Pootle was uploaded in August 2008.

A message was posted on ProZ.com to invite professional translators to participate. In time we'll add the names of the translators who responded.

If anyone else not mentioned here had contributed to translating OpenProj into their language, please send me an e-mail and I'll add your name here. Attribution is important to us.

We take great pains to respect people's privacy, but if you feel that you are listed here in error, please let me know.

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.

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

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

• OpenProj documentation wiki, in a number of languages
• Two forums of OpenProj on Sourceforge
• Open Workbench, TaskJuggler, Gantt Project and KPlato are other opensource project management systems
• A rather large list of project management programs, at Wikipedia

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 pootle.locamotion.org for translation, and get some response from them:

http://sourceforge.net/forum/forum.php?forum_id=708856

3. Please understand that the files hosted on pootle.locamotion.org 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!).

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.

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.

2. The file menu.properties 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. (todo)

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.

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.