Description: Additional page break inserted on export to DOCX Steps to Reproduce: 1. Open attachment 161941 [details] (bug 133930) 2. Export to DOCX 3. Notice a page break before page 6 Actual Results: Page break on pag 6 Expected Results: No page break Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.1.0.0.alpha0+ (x86) Build ID: 26483950760f0aac7bc45e93db4127f66a98fdc6 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL page breaks on every page with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL
Created attachment 162012 [details] work fine for me I can't reproduce it in Version: 7.1.0.0.alpha0+ Build ID: 37d5cccceb9f02d60de326f5b1fc5098dc004739 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
After RT, do you open the file in LibreOffice or MSO ?
Created attachment 162023 [details] Screenshot ODT
Created attachment 162024 [details] Screenshot DOCX (LibreOffice Page 6 and 8 are getting a page break (using LibO)
No additional page in docx in Version: 7.0.0.0.beta1 (x64) Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL but 10 pages in Word 2016 (text from page 7 to 9 is now on page 7 to 10) Because this different to the behaviour you describe, Telesto, I heven't changed status of the bug.
Dear Telesto, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
(In reply to Xisco Faulí from comment #1) > Created attachment 162012 [details] > work fine for me > > I can't reproduce it in > > Version: 7.1.0.0.alpha0+ > Build ID: 37d5cccceb9f02d60de326f5b1fc5098dc004739 > CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded attachment 162012 [details] has the flaw. There is a page break between page 5 and page 6, not seen in the ODT No change Version: 7.1.0.0.alpha0+ (x64) Build ID: <buildversion> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -> Build of today
Page breaks on every page until Version: 5.4.0.2 Build ID: 2b906d450a44f2bbe506dcd22c51b3fa11dc65fd CPU threads: 4; OS: Windows 6.2; UI render: default; Locale: nl-NL (nl_NL); Calc: CL After 6.0 the situation improved with a page break between 5/6 remaining
(In reply to Telesto from comment #8) > Page breaks on every page until > Version: 5.4.0.2 > Build ID: 2b906d450a44f2bbe506dcd22c51b3fa11dc65fd > CPU threads: 4; OS: Windows 6.2; UI render: default; > Locale: nl-NL (nl_NL); Calc: CL > > After 6.0 the situation improved with a page break between 5/6 remaining Sorry and between 7/8
@Justin If there is rainy day and you're in the mood to look at spurious page breaks on export
Yeah. This requires serious emulation because MS formats don't have a concept such as "left page style follows a right page style.". But this one ought to fall under IsPlausableSingleWordSection, and thus define both right and left page in a single style. That will be fairly hard to do. The exporter will need to look specifically for a circular page-style relationship, keep track of those two names, and define a single section that applies while those two names are uninterrupted. Currently, every other page is going to have a pagebreak-with-style -> NEW. I notice that the even pages are missing the footer content - which is the most concerning to me.
(In reply to Justin L from comment #11) > I notice that the even pages are missing the footer content - which is the > most concerning to me. Reported as bug 135216
(In reply to Justin L from comment #11) > Yeah. This requires serious emulation Confirmed. > This one ought to fall under IsPlausableSingleWordSection Well, at least in test test files I made, IsPlausable... returned false. And I think this L/R style merging will need to pre-empt the first/follow style merging. > That will be fairly hard to do. The exporter will need to look specifically > for a circular page-style relationship The exporter already identifies the circular relationship in sw/source/filter/ww8/wrtw8sty.cxx's SectionProperties(). Yup - hard to do - partly because all of these styles are "const". Too hard for me.
(In reply to Justin L from comment #13) > (In reply to Justin L from comment #11) > > Yeah. This requires serious emulation > Confirmed. > > > This one ought to fall under IsPlausableSingleWordSection > Well, at least in test test files I made, IsPlausable... returned false. And > I think this L/R style merging will need to pre-empt the first/follow style > merging. > > > That will be fairly hard to do. The exporter will need to look specifically > > for a circular page-style relationship > The exporter already identifies the circular relationship in > sw/source/filter/ww8/wrtw8sty.cxx's SectionProperties(). > > Yup - hard to do - partly because all of these styles are "const". Too hard > for me. Thanks for looking into it. Some bugs look so 'simple' at first sight from an non DEV perspective :-). Every time write the stuff out, I get scared about they complexity of all of this
A nice complicated-but-minimal version of this bug is attachment 163674 [details]. A similar-but-different cleanroom example will be ooxmlexport15's tdf135216_evenOddFooter.odt
There is a simple solution to this. As a user, don't use different LeftPage/RightPage page styles. Instead, use a single page style with different left/right headers.
(In reply to Justin L from comment #16) > There is a simple solution to this. As a user, don't use different > LeftPage/RightPage page styles. Instead, use a single page style with > different left/right headers. I'm likely not the person who uses Left/Right page styles (or I have never done that). This is simply a re-cycled bug doc :-) Is there a wikipage with developer DOCX comp-ability tips. I have seen more documents with left/right page styles. Posting wisdom/insights here is somewhat pointless, I fear.
The issue with jjjgg.odt (attachment 161941 [details]) is that it fails plausableSingleWordSection b/c: HdFtDistanceGlue aOne(rTitleFormat.GetAttrSet()); HdFtDistanceGlue aTwo(rFollowFormat.GetAttrSet()); //e.g. #i14509# if (!aOne.StrictEqualTopBottom(aTwo)) bPlausableSingleWordSection = false; But if you make a new document from scratch and do not monkey around with changing the sizes of header stuff, then right/left get merged into a single style on import. I am going to mark this as NOTABUG, because (even though the human eye can't tell), the Left and Right style have different internal settings and thus cannot be considered equivalent.