pot template update policy ([PATCH] GnuCash UI strings: more consistency.)

[Christian Stimming]

Am Freitag, 2. August 2013, 20:43:17 schrieb Cristian Marchi:
> While we are talking about translation I need another help from you
> Christian: what's the policy for updating the translation templates in
> the repo? Can I do it from time to time, or do I have to wait specific
> events (just before string freeze, after a test release etc...)? 

As a general rule: No, we don't update the translation po files. Let this be 
done only by the translators themselves.

As an exception rule: On occasional special events we do update all the po 
files. But this is probably at most once per year, such as right after 
switching from the previous stable branch to the new stable branch.

The point is: Updating the po files doesn't change the available translations 
in the program at all. Any translations that were existing for an existing 
msgid will just remain valid, but any other translations for msgid that have 
been changed and are no longer existing will just be left unused. The only 
person that *needs* the update is the translator herself. Hence, that person 
should also care about the update themself and not get caused any conflicts by 
additional updates in our project.

> Is it
> good if I only update the template and commit it, say for it.po, but not
> for the remaining of the po files?

Yes. As you're the translator for it.po, it is up to you to update the po file 
from the most recent template.

Also, you mention the "templates" but you probably meant "the po files". The 
template file, gnucash.pot, is not in the SVN repository but is always 
generated locally. As it isn't in SVN, we don't have to discuss its update 
anyway - it exists only locally. Or in the release tarballs, but there it is 
generated newly every time the tarball was generated.

Regards,

Christian