The export to and the import from csv files works fine in Windows. Also when text in cells contain a LF as an "internal linebreak", because Windows recognizes CR/LF as end of line. But in Linux with only LF at the end of line comes the problem. There is no difference to the "cell-internal-linebreak". Such a spreadsheet is completely jumbled after re-importing. I think it would be nice to have an option to configure the linebreaks both in the export- and the import filter in future releases. If already now there would be an option to configure this, I would be glad to know where to find it. I didn't find yet... I tried Calligra Sheets. It has the option in the export filter but not in import so it's not an alternative. Thanks a lot!
Could you include a problematic example file? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 126820 [details] Screenshot Textimport
Sorry, first I should say, that the main reason for my posting of this report was more a feature request than a bug report. I thought the reason for my problem were the different linebreaks in Windows and Linux. They aren't, as I know now. I didn't recognize the problem on my old Windows machine yet. But while creating the testfile for this report, I tried it on both machines with the same result. My fault was the wrong setting of the text delimiter (single or double quotes). But it seems, as there is another problem. LO stores the last settings in the textimport window. That's nice and should remain this way. But the preview sometimes shows a wrong result. I created 2 almost identical csv-files. One with single quotes as text delimiter, one with double quotes. Field delimiter of both is semicolon. Content of the file "text_delimiter_double_quote.csv": "CellA1_line1[LF]CellA1_line2";CellB1[LF] CellA2;CellB2[LF] The other file similar, but with single quotes. I opened both alternating. For example with the former setting to single quotes I opened the file with the double quotes. The preview in the textimport window was wrong. It showed the decided import but the cell A1 became broken. See the attached screenshot. Now as I know this, I can work around it by clicking any setting so the preview shows what I'll get. Anyway - my real problem is, that a certain program I use makes csv-outputs with not correct text delimiters. In this case, I think, a new option of setting the various linebreaks could be helpful.
Which LibreOffice version are you using?
On the Linux machine (Mint 17.3 64bit): LO 5.1.5.2 On the Windows machine (W7pro 32bit): LO 4.1.4.2 Also LO 4 shows the same behavior regarding the preview as descibed.
Please, attach your test file. Best regards. JBF
Created attachment 127007 [details] Test File 1
Created attachment 127008 [details] Test File 2
I think there is no problem with linebreak. You only have to pay attention to your choice of text separator. If you choose the appropriate one, import is correct. What is your workflow with your csv files? Do you have the ability to check the text delimiter for each file? Instead of changing LO, maybe it is easier to make a pre-processor script which changes the text delimiter in each csv file. Best regards. JBF
Dear Bug Submitter, 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-20170131
Dear Bug Submitter, 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-20170328