> This behaviour is correct indeed, because, for example:
> [...]
cool thanks for the info!
> [...]
> Beware: untested, and without doing the same for the table-cells,
> this will only work if the cells' content is not split over multiple
> pages... :/
i'got that working even with cells over tow pages. good to know how to
realise this without border-collapse... anyway the attribute:
> border-separation="0pt"
causes fop to throw the following exception (but the solution works fine
without the attribute):
11.06.2006 15:31:28 org.apache.fop.cli.Main startFOP
SCHWERWIEGEND: Exception
java.lang.NullPointerException
at
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:167)
at
org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:114)
at org.apache.fop.cli.Main.startFOP(Main.java:159)
at org.apache.fop.cli.Main.main(Main.java:190)
---------
java.lang.NullPointerException
at
org.apache.fop.fo.properties.CompoundPropertyMaker.convertProperty(CompoundPropertyMaker.java:172)
at org.apache.fop.fo.properties.LengthPairProperty
$Maker.convertProperty(LengthPairProperty.java:61)
at
org.apache.fop.fo.properties.PropertyMaker.make(PropertyMaker.java:441)
at
org.apache.fop.fo.properties.CompoundPropertyMaker.make(CompoundPropertyMaker.java:212)
at
org.apache.fop.fo.PropertyList.convertAttributeToProperty(PropertyList.java:348)
at
org.apache.fop.fo.PropertyList.addAttributesToList(PropertyList.java:304)
at org.apache.fop.fo.FObj.processNode(FObj.java:118)
at org.apache.fop.fo.FOTreeBuilder
$MainFOHandler.startElement(FOTreeBuilder.java:308)
at
org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:184)
at
org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1072)
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.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484)
at
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:164)
at
org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:114)
at org.apache.fop.cli.Main.startFOP(Main.java:159)
at org.apache.fop.cli.Main.main(Main.java:190)
> That's a valid approach, but it seems a bit like overkill if you know
> that it is (should be) possible in XSL-FO directly.
i need the xslt anyway for realising some pseudo table header (thats
another story) this leads to cells fitting on one page...
cheers,
gregor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
