Description: Libreoffice Calc gives a correct preview of CSV files even when the region setting for comma symbols is not matched by the CSV numbers contained within (in the locale and in the Libreoffice settings). After importing, the commas are lost if they do not match the one set in the locale or Libreoffice. Some history of the bug is here: https://askubuntu.com/questions/986169/commas-from-csv-only-partially-imported-in-libreoffice-calc Steps to Reproduce: 1.Save a CSV file with numbers containing commas that do not match the Libreoffice or locale settings for comma symbols (possibly: mix some text values in that column) 2. open the file with calc, look at the preview in the text import dialog 3. Look at the final results in Calc, commas are gone Actual Results: Commas are gone in Calc after text import Expected Results: Correct behavior should be: the preview in the text import dialog should reflect how the file is really going to be imported, based on libreoffice or locale settings. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Thank for reporting the bug, but your version of LO is EOL Upgrade to the latest version and try again. If your not agree you can reopen the bugreport
I reopened the bug. It still happens in Libreoffice 5.4.3.2.
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Bug 39829 covers also the preview aspect of this. For now, try this: in the preview window, click the column type (Standard) of the problematic column (I assume Coefficients) and set the Column type from the dropdown to US English. The problem you describe is probably due to the confusion of thousands separators. *** This bug has been marked as a duplicate of bug 39829 ***
(In reply to Buovjaga from comment #4) > Bug 39829 covers also the preview aspect of this. > > For now, try this: in the preview window, click the column type (Standard) > of the problematic column (I assume Coefficients) and set the Column type > from the dropdown to US English. > > The problem you describe is probably due to the confusion of thousands > separators. > > *** This bug has been marked as a duplicate of bug 39829 *** Apologies, I did the previous change accidentally in ninja mode, so no email notification was sent