Bug 75296 - Writer tables sometimes split over page when they shouldn't be
Summary: Writer tables sometimes split over page when they shouldn't be
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 4.2.0.3 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-21 04:37 UTC by Jim Avera
Modified: 2015-01-24 13:33 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Screenshot showing table inappropriately broken over page boundary (104.94 KB, image/png)
2014-02-21 04:37 UTC, Jim Avera
Details
Demo .odt file showing problem. See last table at the end. (47.73 KB, application/vnd.oasis.opendocument.graphics)
2014-02-21 04:38 UTC, Jim Avera
Details
Screen shot showing table inappropriately broken over page boundary (104.94 KB, image/png)
2014-02-21 04:40 UTC, Jim Avera
Details
test document with the right extension (.odt) (47.73 KB, application/vnd.oasis.opendocument.text)
2014-02-21 06:03 UTC, Jean-Baptiste Faure
Details
Demo .odt file using Times New Roman font (49.98 KB, application/vnd.oasis.opendocument.text)
2014-02-21 21:06 UTC, Jim Avera
Details
Screen shot of the demo using Times New Roman (111.72 KB, image/png)
2014-02-21 21:07 UTC, Jim Avera
Details
Table Demonstration (57.66 KB, application/pdf)
2014-03-02 17:17 UTC, Joel Madero
Details

Description Jim Avera 2014-02-21 04:37:57 UTC
Created attachment 94472 [details]
Screenshot showing table inappropriately broken over page boundary

In some circumstances Writer tables are are split across a page boundary even though the Table style does not have "allow table to split across pages" checked, and the table is quite small (it could easily fit on the next page).

Empirically it seems related to borders being turned on for only some of the cells in the table.

Please view the attached screen-shot and the demo .odt file.
Comment 1 Jim Avera 2014-02-21 04:38:37 UTC
Created attachment 94473 [details]
Demo .odt file showing problem.  See last table at the end.
Comment 2 Jim Avera 2014-02-21 04:40:04 UTC
Created attachment 94474 [details]
Screen shot showing table inappropriately broken over page boundary
Comment 3 Jim Avera 2014-02-21 04:43:24 UTC
For some reason bugzilla is not auto-detecting attachment file types correctly.  I re-did the screenshot and manually specified png, but don't know how to make the .odt file appear as a writer doc, not a presentation (sorry)
Comment 4 Jean-Baptiste Faure 2014-02-21 06:03:57 UTC
Created attachment 94476 [details]
test document with the right extension (.odt)

I renamed your test document as odt file instead of odg.

Best regards. JBF
Comment 5 Jean-Baptiste Faure 2014-02-21 06:10:43 UTC
Not reproducible for me with version 4.2.3.0.0+ under Ubuntu 13.10 x86-64.
The file fits on two pages, but I do not have Carlito font installed.

Please could you create a test document with a more standard font ?

Best regards. JBF
Comment 6 Jim Avera 2014-02-21 21:06:06 UTC
Attached is an example using Times New Roman font exclusively.
The demo is also shorter, with the table broken between the first & second pages.
I'll also attach a screen-shot for this new example.

(BTW, is 4.2.3.0.0+ available for download anywhere?  I didn't see it on the LO QA-builds page)
Comment 7 Jim Avera 2014-02-21 21:06:50 UTC
Created attachment 94533 [details]
Demo .odt file using Times New Roman font
Comment 8 Jim Avera 2014-02-21 21:07:41 UTC
Created attachment 94534 [details]
Screen shot of the demo using Times New Roman
Comment 9 Joel Madero 2014-03-02 17:17:06 UTC
Attaching a document - is this not correct? I Don't see any split.

Ubuntu 13.10
LibreOffice 4.2.1 release
Comment 10 Joel Madero 2014-03-02 17:17:36 UTC
Created attachment 94971 [details]
Table Demonstration
Comment 11 Jim Avera 2014-03-02 22:18:45 UTC
Hmm.  We are seeing different results for some reason.

Joel, was the "Table Demonstation" pdf created from "test document with the right extension (.odt)"?   With 4.3.0.0.alpha0+ I'm still seeing breakage.

Is there a way I can create a new "profile" with default settings?  Maybe there is something in my installation which affects rendering.   Or maybe fonts...
(but still, LO shouldn't break such tables regardless of font metrics).

Anyone have any ideas how to track down why Joel & I get different results?
Comment 12 Joel Madero 2014-03-02 22:21:59 UTC
I used 4.2.1.1 release not 4.3 build :)

I used your test document, just downloaded and printed to pdf.

For dealing with the profile: https://wiki.documentfoundation.org/UserProfile
Comment 13 Joel Madero 2014-03-02 22:22:48 UTC
and there is no 4.2.3, that must have been a mistake by JBF - perhaps 4.3 daily not 4.2.3
Comment 14 sophie 2014-03-21 13:55:06 UTC
Hi, it is ok also for me using Version: 4.2.3.1
Build ID: 3d4fc3d9dbf8f4c0aeb61498a81f91c5b7922f13 and Ubuntu 13.10/Gnome 3. 
I'm not sure but your problem may be because of section 1 being a subsection of section 3 that places a not visible space on the page and makes the table flow for you. Also the even distribution between columns may cause the flow of the two columns in section 3. Section 2 seems to have no influence and to be not useful too. 
So nobody could reproduce - set as worksforme - Sophie
Comment 15 Jim Avera 2014-03-27 18:53:35 UTC
I tried the Times Roman demo again on 4.2.4.0.0+ and 4.3alpha and still get a table broken over a page boundary.

There has to be something in my environment (fonts? Options settings?)
which is different than the other testers.   But I'm stumped for ideas
how to figure out what it is.
Comment 16 Jim Avera 2014-03-27 19:03:56 UTC
I tried deleting my profile (actually, renamed the profile directory $HOME/.config/libreoffice/4/user) but it made no difference.

BTW, a new profile directory was not created; is that normal?
I'm certain no libre* processes were running when the profile dir was renamed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.