-
Notifications
You must be signed in to change notification settings - Fork 37
QIF files whith !Type:Invst not working #3
Comments
Hm, that's entirely possible. I'll take a look. |
One of the problems is that the Date value is tacked onto the end of the transaction start line. I'm not tackling that part right now - you can fix that by changing:
to read instead:
and likewise, changing:
to read instead:
The rest of the file parses correctly with a small change, but it spits out the wrong OFX format (it produces a bank statement instead of an investment statement). I'll look at fixing that now. |
See commit 176d035. The parse exception no longer occurs, but I haven't added investment support yet, so the document is instead returned as a bank statement. That may be enough in some sense, but if not, you could add investment support yourself and send a pull request. I may get to it later or someone else may, too. |
I already fixed it. We made the same commit. =) |
Heh, okay. Update the issue! :) Looks like you have a lot of commits going in. If they're generally valuable and you want to make a pull request I'll look them over. Thanks. |
Everything's ok now. I'll make an review and send a pull request. Cheers! |
I reopened the bug since as far as I know neither our fixofx nor your fork are yet generating correct OFX investment statements. Please correct me if I'm wrong. :) |
I tested many QIF files with !Type:Invst, but i always get this traceback:
Parse exception during 'QIF' conversion:
Expected '!Type:CCard' (at char 0), (line:1, col:1)
Here is one of the files:
!Type:Invst
D6/11'06
T18,000.00
NShrsIn
YCesp
I18
Q1,000
^
D22/11'06
T13,000.00
NShrsOut
YCesp
I26
Q500
LRendimento de investimento:Ganhos de capital
^
The text was updated successfully, but these errors were encountered: