Including question and answer text in the CSV output gives a syntactically dubious CSV file.
Questions and answers often include line breaks, which are included verbatim. Some software may handle it correctly, because the newlines are within quoted strings, but many tools do not, making it harder to process the files. It would be better if the newlines could be represented by escape sequences instead.
Current best work around is to skip question/answer text in reports for statistics processing. That is OK, so the issue can wait. (A warning to the user in the UI would be nice though.)
Including question and answer text in the CSV output gives a syntactically dubious CSV file. Questions and answers often include line breaks, which are included verbatim. Some software may handle it correctly, because the newlines are within quoted strings, but many tools do not, making it harder to process the files. It would be better if the newlines could be represented by escape sequences instead. Current best work around is to skip question/answer text in reports for statistics processing. That is OK, so the issue can wait. (A warning to the user in the UI would be nice though.)