Last modified: 2011-03-13 18:04:32 UTC
Currently when writing a collection, chapter headers are placed on a semi-colon indicated line, and modules are placed on a colon indicated line. When rendering however, the PDF converter places the contents of the semicolon line at the top of the first page of the chapter, making the chapter start page busier. Using a page eject after rendering the semicolon line, would make the chapter start page much more readable and would create a title page for the chapter.
I guess you are using the chapter title to add quite a bit of text as an introduction for a chapter. Is that correct? From our experience this is contrary how chapters are "normally" used. Therefore I think this should not be changed I believe you might want to add an introductory article right after the chapter to achieve what you want. Could you please supply an example if my assumptions of what you are trying to do are wrong.
Actually no, I am using the same module name as the chapter name, and the result is that I get three lines (if the chapter header is in sync) all saying the same thing at the top of the page in different styles. Header with underline Chapter Title with top and bottom lines Chapter Title with underline Text If you moved the chapter title with top and bottom lines off of the page it would look neater Header with Underline Chapter title with top and bottom lines Page/break Header with Underline Chapter Title with Underline Text Does that make better sense?
I guess generally it is more desirable to *not* have a page break right after a chapter starts. (At least that is the standard way in most books) But I changed one thing which hopefully makes the "chapter-start-page" look nicer: on the page where a chapter starts the header is omitted. This also seems to be standard for regular books. I am closing this bug, since I believe for the majority of users it is not desirable to have a page break after the chapter start. Once the pdf rendering is customizable via the collectionpage this could be a per-user option. I have updated the respective ticket in our bugtracker: http://code.pediapress.com/wiki/ticket/419#comment:9
