Created attachment 59284 [details] Form in MS Word document interpreted wrong The error is reproduced by downloading the document here (also attached BR-1010B.doc): http://www.signform.no/dss/kundeweb/Blankettarkiv/vis/Download.asp?BlankettFilID=1192&KID=617&C=343219538BR-1010B It is formatted so that the bottom text ("BR - 1010B - 2011 http://www.brreg.no Blanketten er godkjent av Brønnøysundregistrene September 2011") and paging "Side 1 av 6") should be at the bottom, but in Libreoffice's formatting this is not correct. Compare with the ODT version available (attached "BR-1010B.odt"): http://www.signform.no/dss/kundeweb/Blankettarkiv/vis/Download.asp?BlankettFilID=1790&KID=617&C=343219538 All of the forms are available here (Bokmål/Nynorsk is different language versions): and some in english: http://www.brreg.no/english/forms/
Created attachment 59285 [details] File in ODT format interpreted correctly
The author of the documents says that it can be caused by the use of two types of page breaks, of which only one is supported by LibreOffice.
Created attachment 63504 [details] PDF, produced from first attachment using msWord 2007
Thanks for bugreport Using first attachment, reproduced: on Fedora 64 bit in 3.3.4, 3.5.4, 3.6.beta1 on Windows 7 32 bit in 3.5.2 Changing version to 3.3.4 as most early reproduced
Thanks for additional testing. "Version" is most early version of LO where bug reproducible. Not a current version. If bug disappears, we just close it. Changing back to 3.3.4 as most early reproduced
** 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
Confirmed. Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+ Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-25_23:07:36
** 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.0) 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-02-21
One of those pesky forms. I don't understand why footer was not used here, but.. Since breaks were mentioned, I add Justin here due to Bug 64372 for expert opinion.
As far as I can see, sections and section breaks have not been used in either the .doc or the .odt. If that is true, then typical spacing/font differences would account for the "content on wrong page" problem. The .doc file is password locked preventing alteration. An unlocked version would be required for a developer to do any verification on (setting to needinfo).
Created attachment 129863 [details] Form in MS Word document - unprotected I hope this one is of some use.
Yikes - the entire first 5 pages are all one long table. Definitely not a pagebreak/sectionbreak problem.
I changed to low-minor, but I'm not sure this will ever be solved. This document is unusually created, I'd even say wrongly. Rendering difference exists, but I guess it's hard to have pixel by pixel similarity. It would be nice to have someone in CC to decide.
Regarding the original problem, while the document might still be a useful use case if it is a document MS Office could happen to make, the form has been converted to PDF available here: https://www.brreg.no/wp-content/uploads/BR-1010B.pdf Even better, in most cases, the form has been replaced by online web forms: https://www.brreg.no/produkter-og-tjenester/skjemakatalog/samordnet-registermelding-del-1-hovedskjema/
Created attachment 129865 [details] compare MSO and LO Side by side comparison shows match, until the row "8.Organisasjonsform" Paragraph-Line and Page Breaks status shows "Page break before" for that one in MSO, and that's what LO doesn't read properly. Justin, please take a look.
LibreOffice does not support paragraphs with page-break information when they are inside of a table (at least according to the UI).
** 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
Repro 6.2+
Although a different situation, we have the opposite effect in bug 61423 - where the table IS being split due to a new page style (RES_PAGEDESC).
Dear marius, 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
Repro 6.4+
Created attachment 160535 [details] tdf48097_pageBreakInTable.doc: simple unit test - page-break-before in column 1, paragraph 1 Microsoft ignores a paragraph's request for a page break before when in a table cell, UNLESS it is the first paragraph of a cell in column A. Currently, LO imports that page-break request and move it to the table itself - which is the only supported place for it. The UI doesn't allow page-breaks or new page styles inside a table. This could be emulated by splitting the table and adding a page-break before on the table. That should be easily possible since apparently DOC tables are just equivalently configured rows grouped together.
(In reply to Justin L from comment #22) > emulating with a split table should be easily possible... Amateur remark. Easy and tables do not belong in the same sentence.
Created attachment 161257 [details] tdf48097_TwoTables.odt: simple Writer document where two tables are separated by a page break Although not exactly matching this bug document, this simple document composed in Writer (and so untainted by any previous MS formatting) demonstrates that LO importing is poor - since it merges the two tables into one. (Export is OK since MS Word 2003 opens up the .doc and .docx formats that LO produces properly - with one table on each page.) This document was inspired by bug 104017 which should be a duplicate of this one.
*** Bug 104017 has been marked as a duplicate of this bug. ***
(In reply to Justin L from comment #25) > *** Bug 104017 has been marked as a duplicate of this bug. *** I don't think it will actually be of much help, but this particular bug was "fixed" in LO 6.4 when a specific set of RES_PAGE_DESC page-styles were assigned. So it could be another avenue of emulation that could be explored, although one fraught with other difficulties. In any case, make sure the fix designed works for that similar-but-different case.
I'm going to mark this as a duplicate of bug 108233, since that report is very clear, and indicates that it is POSSIBLE for ODF to handle per-row breaks. Only the UI needs to be extended to support that. *** This bug has been marked as a duplicate of bug 108233 ***
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/73ba7a4738ecaa730d4d41439b3a4a6d7693efa3 crashtesting: assert on exporting fdo48097-1.doc to docx It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.