Space after delimiter messes with quoting

[SimonCadge]

Space after delimiter messes with quoting

[SimonCadge]

Cool, ok. If I find time I'll look into contributing to csv-core.

[BurntSushi]

When parsing a CSV file which has a space following each comma

The behavior you see is occurring because you don't have CSV data. You only have something that looks like CSV. Spaces after commas with quoted values are invalid.

I'm on mobile, but I believe most other CSV parsers (including Python's) either will behave similarly or will error.

The trim option doesn't apply here because your CSV data is mangled long before the trim option comes into effect. You need to either fix your data to be valid CSV or do some kind of ad hoc post processing step.

[SimonCadge]

I was actually coming from Python's csv parser which has this functionality. That's why it caught me out.

https://docs.python.org/3/library/csv.html#csv.Dialect.skipinitialspace

[BurntSushi]

Yeah that's in the dialect configuration itself. I had forgotten about that. I'm open to adding an option to csv-core for it, and then exposing it in the csv API. The challenge will be differentiating it from the trim option which is really a different thing altogether. What you're after here is something that changes how CSV parsing works, where as trim is something that does not impact parsing and applies to the values after parsing has completed.

I don't know when or if I'll work on this personally.