1. Open attachment 102915 [details] from bug 81426
Observed behaviour: Header is gone and left section 'Request for Proposal' is in all pages.
Build ID: 7a1add76d542e9929c1feab9e06949990e236616
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Regression introduced by:
author Justin Luth <firstname.lastname@example.org> 2016-06-25 19:21:08 (GMT)
committer Miklos Vajna <email@example.com> 2016-06-29 07:35:54 (GMT)
commit 50bf96d31ab2eb546f6c71cc93c1fa5dd4bf3044 (patch)
parent 1294013bf5d373ded1d050370569acdc2b68c5f5 (diff)
tdf#90697 docx - don't change continuous break into page break
As soon as you set PROP_PAGE_DESC_NAME, you are inserting that
style as a page break. Setting a pagebreak via a continous break
was first introduced in commit 50cb1667020494906afaacb68d4163d1eda527cf
but the unittest for that commit no longer uses this code.
I'm suggesting it be reverted. It really messes up round-tripping
when continuous breaks are removed/replaced with hard page breaks.
There are a few odd cases where the very first section needs to set the
page break via the continuous break, so it hasn't been eliminated
Adding Cc: to Justin Luth
385.docx is a demonstration of a document that will be very difficult for LO to emulate. Before the "regression" the cover page took up 3 pages. Now it properly takes only one page.
This displays the typical problem with continuous section breaks (which LO cannot fully emulate) where headers are set at "random" places and not associated with any page break. In this case, the header used on page2 is from section 4 (probably first defined in section2).
In this particular document, the continuous break is followed by a page-break. In that specific case, the import ought to be able to convert this into a section-page-break and thus solve at least one part of the header problem. (I looked into doing this once, and had difficulties.)
I will not be treating this one as a regression (reducing severity to low - perhaps it should instead be changed to enhancement).
** 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!
Can reproduce with
Build ID: b15b1a2a90fa4c239ff8a6a33e73ff50ea422abf
CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde4;
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-11-28_06:21:05
Locale: nl-BE (en_US.UTF-8); UI-Language: en-US
This looks correct in
Build ID: 6015634de5ada0f9dda9bb4354b2939d8f015a27
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3;
Locale: de-DE (de_DE.UTF-8); UI-Language: en-US
Setting to VERIFIED
Build ID: dee81fb2e1df5091702b3c8b0e4a3f2b58e89291
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US