https://bugs.kde.org/show_bug.cgi?id=339192
--- Comment #10 from geo...@wildturkeyranch.net --- (In reply to Jack from comment #9) > OFX is plain text, so emacs or vim or nano will work just fine. Some OFX > software does not include any white space, making it very hard to read, but > adding white space should not make any difference. There is no need for an > OFX specific editor, unless you want it to actually help parse it for > correctness and break it into human digestible pieces. (I don't know of one > of those, but it would be a neat idea.) > I have written a bit of tcl/tk code that a: verifys correct structure, b: adds white space and indention and c: puts the result in a window that you can search, edit, and save. The addition I think would be nice is to have a command that, given a mouse position, would select to the matching closing </...>. > The transaction ID should be a field within the OFX, so unless you > explicitly removed something, it would still be there. However, if there is > no actual transaction ID included, then it will re-import every time, since > it can't match by ID, and the previous transaction will already have been > matched. I think you miss understand what I edited here. I edited the transaction in KMM. But then, the next down load produced the orgional un-edited transactions in KMM. To me this means that the KMM edit lost the transaction ID so it thought the new transaction was not same as the prior one. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
