The sample provided on bug report 779774 is here: 06/01/2026,"Descri\ption 1\","-123.34","2282.45" 06/01/2026,"Description 2\","-234.45","2048.00" 06/02/2026,"Description 3","-943.00","3225.45"
I then noted that escaping the escape has problems: 06/01/2026,"Descri\ption 1\\","-123.34","2282.45" 06/01/2026,"Description 2\\","-234.45","2048.00" 06/02/2026,"Description 3","-943.00","3225.45" The above correctly has the backslashes, but the parsing is still not correct. The backslash appears to be a completely separate issue from the double quote issue that I've had for years, but the provided data, the BOA backslash is before a double quote. Backslash: https://github.com/Gnucash/gnucash/blob/f3c053fbee8c290d0fd111b125a4a52b03de862e/gnucash/import-export/csv-imp/gnc-tokenizer-csv.cpp#L51 Double Quote: https://github.com/Gnucash/gnucash/blob/f3c053fbee8c290d0fd111b125a4a52b03de862e/gnucash/import-export/csv-imp/gnc-tokenizer-csv.cpp#L104 See comment 4 to bug 799744, authored by John Ralls. > On 06/07/2026 2:18 PM PDT David Cousens <[email protected]> wrote: > > > Thanks John, > > I haven't done any testing on it. Then that seems to imply that BoA is > using the backslash in some context in which the parser is unable to > interpret it. I think earlier in the thread Tom mentioned something > about it being used at the end of a description field rather than as an > escaping of the comma (or other character) being used as the field > terminator. > Tom can you post a line or two from the file where it is giving the > problem so we can see the context (modify any identifying data as > necessary preserving the context). > > David > _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
