Created attachment 143223 [details]
picture showing page break problem
in different versions of LO like LO 220.127.116.11 and before I am getting occationally problems like shown in the picture.
A table is put in and the page break is ok at first. But then somehow this changes like shown. Its not so easy getting this fixed again.
Created attachment 143224 [details]
picture 2 showing page break problem
as can be seen there is really much enough space there for the table to do not split this way. It does not make sense splitting a table this way by an automatic procedure. This is considered as being a unwanted behaviour - a fault.
unfortunately I do not have a test file for that at the moment to attach.
Looking into the attachments I would agree, that table split is not necessary. But without a sample file or clearer steps I don't know could be possible to reproduce the bug => Set to NEEDINFO
BTW: I often had the case, that a table is split, although "allow table to split" is unchecked. I often cpuld solve the probllem when I first enable and then directly disable this option.
I really hope that not only I do have this problem. I have several books and found it really annoying that sometimes when opening the file the page break changes. So I have to check for this each time before I am building a pdf from it. Also the page numbering then changes.
I could be a problem with insufficient memory. There is 4GB or more installed but sometimes this seems not be enough. If I do no real win 7 restart over several days it may happen more often.
Please attach a sample document, as this makes it easier for us to verify the bug.
(Please note that the attachment will be public, remove any sensitive information before attaching it.
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 143539 [details]
picture 3 showing page break problem
same problem to see.
"Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it.)"
I clearly understand this wish !
Unfortunately those are my own books that I need to earn money with. Therefore I am unable posting the content here.
Unfortunately I have not been able yet producing a test file where this always is possible to show. May be someone else is able doing so?
(In reply to Dr. Matthias Weisser from comment #6)
> "Please attach a sample document, as this makes it easier for us to verify
> the bug. (Please note that the attachment will be public, remove any
> sensitive information before attaching it.)"
Make a copy of the problematic file and replacing everything with "x":
The basic plan is to replace all characters with a "x". We can (try to) do this with "Find & Replace".
Edit ▸ Find & Replace (Ctrl+H)
In the Search for field put "." (a single period)
In the Replace with field put "x"
Make sure Whole words only is unchecked
Click Other Options to expand the dialog, and make sure Regular expressions is checked.
Click Replace All
Now you have a document containing lots of "x"s. With luck, the bug still will be reproducible with that document.
More about Sanitizing https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission
(In reply to Telesto from comment #7)
> Make a copy of the problematic file and replacing everything with "x":
Thank you Telesto !
I tried doing such tricks. But unfortunately the pages then had some other size. Therefore the page break changed. I could not use this.
> With luck, the bug still
> will be reproducible with that document.
unfortunately I did not have this luck. Even with the original document the problem was not there all the time. Sometimes it came.
Which file format do you use for your documents ? ODF or OOXML?
Please check the following option of the paragraph styles: in the Text Flow tab the option "Keep with the next paragraph". Generally, this option should be checked only for heading styles.
Status set to NEEDINFO, please set it back to UNCONFIRMED once requested
informations are provided.
Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #9)
> Which file format do you use for your documents ? ODF or OOXML?
I use .odt
> Please check the following option of the paragraph styles: in the Text Flow
> tab the option "Keep with the next paragraph". Generally, this option should
> be checked only for heading styles.
I do not see a problem with normal paragraphs - only with tables. There is a menu "Tabelleneigenschaften Textfluss" where the point "Trennung der Tabelle an Seiten- und Spaltenenden zulassen" is checked.
If the table is too long this should be checked. Normally I do not see a problem with tables even if this is checked. Only sometimes this problem happens. Then it had been quite hard getting fixed. With a long text its time consuming checking the whole text each time before making a new pdf file for errors like that.
Sorry, but until you manage to produce an example file, this cannot progress. I understand the bug does not show itself reliably, but you have to keep trying to produce a minimal example.
This will stay in NEEDINFO and will be closed as INSUFFICIENTDATA, if you never manage to create such a document.
"if you never manage to create such a document."
this is not a problem creating a document. I have several of them. But all are confidential.
Even it I change the characters this will not help much because this really seems to be a memory related problem.
I will still have a look at this. May be I will find something where this shows more often. I am sure that I am not the only one experiencing this.
Dear Dr. Matthias Weisser,
Do you think you could send one of the problematic documents to my email privately? That way I could investigate the issue...
I'm the QA engineer at The Document Foundation and it will be kept confidential.
of course I can do a very private version for you. But I am not so sure if you will be able to replicate this. It does not seem to be so easy. 2 days ago I opened a file and the problem was there with one table at opening. It then disappeared when I edited in one place.
The bad thing with this is that one cannot be sure what the document will look like when doing a pdf. All pages have to be checked first which is really time consuming.
[Automated Action] NeedInfo-To-Unconfirmed
Hello Matthias, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
I'll close. No need to open because there are similar open bugs. Rule of thumb is search before reporting. Although reflow bugs are not easy to find.
Thank you Timur and Dieter !
The problem is that I cannot easily test newer versions because they seem to need more memory than the 5 version did. Therefore I had to stay with LO 18.104.22.168. There are problems with this - but somehow I am able to work.
Its a pity that it had not been possible fixing this in 5. Its there so many years. Still I have to go through nearly all pages in my books before I am able doing a pdf. When I do not do this there are more pages because of faulty page break ! Its time consuming searching all 300 or even 700 pages this way !!