Created attachment 126119 [details] doc On page number 3 there are 2 big images, on LO only one shows and the other goes to the next page.
Created attachment 126120 [details] diference
Version: 5.3.0.0.alpha0+ Build ID: dc4797a79e3f465e1fa930be7c69d8ec7d91c15e CPU Threads: 2; OS Version: Linux 3.16; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group Confirmed. I believe this is because of the footer. LibreOffice handles footers different from Microsoft Office (something that is already reported....no idea if it's confirmed or not). If you can test please try to remove the footer and then compare the document in MSO and LibreOffice. My guess is that it'll look right.
Hello I'm Nadith,I would like to fix this bug. I'm new to libreoffice. I have already built the libreoffice which "Version: 5.3.0.0.alpha0+ Build ID: d945e97d8f85465f04f59fd197ded2edb56caac3 CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; Locale: en-US (en_US.UTF-8) " So,This will be my first hack if i was assigned Can someone help me out to pick good starting point to fix this bug
Hi there, thanks for your interest in helping LO get better! Best way to get you started is in irc://chat.freenode.net/libreoffice-dev
Please report your progress here @Nasith Are you able to fix the bug?
hello ekari, I ask from IRC list most of them convinced me this is kind of tricky bug start with as I'm beginner to LO. So I think I will take this bug later and I think bug is still open then.
OK, I unassigned the bug, you can have a look at other interoperability bugs I reported, I have 11 interoperability open bugs and 1 security bug open.
possibly inherited from OOo..
** 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
still repro in Version: 6.2.0.0.alpha0+ Build ID: 1aa37aa6bee19099b57555a6d839992b054aa405 CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2018-09-23_10:17:54 Locale: ru-RU (ru_RU); Calc: threaded
Dear E.Mi, 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
Still repro with: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: cb2827f5f65324f309fa0e3c30d0b19ad237410e CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Created attachment 174148 [details] PDF exported from Word
(In reply to Cor Nouws from comment #8) > possibly inherited from OOo.. Correct.
repro 7.6+ This is an "every TWIP counts" kind of bug report. As such, it adds no value whatsoever. Closing because it is basically inactionable.