Description: Drawing is broken in Word. Steps to Reproduce: 1.Open attached file 2.Save as DOCX Word 2007-2013 XML 3.Open File in Word Actual Results: Drawing is broken in Word (but fine in LibO when opened with the same version) Expected Results: Drawing should be OK in Word as LibO Reproducible: Always User Profile Reset: No Additional Info: Version: 5.4.0.0.alpha0+ Build ID: 84f2ff67a7e404febf710b1dc7f66d06745c503f CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-09_23:20:01 Locale: nl-NL (nl_NL); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Created attachment 129521 [details] Example file
Confirmed in Version: 5.4.0.0.alpha0+ Build ID: 634589b340316ba64b731b4d923c1056be415494 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group and Version: 4.3.0.0.alpha0+ Build ID: 52cc0c8f05d40db6d076c13f8b8d6d9453ec8930
** 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
Created attachment 165011 [details] Position and size settings in original ODT and exported DOCX Multiple grouped shapes with rotation and whatnot... Lots of settings get bad values here. Version: 7.1.0.0.alpha0+ (x64) Build ID: 4c20bb789c7536f63a6844a4cb4489a18cee53c7 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
Created attachment 165012 [details] Rotation settings of the original and exported file
Could you avoid useless word "broken". It's better in 7.2+.Let's focus on rotation, which is good in Mso and wrong in Lo.
*** Bug 104603 has been marked as a duplicate of this bug. ***
Rotation problem fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=3e4eb070787d4d44b3bdc95046e5b231dbbef42b author Xisco Fauli <xiscofauli@libreoffice.org> 2021-03-25 17:38:20 +0100 committer Miklos Vajna <vmiklos@collabora.com> 2021-03-26 09:10:17 +0100 commit 3e4eb070787d4d44b3bdc95046e5b231dbbef42b (patch) tree 185ec85a2454dcc8ac0428c38fa8b3f76d61d308 parent 1fcc08d5dccaf8280fa7709df6eb310b8f502fb2 (diff) tdf#122717: fix handling of zero width/height lines Closing as dupe of bug 122717 *** This bug has been marked as a duplicate of bug 122717 ***