As I understand it, the two menu items call the same report file with different 
title flags, so there is no overhead in storage or codebase.

Your concern boils down to the fact that both names appear in the menu. 

While this is annoying, it has come up on the lists before that a person has 
expected to find one of these reports, and wondered where it was—not knowing 
that it was there under the other name. I believe it was decided that it was 
easer just to include the same report under both names, making its availability 
clear to a broader set of users. Unless there is complete agreement in the 
field for one name over another in all circumstances (and there doesn’t appear 
to be), it does no harm to include both, in my opinion.

Honestly, it would be more useful in my opinion to clear out the “standard” 
reports that serve no purpose other than to show a potential report programmer 
(I haven’t heard of many of those, besides Doug Doughty and Chris Lam) how they 
might write new reports. The two “vs. Day of Week” reports and the two sample 
reports come to mind. I'm also unsure of the purpose of most of the Budget 
reports, and when I asked on the lists for descriptions of these, I did not 
receive any input, suggesting that I am not alone in wondering at their purpose.

But the two entries for the same report? Not a big deal.

David T.

On July 12, 2018 at 8:51:25 AM, Adrien Monteleone 
(adrien.montele...@lusfiber.net) wrote:

I understand that perfectly, hence my possible RFE to have the New Book Wizard 
handle this somehow. (and if it doesn’t, one can always rename it in the 
options as you mention)

At the very least, regardless of what you want or need to call it, we don’t 
need two of the same report in the menu. It’s just clutter and serves to add 
confusion.

Regards,
Adrien

> On Jul 12, 2018, at 7:08 AM, Mike or Penny Novack 
> <stepbystepf...@dialup4less.com> wrote:
>  
> On 7/12/2018 12:34 AM, Adrien Monteleone wrote:
>> If I had a vote, I’d say keep one and just delete the other entirely. Even a 
>> ’see also’ is just clutter.
>>  
>> As to which name to keep, the easiest and likely most discoverable is 
>> “Income Statement”.
>>  
> The "issue" (if there is one) is that this report (in terms of what it shows) 
> is known be different NAMES depending on the type of entity for which the 
> books are being kept. Note that the name of the report (in gnucash) and the 
> title of the report in the report itself need not be the same (you can change 
> the title via Edit=>Options.
>  
> I mainly keep books for non-profits, for which the report is known as the 
> "Revenue Statement" or "Statement of Revenues and Expenses".
>  
> For a for profit business known as "Profit and Loss" and for personal books 
> "Income Statement".
>  
> Michael D Novack
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.


_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to