Created attachment 75561 [details] Example word document that libreoffice makes unreadable. Problem description: When attempt to view the attached single page document, the various parts are overlayed on top of each other so that it is unreadable. Steps to reproduce: 1. Open document in libreoffice 2. View page 3. .... Current behavior: Unreadable document Expected behavior: Readable document. Operating System: Ubuntu Version: 3.6.2.2 release
Created attachment 75563 [details] Screenshot of the same file in MS wordviewer
Created attachment 75567 [details] Screenshot of the way libreoffice renders the file
Confirmed with 14.02 master. The textboxes have wrong positions and background images are shown as solid white shapes.
Reproducible with LO 4.4.0.3, Win 8.1. The text boxes are at wrong places and the background images are greyed.
The textbox placement is no worse now than in 3.3.0, and the background images are as good as they've ever been, so I think this can be "Inherited from OOo" I wonder about attachment 75563 [details]. It doesn't look very legible with the background images at full intensity - in contrast, the desaturated background images that LO 4.4 shows look reasonable underneath the green text. A screenshot from a recent Word (not Word Viewer) would be useful for comparison.
** 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.0) 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-02-21
Reproducible with: Version: 5.4.0.0.alpha0+ Build ID: 33f5bc54aaa7fe7aa9335726e30f9c349155e04d CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-12-01_23:21:05 Locale: nl-NL (nl_NL); Calc: CL
Created attachment 129372 [details] Example DOCX
Repro with Version: 6.0.0.0.alpha0+ Build ID: 1d0fbc9927f357d25859b7cca7ea5e9a9637681e CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: group moggi's auto updater build, 2017-10-01
** 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
Bug still present in Libreoffice 5.4.6.2
Created attachment 147777 [details] Screenshot for Libreoffice 5.4.6.2
Thanks for reconfirming drraph! Just confirming that this is still present on recent master, and it's not surprisingly a cross-platform issue Version: 6.3.0.0.alpha0+ Build ID: beae6c7a7f163daad0d4dea63a3d403af2745fd1 CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-12-06_23:52:29 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
The original document and its docx export show the shapes are text boxes that are imported as frames instead of shape objects.
Created attachment 166776 [details] Example DOC compared MSO 2016 LO 7.1+ Repro 7.1+. One of those cases where MSO opens wrong/different DOCX it resaved.
*** Bug 137800 has been marked as a duplicate of this bug. ***
Problem unchanged in 7.2.5.2. :(
Still present also in master Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 583185235389b55d6cfffac3067c0e1ccb2852b1 CPU threads: 10; OS: Mac OS X 10.16; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
This is an excellent example of how complicated layout is. It seems that it is true for MS Word as well. The document consists of a single empty paragraph with many textboxes anchored to it via "Entire Paragraph Area". Image wrap affects "Paragraph Area". We have two things affecting wrap. The first is the WordArt "Reception News Letter" which has parallel wrap. The second are the "background" trees. Our main problem comes because LO think there is enough space to wrap the single (empty) paragraph around the word art. So our paragraph area starts at around 6 inches. In contrast, MS Word doesn't consider there to be enough space to wrap beside the wordart, so (the empty paragraph) starts below "Reception News Letter". It has to wrap around the tree, so it starts as 3 inches. You can manually see this if you set "Reception News Letter" to no wrap. Then the whole document is fixed. So, all the anchor/frame/layout details appear to be imported perfectly. It is only a decision to wrap or not that is incompatible. Since this entire bug rests upon precise wrapping decisions, I am marking it as a duplicate of bug 112313 *** This bug has been marked as a duplicate of bug 112313 ***