My favorites | Sign in
Project Logo
                
New issue | Search
for
| Advanced search | Search tips
Issue 175: Titles and contents are separated by pagebreaks
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  roberto.alsina
Closed:  Sep 08
Type-Defect
Priority-Low


Sign in to add a comment
 
Reported by roberto.alsina, Aug 29, 2009
In some cases, titles end at the bottom of a page, and the section 
contents start in the next page.

That is not correct.

See test_issue_175.txt for an example.

Comment 1 by roberto.alsina, Aug 29, 2009
Test committed in r916
Status: Started
Comment 2 by roberto.alsina, Aug 29, 2009
I think this is the problem:

When you create a title, the title itself has "KeepWithNext" set, but here is the 
sequence of flowables:

Reference
KeepTogether ( Paragraph [heading] )
OutlineEntry
Paragraph [content]

So: 

1) The KeepTogether is pretty useless
2) Even if KeepWithNext works, it's consumed by the OutlineEntry

I need to kkep in mind that if the OutlineEntry, the reference and the heading 
paragraph are not in the same page, something else is broken! 

Comment 3 by roberto.alsina, Aug 29, 2009
Probably fixed in r917
Comment 4 by roberto.alsina, Aug 29, 2009
(No comment was entered for this change.)
Status: Fixed
Comment 5 by roberto.alsina, Aug 29, 2009
Grmbl, the PDF TOC is now wrong in that test case :-(
Status: Accepted
Comment 6 by roberto.alsina, Aug 29, 2009
A better fix is in r919
Comment 7 by roberto.alsina, Aug 29, 2009
As of r921 the original test case is fixed, but this happens in demo.txt (Section 1).
Labels: -Priority-Medium Priority-Low
Comment 8 by roberto.alsina, Aug 29, 2009
Made the test case fail for that specific bug.
Comment 9 by roberto.alsina, Aug 31, 2009
I think this is really, really, really fixed in r926
Comment 10 by roberto.alsina, Aug 31, 2009
(No comment was entered for this change.)
Status: Fixed
Comment 11 by roberto.alsina, Aug 31, 2009
Grmbl, not quite fixed. Works in my test cases, fails in demo.txt. 
Status: Accepted
Comment 12 by roberto.alsina, Sep 08, 2009
This seems to be caused by a Reference inserted in createpdf.py at line 1565.
However, those references *are* useful, because if they are not there, some internal 
targets will not be resolved.
Comment 13 by roberto.alsina, Sep 08, 2009
Fixed in r1002
Status: Fixed
Sign in to add a comment

Hosted by Google Code