In this 3GPP document (3GPP TS 23.401 V10.4.0), the page numbering presented by LibreOffice matches Microsoft Office until Page 197. At this point, apparently due to the choice of where to start a multipage table, the page numbering goes out of alignment. Table 5.7.2-1 is more than 2 pages long. The naive impression is that LibreOffice decided the table was too big to fit on the page and so moved it to the start of the following page and then discovered it was too big for even a blank page, but did not move the table start back to the original page. This leaves a mostly empty first page in LibreOffice and a full page in Microsoft Office. The 3rd Generation Partnership Project (3GPP) controls the standards around some mobile phone protocols. 3GPP documents are available as Microsoft Word documents. These documents are important to all implementors and testers of nodes within a mobile network (mobile phones, radio transceivers, switching network, packet core, etc). It is important that the fidelity of the documents is preserved when viewing them.
Created attachment 108199 [details] LibreOffice view of Table 5.7.2-1 on Page 197 from 3GPP TS 23.401 V10.4.0
Created attachment 108200 [details] PDF view of Table 5.7.1-1 on Page 197 from 3GPP TS 23.401 V10.4.0
Official Microsoft Word version: http://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-a40.zip An unofficial PDF version: http://www.qtc.jp/3GPP/Specs/23401-a40.pdf
I confirm bug with LibO 4.3.2.2 and 4.4.0.0.alpha0+ Build ID: 3e2bd1e4022e25b77bcc8eba5e02c1adc57008a1 TinderBox: Win-x86@42, Branch:master, Time: 2014-10-16_01:04:13 same bug with OOo 3.3.0, LibO 3.3.3 and AOO 4.1.0, hence bug is inherited from OOo. I add Writer developer to CC list
** 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
As per request, this bug is still present in LibreOffice Version: 5.0.4.2 on Fedora 23. LibreOffice Build ID: 5.0.4.2-3.fc23. See attached new PNG image, which look much like the previous image.
Created attachment 121967 [details] LibreOffice-5.0.4.2 view of Table 5.7.2-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 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
As suspected, this appears to be due to keep-with-next being set on all of the paragraphs. Removing that in this table seems to fix it. This is acting the same as a table that is marked as "keep with next" in LO. Since everything is trying to keep together, as well as keeping with the paragraph following it - well that creates a pretty big mess for a multi-page table. So just remove the unnecessary keep-with-next property (select the entire table, then remove it from all of the paragraph's properties).
Created attachment 172316 [details] Sample from page 197 Here is 8 or 9 pages DOC (MSO is indecisive) starting from page 197.