https://bugs.kde.org/show_bug.cgi?id=330737
--- Comment #11 from allan <agande...@gmail.com> --- (In reply to Jack from comment #10) > When you say "temporarily substitute" I'm not sure if you mean just for this > export, or some shorter time. If the field separator exists within a field, > I would either quote the entire field or escape that character. As a user, > I would not be happy if the application changed the separator I requested. An interesting point. Firstly, would you as an informed user select a field separator that is bound to clash with a category splitter? Whilst you may not be intending to import the exported file back into KMM, never-the-less, those colons are going to split a complex category into separate fields in the export file. Is that desirable? I wouldn't have thought so. The use of the expression "temporarily substitute" is probably misleading. With my blinkers on, and while testing by importing into KMM the exported file, the substituted colons would be reinserted during import. To that extent, the '# ' separators are temporary. However, they still remain in the exported file, so in that respect, they are not temporary. I have followed the csv importer, in giving a choice of four separators ( ',' - '; ' - ':' - tab). Perhaps the choice of the potentially disruptive ':' should not be given? Or, more simply, for me, instead give a dire warning of the risk in their use? -- 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
