Fileopen DOCX: images outside table
Steps to Reproduce:
1. Open the attached file
2. Image should be inside the table, but aren't
Images floating above the tables
Image should be inside the tables
User Profile Reset: No
Build ID: 1b21ff86effe58ae368457de8fec654ba4c8edd9
CPU threads: 4; OS: Windows 6.3; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2018-07-30_03:13:35
Locale: nl-NL (nl_NL); Calc: CL
No images in
Build ID: f200d5700782ae179fd96b6ad4b0fe8e7edd1616
CPU threads: 4; OS: Windows 6.29; UI render: default;
Locale: nl-NL (nl_NL); Calc: CL
Created attachment 143889 [details]
Created attachment 143914 [details]
comparison MSO 2010 and LibreOffice 6.2
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.10; Render: default;
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Version 220.127.116.11.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
@Justin Luth, I thought you could be interested in this issue...
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!
and as an exercise in mirth, use LO to round-trip the file and everything will be reversed. Now LO looks like how the original was expected to look, and Office 2003 looks like the broken LO.
(In reply to Justin L from comment #5)
> and as an exercise in mirth, ... Office 2003 looks like the broken LO.
Not true with Office 2016 though. 2016 looks fine the whole time.
The big difference in the roundtrip is that initially LO imports the circles as draw shapes, and the round-trip converts them into images. Apparently LO natively handles the area taken up by shapes very differently from images.
Since round-tripping this already looks VERY different in LO, and it also "fixes" the problem, I'll just leave this bug as is. Occasionally there is talk of hiring someone to fix image handling - this is probably a good bug to include in that workload, since it highlights some of the fundamental differences.
Still reproducible in
Build ID: de4839e66d3d195315729b95cc144cdab96b6e74
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US