0

Controlling page flow in PDF - "keep-with-next"

phsteyt

18 March 2009 05:34

None

Follow

Hello

I am now in the polishing phase of the PDF manual that is generated along the online Help system I have constructed with HS3.

My concern is that many titles appear as last lines in pages, while I would of course like to keep them togheter with the first next item (the first next paragraph, a subtitle with its own first next paragraph, ..).

I did not manage to use the "keep-with-next" CSS parameter (actually a CSS2 feature): it creates an error while compiling the pdf.

Any idea how I could manage to achieve a better text flow control?

Thanks a lot in anticipation

P-H

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Mike Shaw (Innovasys) 18 March 2009 05:43

  Hello,

  There is a PDF setting for Page Breaks which can be found in the Booklet Settings. The options are "Before Top Level Entries" and "Before All Entries".

• 0
  
  phsteyt 18 March 2009 05:54

  Ok - I see - Thanks for the tip

  However, as I have a very finely granulated document, this results in having numerous pages 1/2 or 2/3 empty ...

  If I may suggest, being able to set the page breakdown a Top, Topic, H1, H2 or ... level could be useful in a case like mine (hint, hint, hint...)

  Have a good day

  P-H

• 0
  
  Mike Shaw (Innovasys) 18 March 2009 06:11

  A workaround for this would be to place the following HTML before each heading that isn't behaving correctly:
  
  <p style="page-break-after:always">&nbsp;</p>
  
  

• 0
  
  phsteyt 18 March 2009 07:25

  ... Just tried - it indeed does the job. However, it is very demanding since I need to

  1. locate the first orphan title in my pdf
  2. go back to the html and apply the trick to push the title to the next page (... and everything following)
  3. generate the pdf
  4. locate the next orphan
  5. go back to the html and insert the page break
  6. generate the pdf
  7. ... etc

  And my document has over 220 pages...

   ... and this would need to be redone at each revision (1 monthly revision minimum...)

  I keep this as a fallback solution - but of course a generic CSS solution would make my life way easier....

  Thanks all the same - I keep this trick for another usage anyway...