This first error saying text-align="char" looks like an attempt to use the feature of CALS tables that would align columns along a certain character, such as a "." for decimal point. This is specified on a table's colspec with

align="char" char="."

This should generate text-align="." for that table column. Unfortunately, text-align is listed in the FOP compliance document [1] as only partially supported:

"Only start, end, center and justify are supported"

The fact that your error message says text-align="char" suggests the table column was coded in the XML as

align="char" char="char"

Is that the case?


Bob Stayton
Sagehill Enterprises

On 2/14/2018 6:14 AM, Bernhard Kleine wrote:
I have successfully transformed all the different chapters of the book and the appendix. Still when transforming the entire book I get two errors. The one about png as before and

ERROR - Invalid property value encountered in text-align="char": file:/K:/BuchprojektSpringer/VierteAuflageXmlDeutsch/Lehrbuch.xml_xslt:5447:5425: No conversion defined char; property:'text-align' (Siehe Position 5447:5557) file:/K:/BuchprojektSpringer/VierteAuflageXmlDeutsch/Lehrbuch.xml_xslt:5447:5425: No conversion defined char; property:'text-align' at at at at at at$MainFOHandler.startElement( at at net.sf.saxon.event.ContentHandlerProxy.startContent(Unknown Source) at net.sf.saxon.event.NamespaceReducer.startContent( at net.sf.saxon.event.ComplexContentOutputter.startContent( at net.sf.saxon.event.ReceivingContentHandler.startElement( at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource( at net.sf.saxon.event.Sender.send( at net.sf.saxon.jaxp.IdentityTransformer.transform( at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP( at org.apache.fop.cli.Main.main(

 BTW I would accept these error messages when they could point to the place they occur. The way it is now is totally unhelpfull, from the stone age of computing like MS Windows 3.1 error messages!


D-79853 lenzkirch,
thunderbird mit enigmail
GPG schlüssel: D5257409
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

oXygen-user mailing list

oXygen-user mailing list

Reply via email to