CSV isn't really a standarized format, or actually it is ( RFC 4180 - Common Format and MIME Type for Comma-Separated Values (CSV) Files ), but it is a standard that nobody implements, so it isn't much valuable. We try to emulate "what Excel does" which is kind of the de-facto standard for CSV files. You can read a longer explanation along with the many pitfalls of CSV here: : Understanding CSV files. | FlexCel Studio for VCL and FireMonkey documentation
Now, I am not sure I understand why you want to enclose a field like "result name 1" in quotes, just because it has whitespace. From the standard:
Fields containing line breaks (CRLF), double quotes, and commas
should be enclosed in double-quotes. For example:
And that's what FlexCel does, but it does it automatically. If the field was named "result name 1" FlexCel would automatically add the quotes. But not for just whitespace.
Same, if you set a cell as "result name 1" (with quotes) FlexCel will enter exactly that in the field. (that is, the name with quotes). To do so, it must escape the quotes, and it does so byw writing """ instead of ".
The idea is that you shouldn't have to worry about the CSV escaping, FlexCel will take care of that. If you open the CSV file in Excel, it should have the same cell values as the original file had.
If you are trying to open the file in some other tool that requires quotes when there is whitespace, we can see to add an option for that. But such a tool wouldn't be able to open Excel-generated CSV files, as those don't quote whitespace.