Description: If a style has a break defined before page, the information is lost when the file is saved in RTF format. If the page break is defined in the paragraph, but not in the style page breaks are retained. Steps to Reproduce: 1. Open Writer and enter some paragraphs with different styles 2. Change a style definition with page break before in "Text Flow" 3. Save the file in RTF format 4. Reopen the file: the style has no page break Actual Results: Page breaks both in paragraph and paragraph style are lost Expected Results: Page breaks retained as in original file Reproducible: Always User Profile Reset: Yes Additional Info: In RTF file the \pagebb keyword should be saved both in style and paragraph definition. Similar, but different from Bug 116753
Created attachment 157477 [details] Original file
Created attachment 157478 [details] File saved as RTF
Surprising result: 1. I opened file frome attachment in comment 1 2. I changed paragraph style of text "Heading 4 - Page break before" to Heading 3 style 3. I saved as rtf and reopened Result: All page breaks are lost in paragraph styles, but page break remains in paragraph "Heading 4 - Page break before" Version: 7.0.0.0.alpha0+ (x64) Build ID: eeb2d19e77d6dc47c68e8ba0920a02cf64a1247b CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB Calc: threaded => NEW
(In reply to Dieter Praas from comment #3) > Surprising result: > > 1. I opened file frome attachment in comment 1 > 2. I changed paragraph style of text "Heading 4 - Page break before" to > Heading 3 style > 3. I saved as rtf and reopened > > Result: All page breaks are lost in paragraph styles, but page break remains > in paragraph "Heading 4 - Page break before" > > Version: 7.0.0.0.alpha0+ (x64) > Build ID: eeb2d19e77d6dc47c68e8ba0920a02cf64a1247b > CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; > Locale: de-DE (de_DE); UI-Language: en-GB > Calc: threaded > > => NEW Hi Dieter. Line "Heading 4 - Paragraph page break before" has a page break assigned directly to the paragraph, not to the style: I think this explains the different behaviour.
Bug still present in Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Bug still present Version: 7.3.7.2 (x86) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded I added with a text editor the keyword \pagebb in the following rtf command ad it worked. {\s1\sbasedon15\snext16\dbch\af5\dbch\af7\afs36\ab\ilvl0\outlinelevel0\sb240\sa120\keepn\pagebb\loch\f4\fs36\b Titolo 1;} Hope this helps.
Dear Marco, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still present Version: 25.8.4.2 (X86_64) Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df CPU threads: 22; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: CL threaded