I've msgmerged a new gnucash.pot for the 5.6 release so string freeze is now in
effect until the release.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reminder: GnuCash 5.5 release is next Sunday so we have a string freeze this
week to let the translators catch up.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Devs,
GnuCash 5.4 release is only a week away, so I've made and merged an updated
gnucash.pot for the translators to work on. Please don't push any commits with
new or revised translatable strings until after the release.
Regards,
John Ralls
___
+1
--
Sent from my Android phone with GMX Mail. Please excuse my brevity.
On 19/06/2023, 17:07 john wrote:
Pedro,
I don't know. I can't find anything in project settings nor in the
documentation about project settings that relates to notifications, nor
do I see any
Pedro,
I don't know. I can't find anything in project settings nor in the
documentation about project settings that relates to notifications, nor do I
see any difference in the settings with Gramps. I've opened
https://care.weblate.org/#ticket/zoom/6679 about it.
Regards,
John Ralls
> On
Hello developers,
I just finished my translation because of this message.
Strangely, I'm not receiving Weblate notifications for Gnucash, although
I receive them for the other projects I watch.
I just checked my notifications, and they are active. Is it my mistake
somewhere, or is it the
Reminder for all developers: The 5.2 release is one week away so please don't
push any commits involving translatable strings until after that release.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
Developers,
With the release of 4.902 we're in string freeze until the 5.0 release on the
26th. This applies to maint as well because we'll merge any changes in maint to
master every Friday for the rest of the month.
Regards,
John Ralls
___
gnucash
Devs, the 4.13 release is in two weeks so that means that there's a string
freeze on maint until then.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
We'll be releasing GnuCash 4.12 on September 25th, so string freeze on the
maint branch will begin this coming Sunday, 11 September.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman
, but similar messages to existing messages.
Regards
Frank
Am 16.06.22 um 21:01 schrieb John Ralls:
> We're less than two weeks from release of 4.11 so a string freeze is in
> effect until then. Sorry that I missed posting this reminder last Sunday.
>
> Regards,
We're less than two weeks from release of 4.11 so a string freeze is in effect
until then. Sorry that I missed posting this reminder last Sunday.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org
e 19th.
>
> Regards,
> John Ralls
>
>> On Dec 2, 2021, at 10:45 AM, Frank H. Ellenberger
>> wrote:
>>
>> Dear contributors,
>>
>> I just had a look into https://wiki.gnucash.org/wiki/Release_Schedule:
>>
>> Release String Freeze
a look into https://wiki.gnucash.org/wiki/Release_Schedule:
>
> Release String Freeze
> 4.9 2021-12-05
>
> If you still have string changing patches around, hurry up!
>
> Regards
> Frank
> ___
> gnucash-devel
Dear contributors,
I just had a look into https://wiki.gnucash.org/wiki/Release_Schedule:
Release String Freeze
4.9 2021-12-05
If you still have string changing patches around, hurry up!
Regards
Frank
___
gnucash-devel mailing list
arball to the Translation Project, so string freeze is in effect
> on the maint branch until the release is complete.
>
> Please do not add or modify any string submitted for translation during the
> string freeze.
>
> Regards,
> John Ralls
__
We're two weeks away from releasing GnuCash 4.7 and I've just sent off the
pre-release tarball to the Translation Project, so string freeze is in effect
on the maint branch until the release is complete.
Please do not add or modify any string submitted for translation during the
string freeze
We're two weeks away from releasing GnuCash 4.6 and I've just sent off the
pre-release tarball to the Translation Project, so string freeze is in effect
on the maint branch until the release is complete.
Please do not add or modify any string submitted for translation during the
string freeze
I forgot to CC the list.
Weitergeleitete Nachricht
Betreff: Re: [GNC-dev] String Freeze
Datum: Wed, 17 Mar 2021 19:36:10 +0100
Von: Frank H. Ellenberger
An: Geert Janssens
As there is not much progress, neither by documenters nor translators, I
see no reason
Does string freeze also cover gnucash-docs ?
Geert
Op zondag 14 maart 2021 22:58:35 CET schreef John Ralls:
> Devs,
>
> It's two weeks until our 4.5 release and that means it's time for a string
> freeze on maint. Please don't push any commits with changes to any
> translatable s
evs,
>
> It's two weeks until our 4.5 release and that means it's time for a string
> freeze on maint. Please don't push any commits with changes to any
> translatable string, not even minor spelling or punctuation changes, to maint
> until after we release GnuCash 4.5.
>
&g
Devs,
It's two weeks until our 4.5 release and that means it's time for a string
freeze on maint. Please don't push any commits with changes to any translatable
string, not even minor spelling or punctuation changes, to maint until after we
release GnuCash 4.5.
Regards,
John Ralls
John,
> We're trying an experiment for this maintenance release: We're doing a string
> freeze two weeks before the 4.3 maintenance release. I think you can use a
> GitHub-generated tarball to generate your potfile. It's at
> https://github.com/Gnucash/gnucash/archive/4.3-string-f
sent, awaiting response... 302 Found
Location:
https://codeload.github.com/Gnucash/gnucash/tar.gz/4.3-string-freeze
[following]
--2020-12-13 08:03:17--
https://codeload.github.com/Gnucash/gnucash/tar.gz/4.3-string-freeze
Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
Connecting
Benno,
We're trying an experiment for this maintenance release: We're doing a string
freeze two weeks before the 4.3 maintenance release. I think you can use a
GitHub-generated tarball to generate your potfile. It's at
https://github.com/Gnucash/gnucash/archive/4.3-string-freeze.tar.gz
Please
;
> If we schedule a string freeze 2 weeks before each release, coders have
> still two and a half month to apply changes without restrictions.
> And translators will have 2 weeks to do their work.
>
> If nobody objects, we will apply this rule for 4.3:
> Pull Requests before: Sa,
Dear coders and translators,
watching translations often arrive short after a release is frustrating.
But translators often do not know, when they should start tp cover all
changes.
If we schedule a string freeze 2 weeks before each release, coders have
still two and a half month to apply
Hi Geert,
the formal set of rules from 2.4 times are still valid:
http://wiki.gnucash.org/wiki/String_Freeze
However, as we've just entered string freeze mode, I think we should
still be open for typo corrections. Translators will have to cope with
approx. 1000 changed or new strings, so
://wiki.gnucash.org/wiki/String_Freeze
However, as we've just entered string freeze mode, I think we should
still be open for typo corrections. Translators will have to cope with
approx. 1000 changed or new strings, so still changing a few of them
doesn't really get anyone into trouble
It's been a while since the previous string freeze, so I'm a
bit rusty...
Can someone remind me again how we handle string
corrections that appear during string freeze ? Like the
two patches Aurimas has posted today ?
Are these authorized exceptions to the string freeze ?
Geert
On Nov 20, 2013, at 1:59 PM, Geert Janssens janssens-ge...@telenet.be wrote:
It's been a while since the previous string freeze, so I'm a
bit rusty...
Can someone remind me again how we handle string
corrections that appear during string freeze ? Like the
two patches Aurimas has posted
they are no longer in
any of the translated po files either.
Restoring the option also means re-introducing the translatable strings.
Although they used to be translated, they aren't anymore now. So I guess
restoring the option results in a string freeze break, right ?
How should I deal
the option results in a string freeze break, right ?
Technically, yes, but it concerns only those translations which have
done a msgmerge in the time since 2.3.16. This is happened only for
nl.po, the Dutch translation by Mark Haanen. He's been the most active
translator, so I guess he will even
.
Although they used to be translated, they aren't anymore now. So I guess
restoring the option results in a string freeze break, right ?
Technically, yes, but it concerns only those translations which have
done a msgmerge in the time since 2.3.16. This is happened only for
nl.po, the Dutch
the option also means re-introducing the translatable
strings. Although they used to be translated, they aren't anymore now.
So I guess restoring the option results in a string freeze break,
right ?
Technically, yes, but it concerns only those translations which have
done a msgmerge
the option also means re-introducing the translatable
strings. Although they used to be translated, they aren't anymore now.
So I guess restoring the option results in a string freeze break,
right ?
Technically, yes, but it concerns only those translations which have
done a msgmerge
...@code.gnucash.org
To: gnucash-patc...@gnucash.org
Sent: Tue, October 19, 2010 2:32:50 PM
Subject: r19680 - gnucash/trunk/src/backend/sql - Bug 632166: A Better fix that
doesn't break string freeze or introduce a Gtk GUI dependency into the backend.
Author: jralls
Date: 2010-10-19 14:32:50 -0400 (Tue, 19
/src/backend/sql/gnc-transaction-sql.c
Log:
Bug 632166: A Better fix that doesn't break string freeze or introduce a Gtk
GUI dependency into the backend.
___
gnucash-patches mailing list
gnucash-patc...@gnucash.org
https://lists.gnucash.org/mailman
On Oct 19, 2010, at 12:29 PM, J. Alex Aycinena wrote:
On line 724, should
Commodity save failed: Probably and invalid or missing currency
be
Commodity save failed: Probably an invalid or missing currency
(i.e., minor typo)?
It should indeed. Thanks.
Regards,
John Ralls
Zitat von Derek Atkins de...@ihtfp.com:
I do not feel the string freeze affects the docs, so you should feel
free to update them. The string freeze is due to the way
application translation works. If you change a string the the
translation fails so instead of seeing Italian you'll see
to wait until after 2.4 due to the
string freeze? It would be nice to have the changes included in the
2.4 release and, since it is locale specific (e.g., US only), perhaps
it can be allowed even if other changes to the help text aren't. Or
does the string freeze only apply to text embedded in code
I do not feel the string freeze affects the docs, so you should feel free to
update them. The string freeze is due to the way application translation
works. If you change a string the the translation fails so instead of seeing
Italian you'll see the (new,changed) string. The docs however
Dear Yasuaki,
thank you very much for the patch. However, in this particular case I'd like
to defer this patch until after 2.4.0 is out. I've attached the patch to a
newly created bug https://bugzilla.gnome.org/show_bug.cgi?id=628444 so that it
won't be forgotten. Thanks!
Christian
Am
Hello, Christian and Geert.
Thank you for accepting my patches.
I continue to translate GnuCash.
Regards,
Yasuaki
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
string freeze
because the label _Edit is
used at the other place.
Best regards,
--
Yasuaki Taniguchi
yasua...@gmail.com
Index: src/gnome/glade/account.glade
===
--- src/gnome/glade/account.glade (revision 19471)
+++ src/gnome
we can only
improve this. These are the known exceptions which are allowed during
string freeze phase as well.
@Devs: Feel free to commit the patches immediately; I don't know when
I will have SVN access next time.
Best Regards,
Christian
Zitat von Yasuaki Taniguchi/ yasua
the
strings are untranslated in the program altogether, so we can only
improve this. These are the known exceptions which are allowed during
string freeze phase as well.
@Devs: Feel free to commit the patches immediately; I don't know when
I will have SVN access next time.
Ok, I have committed
Op maandag 12-07-2010 om 14:03 uur [tijdzone +0200], schreef Cristian
Marchi:
No problem for me in regards of the italian translation. I just hope
that developers give us a few days before a new release to update the po
files.
Same here for the dutch translation.
No problem for me in regards of the italian translation. I just hope
that developers give us a few days before a new release to update the po
files.
Il 10/07/2010 16:52, Geert Janssens ha scritto:
Dear translators,
I am aware that we are in string freeze and I attempt to take
2010/7/12 Christian Stimming stimm...@tuhh.de
Am Saturday 10 July 2010 schrieb Geert Janssens:
So the options are either:
* apply the changes now, introducing a small number of fuzzy/new strings
* apply the changes only in the 2.5/2.6 development series.
I'd prefer the commit the
Dear translators,
I am aware that we are in string freeze and I attempt to take this into
account while improving the development release.
Recently I have committed some changes to the code base to improve the
consistency (and translatability) of our report options dialog boxes [1
Frank H. Ellenberger f.ellenber...@online.de writes:
Am Freitag, 23. April 2010 um 18:41:38 schrieb Phil Longstaff:
Since string freeze has been declared, we need discussion on whether
this goes into 2.4.0 or not. Should I create a 2.4 branch with current
trunk so that I can start to cherry
Am Freitag, 23. April 2010 um 18:41:38 schrieb Phil Longstaff:
Since string freeze has been declared, we need discussion on whether
this goes into 2.4.0 or not. Should I create a 2.4 branch with current
trunk so that I can start to cherry-pick changes and not stop
development?
If we use iso
in a bigger rework of the iso-4217 stuff as
discussed in the
https://lists.gnucash.org/pipermail/gnucash-devel/2009-October/026558.html
thread? I would like to upload my changes, which conflicts with yours, if
done parallel.
Since string freeze has been declared, we need discussion on whether
Hello, Christian and Derek.
just committed (r18582).
Thanks a lot for your discussion and approval of this change.
Regards,
--
Yasuaki Taniguchi
yasua...@gmail.com
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
Hello, developers.
I want to change the word Split.
The GnuCash uses the word Split in two meanings: split transaction
and split stocks.
When I translate them into Japanese, I have to use the different words for them.
So I propose that we should keep the string which means split
transaction as
Zitat von Phil Longstaff plongst...@rogers.com:
I want to release 2.3.9 in the next week or so.
That's good to hear!
Can we also consider
that the first revision under a string freeze? Does anyone have any
upcoming string changes?
I don't have string changes right now, but I expect some
Yasuaki Taniguchi/谷口康明 yasua...@gmail.com writes:
Hello, developers.
I want to change the word Split.
The GnuCash uses the word Split in two meanings: split transaction
and split stocks.
When I translate them into Japanese, I have to use the different words for
them.
So I propose that
Christian Stimming stimm...@tuhh.de writes:
Zitat von Phil Longstaff plongst...@rogers.com:
I want to release 2.3.9 in the next week or so.
That's good to hear!
Can we also consider
that the first revision under a string freeze? Does anyone have any
upcoming string changes?
I don't
: Mon, January 25, 2010 11:17:58 AM
Subject: Re: String freeze
Christian Stimming stimm...@tuhh.de writes:
Zitat von Phil Longstaff plongst...@rogers.com:
I want to release 2.3.9 in the next week or so.
That's good to hear!
Can we also consider
that the first revision under a string freeze
Am Montag, 25. Januar 2010 schrieb Derek Atkins:
The GnuCash uses the word Split in two meanings: split transaction
and split stocks.
When I translate them into Japanese, I have to use the different words
for them.
The locations of string to change in 2.3.8 are as follows:
Am Montag, 25. Januar 2010 schrieb Phil Longstaff:
I want to release 2.3.9 in the next week or so.
That's good to hear!
Can we also consider
that the first revision under a string freeze? Does anyone have any
upcoming string changes?
I don't have string changes right now, but I
I want to release 2.3.9 in the next week or so. Can we also consider
that the first revision under a string freeze? Does anyone have any
upcoming string changes?
Phil
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org
Is trunk in string freeze already ? I am about to commit a patch that adds 3
new translatable strings.
Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Zitat von Geert Janssens janssens-ge...@telenet.be:
Is trunk in string freeze already ? I am about to commit a patch that adds 3
new translatable strings.
No, trunk is (still) not yet in string freeze. There have been approx.
20 changed or new strings between 2.3.7 and 2.3.8, mostly because
On Wednesday 9 December 2009, Christian Stimming wrote:
No, trunk is (still) not yet in string freeze. There have been approx.
20 changed or new strings between 2.3.7 and 2.3.8, mostly because the
time interval turned out so large. So just go ahead and add further
strings, if they improve
No, it is not in string freeze, though I think the next release (2.3.9) should
include a freeze. Go ahead.
Phil
From: Geert Janssens janssens-ge...@telenet.be
To: gnucash-devel@gnucash.org
Sent: Wed, December 9, 2009 9:50:41 AM
Subject: String freeze
In 2.3.4, I worked to get all of the sql table changes in. The schema is now,
basically, frozen except for really important changes.
In about 2 weeks, I want to release 2.3.5. This will be the release at which
strings will be frozen so that translation work can be done.
After that, I think I
so that translation work can be done.
Sounds good to me.
Before the final string freeze, some of the newly introduced strings might
still need to be changed, but I think almost all of them are ready for string
freeze.
Examples for new strings which still need to be changed are e.g.
src/report
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
Hello together,
it may be, that I missed something. But how do we keep it with a string
freeze? I remember, at least my CUSIP/ISIN patch is changing a few strings.
Will they be untranslated in 2.2.7 or got the translators a chance?
Regards
Frank
Am Freitag, 26. September 2008 19:15 schrieb Frank H. Ellenberger:
Hello together,
it may be, that I missed something. But how do we keep it with a string
freeze? I remember, at least my CUSIP/ISIN patch is changing a few strings.
Will they be untranslated in 2.2.7 or got the translators
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
On Wed, 2007-04-18 at 08:44 -0400, Josh Sled wrote:
Is anyone else going to be able to commit to being around, if only for
part of it? It'd be nice to know if/when I can step out to run errands
during the day. :)
I should be online.
David
___
Josh Sled [EMAIL PROTECTED] writes:
I'm thinking of announcing this – at least for the 21st – as 1500 UTC
(11am EDT) to 2200 UTC (6pm EDT).
Is anyone else going to be able to commit to being around, if only for
part of it? It'd be nice to know if/when I can step out to run errands
during
Christian Stimming [EMAIL PROTECTED] writes:
Am Sonntag, 15. April 2007 17:48 schrieb Josh Sled:
In #gnucash yesterday, hampton made an excellent suggestion that we
should work to reduce the number of open bugs before the string freeze.
Not necessarily related, but I think it would
In #gnucash yesterday, hampton made an excellent suggestion that we
should work to reduce the number of open bugs before the string freeze.
Not necessarily related, but I think it would be interesting to have a
proper Bug Day early-ish in the release schedule.
As per the schedule at http
Am Sonntag, 15. April 2007 17:48 schrieb Josh Sled:
In #gnucash yesterday, hampton made an excellent suggestion that we
should work to reduce the number of open bugs before the string freeze.
Not necessarily related, but I think it would be interesting to have a
proper Bug Day early-ish
-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
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
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
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,
before the 2.0.0 release we had a particular String Freeze period
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
Dear developers,
As discussed here and on IRC before, we plan to have a String Freeze period
between sometime now and the 2.0.0 release. This should give the translators
the time necessary to achieve full translation. More information about the
purpose and what it means is on http
Am Sonntag, 5. Februar 2006 15:51 schrieb Neil Williams:
Are we having a string freeze before 1.9.0?
Yes, we will need a formal string freeze period, and we (read: me) will have
a clear definition for what this means. But not in 1.9.0. In one of the later
1.9.x releases.
http
85 matches
Mail list logo
