docbook-apps

Hi all,

We've updated our DocBook->PDF build process from fop 0.25 to 0.92beta, involving:

* DocBook XSL 1.70.1
* a customised layer
* Saxon 6.5.5
* FOP 0.92beta

So far the following issue(s) are preventing PDFs from being built:

[fop] 16-Nov-2006 15:37:19 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 1/39832)
[fop] 16-Nov-2006 15:37:19 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 1/40066)
[fop] 16-Nov-2006 15:37:19 org.apache.fop.fonts.FontInfo notifyFontReplacement
[fop] WARNING: Font 'ArialBlack,normal,400' not found. Substituting with default font.
[fop] 16-Nov-2006 15:37:20 org.apache.fop.fonts.FontInfo notifyFontReplacement
[fop] WARNING: Font 'Arial,normal,700' not found. Substituting with default font.
[fop] 16-Nov-2006 15:37:20 org.apache.fop.fonts.FontInfo notifyFontReplacement
[fop] WARNING: Font 'ZapfDingbats,italic,400' not found. Substituting with default font.
[fop] 16-Nov-2006 15:37:21 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 82/435)
[fop] 16-Nov-2006 15:37:21 org.apache.fop.fonts.FontInfo notifyFontReplacement
[fop] WARNING: Font 'LetterGothic,normal,400' not found. Substituting with default font.
[fop] 16-Nov-2006 15:37:21 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 103/442)
[fop] 16-Nov-2006 15:37:21 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 103/1349)
[fop] 16-Nov-2006 15:37:21 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 103/2246)
[fop] 16-Nov-2006 15:37:21 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 124/454)
[fop] 16-Nov-2006 15:37:21 org.apache.fop.fonts.FontInfo notifyFontReplacement
[fop] WARNING: Font 'LetterGothic,italic,400' not found. Substituting with default font.
[fop] 16-Nov-2006 15:37:22 org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
[fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 165/333)
[fop] 16-Nov-2006 15:37:22 org.apache.fop.cli.InputHandler error
[fop] SEVERE: javax.xml.transform.TransformerException: Some content could not fit into a line/page after 50 attempts. Giving up to avoid an endless loop. (fo:list-item, location: 163/1562)

The main SEVERE one is described in this FOP bug:

http://issues.apache.org/bugzilla/show_bug.cgi?id=39840

Jeremias says this is due to the fact that the "document is littered with keeps". This appears to be a result of using DocBook XSL 1.70.1. Does anyone know if later versions of DocBook XSL are compatible with FOP 0.92 or later?

Thanks,

P.

On 11/20/06, Paul Moloney <paul_moloney@hotmail.com> wrote:
> Jeremias says this is due to the fact that the "document is littered with
> keeps". This appears to be a result of using DocBook XSL 1.70.1. Does anyone
> know if later versions of DocBook XSL are compatible with FOP 0.92 or later?


Here's a section from Bob's book on this:
"Note in particular that the last attribute inherited from
formal.object.properties adds a keep to the table block. This keeps
the table title with the table, but it also means the table will be
forced to a new page if the whole table doesn't fit on the current
page. That may be inappropriate for long tables that could start on
the current page. For individual tables, you can use a processing
instruction to allow a table to break, as described in the section
"Keep-together processing instruction". Or you can change the
attribute value to auto to turn off the keep for all tables, and use
the PI in individual tables to keep them together. This change can be
made in the table.properties attribute-set. You don't have to worry
about keeping a table's title together with the table, because the
title block itself has a keep-with-next property."

http://www.sagehill.net/docbookxsl/PrintTableStyles.html#table.properties

I'd try setting the keep-together.within-column to auto, as he
suggests, and seeing if the bug persists.


HTH,
Keith