https://bugs.kde.org/show_bug.cgi?id=330737
--- Comment #12 from allan <agande...@gmail.com> --- On 04/11/14 17:56, Jack wrote:> I'll reply to the bug later - I can't adequately get to BKO with my > tablet or with the laptop I'm using right now..... > i think our main difference is that you are thinking of this > specifically as a way to export some data from KMM, and I'm thinking of > it in the context of a general delimited file exporter. In general > terms of delimited files, I have no problem with using a delimiter that > might occur within one of the fields, because I expect that either the > field will be quoted (either ' or " - hopefully one of those is not > within the quoted field) or the delimiter within a field will be > escaped, usually with a backslash. Of course, in this specific instance, the Category value is not quoted and the colon is not escaped. > It's certainly a valid approach > for this exporter to restrict options to minimize the chance of clashes, > but I'd also for example allow the possibility of a # within a payee > name (especially if it originally got created during an import). > I think any approach here can be valid - just be constent and document > (for the user) what the restrictions are - principle of least surprise. > Jack I think the cleanest, safest, approach is to remove the potential source of problems and confusion, the colon as field delimiter. There will therefore be no filtering of # characters in any alpha field. I have now removed the colon option, and also the code dealing with its interception. This has now been tested and all looks good to me. I'll wait a while before committing, as I said earlier. -- 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
