I have entered this as a bug against ledger-mode.  I should be able to
fix it this weekend.

On Tue, Jun 10, 2014 at 11:16 PM, Hans Erik van Elburg
<[email protected]> wrote:
> Here we go:
> - using TAB (align) on a reckon generated posting, eats almost the whole
> posting, this seems to be caused by literal tab characters in the generated
> file
> - i instructed reckon to use comma format, but the generated output contains
> decimal dots again which is incompatible with the euro format in my ledger
> files so i had to convert them back by hand
>
> Used command:
> reckon --contains-header --comma-separates-cents --currency '€' --account
> Bezit:Betaalrekening:XXXXXXX -f XXXXXXX.csv -l ../ledger.ledger -o
> XXX_output.dat
>
> This generated posting:
> 2014/03/05    KN: 300031560; YYYYYYYYY; 798051; IC; Af; Incasso; ZAAILING
> WEBWINKELS 300038898 300031560 VOF ZAAILING?LEIDEN
>     Uitgaven:Boodschappen:Eten:GV                    €39,67
>     Bezit:Betaalrekening:XXXXXXXX                    -€39,67
>
> is destroyed by ledger-mode after giving a <TAB> it becomes:
> 2014/03€39,6-€39,67
>
> Ledger-mode command "Clean-up buffer" destroys the whole file ;-)
>
> I had to manually edit all postings to get rid of this. Of course once you
> found out it is the literal tab characters one could easily automate this.
> But still, it is inconvenient.
>
> One could of course also say this is a quirk in ledger-mode, as ledger just
> normally processes these files.
>
> BR,
> Hans Erik
>
> Op woensdag 11 juni 2014 02:35:57 UTC+2 schreef Craig Earls:
>>
>> I am curious what was not "ledger-mode compliant" about your file.  If
>> there is something the ledger will work with and ledger-mode won't
>> then I have more work to do.
>>
>> On Tue, Jun 10, 2014 at 2:14 PM, Hans Erik van Elburg
>> <[email protected]> wrote:
>> >
>> > I tried "reckon", but the learming promiss did not realize at all. The
>> > automatic recognition of columns did, but then I had to manually tell
>> > reckon
>> > how to post all transactions. This caused a lot of work (no
>> > autocompletion
>> > like in emacs). After this I ended up with a file that was not emacs
>> > ledger-mode compliant. Had  to re-edit all transactions in emacs again.
>> > So I
>> > think the whole process did not really save me time at all, on the
>> > contrary.
>> >
>> > The "ledger convert" caused less trouble, the extra configuration to
>> > tell it
>> > what columns to convert is a one time treshold only.
>> >
>> > I tend to only use these conversion mechanisms when there is a mismatch
>> > that
>> > I can not otherwise pin down.
>> >
>> > BR,
>> > Hans Erik
>> >
>> > Op dinsdag 10 juni 2014 11:53:26 UTC+2 schreef Edwin:
>> >>
>> >> On Tue, 10 Jun 2014 11:31:14 +0200, Stefano Zacchiroli wrote:
>> >> > On Fri, May 30, 2014 at 09:54:39AM +0200, Jostein Berntsen wrote:
>> >> > > I like to use reckon:
>> >> >
>> >> > Has anyone here used both reckon and icsv2ledger, and fancy posting a
>> >> > brief comparison of the two?
>> >> >
>> >> > I've just integrated icsv2ledger in my accounting work-flow. I've
>> >> > managed to make it do what I want, but I've also found it a bit rough
>> >> > around the edges --- I can elaborate more if people on this list are
>> >> > interested.
>> >> >
>> >> > If others have found reckon to be more flexible than icsv2ledger,
>> >> > I'll
>> >> > be happy to reconsider my tool choice.
>> >>
>> >> It has been some time since I used icsv2ledger, so this might be
>> >> slightly out of date. The main differences between the two are:
>> >>
>> >> 1) Reckon's scope is wider in that you can pass it your old ledger
>> >> files
>> >> and it
>> >> will "learn" from that. It will try to directly match payments
>> >> in the csv file to accounts you in your ledger file.
>> >>
>> >> 2) Reckon tries to automagically read your csv file, so you have to
>> >> specify less when you want to convert the csv file. (If it doesn't
>> >> correctly detect your csv format then feel free to file a bug report
>> >> for
>> >> Reckon).
>> >>
>> >> Cheers,
>> >>
>> >> Edwin
>> >>
>> >> >
>> >> > TIA,
>> >> > Cheers.
>> >> > --
>> >> > Stefano Zacchiroli  . . . . . . .  [email protected] . . . . o . . . o
>> >> > . o
>> >> > Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . .
>> >> > o o
>> >> > Former Debian Project Leader  . . @zack on identi.ca . . o o o . . .
>> >> > o .
>> >> > « the first rule of tautology club is the first rule of tautology
>> >> > club »
>> >> >
>> >> > --
>> >> >
>> >> > ---
>> >> > 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.
>> >> >
>> >> >
>> >> --
>> >
>> > --
>> >
>> > ---
>> > 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.
>>
>>
>>
>> --
>> Craig, Corona De Tucson, AZ
>> enderw88.wordpress.com
>
> --
>
> ---
> 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.



-- 
Craig, Corona De Tucson, AZ
enderw88.wordpress.com

-- 

--- 
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.

Reply via email to