To reproduce: --- 1. Create a new spreadsheet 2. Make A1 a multiline cell with hard breaks (eg: 'abc<ctrl-enter>def') 3. Make A2 a single line cell (eg: 'ghi') 4. Copy A1 and A2 together 5. Paste contents across to an external text-only editor (like Geany) Contents for the above example will paste across as: "abc Def" ghi Note that the multiline cell has been wrapped in double-quotes. If the multiline cell contents contain a double quote, it ends up escaping by doubling up the quotes. ie: abc"def becomes abc""def on copy. What should happen (in my opinion) --- All text should paste across exactly as if the contents were copied directly, with no wrapping quotes (or double-up escaping). ie: the example shoudl paste across as: abc Def ghi Previous versions of Calc did precisely this. Excel also does this. In case this multiline-quote-enclosing/escaping was introduced as a feature to try and make it clear in the pure-text paste where individual cells/rows are delimited... this does not work and causes more confusion than without it. Consider the case where a single line cell has a leading double quote in it. This double quote is NOT escaped, so you cannot parse the pasted pure text contents to determine with certainty what the cell delimiting was. It should paste across as pure text. No wrapping quotes or escapes. If there is a convincing argument for some other pasting scheme, it should at least be a configurable option. This issue exists in 3.5.4, as well as the master as of Nov 21, 2011 (1c31558e9739ea6cf0cfa58d5cbda8d808eb0527) - thanks to shm_get for confirming this.
reproduced on master
I incorrectly stated in the initial report that Excel does not do this... it does. I just checked Excel 2003 and Excel 2007. They both do the quote-wrapping on multiline text paste. I now expect that consistency with Excel was why this was added to LO at some point. I still think it is not the right way to do it, though for the same inconsistency arguments initially stated.
To clarify why it is self-inconsistent and ambiguous, the following cell contents: A1 -- "abc def" B1 -- "ghi C1 -- jkl" pastes across as: "abc Def" "ghi jkl" but this is also EXACTLY how the cell contents below paste across: A1 -- "abc def" B1 -- "ghi jkl" <C1 empty> ie: no automation can reliably reverse this to spreadsheet cell contents. It should either be perfectly reversible, or consistently simple. I think the old OpenOffice way was the latter, and preferable. Or make it a configurable option how text pasting operations work. But what would you label the inconsistent/irreversible quoting scheme as?
If a cell text containing "'s is not enclosed in quotes, then that is a bug.
As you mention this has been most likely added for interoperability reasons so this can't be a regression.
** 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 on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) Thank you for your help! -- The LibreOffice QA Team
** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
(Note: I'm making this comment because this is just another of the thousands of forgotten btanb) I don't think this is a bug, it's rather a feature that it's wanted or not. The pasted text is enclosed in double quotes if it contains a new line. It's the way Calc makes the text looks like 'it starts here' and 'it ends here'. As for why the text can't be reconstructed back to spreadsheet uniquely, as in the example where two different cell contents paste as two equal texts, well text lines are not cells. If that feature would be needed, then every extraneous character (newline, tab, etc.) should be escaped when pasting as text e.g. with \n \t etc. and then unscaped when pasting text back into Calc. That could be a feature request, but certainly this is not a bug. Basically my opinion is that wanting that pasting cells as text should be always reversible is more complex than it seems, due to the implications of my earlier statement: text lines are not cells. Changing Calc to paste cell content being reversible might make the pasted text unusable for most uses imho. Personally I want Calc to paste newlines as newlines in my text editor; getting rid of the double quotes is an unwanted side-effect but I understand the need of r them. A few times I wanted Calc to escape those special chars, but nothing that a little editing or formula mangling can't do. If anyone with experience in these things shares my view, change status to resolved.
Yep, based on the previous comments, we should close.