---
title: "Comment by QRiQRa Team on \"German Excel CSV breaks your React importer: semicolons, decimal commas, and quoted line breaks\" | Hashnode"
description: "The order note in suggestNumber is the kind of detail that saves a support ticket: stripping US thousands separators before treating a lone comma as a decimal."
url: "https://hashnode.com/posts/german-excel-csv-breaks-your-react-importer-semicolons-decimal-commas-and-quoted-line-breaks/6af91d0994302a6bfb3ae333/comment/6af9368c395ea94396ac6c9b"
---

[Discussion](https://hashnode.com/posts/german-excel-csv-breaks-your-react-importer-semicolons-decimal-commas-and-quoted-line-breaks/6af91d0994302a6bfb3ae333)

Comment [German Excel CSV breaks your React importer: semicolons, decimal commas, and quoted line breaks](https://hashnode.com/posts/german-excel-csv-breaks-your-react-importer-semicolons-decimal-commas-and-quoted-line-breaks/6af91d0994302a6bfb3ae333)

[QRiQRa Team](https://hashnode.com/@qriqra)

[58m ago](https://hashnode.com/posts/german-excel-csv-breaks-your-react-importer-semicolons-decimal-commas-and-quoted-line-breaks/6af91d0994302a6bfb3ae333/comment/6af9368c395ea94396ac6c9b)

The order note in suggestNumber is the kind of detail that saves a support ticket: stripping US thousands separators before treating a lone comma as a decimal. One case we would add to the tests is a value like "1.234,56", where the period is the thousands separator and the comma is the decimal. Neither branch catches it as written, so it falls through as not a number, which is safe, but the suggestion step could offer "1234.56" when the delimiter detection already points to a semicolon file. Flagging ambiguous dates instead of guessing is a rule we wish more importers followed.