I'll see about getting newer Docbook XSL setups and customizing them for table widths.
Funny thing is, I don't know that I even *have* any tables, at least not that I put in myself...

Anyway, here's the stack trace:


[ERROR] null
org.apache.fop.apps.FOPException
        at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:74)
        at org.apache.fop.apps.Fop.main(Fop.java:19)

---------

java.lang.NullPointerException
        at org.apache.fop.fo.PropertyManager.getTextDecoration(PropertyManager.java:328)
        at org.apache.fop.fo.FObjMixed.<init>(FObjMixed.java:28)
        at org.apache.fop.fo.flow.Block.<init>(Block.java:72)
        at org.apache.fop.fo.flow.Block$Maker.make(Block.java:37)
        at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:255)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.fop.apps.Driver.render(Driver.java:457)
        at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:69)
        at org.apache.fop.apps.Fop.main(Fop.java:19)

---------

java.lang.NullPointerException
        at org.apache.fop.fo.PropertyManager.getTextDecoration(PropertyManager.java:328)
        at org.apache.fop.fo.FObjMixed.<init>(FObjMixed.java:28)
        at org.apache.fop.fo.flow.Block.<init>(Block.java:72)
        at org.apache.fop.fo.flow.Block$Maker.make(Block.java:37)
        at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:255)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.fop.apps.Driver.render(Driver.java:457)
        at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:69)
        at org.apache.fop.apps.Fop.main(Fop.java:19)



On Fri, 2003-02-21 at 13:35, J.Pietschmann wrote:
Aaron Weber wrote:
> [INFO] area contents overflows area
This happens if, well, the contents overflows the allocated area.
Usually caused by long words and word-like strings in table cells.

> [ERROR] null
Possibilities
- Most often, a mandatory (for FOP) property was not set.
- Footnotes on the last page which did not fit that page.
- Unspecified problems with markers.
Run FOP with the -d flag to get a stacktrace, and post the
first few lines here.

> Any tips? I'll try & get rid of the offending table-layout issues,
> but... I don't know about adding table-column width attributes to every
> table in the document.
Upgrade to the latest DocBook XSL, which fixes many issues.
Also, you can specify table column widths in DocBook, check
the DocBook documentation.

J.Pietschmann


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to