Hi, I am currently working with a master document, and despite fixing the layout at the level of the subdocument, there are crippling problems with regard to the placing of images, as some of them, upon the text being reflowed, end up pushed down to the next page, but instead of just staying on the next page they jump 5 to 15, even 60 pages (!), and thus leave all of those pages behind them simply empty, which is making it impossible to publish any usable PDF version. I have labeled this as "critical", though I should have labeled it as a "blocker".
(In reply to comment #0) > I have labeled this as "critical", though I should have labeled it as a > "blocker". Yeah, every bug is of utmost importance for their reporter. No news. FYI, this is (roughly) how we evaluate each bug’s importance: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Without test document and a clear step by step scenario to reproduce the problem, it impossible to reproduce it and to fix the bug if there is one. Set importance back to standard value until this bug has been confirmed. Please try again with the current stable version 4.3.1. Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided requested informations. Thank you for your understanding. Best regards. JBF
*** Bug 84291 has been marked as a duplicate of this bug. ***
Set status back to UNCONFIRMED. Requested info has been provided for duplicate of this bug: Bug 84291 https://bugs.freedesktop.org/show_bug.cgi?id=84291
Created attachment 107014 [details] master doc exported in pdf with LO 4.3.3.0.0+ Not reproducible for me with attachment 106806 [details] from duplicate bug 84291. I did my test with version 4.3.3.0.0+ built at home under Ubuntu 14.04 x86-64. Please, could you try again with the current 4.3.2 stable version recently released ? Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided requested informations. Thank you for your understanding. Best regards. JBF
Created attachment 107057 [details] Successively created PDF's of master.odm with 4.3.2.2
I downloaded and installed the stable release from: http://download.documentfoundation.org/libreoffice/stable/4.3.2/deb/x86_64/LibreOffice_4.3.2_Linux_x86-64_deb.tar.gz Info in "About dialogue" is: Version: 4.3.2.2, Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d The problem still exists. Here is how I've tested it: I've opened "master.odm" from attachment 106806 [details]. Initially, writer shows the correct page count of 81 in the lower left corner. Then I ran "File - Export as PDF..." and created attached "master1.pdf" with 92 pages; page 36 is the first empty page that should not be there. The page count in writer also changed to 92. Then I re-ran "File - Export as PDF..." and created attached "master2.pdf" with 84 pages, three to many. The page count in writer changed to 84 and after some time without doing anything in writer dropped to 81. Then I exported again and "master3.pdf" was created with the correct 81 pages. Unfortunately, the original document I can export to PDF only once after opening. When exporting again, writer shows "Repagination..." in the status bar at the bottom and it will not finish for an hour or so.
Indeed, upon export to PDF repagination is done, which reflows the text and which in turn changes the page count. As the TOC is not updated anymore during this process, the pages mentioned in the TOC do not correspond anymore to the real pages. The change in page numbers is caused by some of the figures jumping numerous pages and leaving empty pages behind them.
@JBF: Does the behaviour occur for you with the current stable release 4.3.2? Can it be an external library issue? If more info is needed to reproduce the bug, I'm happy to help.
Can a test file be provided pls? Also is this still happening with LO 4.4b2? http://www.libreoffice.org/download/pre-releases/
You can download a test file from here: https://www.dropbox.com/s/vz43d9x0v1t3fxr/master_for_support.zip?dl=0
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.