Created attachment 129994 [details] sample csv file The cvs document in the attachement is being imported incorrectly into the Calc. Consider line 44, row F: value 2544 is imported instead of 2.544 line 68, row H: value 99963 is imported instead of 99.963 line 68, row O: value 128998 is imported instead of 128.998 and so on.
Can not reproduce. All cells mentioned are correctly imported from the CSV with Semicolon separators. On Windows 8.1 Ent 64-bit en-US with Version: 5.2.3.3 (x64) Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf CPU Threads: 8; OS Version: Windows 6.29; UI Render: default; Locale: en-US (en_US); Calc: group Please verify that you have configured the Text Import dialog "Separator Options" to _only_ use Semicolon as the field separator.
Created attachment 129997 [details] CSV impot dialog
Created attachment 129998 [details] CSV import issues As you can see, the marked numbers have been imported without decimal commas. In the original csv file, hovewer, there are point delimiters.
Again can not confirm on Windows 10 Pro 64-bit en-US with Version: 5.2.4.1 (x64) Build ID: 9b50003582f07ac674d6451e411e9b77cccd2b22 CPU Threads: 8; OS Version: Windows 6.19; UI Render: default; Locale: en-US (en_US); Calc: group Please provide a clip of the Text Import dialog and settings used (it pops-up when opening the .CSV file), as can be seen in attached clip--the Text import is correct with utf-8 and en-US import with Semicolon delimiter selected. Need to know the local and language in use.
Created attachment 130006 [details] text import dialog for sample csv - utf-8, en-US, ";" separator
That the strange thing because in the "Import dialog" the table seems to be correct. But in the spreadsheet, some values are wrong. I did one more test and replaced all the '.' in the original csv with ',' - and it seems to work afterwards. So it looks like that the import module does things wrongly only with point decimal delimiters. I'm using German locale with german Windows 10 64 bit.
Suspect then that the MS Windows OS local setting is interfering with the CSV text import. You can suppress from Tools -> Options -> Language Settings: "Ignore system input language" in the Enhanced section. The import dialog should then respond correctly to settings on the panel. Of course restore default once you've imported the CSV. Give that a try and let us know if you get a clean import. And if that resolves the issue, logic/UI for Text Import dialog might need a tweek to offer the ability to suppress system local during import.
Unfortunately, neither "Ignore system input language" option nor unchecking "Decimal separatoy key" resolved the issue. But setting "Default locale" to English-UK seems to did the trick. So I'm wondering why the csv import dialog is not propagating the selected locale to the spreadsheet context... Because in the dialog everything looks ok...
Just to be sure we have complete OS details, please post text from the default Help -> About LibreOffice dialog and the Summary content from the msinfo32.exe diagnostic.
Version: 5.2.3.3 Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Locale: de-DE (de_DE); Calc: group Betriebsystemname Microsoft Windows 10 Home Version 10.0.14393 Build 14393
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170628
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170727
Sintegrial provided the info in comment 10 that Stuart requested, so reopening as UNCONFIRMED.
Created attachment 135672 [details] CSV with decimal separators corrected to commas In the F column the values are numbers, but with incorrect decimal separator for German locale. They should be using commas. Now as they are detected to be "Number" format, the import treats 2.544 as two thousand five hundred and forty four due to German locale using period as the thousands separator.
(In reply to Buovjaga from comment #14) > Created attachment 135672 [details] > CSV with decimal separators corrected to commas > > In the F column the values are numbers, but with incorrect decimal separator > for German locale. They should be using commas. Now as they are detected to > be "Number" format, the import treats 2.544 as two thousand five hundred and > forty four due to German locale using period as the thousands separator. In another report, I bumped into a more elegant way that does not require changing the .csv: https://wiki.documentfoundation.org/Faq/Calc/136/fr So in the import dialog, change the columns with the period decimal to type "English (US)". Note that Shift and Ctrl keys work when selecting the columns in the dialog.