Created attachment 141901 [details] Copy the table to a new Calc-file. Look for line break in third column. Open the attached database. There is a table with 3 fields. Last field contains linebreaks (LONGVARCHAR needed for this). Copy the table with right mouseclick. Paste the content of the table to a new opened Calc-document. Header of the table will be shown with gray background, content of the third column has no line breaks. Now drag the table from Base to the opened Calc-document and drop it there. Header of the table won't be formatted (because it isn't the same wizard working?). Switch the height of the rows. Content of the third column will show line breaks, which had been created with Shift + Enter or Ctrl + Enter. Remark: This is the only way to get line breaks from a whole table to Calc. There isn't any way to get it back from Calc to Base for a whole table, because the wizard wont transport the line breaks. Have tested all these with LO 6.0.3.2, OpenSUSE 64bit rpm Linux.
@Robert : did this ever work previously ? I don't recall being able to paste line-broken content from Calc to Base in previous versions (using excel sheet as db source), but I'll admit I don't usually line-broken content in db fields anyway.
When I do this : Copy the table with right mouseclick. Paste the content of the table to a new opened Calc-document. Header of the table will be shown with gray background, content of the third column has no line breaks. The data content gets pasted as all underlined, all struck-through - which is clearly incorrect (see screenshot). In addition, the line breaks are ignored. So confirming.
Tested with Version: 6.0.3.2 Build ID: 8f48d515416608e3a835360314dac7e47fd0b821 Threads CPU : 4; OS : Mac OS X 10.13.4; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Pretty certain that the copy table paste table behaviour didn't behave like that in previous versions of LO, so regression.
Reproduced in Version: 5.4.6.2 Build ID: 4014ce260a04f1026ba855d3b8d91541c224eab8 Threads CPU : 4; OS : Mac OS X 10.13.4; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Reproduced with Version: 5.3.1.2 Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 Threads CPU : 4; Version de l'OS :Mac OS X 10.13.4; UI Render : par défaut; Moteur de mise en page : nouveau; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Created attachment 141945 [details] Screenshot of paste to Calc via context menu in Base
Reproduced in Version: 5.2.7.2 Build ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10 Threads CPU : 4; Version de l'OS :Mac OS X 10.13.4; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Also reproduced with Version: 4.4.5.2 Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Locale : fr_FR.UTF-8
And reproduced with LO4162 - looks like this was there from early on, possibly even in the initial release, therefore no regression ?
Same behavior with LO 3.6.7.2. Seems to be inherited from OOo. Sometimes I don't get content all underlined and struck-through. But this bug is about line-break. Interesting: Import to Writer shows the line break ...
(In reply to robert from comment #11) > Sometimes I don't get content all underlined and struck-through. But this > bug is about line-break. Content will be shown without struck-through if I create a query and copy and paste the query to Calc ... Seems there is something saved for the table which destroys the textformat. But let us first fix the bug with the line breaks.
Can confirm the behavior. Copy/Paste (context menu) of a Base table to Calc makes multi-line text entries single line, whereas Drag & Drop keeps the line breaks. LO 6.0.3.2, win10 x64, de-de, Base setting "extended database setting" "Text lines with CR+LF" off But more important: Re-Import of the table from Calc to Base works in neither way - not via copy/paste nor drag & drop (like Robert stated before). Any workaround for this direction?
On pc Debian x86-64 with master sources updated today, I could reproduce this. Remark: in copy-paste right click case, the content is not grayed but underlined and struck-through
If someone knows where to begin to investigate. I don't know what part of code which deals with copy paste.
I will set this one to component "LibreOffice", because it is a bug with copying from one component to another (Base to Calc and back). Hope someone will see this and gives a a hint, which part of code it could be ...
Dear robert, 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
Buggy behaviour is still the same in LO 6.2.4.2 on OpenSUSE 15 64bit rpm Linux
Dear Robert Großkopf, 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://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
Bug is still the same with OpenSUSE 15.2, 64bit rpm Linux and LO 7.1.4.2
*** Bug 138114 has been marked as a duplicate of this bug. ***