Backport policy regarding new strings ?
Geert Janssens
janssens-geert at telenet.be
Mon Jan 21 11:42:23 EST 2013
- Previous message: Backport policy regarding new strings ?
- Next message: r22681 - gnucash/trunk/src - Implement a Book Option to give users the choice to use the transaction number field (default and current behaviour) or, alternatively, the split action field of the anchor split for 'Num' column on registers, reports, import and export, where applicable. The difference between the two is that with the default, the same 'Num' is displayed for a given transaction regardless of what register it is viewed in and with the new option, a different 'Num' can be entered/displayed for a given transaction in each register it is viewed in. In both cases, the 'next number logic' of the 'Num' cell is based on the account of the register the transaction is entered/viewed from but in one case it fills the transaction number, in the other, it fills the split action field of the anchor split (with the transaction number field displayed in the register cell labeled 'T-Num'). In both cases, both fields are visible and can be used as free-form text in double-line mode for any value the user wants. If the new option is not selected, there should be no change in Gnucash's behaviour with the exception of displaying the book options dialog in 'new book' situations.
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Hi Yawar,
I believe I have already committed the patch for trunk in r22711. So
with that I think the bug report can be closed.
Regards,
Geert
On 20-01-13 21:57, Yawar Amin wrote:
> Hi Christian,
>
> On 2013-01-20 14:55, Christian Stimming wrote:
>> [...]
>> It's up to you (or anyone who wants to commit). We don't have any agreement on
>> this right now.
>>
>> However, I would suggest not to add a new string in the 2.4.x branch. Most
>> probably, there will be no translator activity between now any another 2.4.x
>> release. This means the new string will show up untranslated. I think this
>> should be avoided, unless there are really strong reasons (for having an
>> untranslated string show up, rather than no new string and/or a string with
>> minor errors.)
>>
>> In the case of the new tip-of-the-day, I think there is not a strong reason to
>> have it in the 2.4 branch. Just add it to trunk and it will be in the next
>> release and translation series.
>>
>> Please feel free to add this suggestion into the wiki page... I currently
>> don't easily see how I can explain this there. Thanks!
> Thanks, I've added an explanation that should roughly cover our caution
> against adding strings
> (http://wiki.gnucash.org/wiki/index.php?title=String_Freeze&action=historysubmit&diff=9347&oldid=7259).
>
> Geert, let's go ahead with Christian's suggestion to commit the patch to
> trunk but not to 2.4
>
> Regards,
>
> Yawar
>
>
- Previous message: Backport policy regarding new strings ?
- Next message: r22681 - gnucash/trunk/src - Implement a Book Option to give users the choice to use the transaction number field (default and current behaviour) or, alternatively, the split action field of the anchor split for 'Num' column on registers, reports, import and export, where applicable. The difference between the two is that with the default, the same 'Num' is displayed for a given transaction regardless of what register it is viewed in and with the new option, a different 'Num' can be entered/displayed for a given transaction in each register it is viewed in. In both cases, the 'next number logic' of the 'Num' cell is based on the account of the register the transaction is entered/viewed from but in one case it fills the transaction number, in the other, it fills the split action field of the anchor split (with the transaction number field displayed in the register cell labeled 'T-Num'). In both cases, both fields are visible and can be used as free-form text in double-line mode for any value the user wants. If the new option is not selected, there should be no change in Gnucash's behaviour with the exception of displaying the book options dialog in 'new book' situations.
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the gnucash-devel
mailing list