[Xmlgraphics-fop Wiki] Update of "Troubleshooting/CommonLogMessages" by LouisMasters

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.

The following page has been changed by LouisMasters:
http://wiki.apache.org/xmlgraphics-fop/Troubleshooting/CommonLogMessages

The comment on the change is:
First try at a troubleshooting page for log messages

New page:
##language:en
== Troubleshooting Common Log Messages ==

This page will try to explain the more common information, warning and error messages encountered when using FOP 0.91.

== Information Messages ==

These messages provide general feedback on FOP and inform the user of possible issues with the processing.

=== Message ===

{{{
INFO  [LayoutManager] table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%"
}}}

==== Solution ====

The width attribute has been omitted and the default is 'auto'.  The 'auto' layout is not supported so you receive this message.  Add a valid width attribute to table tag.

==== Example ====
Original:

{{{<fo:table table-layout="fixed">}}}

Fixed:

{{{<fo:table table-layout="fixed" width="100%">}}}

=== Message ===

{{{
INFO  [TableContentLayoutManager] break-after found
}}}

==== Solution ====

None.  This looks like a debug message and will probably be removed in a future release.

== Warning Messages ==

These messages indicate possible problems with processing.

=== Message ===

{{{
WARN  [LayoutManager] TODO Add collapsed border painting for spanned cells
}}}

==== Solution ====

None.  This looks like a debug message and will probably be removed in a future release.

=== Message ===

{{{
WARN  [LayoutManager] static-content overflows the available area
}}}

==== Solution ====

The static area defined is not large enough to fit the elements within it.  This may be due to content growing beyond expectations or simply declaring the area too small.  Try adjusting your extents to find the correct size.

=== Message ===

{{{
WARN  [FONode] Warning(Unknown location): fo:table, table-layout="auto" is currently not supported by FOP
}}}

==== Solution ====

The table-layout attribute has been omitted and the default is 'auto'.  The 'auto' layout is not supported so you receive this message.  Add a table-layout and possibly a width attribute to the table tag.

==== Example ====
Original:

{{{<fo:table>}}}

Fixed:

{{{<fo:table table-layout="fixed" width="100%">}}}

=== Message ===

{{{
WARN  [FONode] Warning(Unknown location): fo:table-column, In the separate border model (border-collapse="separate"), borders cannot be specified on a fo:table-column, but a non-zero value for border was found. The border will be ignored.
}}}

==== Solution ====

Still under investigation.
''See http://xmlgraphics.apache.org/fop/compliance.html#fo-property-border-collapse for more details''

=== Message ===

{{{
WARN  [FONode] Warning(Unknown location): fo:table-row, fo:table-row does not have padding (see the property list for fo:table-row in XSL 1.0), but a non-zero value for padding was found. The padding will be ignored.
}}}

==== Solution ====

Remove superfluous row padding.

=== Message ===

{{{
WARN  [BreakingAlgorithm] Line 1 of a paragraph overflows the available area. (fo:block, "SOMEVERYLONGDATA")
}}}

==== Solution ====

This is due to content overflowing the area.  Try resizing the area or adding the overflow and/or wrap-option attributes. 
''See http://xmlgraphics.apache.org/fop/compliance.html#fo-property-overflow and http://xmlgraphics.apache.org/fop/compliance.html#fo-property-wrap-option for more details.

=== Message ===

{{{
WARN  [BreakingAlgorithm] Part/page 1 overflows the available areain block-progression dimension. (fo:static-content, "There is some very long data here!")
}}}

==== Solution ====

The  area defined is not large enough to fit the elements within it.  This may be due to a mis-sized image, content growing beyond expectations or simply declaring the area too small.  Try adjusting your extents to find the correct size.

=== Message ===

{{{
WARN  [TableContentLayoutManager] 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 72028 millipoints, but the row shouldn't get any taller than MinOptMax[min=opt=max=56692] millipoints. (fo:table-row, "DATA HERE")
}}}

==== Solution ====

Still under investigation.  Try adjusting the content height or use height.minimum, height.maximum and height.optimum to set the height.

=== Message ===

{{{
WARN  [ColumnSetup] There are fewer table-columns than are needed. Column 2 was accessed although only 1 columns have been defined. The last defined column will be reused. (fo:table, "XXX:, yyy")
}}}

==== Solution ====

This is usually due to a mistake in coding the XSL.  Check to make sure you have not declared more table cells than you have columns or that you are not spanning more columns than you have declared.

=== Message ===

{{{
WARN  [ColumnSetup] Please note that according XSL-FO 1.0 (7.26.9) says that the 'column-width' property must be specified for every column, unless the automatic table layout is used.
}}}

==== Solution ====

This is usually due to a mistake in coding the XSL.  Check to make sure you have not declared more table cells than you have columns or that you are not spanning more columns than you have declared.

=== Message ===

{{{
WARN  [FOTreeBuilder] Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs. layout-master-set (http://www.w3.org/1999/XSL/Format)
}}}

==== Solution ====

This is usually due to a mistake in coding the XSL.  Check the log for a more serious error message that may be causing this warning to occur.  For example, an error in the ordering of your regions will result in warnings of this type.

=== Message ===

{{{
WARN  [FOTreeBuilder] Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs. root (http://www.w3.org/1999/XSL/Format)
}}}

==== Solution ====

This is usually due to a mistake in coding the XSL.  Check the log for a more serious error message that may be causing this warning to occur.  For example, an error in the ordering of your regions will result in warnings of this type.

== Error Messages ==

These messages indicate serious issues with processing.

=== Message ===

{{{
ERROR (Unknown location): For fo:simple-page-master, fo:region-body must be declared before fo:region-before.
}}}

==== Solution ====

The region ordering must adhere to the XSL-FO specification.  Fix the ordering in your page-master.  This may also be causing other warning messages to be generated. 
''See http://www.w3.org/TR/xsl/slice6.html#fo_region-body for more details''

==== Example ====
Original:

{{{
<fo:region-before extent="70mm"/>
<fo:region-after extent="5mm"/>
<fo:region-body margin-top="71mm" margin-bottom="7mm"/>
}}}

Fixed:

{{{
<fo:region-body margin-top="71mm" margin-bottom="7mm"/>
<fo:region-before extent="70mm"/>
<fo:region-after extent="5mm"/>
}}}

=== Message ===

{{{
ERROR [FONode] fo:table-body must not be empty. Expected: marker* (table-row+|table-cell+)
}}}

==== Solution ====

Quite obvious, but still investigating.  This was previously silently ignored and it looks like the table still renders OK.

=== Message ===

{{{
INFO  [STDOUT] [Fatal Error] someReport.xsl:265:120: Attribute "abc" was already specified for element "fo:table-cell".
}}}

==== Solution ====

Remove duplicate attribute.

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org