Reports, probably again

[Phil Longstaff]

Well, what the development team needs is a description of what the output should be.  If XML, what are the tags.  If CSV, what is the output like.

Phil



________________________________
From: Colin Scott <gnucash at double-bars.net>
To: yhg at highlandsoft.net; gnucash at double-bars.net; stepbystepfarm at mtdata.com; james.wilde at sunde-wilde.com
Cc: gnucash-user at gnucash.org
Sent: Monday, August 8, 2011 8:13:00 PM
Subject: Re: Reports, probably again


> Another alternative: output in XML, so that context (headings and 
> such) can be identified. Many XML tools exist for further parsing 
> and processing, and XSLT can directly produce reports from the XML, 
> for those with the programming skill or recurring production needs.

I'd be perfectly happy with that - though I suspect CSV would be easier for the team to do!

Colin
_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.