Stupid beginner question about string freeze

[Christian Stimming]

Am Freitag, 26. September 2008 21:11 schrieb Frank H. Ellenberger:
> Am Friday 26 September 2008 20:08:24 schrieb Christian Stimming:
> > I think we rather risk leaving them untranslated.
>
> ACK
>
> > there wasn't any feedback from translators about that time, so that I
> > think there isn't much benefit in here.
>
> Only for my better understanding: had they to conclude this from the "Early
> 2.2.7 release?" thread or are there other channels, which I don't know?

There are no other channels. Basically this is just guessing from my side and 
from the other developers here. In the past, occasionally some translators 
have asked specifically about the release schedule including the string 
freeze period. This hasn't happened in recent months. That's what I was 
referring to by saying "there wasn't any feedback".

However, currently we (=the gnucash developers) don't offer any easy way for 
translators to obtain the current SVN gnucash.pot translation template. 
That's unfortunate because the string freeze period only makes sense if the 
input data for the translators (=gnucash.pot) is easily accessible right at 
the beginning of that string freeze period. Currently, this can only be 
obtained by maintaining a complete working copy of the gnucash SVN, which is 
a task that cannot be expected from most of the translators.

Right now all we can do is release the package with some untranslated strings 
and hope for translations for *those* strings to arrive over the months. 
Unfortunately at the time we make another release that includes *those* 
translations, some other string changes will have appeared so that by now, 
*other* strings will be untranslated... I guess you get the picture. The only 
way out of this were if we had a volunteer or an automated way of uploading 
gnucash.pot each time a string was added or changed in the 2.2 branch. I 
planned to do that for some time, but it turned out I don't even have the 
time for that, because it would require reviewing all 2.2 commits for string 
changes and updating a gnucash.pot *quickly* once such a string change was 
committed. Sorry for that.

Regards,

Christian