Re: Do Fop have problems with keep-with-...?
Steinar Bang [EMAIL PROTECTED]: J.Pietschmann [EMAIL PROTECTED]: [snip!] If you are generating FO from DocBook, this will probably be hard, or harder. You can try to fiddle with the docbook style sheets to achieve this effect. Some workaround around those lines, is what I will try tomorrow. What I did was to put beginpage/ elements at appropriate places in the DocBook XML source, to force line breaks _before_ the problematic sections. This is a hack, because it is vulnerable to changes to the XML source. But it is less ugly than the other hacks on the table, and I'll remove the beginpage/ elements when Fop supports keep-*. I noticed that the DocBook XSL style sheets didn't have a template for beginpage, so I put the following in my local FO-producing style sheet: xsl:template match=beginpage fo:block break-after=page/ /xsl:template
Re: Do Fop have problems with keep-with-...?
Steinar Bang wrote: Does Fop still have a problem with keep-with-*? Yes, and this will persist for some time. I have a problem with the title of a section, in a DocBook XML article, not sticking with the rest of the section, when a page break is inserted. The keep-with-* properties work on table rows. The usual recommendation is to use a two row, one column blind table and put the title in the first and the first paragraph in the second row. If you are generating FO from DocBook, this will probably be hard, or harder. You can try to fiddle with the docbook style sheets to achieve this effect. If you are at it, you can fix a few other problems DocBook generated have (fo:table-and-caption, references to fo:page-sequence and to fo:block with a break-before) Your alternative is to use a commercial FO processor. J.Pietschmann
Re: Do Fop have problems with keep-with-...?
J.Pietschmann [EMAIL PROTECTED]: [snip!] If you are generating FO from DocBook, this will probably be hard, or harder. You can try to fiddle with the docbook style sheets to achieve this effect. Some workaround around those lines, is what I will try tomorrow. I won't fiddle with the DocBook XSL style sheets directly, but I will replace a template or several templates, in a local XSL style sheets. The local style sheet is already in place. This is where I set the page size to be a4 instead of the default letter, and this is where I override the standard table template, to fix stuff. If you are at it, you can fix a few other problems DocBook generated have (fo:table-and-caption, Already done in the local style sheet, see http://marc.theaimsgroup.com/?l=fop-userm=101829073309486w=2 references to fo:page-sequence and to fo:block with a break-before) What are the problems with these? I haven't run into them yet. Your alternative is to use a commercial FO processor. Or PassiveTex, perhaps...? http://www.hcu.ox.ac.uk/TEI/Software/passivetex/ But I think I would miss the SVG rendering of Fop.
