Thanks for the clarification. Is there any alternative solution then for the task I described in my first message?
I am importing my bank statements into ledger automatically and for about 90% of all entries, I can assign the correct ledger accounts automatically just by looking at the metadata imported from the bank statement. Sometimes there are rules like 70% to that account, 30% to that account, but that's about it. I wanted to export to XML format, write a little Ruby script that transforms the XML, and import the data into ledger again to write the textual format. The same I could do with a Python script that could read/write ledger files directly. The workaround I'll probably implement in a few days is writing a script that can write the subset of the XML format that I actually use back to the textual format. Any alternative solutions for implementing such logic? On Monday, March 14, 2016 at 12:40:25 AM UTC+1, John Wiegley wrote: > > >>>>> Ralf Ebert <[email protected] <javascript:>> writes: > > > I tried to use the Python module already, but it seems to have the same > > problem - from what I have seen in the documentation, examples and > sources, > > it can read an existing journal, but it doesn't seem to be possible to > > manipulate transactions and write an updated ledger file. Or do I miss > > something here? > > You've not missed anything. I think I simply didn't implement it for 3.x > because (a) it's complicated, and (b) I didn't think anyone would use it, > making it not worth the effort. Given that it took 5 years for anyone to > notice it wasn't there, that argues for (b). > > -- > John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F > http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
