I still have a lot of errors using FOP in 0.92beta or better from Trunk I think. Since a while I can't update from Trunk: TortoiseSVN said: Error: PROPFIND request failed on '/repos/asf/xmlgraphics/fop/trunk' Error: PROPFIND of '/repos/asf/xmlgraphics/fop/trunk': could not connect to server (http://svn.apache.org) Anything wrong with the server? Last year it worked fine.
First message I got while converting a XML to PDF is org.apache.fop.fo.flow.TableColumn bind WARNING: table-layout="fixed" and column-width unspecified => falling back to proportional-column-width(1) Deleting table-layout="fixed" because it is not supported (http://xmlgraphics.apache.org/fop/compliance.html#fo-property-table-layout), produces another error/warning: WARNING: Warning(Unknown location): fo:table, table-layout="auto" is currently not supported by FOP 04.01.2007 11:11:34 org.apache.fop.fo.PropertyList convertAttributeToProperty FATAL: Ignoring property: column-width="proportional-column-width(1)" (proportional-column-width() function may only be used when fo:table has table-layout="fixed".; property:'column-width') What does this mean? Using column-with in fo:table which is supported by FOP (http://xmlgraphics.apache.org/fop/compliance.html#fo-property-column-width) without table-layout="fixed" produces an error. And using it with table-layout="fixed" because this is not support produces also an error. Somebody is understanding this? And table-layout="auto" are also not supported. Next error seems to mean that the first row of a table is taller than the row should be: org.apache.fop.layoutmgr.table.TableContentLayoutManager createElementsForRowGroup WARNING: The contents of row 1 are taller than they should be (there is a block-progression-dimension or height constraint on the indicated row). Due to its contents the row grows to 76820 millipoints, but the row shouldn't get any taller than MinOptMax[min=opt=max=14000] millipoints. (fo:table-row, no context info available) For some tables I specified a column-width, maybe this could be the error. But I do not specified the widths in millipoints but used proportional measure. So, there should be no taller row than they should be, or !? After the next rows the error causes with FOP in the FO-File <fo:table-column column-number="1" column-width="proportional-column-width(1)"/> <fo:table-column column-number="2" column-width="proportional-column-width(0)"/> <fo:table-column column-number="3" column-width="proportional-column-width(1)"/> <fo:table-body><fo:table-row height="14pt"> Another error seems to have a problem with the PageBreakingAlgorithm: org.apache.fop.layoutmgr.PageBreakingAlgorithm updateData2 WARNING: Part/page 1 overflows the available area in block-progression dimension. (fo:static-content, no context info available) To engender a PageBreak, I'm using <fo:block break-after="page"/>. For the time being last error: org.apache.fop.layoutmgr.StaticContentLayoutManager doLayout WARNING: static-content overflows the available area. (fo:static-content, no context info available) While writing this rows I found out, that this error occurs in the following row of the generated FO-File: <fo:page-sequence xmlns:axf="http://www.antennahouse.com/names/XSL/Extensions"; master-reference="body" hyphenate="true" language="de" format="1" initial-page-number="1" force-page-count="no-force" hyphenation-character="-" hyphenation-push-character-count="2" hyphenation-remain-character-count="3"> <fo:static-content flow-name="xsl-region-before-first"> <fo:block font-family="Arial, Helvetica, sans-serif,Symbol,ZapfDingbats" margin-left="0pt"> <fo:table width="100%" table-layout="fixed"> <fo:table-column column-number="1" column-width="proportional-column-width(1)"/> <fo:table-column column-number="2" column-width="proportional-column-width(0)"/> <fo:table-column column-number="3" column-width="proportional-column-width(1)"/> <fo:table-body> ... I don't know why this error occurs. This XSL:FO is generated from the Docbook-XSL I think. Maybe these are all trivial errors/warings -> However PDF is generated. But it let being to suspicious. Has anybody some explanations? Or these are just faults whereof is still working? Thanks a lot! Best Regards, Leeloo __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
