Three files have been attached: Master document, subdocument and pdf file. I have a master document with about 80 subdocuments. It is impossible for me to get this export to a pdf correctly. The same issues show up if it is printed. The sample document demonstrates the formatting problems. -Enable View - Text Boundaries. At the bottom of the first page you will probably see the text area extending down into the footnote area. -Enable View - Nonprinting Characters. The hidden text will now appear and the text area will show correctly, although footnote numbers will still be incorrect throughout the document. -Disable View - Nonprinting Characters. The text areas will now all be displayed correctly. They will not be extended down into the footnote area anymore. -Export to PDF. It will now re-paginate the document and when exported the text areas will be messed up again as can be seen by the paragraph at the bottom of the right column on the first page. This document was created as an odt file and was never imported from another format. I have the severity set to critical because it is impossible to create a proper final pdf document. There have been a number of bug reports about repagination, tables, and footnote problems. I suspect that this should be a good test case to troubleshoot all those bugs. Having a clean profile does not affect it.
I am currently using version 4.3.0.3
The subdocument will appear correctly as far as the text area is concerned when it is edited on separately, althought the footnotes will still be incorrectly ordered throughout the document. The problem mainly occurs when using a master document. And please don't say the solution is to edit separately. I have about 80 subdocuments and there is no way I want to got through each one changing styles if there needs to be a change.
@David Reprioritizing: Hi David - couple points: 1. I'm resetting this priority according to our bugflow chart: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Normal - can prevent high quality/professional work Medium - default Major/Critical/Blocker are all reserved for crashers and loss of data. 2. We'll need some kind of attachment (the simpler the better) that demonstrates the problem. Please set to UNCONFIRMED when you have attached a document. Thanks for your understanding and help!
Created attachment 103519 [details] master document
Created attachment 103520 [details] sample document
Created attachment 103521 [details] pdf output Sorry about that. Forgot to add the attachments. Setting to unconfirmed.
This bug is more than being able just to do high quality work, it is impossible to output correct data.
For me, enabling/disabling nonprinting chars does not show the text areas correctly. I don't understand "when exported the text areas will be messed up again as can be seen by the paragraph at the bottom of the right column on the first page." Even your own attached PDF shows there is nothing messed up in that part. Maybe post a screenshot highlighting a problematic area while comparing it to a correct rendering?
@Beluga - Please carefully check the pdf against the sample document again and you will that there is indeed a difference between the text in the pdf and the text in the bottom right cell in the sample document. Open the test.odm document. Enable Table | Table Boundaries. Verify that the Font Effect | Hidden option is enabled for the "-hide" character style. Now notice how the table outline extends down into the footnote area. That means that not all the text that is in that cell is actually being displayed since it's not in the text area. Now disable the Hidden option for the "-hide" character style. Now the table formats correctly. The footnotes that are hidden are in the left column. Count how many rows of text there are in the bottom cell in the right column. There are 14 rows in that cell, some of which get extended to the next page. In the pdf there are only 10 rows plus one that got extended to the next page. You can also count the words if you want to verify that not all of them are shown. Notice also how the footnote numbers are out of order on the second page and various other pages (even if the hidden option is disabled). Also, toggling the hidden option a few times, or dragging the column boundaries to change the column widths will cause it to crash. I am using LibreOffice 4.3.4.1.
@Beluga - You are correct about how toggling View | Nonprinting Characters does not change anything. I don't know what version I was using when I first reported this problem, but as of 3.4.3.1 that function is not behaving as it once did.
Created attachment 109613 [details] Backtrace of crash from toggling font effect Hidden I reproduced everything said in comment 9. The style -hide is found under Character styles - Footnote Anchor. Crashed after second toggle of Hidden (couple of secs after pressing ok). Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Let's set to NEW.
** 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.2 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-04-16
Yes, the bug is still there on a fresh update of 5.3.0 alpha on Linux. Disabling View - Non-printing Characters now seems to have no affect on the display.
** 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 fails with version 6.2.1. It also now crashes with this document when doing Tools - Update - Update All
Created bug 124300 for the crashes (seems to be the same root cause for both ways to cause it).
Still repro with 7.2 on Linux
Dear David, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug