DOC file: attachment 108383 [details] First reported bug related to this file: bug 85430 PDF export using 4.4.0.0 alpha1 from Oct 24: attachment 108384 [details] PDF export using Word 2010: attachment 108385 [details] Problems: Frames on pages 3, 4, 7, 23, 26, 27, 51, 52 and 53 have incorrectly "Wrap through" and they don't have a gradient. Frames on pages 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 and 42 have incorrectly "Wrap through". Frames on pages 11, 12 are in the wrong position, not hiding the Chinese text.
Quick addition: on page 5, Figure B has a frame between the houses with the text "Wind" that should not be on top of the arrow.
Reproducible already with LO 4.3.2.2 (Win 8.1)
Hi Beluga, Would it be possible for you to split this in one issue for each problem? You may also want to look for possible existing issues that say the same? thanks, Cor
Ok let's keep this one for the wrap problem. Gradient problems are in bug 85480 Position problems are in bug 85481 I searched for dupes, but couldn't find any. Keywords used: frame wrap, frame gradient, frame position.
Wrap problem: Reproducible with LO 4.3.2.2 (Win 8.1)
** 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.4 or later) 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 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: 2015-12-20
Still reproducible with LO 5.1.0.1 (Win 8.1) for page 3, 32, 32-42, 51-53
Problem is still reproducible on the latest 5.1.1.3 version for Windows 7 SP1 64-bit.
Still confirmed. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha1+ Build ID: 64024d7c18bd114eb9958cf80eea9129e09923bd CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on November 3rd 2017
** 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
Problem still exist on the latest release. Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group threaded
Still confirmed Version: 6.4.0.0.alpha0+ (x64) Build ID: ed882d693f37779e3a09641e7cd43b7a925d2312 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-25_00:58:18 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
In Word 2003, these are marked as "In front of text" which is equivalent to wrap-through. So I would call this one NOTABUG. The reason that the text is disappearing underneath the frame is because it is not using fixed spacing 22 properly. (It looks like single spacing instead of 1.5ish spacing.) But that is the report of another bug for this document already.
Thanks, I will close.