Adding translations

[Christian Rose <menthos menthos com>]

I noticed some recent mistakes regarding adding of new translations, and
I'd like to remind people of some good guidelines when adding
translations.

* When adding new translations in various modules in cvs, don't forget
to add the language code to the ALL_LINGUAS line in the "configure.in"
file in the module. Otherwise your translation won't be used at all in
the software!

* When updating the ALL_LINGUAS line, keep the language codes in
alphabetical order so that it's easy to spot if some language code is
missing.

* Add new translations both to HEAD and to the current branch (if there
is one). Add it to HEAD first, and then to the branch. If you do it the
other way around, HEAD cvs will list a dead revision for that file.

* Always check your file with "msgfmt -cv LL.po" before all commits, to
catch some easily made syntactic errors that might otherwise crash the
software at runtime, and other errors.

* Make sure the po file doesn't have the executable bit (+x) set before
committing. There's no point in storing the po file as an executable in
cvs.

* Always add a ChangeLog entry when you add or change stuff in CVS. This
is important to be able to easily see what file was added or changed at
what point. A ChangeLog entry should preferrably look something like:

YYYY-MM-DD[space][space]Full Name[space][space]<email@address>
[return]
[tab]* LL.po: Updated LANGUAGE translation.
[return]

Example:
2002-09-25  Christian Rose  <menthos@menthos.com>

	* sv.po: Updated Swedish translation.


Good practice is to also use this as the cvs commit comment, and not
just "Updated Swedish translation", since it is easier to read and also
carries the email address if someone needs to contact you regarding the
commit.


Cheers,
Christian