The default hard-coded behaviour does not work for all CSV parsers.
I've worked around the issue by adding support for using the configured escape character instead of doubled-up doublequotes ""
I've added a pull request for this feature: #41
In case you're curious, we're trying to generate CSVs for ingestion into a Vertica database and "" needs to be \"