https://bugs.documentfoundation.org/show_bug.cgi?id=167321
--- Comment #22 from Mike Kaganski <[email protected]> --- (In reply to Dodo Ivanecky from comment #20) > No, it's irrelevant. Because switching the feature off is not the same as > fixing it. There is nothing in your description that proves it needs fixing. CSV is a "comma-separated values" loose file format. If you ask LibreOffice to auto-detect *field* separators, and give it the source like your > 0,235 > 0,3253 > 0,5121 then no amount of locale (neither set up in LibreOffice's Language and Locale settings, nor selected in the Text Import dialog) could ever help to distinguish the commas in the data between "decimal" and "field" separators. The RFC 4180 standard (https://www.rfc-editor.org/rfc/rfc4180) would tell that unmasked commas are indeed field separators - independently of the locale! And if someone would create a standard-compliant CSV for a locale with decimal comma, the CSV would look like > "0,235" > "0,3253" > "0,5121" So no, there doesn't look to be a problem in the current implementation - or you didn't explain how it should work to be better. -- You are receiving this mail because: You are on the CC list for the bug.
