Created attachment 86322 [details] Java source file Problem description: I copy and pasted a java source code to librewriter, but instead of complete code paste only a single statement got pasted. MS Office 2007 works well in this regard. tested on Windowx XP SP3 and ubuntu 12.04 LTS. Steps to reproduce: 1. Open attached java source file in text editor in read-only mode 2. Select all code from source file for copy operation using Ctrl+A and Ctrl+C. 3. Open LibreWriter and Press Ctrl+V to paste the copied source code. 4. You will see the bug then. Current behavior: Incomplete paste operation. Expected behavior: Complete paste operation Operating System: All Version: 4.1.1.2 release
Examination of Quiz.java shows that carriage-return separates lines. This could well be the trigger for the problem. I have not reproduced exactly "only a single statement gets pasted", but I can get the whole file joined together into one paragraph. Since the problem description says the problem is the same on Linux, it is strange that my bad result differs from the reporter's result. Ankur, can you confirm my understanding that you see a different result? When I save the "joined together" document as an .fodt, I see that the carriage returns are represented as "
". How to get the bad result: (*) Wine Notepad, running on wine, does not recognize the carriage returns in its own display, and the paste into Writer gives everything run together in one paragraph. How to get good results: (*) Writer menu option Insert > File produces good results. (*) emacs tells me that Quiz.java is a Mac file, and on input it converts carriage return to linefeed-only (the Linux convention); pasting into Writer works well. (*) gedit is less forthcoming about what it is doing, but the result is good. My LibreOffice is master commit 95e95e0, fetched 2013-09-19, and configured with: --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src HTH, Terry.
Created attachment 86361 [details] result of pasting into Writer in 3.4.2 on WinXP
Reproduced in 3.4.2 and 3.5.0 in WinXP 32 bit (therefore not a regression) In LibreDraw and Calc works correctly. Possible workaround: paste first into Draw, then select text, copy and paste now into Writer. IMHO this bug may result in problems with interoperability with MacOS users. There this ODh character is widely used.
Thank you, Sahsa. Your result matches the original problem description and is quite different from mine. It might help the programmer if you identify the program in which you did the copy operation. Mind you, I do not know that different programs would put different things on the clipboard. So far, we do not have a report from a Mac user. That is the other popular platform for LibreOffice. As the carriage-return as a line separator is the Mac convention, it would be surprising if LibreOffice on the Mac screws up. Pending that information, I am marking this as a Windows bug. Meanwhile, I think I shall ask the discuss list whether my observed "bad" behavior is in fact a bug. As ugly as the result is, it is not entirely unreasonable. Terry,
Used notepad and TotalCommander (pressed F3)
Hi Terry, Sorry firstly; I have the bug on Windows XP SP3 and getting a good result under ubuntu 12.04 LTS. As explained by you that Inserting a file from menu will give good result doesn't happens on WinXP (*) Writer menu option Insert > File produces bad results. I have used MS Notepad and Notepad++, but getting the same bad result in LibreWriter. Ankur,
Created attachment 93571 [details] Test case to simply demonstrate the problem This test file demonstrates that, in a paste operation, all characters following "CR not immediately followed by LF" are discarded until a CR/LF pair is seen. I observe this behaviour in the two versions I have tested: LO 4.1.1.2 and 4.2.0.4
Created attachment 93585 [details] Test Case with example results Clarifying my previous post, the problem shows up on Windows XP. I have checked on Linux and the behaviour is different. Specifically the line feeds are being interpreted as expected, but all carriage returns are embeded as "
" (as reported in Comment 1). I concurr with Comment 4 that this is a Windows bug, although the Linux behaviour is not what most would expect either.
** 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.4.2 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: 2015-05-02
I no longer have wine available, so cannot do the test which I reported in comment 2, but here is what I see with LibreOffice 4.4.2.2 running on Windows Vista: (*) Insert > Document brings in only the first line of Quiz.java. (*) Copy from emacs 24.3.1 and paste into LibreOffice gives good results. (*) Copy from Notepad Version 6.0 (Build 6002: Service Pack 2) gives one line, which I am retyping: import javax.microedition.midlet.*;","IBM"}; with the cursor after the ending semicolon. This is quite different from the results with Notepad under wine that I reported in comment 2. The imported line up to the first semicolon is the first line of Quiz.java. The double-quoted comma appears many places in Quiz.java and the remainder of the line appears two places. When I save the result in a .fodt, the saved line appears as one line, which I am retyping here with added line breaks: <text:p text:style-name="P1"> import javax.microedition.midlet.*;","IBM"}; </text:p> HTH, Terry.
** 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.1.5 or 5.2.1 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-20160920
I still get the results described in comment 11 using bibisect-win32-5.3 repository commit 479ca41, source hash f8c463b3.
** 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
Dear Ankur Vishwakarma, 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
Repro 6.4, no repro 7.0 and 7.4+. WFM.