Created attachment 167026 [details] Sample DOCX and DOC compared in MSO and LO Open DOCX attachment 81684 [details] from bug 81522 and see that MSO Tight wrap is not read correctly in LO. It's 2007 but regardless, same if resaved in MSO as DOCX. Never was fine, current status is from 4.2 up to LO 7.1+. Same graphic from same DOC attachment 81320 [details] in bug 66119 is also not fine but is different, wrap is OK but position is NOK. So I report separately. Moral is: always test a counterpart too. "Demo-Hayden-Management" is well-known trouble for LO, seen in more DOC and DOCX bugs. Only some reference the same attachment, more have derivatives. Some other issues with this DOCX: bug 107055 for header, bug 128877 for image location, no report? for wrong position of Summary seen with latest master.. DOCX is 2 pages and this bug makes it 3 in LO.
My Word calls this a "Flowchart with growing images" type SmartArt. @Miklos: I thought you might be interested in this one.
(In reply to Timur from comment #0) > "Demo-Hayden-Management" is well-known trouble for LO, seen in more DOC and > DOCX bugs. Only some reference the same attachment, more have derivatives. Would be a fun exercise to turn bug #66119 (DOC) and bug #67339 (DOCX) into meta bugs. Such "this document falls apart for 27 reasons" documents could be useful for bug mining with their authors being way more imaginative than us. I already have some opened from parts of these baddies like bug #136650 and I'm rather certain that bug #135235 also affects the black and orange shapes, although this rounding error is not the reason for those to show up on the wrong page. Also: bug #58521 is making those endnotes show up on an extra last page.
Still reproducible with the latest LO 7.6 dev master: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2478d4b1a4cec495f1bf68f1e62c01031cdeec86 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fa-IR (fa_IR); UI: en-US Calc: threaded
Dear Timur, 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