During my upgrade from 0.20.3 to 0.91, I have been keeping a list of new log messages and rendering issues/errors and my investigation into their causes. I am listing them below for two reasons:
1. To elicit feedback from anyone who may have insight or a solution.
2. To build a thread containg a common list that can be referred to when someone has a problem during implementation.
The issues below are only the most common that I am seeing in the majority of my documents. Happily, I have hit very few major issues during my regression testing of 0.91. I will upgrade the list as necessary.
Please feel free to comment, add, remove or solve.
-Lou
My list so far:
No message, but external image scaling is mucked up.
Solution: Add content-height and content-width to external-graphic
Example:
Before: <fo:external-graphic scaling="uniform" height="10mm" src="">
After: <fo:external-graphic content-height="scale-to-fit" content-width="scale-to-fit" scaling="uniform" height="10mm" src="">
INFO [LayoutManager] table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%"
Solution: Add width attribute to table tag
Example:
Before: <fo:table table-layout="fixed">
After: <fo:table table-layout="fixed" width="100%">
WARN [LayoutManager] TODO Add collapsed border painting for spanned cells
Solution: None - this looks like a debugging message.
Example:
Before:
After:
WARN [LayoutManager] static-content overflows the available area.
Solution: Adjusting content area and still investigating.
Example:
Before:
After:
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.
Example:
Before:
After:
WARN [FONode] Warning(Unknown location): fo:table, table-layout="auto" is currently not supported by FOP
Solution: Add table-layout and width attribute to table tag
Example:
Before: <fo:table>
After: <fo:table table-layout="fixed" width="100%">
10:01:48,302 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: Tried border-collapse="collapse" but no good - still investigating.
Example:
Before:
After:
Notes: See http://xmlgraphics.apache.org/fop/compliance.html#fo-property-border-collapse
This is a showstopper unless a workaround is found.
WARN [BreakingAlgorithm] Line 1 of a paragraph overflows the available area. (fo:block, "WITopt")
Solution: None - this is due to data overflowing the cell.
Example:
Before:
After:
INFO [TableContentLayoutManager] break-after found
Solution: None - this looks like a debugging message.
Example:
Before:
After:
WARN [BreakingAlgorithm] Part/page 1 overflows the available areain block-progression dimension. (fo:static-content, "Copyright ⌐ 1993-2006 LOG-NET, INC. Confidential")
Solution: Fix size.
Example:
Before:
After:
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: Still investigating.
Example:
Before:
After:
This is a showstopper unless fixed.
WARN [FOTreeBuilder] Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs. root (http://www.w3.org/1999/XSL/Format)
Solution: Still investigating.
Example:
Before:
After:
This is a showstopper unless fixed.
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.
Example:
Before:
After:
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: User error - Found erroneous number-columns-spanned="3" in table with only one column defined
Example:
Before:
After:
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: User error - Found erroneous number-columns-spanned="3" in table with only one column defined
Example:
Before:
After:
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: Adjust height according to the content or use height.minimum instead of height but this affects the size of the row - needs more investigation
Example:
Before:
After:
- 0.20.3 to 0.91b migration log messages Louis . Masters
- Re: 0.20.3 to 0.91b migration log messages Jeremias Maerki
- Re: 0.20.3 to 0.91b migration log messages Louis . Masters
- Re: 0.20.3 to 0.91b migration log messages Louis . Masters
- Re: 0.20.3 to 0.91b migration log mess... Jeremias Maerki
- Re: 0.20.3 to 0.91b migration log mess... Clay Leeds
- Re: 0.20.3 to 0.91b migration log messages Glen Mazza
- Re: 0.20.3 to 0.91b migration log messages Andreas L Delmelle
- Re: 0.20.3 to 0.91b migration log messages Chris Bowditch
