Fixture
name;price;sku
Blue Shirt;19.99;SKU-001
Red Shirt;24.50;SKU-002What this case isolates
Every non-empty row contains three fields and the same semicolon separator. There are no broken quotes, duplicate headers, or width mismatches. That means the parser can identify the table without deciding what any value is supposed to mean.
The delimiter tool should identify semicolon-separated structure.
The header and both data rows should all parse to three columns.
The tool can re-serialize the same fields with commas and UTF-8 output.
The corrected copy should parse as a comma-separated three-column CSV.
Why the repair is safe
The operation changes separators between already identified fields. It does not infer a price, SKU, product name, or missing value. Proper CSV serialization also quotes a field automatically if it contains a comma, so this is safer than raw Find & Replace.
What would make the same job unsafe?
If one row had a different width or an unclosed quoted field, the parser could no longer prove all field boundaries. CSVFixLab would then block repair instead of treating the delimiter as the only problem.
Lab fixture maintained with the CSVFixLab MVP test suite.