Created attachment 83341 [details] objects created in Writer ready to be saved in DOC and tested... Problem description: If you draw rectangle; rotate it for example 90 degree; group it with some other shapes (another rectangle for example) and save it in DOC... the shape that was rotated will no be rotated. It only happens if objects are grouped... otherwise, shapes will be saved correctly. Steps to reproduce: 1. Draw rectangle 2. Copy that rectangle 3. Rotate copied rectangle using available option from toolbar Drawing Properties 4. Group rotated recntagle with the first one 5. Save file as DOC Current behavior: Rotated shape is not rotated, ie. original position is remained. Expected behavior: Rotated shape should remain rotated even if shapes are grouped. Operating System: Ubuntu Version: 4.0.4.2 release
Addition info: This happens when file is opened in Microsoft Office Word (that would be sixth step to reproduce).
Hi Ljiljan, I cannot confirm this at the moment, but to start I make the summary a bit more clear. thanks for reporting! Cor
Created attachment 83350 [details] ZIP containing ODT/DOC/DOCX/PDFs of the original file with text in the shapes. I am attaching an archive showing how the original document (modified to include text in the shape) appears under MacOS 10.6.8 running TDF/LO v4.0.3.3 and Word 2011 for Mac. I have included the text to illustrate rotation direction and how this bug relates to bug 37828. In this particular case the resultant DOCX actually appears worse than the DOC. Whether opened using LO Writer or MS Word 2011 the DOC/DOCX do not include correctly defined grouped AutoShapes, when the group includes one or more rotated objects.
Setting status to NEW, version to 4.0.3.3 (although it probably goes right back to OOo), and platform to All as a result of testing under MacOS. I have also observed the same behaviour under Crunchbang 11 running TDF/LO v4.1.0.4.
this could possibly also have a connection to https://bugs.freedesktop.org/show_bug.cgi?id=66843
** 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.1 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-04-01
Re-tested attachment from comment 0 under GNU/Linux x86_64 using: v3.3.4.1 OOO330m19 Build: 401 v3.4.6.2 OOO340m1 Build: 602 v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b v3.6.7.2 Build ID: e183d5b v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a v4.2.8.2 Build ID: 48d50dbfc06349262c9d50868e5c1f630a573ebd v4.3.5.2 Build ID: 3a87456aaa6a95c63eea1c1b3201acedf0751bd5 v4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 All versions exhibit similar problem with the group containing one rotated object when saving to DOC. Appears to be a mild change / improvement in handling under v4.3 and v4.4 but still problematic. Version set to "Inherited from OOo".
Created attachment 114602 [details] ZIP of DOCs written out under different versions of LO. (In reply to Owen Genat from comment #7) > All versions exhibit similar problem with the group containing one rotated > object when saving to DOC ... and reopening using LO (not Word as specified in summary). Apologies. I do not have access to Word at present. I have attached the DOCs for someone else to test.
** 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.5 or 5.1.2 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-04-16
I confirm that this bug is still present is LibreOffice 6.1 on Ubuntu 16.04
Dear Ljiljan, 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
Dear Ljiljan, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug