===========================================================
===		Getting started				===
===========================================================

Creating a localisation
-----------------------

Find the ISO standard country code for your translation (e.g. "nl" for Dutch, "es" for Spanish, ...) and copy the template using the country code.
e.g.
	cp messages.po nl.po

To make sure the build script recognizes your new localisation, edit the "ALL_LINGUAS" variable in "configure.ac".
All values need to be space seperated.
e.g.
	ALL_LINGUAS="nl es pt_BR fr"

The last thing to do, is add your translation to the monodevelop project (po.mdse). You don't really need monodevelop to do this,
any basic text editor is more then enough, since the file format is really simple.

Updating the template
---------------------

If, for some reason, messages.po is outdated and needs to be updated, then there are 2 ways to do it.

1) Contact one of the main developers, which is probably the simplest thing to do.

2) If you really want to do it yourself, you need a patched version of monodevelop in order to generate a correct template.
Apply "monodevelop.diff" to monodevelop 1.9 or later, load Galaxium.mds and run the Update command on the "po" project.


===========================================================
===		How to get commit access		===
===========================================================

First time translator
---------------------

As a precaution, first time translators need to send us a patch so we can check their work.
In other words, we try to find another native speaker who quickly reads over your work, to make sure the
translation is correct. (Don't worry about spelling errors, incomplete translations, ... we just want to avoid profanities.)

Experienced translators
-----------------------

Contact one of the main developers (Phil, Ben or Paul), give us a shortlist of applications you helped translate,
and you will get commit access as soon as possible.
