Created attachment 61580 [details]
Figures created using MS Word autoshapes do not import at all in LO
The attached document has three different figures created with auto shapes. LO does not import any of the figures at all. This problem appears specific to Autoshapes in .DOCX format.
confirmed using LO 3.5.3 on Linux amd64.
Created attachment 66283 [details]
Test document in LO 184.108.40.206
The bug is confirmed in LO 220.127.116.11 under Windows 7 SP1 32 bit.
The position of some shapes is VERY strange. Some of them are shown as rectangles and some of them are missed.
I've attached the PDF.
Created attachment 72409 [details]
Test document in 18.104.22.168.alpha0+
The symptoms have changed since comment 2, and now this bug seems to be solved (i.e. the shapes *are* imported), still leaving us with bug 49260 (imported, but in wrong place).
Tested in Version 22.214.171.124.alpha0+ (Build ID: ca3aba4cdf766cf33b0dbbe495c9e6f57f06982)
Created attachment 94451 [details]
Test document in Word 2010
The situation is much better in LibreOffice 4.1.4: the shapes are on correct places. But I see a problem with arrows: on page 5 they have incorrect direction in top figure and are not imported for bottom figure. I attach a pdf from word 2010 which shows how the document should be represented. Also, I see bug 70942.
Still reproducible as described in the previous comment with LibreOffice 4.2.5 and 126.96.36.199 on Debian. I decrease importance of the bug, because now the situation is not so bad as in the initial description.
Reproducible with LibreOffice 188.8.131.52beta1 on Debian.
Migrating Whiteboard tags to Keywords: (filter:docx)
Build ID: a9f56091b6422ec8c42f09b8472200ae4ab12548
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-05_23:12:26
Locale: nl-NL (nl_NL); Calc: CL
** 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!
Created attachment 139850 [details]
Stripped down test document
Stripped down version to demonstrate the issues. This is likely a VML issue. When file is upgraded to OOXML, the shapes are correctly imported.
Reproducible in Version: 184.108.40.206.alpha0+ (x64)
Build ID: 3deac9691011711a3b9e50d19499c588af074d7f
repo in Version: 220.127.116.11.alpha0+
Build ID: 45f4de6d333aa3fa5873cf8e1146286c74960557
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;