I think it would be useful if Spreadsheet editor can keep the original text delimiters and separators of CSV documents. It is a related to this question: http://ask.libreoffice.org/en/question/23332/csv-files-lose-formatting-after-save/ People use CSV files to import/export records from different apps and hardware. These tools often do not prepared to handle different kind of formatting. I know it is possible with additional "Save As" steps but it is not user-friendly.
I agree that the default should be to keep the same field and text delimiters. If the user wants to change then it should be his/hers *option*, not a software decision.
*** Bug 71376 has been marked as a duplicate of this bug. ***
Files saved in this way become corrupted, so that is not just an 'enhancement'.
*** Bug 101173 has been marked as a duplicate of this bug. ***
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Yes, the issue persists to this day. Version: 6.0.5.2 Build-ID: 6.0.5-1 CPU-Threads: 4; BS: Linux 4.17; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group Steps to reproduce: 1. Create a file test.csv with the contents: foo;bar 2. Open the file in Calc, leaving the import settings untoched. 3. Write "baz" in A2, "quux" in B2. 4. Choose File | Save and confirm CSV format. Expected file contents: foo;bar baz;quux Actual file contents: foo,bar baz,quux
Dear oliver nadj, 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This is fixed. I can't reproduce the problem following the instructions in comment 6. I think it was fixed in LO 5.4 by the patch for #55236 which saves the formatting settings from the open dialog.
(In reply to aljosha.papsch from comment #6) > Yes, the issue persists to this day. > > Version: 6.0.5.2 > Build-ID: 6.0.5-1 > CPU-Threads: 4; BS: Linux 4.17; UI-Render: Standard; VCL: gtk3; > Gebietsschema: de-DE (de_DE.UTF-8); Calc: group > > Steps to reproduce: > > 1. Create a file test.csv with the contents: > > foo;bar > > 2. Open the file in Calc, leaving the import settings untoched. > 3. Write "baz" in A2, "quux" in B2. > 4. Choose File | Save and confirm CSV format. > > Expected file contents: > > foo;bar > baz;quux > > Actual file contents: > > foo,bar > baz,quux Still reproducible in Version: 7.1.4.0.0+ / LibreOffice Community Build ID: 06d5d625e1dc8489e51b962353ac423669e61fed CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Created attachment 171606 [details] Calc's 'Text Import' dialog with field separator setting for filtered import of CSV, and reused at export (In reply to Xisco Faulí from comment #9) > (In reply to aljosha.papsch from comment #6) > > Yes, the issue persists to this day. > > > > Version: 6.0.5.2 > > Build-ID: 6.0.5-1 > > CPU-Threads: 4; BS: Linux 4.17; UI-Render: Standard; VCL: gtk3; > > Gebietsschema: de-DE (de_DE.UTF-8); Calc: group > > > > Steps to reproduce: > > > > 1. Create a file test.csv with the contents: > > > > foo;bar > > > > 2. Open the file in Calc, leaving the import settings untoched. > > 3. Write "baz" in A2, "quux" in B2. > > 4. Choose File | Save and confirm CSV format. > > > > Expected file contents: > > > > foo;bar > > baz;quux > > > > Actual file contents: > > > > foo,bar > > baz,quux > > Still reproducible in > > Version: 7.1.4.0.0+ / LibreOffice Community > Build ID: 06d5d625e1dc8489e51b962353ac423669e61fed > CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded Xisco, please rethink. When I take the simple step of setting values (i.e. removing undesired separators) from the 'Text Import' dialog--the format is retained on export save back to .CSV It is an export filter action, not a native format, of a document that has been taken through import filters. Setting a format on import (here removing <Tab> & <Comma>), that is then maintained for the export, is a reasonable accomodation. And a requirement justifiable for reasonable workflows. CSV are not native formats, we don't "edit" CSV.
So: 1. Originally, this was a duplicate of bug 55236. This is resolved. 2. Since comment 6, new issue got discussed, with "leaving the import settings untoched" piece being the main culprit, and the user error being expecting that when you keep several separators enabled on import, the export will guess the correct one automatically. Closing this as a duplicate of the older bug; id needed, a UX problem arising from several separators used on import might be considered in a separate issue (one intrusive way could be, e.g., to have a warning on save when such settings are remembered). *** This bug has been marked as a duplicate of bug 55236 ***
*** This bug has been marked as a duplicate of bug 152336 ***