Created attachment 63901 [details] switch beetween Print and Web Layout to see bug I dont know if this is related to #35449, but looks similar. System is Ubuntu 11.10 LibreOffice 3.5.4.2 release Attachment was originally Word .doc and converted to .odt Table of contents doesnt show entirelly. Corresponding pages neither. Switch to "Web Layout" and full pages are visible. +++ This bug was initially created as a clone of Bug #35449 +++ Hello, first I know that tables are not thought to be used in writer this way. But it's possible to do so and also hints at the internet recommend to use large tables to get independent columns for your document. The attachment contains a file consisting one table with just one line and two columns. This table goes over many pages and footnotes are set. Since this table got longer and longer problems appeared at page break. The Document is fine at "Web Layout", but gets problems at "Print Layout". Appearance: At "Print Layout" it seems that text is cut of at end of random pages, also the number of Page Count is less than it should be. Pressing Ctrl + A you see that the text get marked and the marking runs out of page. This also causes high CPU-usage, and even can freezes the window. Switching to "Web Layout" brings the whole written text back and everything works fine. If the problem not totally accrues after opening the document, it will accrue after switching from "Web Layout" to "Print Layout" (watch Page Count!). Systems: This behaviour was tested on Windows XP and Ubuntu-Linux (10.04 32bit and 10.10 64bit),with LibreOffice 3.3.1 and OpenOffice 3.2.1 as well. My opinion: This problem causes big confusion by users, even because it appears different at PCs with more or less power. If it should be impossible to implement a good working "Page Layout" with large tables, there might be at least a warning that tells the user that there will be problems. It could hint him to "Web Layout" or to different possibility’s like using boxes or marginalia, if this is adequate to his goal. I hope you see what I mean, if there are any questions I'm willing to help.
bug existed before .doc was converted to .odt
Hi thanks for your report. It is indeed related to the table. So good to keep issue 35449 in mind too. When you put the cursor in the table#36, and choose Table > Convert > To text, the TOC shows fully, also in print layout.
And I set the version on 3.3.0. But I guess if you try OOo 1.1.5 or 2.1, you'll have the same problem
** 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 (4.3.5 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 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) Thank you for your help! -- The LibreOffice QA Team
Can't test in 4.4.0 due to https://bugs.freedesktop.org/show_bug.cgi?id=86208 and https://bugs.freedesktop.org/show_bug.cgi?id=87663 Confirmed in 4.2.8
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.