Description: Fixed width data delimited by commas, for example: "ABCDEF: ",201 ,200 ,0 ,"XX ",224 ,"12345XYZ ",99 The quotation marks, which are part of the data, are removed by the import process. Steps to Reproduce: Using the example data provided: 1.menu: edit/paste special/paste special/use text import dialog 2.select "fixed width" 3.place a marker before and after each comma 4.click OK Actual Results: The quotation marks, which are part of the data, are removed by the import process. Expected Results: The data is fixed width. The data between the delimiters must not be modified. Referring to the example data: Column A should contain "ABCDEF: " Column E should contain "XX " The quotation marks are part of the data and should appear in the cell. Reproducible: Always User Profile Reset: No Additional Info: This also happens in version 7.4. I updated to 7.6 and the defect exists in both versions. ------- Version: 7.4.4.2 / LibreOffice Community Build ID: 85569322deea74ec9134968a29af2df5663baa21 CPU threads: 2; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded ------- Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 2; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded ------- Selecting column type "Standard" or Text" during import makes no difference. Also, switching from "Fixed width" to "Separated by" and setting "String delimiter" to nothing then switching back to "Fixed width" for the rest of the dialog makes no difference.
While I can arrive to the desired result using the "Separated by" alternative, I guess that's not the point of the report. I'm not sure whether there is some set of options that would achieve the desired result using "Fixed width". Perhaps some of the grayed out options should rather be available for the "Fixed width" alternative too? Setting as NEW.
Dear Tom Daly, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug