Description: vales in the csv file: -26.398,-54.418 -26.385,-54.464 -26.329,-54.623 values in the Calc cell -26398,-54418 -26385,-54464 -26329,-54623 Steps to Reproduce: Open a text csv file with de content: -26.398,-54.418 -26.385,-54.464 -26.329,-54.623 Actual Results: -26398,-54418 -26385,-54464 -26329,-54623 Expected Results: -26.398,-54.418 -26.385,-54.464 -26.329,-54.623 Reproducible: Always User Profile Reset: No Additional Info: The software should not have removed the decimal point.
Created attachment 166350 [details] A csv fole with coordinates
Created attachment 166358 [details] The CSV fields holding lat-long are correctly handled as signed decimal with Text Import dialog Can not confirm, user profile reset to default/first launch. Text Import... dialog set for with just 'Comma' Separator option Version: 7.0.1.2 (x64) Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Please retest from Safe mode, or with full profile reset.
If I'm not wrong, it's a matter of select in the 'Text import' box a language using a dot as decimal separator, so you can avoid selecting for every column the right column type 'US English'. In my case with Spanish, using 'English UK' works fine with many of the csv files having dot as decimal separator but the dates DD/MM/YY. I don't think this is a bug.
Dear Carlos Brys, 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
Dear Carlos Brys, 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-FollowUp