I've now made a hard-coded list of potential tags that are supported and
will be linked to in the general ledger spreadsheet. This list should
probably be in a configuration file of some sort eventually, rather than
hard coded.
Indeed, note that the hard-coding goes into two different scripts, and
thus the lists could easily get out of sync.
Change the column of Receipt and Invoice in the CSV file first, then the
generated ODS file must have the same change propagated, which requires
changes to the column numbers hard-coding in csv2ods.py.
Perhaps if/when this application is refactored these things shouldn't be
hard-coded in this way in the first place.
I developed this, and therefore have the full git commit history, in my
personal "Small-Hacks" repository, which can be cloned from:
git://gitorious.org/bkuhn/small-hacks.git
More details on that are available by visiting:
https://gitorious.org/bkuhn/small-hacks
The basic idea here is that given non-profit-test-data.ledger herein,
there should be a script that I could run, in this fashion:
$ general-ledger-report -b 2011/03/01 -e 2012/03/01 -f tests/non-profit-test-data.ledger
that would generate:
non-profit-test-data_chart-of-accounts.txt
non-profit-test-data_general-ledger.ods
Note that the ODS file currently has placeholders, as I haven't fully
figured out how to use the =hyperlink() function to make relative
hyperlinks.
Upon discussion with John Wiegley <johnw@newartisans.com> on #ledger on
irc.freenode.net, the following was indicated:
<johnw> bkuhn: as long as the GPL infection stays in contrib, I see no problem
with it
...
<bkuhn> ... I got the ... answer, which is "johnw will accept GPL'd stuff
in contrib/..., as long as it's careful to not cause GPL to cover
the main Ledger codebase that's not in contrib/..."
Therefore, the non-profit-audit-reports/ application will be licensed
GPLv3-or-later.
