2012/10/16 Michal Čihař <michal(a)cihar.com>om>:
Hi
Dne Sun, 14 Oct 2012 16:04:45 +0200
Dieter Adriaenssens <dieter.adriaenssens(a)gmail.com> napsal(a):
I don't find any clear rules on when to
add/update translatable
strings (from the developer point of view). I have a suggestions :
These are basically okay, maybe this should be put into wiki?
That's the idea, but I wanted to check with the other developers first.
I'll put it on later today.
master (dev)
:
- freely add and change translatable strings
when preparing a future stable (4.0-alpha/rc)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
(but exceptions allowed after discussion on mailing list)
- updates fixing typos and grammar are allowed
current stable (QA_3_5)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
- updates fixing typos and grammar are allowed
old releases
- no maintance on translatable strings (no new strings, no fixes on
existing strings)
What do you think?
BTW : the reason I mentioned allowing grammar/typo fixes in current
stable, is because it has almost no influence on the translating
process. A string with an fixed typo does not have to be retranslated.
These are okay as long as you change source string in all po files,
otherwise the strings will appear as fuzzy and will require attention
from translators.
What do you mean by 'all po files'? Is running po-update sufficient?
Or do you mean it has to be changed in every branch were the string
exists?
--
Kind regards,
Dieter Adriaenssens