Problem description: Text copied into a right-indented text into a comment is not formatted properly Steps to reproduce: 1. Set the right indent icon to be 2 (or more) cm LESS than the right margin. 2. Copy some text from that region. 3. Create a comment, and paste the text into the comment. Current behavior: It does not get rendered/wrapped well. Copied text with the big right indent, ‘misbehaves’ by displaying the text with only a few characters width. The greater the right indent, the worse the effect. For example, with 4 cm right indent the comment is only 5 characters wide. Expected behavior: The word wrap would work as if one had typed directly into the comment -- or had copied and pasted text that did not have a right indent. Probably not a problem that most people encounter, but I often use 4cm right indent.
A more precise description. 1. The 'paragraph indent' is copied from the text into the comment. 2. Right click in the comment does not give 'paragraph' as an option, but if one goes to the Format menu, then it is possible to 'fix' the problem. 3. Perhaps text that is copied from a text into a comment should 'lose' any paragraph indenting? 4. In short, a matter of taste whether this is a 'bug' or 'design choice'.
Thanks for bugreport Please, attach odt document where is original text, result of copy-paste to comment and comment which formatted as should be
Created attachment 62342 [details] illustration of 'problematic' behaviour
Thanks for document with additional explanations For throwing formatting away exist function Edit->Paste special (shortcut Ctrl-Shift-V), but in comment it not works correctly. If we select "Unformatted text", pasted text is still formatted. Steps to reproduce: 0. Open attachment in Writer 1. Select some text in bottom half of page 2. Insert->Comment 3. Ctrl-Shift-V, variant "Unformatted text" Expected: in comment pasted ordinary text Actually: in comment pasted one character wide text Reproduced in 3.3.4 and 3.5.4 on Fedora 64 bit (Windows not tested) Changing version to 3.3.4 as most early reproduced In case of "Unformatted text" formatting for comment is taken from that place in text, where comment is placed. In this case it works bad, though formally correct.
Not an enhancement, that is a bug because paste special does not work as it should. Tested with version 4.3.3.0.0+ (Build ID: 18b9cb260a5ec358f6a7b73362bbc306af0417b1) built at home under Ubuntu 14.04 x86-64. Reproducible with the master too. Version: 4.4.0.0.alpha0+ Build ID: 24fb87501ef9d5aa715d572de7eb5efe49a0d9c3 Summary made more clear (I hope). Best regards. JBF
Workaround: menu Format > Clear Direct Formatting works in comments. Best regards. JBF
** 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.1 or preferably 5.0.2.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-10-14
The bug is still present, and has the same appearance as described in Comment 4, if one follows the procedure described there. Test with: LO: 5.0.2.2 Windows 7 (Enterprise)
** 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.6 or 5.2.3 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-20161108
Nothing changed since last check (comment #6 and comment #7). Tested in master : Version: 5.3.0.0.alpha1+ Build ID: c64b8ffe851d3320a15071fa4bc4b0f12e9939d5 Threads CPU : 4; Version de l'OS :Linux 4.8; UI Render : par défaut; VCL: gtk3; Layout Engine: new; Ubuntu_16.10_x86-64 Locale : fr-FR (fr_FR.UTF-8); Calc: group Best regards. JBF
*** Bug 112935 has been marked as a duplicate of this bug. ***
The equivalent report for Calc is bug 112935.
Repro in 6.2+.
Seems like this was fixed already in 6.2. WFM. Please test. If someone still reproduces, please explain.