forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-402) Specify page breaks in XML source
Date Fri, 03 Dec 2004 22:58:29 GMT
The following comment has been added to this issue:

     Author: Dave Brondsema
    Created: Fri, 3 Dec 2004 4:56 PM
Try <section class="page"> with no extra-css required.  I think it'll work, but I don't
have time to try right now.

This is an undocumented "feature" I put in so that wholesite.pdf could have breaks per-page.
 If this works and is useful, we should make the class name more unique, and documente the
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-402
    Summary: Specify page breaks in XML source
       Type: New Feature

     Status: Unassigned
   Priority: Trivial

    Project: Forrest
             Skins (general issues)

   Reporter: Ross Gardler

    Created: Fri, 3 Dec 2004 8:23 AM
    Updated: Fri, 3 Dec 2004 4:56 PM

>From a mail to the users list by Jacques, Olivier (OCBU-Test Infra):

> As per suggested in the documentation, here is why I wanted to create a new skin: insert
page breaks at certain points in the document.
> This is done using CSS with the attribute: "page-break-before: always"
> So I did, in "mytigris.css":
> h3, h4 {
>  margin-bottom: 0;
>  page-break-before: always;
> }
> It would be great to have this hability from within the document XML source.

Yes, I have often thought this (although in my case it is for PDF output I want control).

You can do this in HTML without the need to create a new skin by using classes:

For example:

<h1 class="pageBreakBefore">

Then in skinconf.xml <extra-css> you put:

.pageBreakBefore {
 margin-bottom: 0;
 page-break-before: always;

To respect those classes in PDF will require changes in the Formatting Object stylesheets.
I think this an excellent enhancement so I will add it to the issue tracker.


This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message