https://bugs.kde.org/show_bug.cgi?id=339192
--- Comment #9 from Jack <ostrof...@users.sourceforge.net> --- 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.) 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. -- 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
