[dbdoclet] Re: Page breaks and orphan headings

Hi Michael,

a PI like that might help, if it is something that FOP can understand. =
Of course it should be controllable by an option, just in case someone =
wants to have the class descriptions run back to back.

It seems that (at least by default) dbdoclet creates a sect1 element for =
each class/interface. It would probably be enough to stick the PI before =
each sect1 that actually is a class. I managed to get a page break in =
the PDF by inserting a custom PI (one that inserts a <fo:block =
break-before=3D'page'/> element), but I don't want to do that manually =
for every class...

What would one then have to do configuration-wise to make FOP recognize =
the PIs and get them in the PDF?

As for the FOP keep-before-next problem, since FOP does not seem to be =
going anywhere currently, I'm tempted to pick up a license of either XEP =
by RenderX or AntennaHouse's XSL Formatter. They claim to support full =
XSL-FO, and I keep hearing good things about them. Of course I could =
just dive in and implement the rest of FOP's missing XSL-FO, but I am =
just a timeless mortal. :(

--Jere

> -----Original Message-----
> From: ext Michael Fuchs [mailto:michael.fuchs@xxxxxxxxxxxxxxx]
> Sent: Wednesday, December 08, 2004 12:53 PM
> To: dbdoclet@xxxxxxxxxxxxx
> Cc: Kapyaho Jere (Nokia-TP-MSW/Tampere)
> Subject: Re: [dbdoclet] Page breaks and orphan headings
>=20
>=20
> Hello,
>=20
> >To get each class or interface description to start on a new=20
> page, I can =3D
> >put a "break-before" attribute for sect1 in my customization layer. =
=3D
> >However, the constant fields appendix is then messed up, and=20
> so is my =3D
> >part 1, the descriptive text. Is there a simpler solution=20
> than creating =3D
> >custom page masters?
>=20
> would it help if dbdoclet inserts a processing instruction=20
> like <?dbdfo class-separator=3D"page-break"?>
> before each sect1?=20
>=20
> >There seem to be quite a lot of orphan headings in the PDF,=20
> for example =3D
> >a method name is often the last line on the page, and the method =3D
> >description starts on the next page. Bob Stayton wrote on the =3D
> >docbook-apps mailing list that it is a FOP problem (no support for =
=3D
> >keep-with-next). Can you confirm this? Any suggestions on=20
> another FO =3D
> >processor that handles this properly?
>=20
> Until now I always used fop and I know the problem :-(. I=20
> think you should ask this question in the=20
> docbook-apps mailinglist.=20
>=20
> Regards
> Michael
>=20
>=20

Other related posts: