-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I used to translate on battle of Wesnoth, they have a nice site
http://www.wesnoth.org/gettext/ on which they keep track of progress.
Though I do not know if they do a pot update automaticly it might be
useful to contact them (Nils Kneuper aka Ivanovic) to know how they do
it. Or some other project, because I guess we do not need to reinvent
the wheel.
Foppe
Leandro Regueiro schreef:
>> Updating the .pot file in an automated is necessary. Daily basis
wouldn't hurt.
>> I don't think it's necessary to update the .po files from .pot so
>> often, as most translators should know how to do it and they might
>> feel it interferes with their work (if the file is updated before
>> their patch is commited). So I suggest to commit .po files updates
>> once a month.
>
> Really the updating of .po files only is needed just before a new
> version is going to be built. But generating a .pot file every week or
> best, every day is necessary. The translators know how to update their
> .po files using the .pot file, but this .pot file must exist and be
> updated. This way only the .pot generation needs to be automated.
>
> Bye,
> Leandro Regueiro
>
> --
> ___
> Inkscape-translator mailing list
> Inkscape-translator@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknTWoIACgkQtK8Zi+dRolWqvACffMKrWeICOExRK/2JS2ZYXbuA
6ykAnRu8yP/xRPoL2AS5Krz/5I/Abixf
=3UEv
-END PGP SIGNATURE-
--
___
Inkscape-translator mailing list
Inkscape-translator@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-translator
