-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ethy H. Brito schrieb: > On Thu, 25 Jan 2007 10:00:54 -0500 > Derek Atkins <[EMAIL PROTECTED]> wrote: > >>>> Are you offering to code this and send in a patch? :-D >>>> >>> yes I am. In fact I am working on the idea reading the code to catch your >>> programing style and propose something that fits in. >> Cool! I look forward to your patch. :) > > Here go my thoughts: > > I think the "problem" has to be dealed at check number increment/decrement. > If this is done correctly, the import matching do not have to be smart > (a simple str[n]cmp will do the job as it is today) > Please correct me. I have no deep knowledge of GC innards.
As I already said: Are you talking about the matching rules of imported and/or downloaded transactions? In case this concerns OFX or HBCI (whereas QIF is different), do I understand correctly that you're talking about the function split_find_match() in src/import-export/import-backend.c, especially (svn-trunk) lines 659ff? In particular, as you've mentioned OFX here, http://lists.gnucash.org/pipermail/gnucash-user/2007-January/019062.html I would strongly suggest to simply add a numerical comparison (in additiona to the string comparison) in import-backend.c, as this achieves your original goal of "good scores to imported transactions" obviously much much easier. Thanks for any proposals, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRbo3s2XAi+BfhivFAQK37gP+Pjk9qbNrVzoXq+2W2mS/IqO7JTYKa7Tu iZgP89crei81mMyrs4KhbjobtcUPcANOYSz9Td2bkDyjVmM0Miqc1+gxKaHCxyEd FSVqlZet3WeO03/7+8eDRqFl12rG7k5ioBtK0p/j0+jd4+42OCDmSlryelHjS6HG zAmLwF+BiRM= =GZI8 -----END PGP SIGNATURE----- _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
