Created attachment 65544 [details] An example TSV file showing the issue with exponential-formatted numbers. Problem description: Selection of the detect special numbers seems to work backwards from documentation (http://help.libreoffice.org/Common/Text_Import#Detect_special_numbers) and (at least my) expectations. Steps to reproduce: 1. Open temp.tsv (attached) using scalc 2. Select (or don't select) "Detect special numbers" on import. Current behavior: "Detect special numbers" selected -> 3E is left as text "Detect special numbers" unselected -> 3E is converted to 3 Expected behavior: The exact opposite behavior (but with the option still left unselected by default...I believe this matches Excel's behavior, not that Excel is the touchstone to meet :) ). Platform (if different from the browser): CentOS 5.6, x86_64 Other notes: Interestingly, the documentation seems to be incorrect either way about not interpreting any exponential number...you'll notice that the 2nd item in temp.tsv (3E2) is interpreted as a number regardless of this option's value. However, Excel does the same thing, so I actually prefer it that way for interoperability purposes. In any event, this software is truly great, thanks! And, as always, I apologize in advance if this is something braindead that I'm not understanding properly. Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Confirmed on Version 3.6.2.2 (Build ID: 360m1(Build:2)) on Kubuntu 12.10
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) Thank you for your help! -- The LibreOffice QA Team
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
I can't confirm that with Version: 6.2.0.0.alpha0+ Build-ID: 62cd86977ca41677c56fb2d1f97bb1c5cbdbd416 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded With special numbers activated Calc imports: 3E 3,00E+02 4F Without special numbers activated Calc imports: 3E 300 4F This matches what the help says: 'When this option is enabled, Calc will automatically detect all number formats, including special number formats such as dates, time, and scientific notation.' https://help.libreoffice.org/6.1/en-US/text/shared/00/00000208.html?&DbPAR=CALC&System=UNIX I close this bug as RESOLVED WORKSFORME. Please reopen as NEW if the problem still occurs in your installation. Please test with the newest possible LibreOffice version for your OS.