On 2 October 2012 07:40, thierry <[email protected]> wrote: > > > On Monday, October 1, 2012 8:24:29 AM UTC+2, Russell Adams wrote: >> >> >> On Sun, Sep 30, 2012 at 10:29:17PM -0700, Zack Williams wrote: >> > On Sun, Sep 30, 2012 at 12:31 PM, thierry <[email protected]> wrote: >> > The only downside compared to any of the other CSV programs is that >> > it's not interactive, and you have to write the mapping tables as a >> > ruby array. >> >> Not to beat a dead horse further, but CSV2Ledger (my perl variant) >> does the same thing. Dynamic renaming based on payee, account >> matching, even file matching using a YAML format. > > > I was too using a personal perl script, doing the mapping from a table. But > I tried the 'i' of icsv2ledger, and felt in love with this 'i'. On contrary, > rubycsv and CSV2ledger does not (yet?) implement this 'interactiveness'. > Also CSV2ledger is not unicode compliant, and I am not living in an ASCII > world :-).
It was the interactiveness that was the key feature for me as well. I came from using MS Money, and so was used to it automatically suggesting payees and accounts from the string supplied by the bank, so I wanted something similar when I processed my download from the bank.
