Am Donnerstag, 20. Juli 2006 19:45 schrieb Derek Atkins:
> That makes sense to me! That would mean that no string change for
> 2.0.1, but as soon as 2.0.1 gets tagged we can backport the string
> changes for inclusion into 2.0.2! I'm happy with that.
Ok, I've changed
http://wiki.gnucash.org/wik
That makes sense to me! That would mean that no string change for
2.0.1, but as soon as 2.0.1 gets tagged we can backport the string
changes for inclusion into 2.0.2! I'm happy with that.
-derek
Quoting Eneko Lacunza <[EMAIL PROTECTED]>:
> Hi,
>
>> From a translator point of view, I think the
Hi,
>From a translator point of view, I think the best would be to have all
string-related changes applied in batch (at once), in the begining of a
new point release development.
This way we can maximize the time for translators to notice changes and
update translations, before a new point releas
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?
-derek
Quoting Christian Stimming <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear Translators et al,
>
> befor
-BEGIN PGP SIGNED MESSAGE-
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 rele
