> The translations are not complete, but the make_msgs.py utility has an
> easy upgrade mechanism, so you can start now and just fill in when there
> are new translations to be made.
Ok, I think they are complete now. Might be I overlooked some stuff, but
that can only be quite rare strings.
> But please don't start yet, as the first version is very crude and
Ok, you now can start to produce other translations, if you want to. I did
some more changes today, as are:
modules/system/*.py - those with translations were cleaned up a bit
comments/html.py - added translations for the comment form
pycs_translation.py - small fix
and the most important ones:
make_msgs.py - scans all .py files and produces a catalog
TRANSLATIONHOWTO - a small documentation for the above script
Phil: even if you won't do the translations, you might read the file, as
it contains some hints on the format the scanner expects. Especially the
translated strings should be written as _("...") or _('...'), not with
your usual _( "..." ) format, as the latter would break make_msgs.py.
Others: fetch the newest CVS stuff, read TRANSLATIONHOWTO, create your own
translation file for your favorite language and start hacking :-)
Maybe it might be a good idea to ask on this list before starting, to make
sure that no two developers are translating to the same language.
The translations are not complete, but the make_msgs.py utility has an
easy upgrade mechanism, so you can start now and just fill in when there
are new translations to be made.
German translation is already in CVS and will be maintained by me.