Translation Status: Proposed end of String Freeze

Derek Atkins warlord at MIT.EDU
Thu Jul 20 11:09:16 EDT 2006

I would propose that 2.0.1 not have changed strings, but we allow it
for 2.0.2.  But that's just my personal opinion.  What do you the rest
of you think?


Quoting Christian Stimming <stimming at>:

> Hash: SHA1
> Dear Translators et al,
> before the 2.0.0 release we had a particular "String Freeze" period.
> This was a time when all strings were fixed. It was guaranteed that no
> string changes occur. This should help to offer complete translations at
> the 2.0.0 release, and several languages reached this challenging mark!
> Congrats.
> Now 2.0.0 is out. We *could* have a string freeze for even some more
> releases, but actually I think this isn't really necessary. Instead, I
> propose the developers should now be allowed to make all queued string
> changes (e.g. and
> ) iff these changes went
> through the normal backporting audit.
> We *could* have some particular 2.0.x releases which have a string
> freeze beforehand, and others without it, but I think the minimal amount
> of string changes don't justify this additional bookkeeping overhead. So
> I simply propose an end to the string freeze. Other ideas? Proposals?
> I've updated accordingly.
> Christian
> Version: GnuPG v1.4.2.1 (MingW32)
> Comment: Using GnuPG with Mozilla -
> iQCVAwUBRL+aKGXAi+BfhivFAQJ4mgP9GOTxQmpPsok2lq1KuNYlO/udEcQMaonr
> rt3z/Bl4xD1YyU8Z5xNnQNCxZpJZn4hvYcWR1lYE5fc7BDsd8EpltZAcik1VI57b
> LkByDC/Kh1TknpctG4uvHVdSAbZUvpKrh4L01ZqAhtGvxRicEr8hS7e7D/Re63/6
> stApgHX9PJ4=
> =iBCy
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at

       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL:    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available

More information about the gnucash-devel mailing list