Created attachment 87106 [details] Three files inside - *.odt, first saved and second saved *.csv Open the attached *.odt-file. Save this file as *.csv. You could see in the attached file, how it works: Puts " around all text - also the decimal-separated values - with a comma. Separates all with the comma. Load this file again in LO. Save it again. All " around the text has been gone. The fields are separated with a tabulator. I expect LO would handle a file-saving the same way and hasn't to to with the number of versions of a file I will save.
I'm rather humble facing the "CSV misteries" : - the name "CSV" stands for Comma Separated Values, and nobody is surprised to find a field separator like Tab or Semicolon, - for years I experienced (with Works, Excel, OOo, etc.) a "trial and error" policy (between dropping the data icon onto the program icon ; loading CSV when allowed ; importing when provided ; etc.) : it depends on the language of the system, the language of the text processor, and... the captain age. - On Lib0, I find a dialog box to parameterize the CSV input and a other dialog box to parameterize the CSV output (tick the "edit filter parameter" box at the bottom of the "save under" dialog), this suffices to my happiness.
Not reproducible for me with version 4.1.4.0.0+ under Linux / Ubuntu 64 bits. Did you try with the current stable version ? Best regards. JBF
(In reply to comment #2) > Not reproducible for me with version 4.1.4.0.0+ under Linux / Ubuntu 64 bits. > > Did you try with the current stable version ? I have tried it with LO 4.1.1.2. Have now tested it with LO 4.1.3.2 - the same behavior. Fist saved with "" around the text and a comma as separator, second with a tabulator as separator and nothing around the text. Can't reproduce it with 4.2.0.0.beta1. If it isn't reproducable with 4.1.4 for you let us hope the bug has gone - but what has been changed? Let us wait for the first 4.1.4-Version available for me - don't know where to get one now for Linux-64bit-rpm-systems. Regards Robert
As you said 4.2 wasn't showing the problem any longer marking as WFM. If it's still an issue with current 4.2 release please set to UNCONFIRMED again. Thanks!