AUDIT: r20507 - gnucash/trunk/src/engine - Various spelling fixes in comments and translatable strings.

[Christian Stimming]

Am Sonntag, 3. April 2011 schrieb Geert Janssens:
> > > Trac: http://svn.gnucash.org/trac/changeset/20507
> > > 
> > > Modified:
> > >    gnucash/trunk/src/engine/Account.c
> > > 
> > > Log:
> > > Various spelling fixes in comments and translatable strings.
> > 
> > Thanks for the spelling fixes. I got a little bit nervous about the
> > "translatable" strings - but although you did change strings, to me those
> > strings seem to be not translatable.
> 
> Indeed you're right. I didn't pay attention and *thought* I had changed
> translatable strings.
> 
> > That's perfectly fine and just makes our job even easier, i.e. you did
> > spelling fixes but they do not concern any translatable string.
> 
> From you reaction I conclude that changed translatable strings should be
> backported ?

No, my reaction was about a different issue: If there have been changes in 
translatable strings, it inevitably means all translators will have to update 
the translations, and I as German translator will have to do that for the 
German translation, i.e. there will be work for me to do. Once I realized 
there isn't any work to do (because nothing translatable was touched), I was 
relieved.

Changes in translatable strings may or may not be backported, just as usual 
feature changes may or may not be backported. If the string changes are not 
bugfixes but instead "something new", I would not recommend backporting, so 
that the existing translations of those strings will remain active. Bugfixes 
such as spelling fixes for translatable strings should indeed be back-ported.

Regards,

Christian