> On Mar 18, 2022, at 8:50 AM, Michael or Penny Novack 
> <stepbystepf...@comcast.net> wrote:
> 
> 
> 
>> B. WIDTH AND COLUMNS ALIGNMENT
>> 
>> Maybe I didn't use the right words: I don't care about things being pretty 
>> (color, lines, etc). The report is messed up in its basic structure. Maybe 
>> showing you is better. I don't know if I can send a picture as attachment on 
>> the mailing list. I will try sending it in the next e-mail. 
> 
> You don't need to send me a picture. I do know what you are talking about. 
> But I am also considering things like having column alignment under the 
> meaning of "pretty".
> 
> I (also) have columns not lined up in the "raw report" as produced by 
> gnucash. But I have deep nesting (in some of my boos) and the nesting is not 
> the same for all parts of income or expenses. So I expect to be exporting the 
> raw report and then editing outside of gnucash and I fix the column alignment 
> then. This is less of a burden to me because I am going to have to edit the 
> reports anyway. Because:
> 
> 1) As treasurer I will need levels of detail to determine things like "do I 
> need to fill out a 1099-MISC for this intern when (is their PAY > $600; what 
> they get for mileage reimbursement isn't "pay"). All the board will want to 
> see then I present at the meeting is "total amount for all interns". So I 
> will need both "full detail" and "detail at the level a board would want from 
> conceptually the report.
> 
> 2) I will be adding annotation to the report handed out to the board (or for 
> the annual report to the public). In other words, flag anything unusual and 
> explain in a footnote. Thus an expense item zero when something would be 
> expected there the annotation might be "vendor did not send us the invoice 
> for printing and mailing the annual meeting notices until after the end of 
> the quarter".
> 
> 3) Related to the above example , I want to SELECTIVELY show or not show zero 
> amounts.
> 
> BUT --- your problem with a fixed text not being translated is a "bug" and 
> should be brought to the attention of whoever is handling "French 
> translation". However, to be fair (to do the user's part) instead of JUST 
> reporting this by itself look at all of the reports to see if there aren't 
> other fixed text lines that were forgotten in the "French" version. I did 
> this for a living (designed/wrote/tested software). When we budgeted for a 
> project, that included a bucket for USER time.
> 
> This is why I, a retired pro with decades in the cypher mines (and doing 
> :financial software to boot) am NOT helping with development. I am not going 
> to volunteer to do the design/coding without user commitment to their part of 
> the process << both in the design phase and the testing phase >>
> 

What version of GnuCash are you using? That string should be translated in 
GnuCash 4.6 and later.

Regards,
John Ralls


_______________________________________________
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