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

[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 JeremiasMaerki:
http://wiki.apache.org/xmlgraphics-fop/Troubleshooting/CommonLogMessages

The comment on the change is:
Some clarifications

------------------------------------------------------------------------------
  
  ==== Solution ====
  
- None.  This looks like a debug message and will probably be removed in a future release.
+ None.  This looks like a debug message and will be removed in a future release.
  
  == Warning Messages ==
  
@@ -50, +50 @@

  
  ==== Solution ====
  
- None.  This looks like a debug message and will probably be removed in a future release.
+ The property border-collapse has a default value of "collapse" which is currently not supported. Specify border-collapse="separate" to force the table into the separate border model. This will make the message go away. The next release will properly force all tables to the separate border model until the collapsing border model is implemented.
  
  === Message ===
  
@@ -70, +70 @@

  
  ==== 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.
+ The table-layout attribute has been omitted and the default is 'auto'.  The 'auto' layout is not supported so you receive this message.  Add table-layout="fixed" and possibly a width attribute to the table tag.
  
  ==== Example ====
  Original:
@@ -116, +116 @@

  === Message ===
  
  {{{
- WARN  [BreakingAlgorithm] Part/page 1 overflows the available areain block-progression dimension. (fo:static-content, "There is some very long data here!")
+ WARN  [BreakingAlgorithm] Part/page 1 overflows the available area in 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.
+ 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 ===
  
@@ -131, +131 @@

  
  ==== Solution ====
  
- Still under investigation.  Try adjusting the content height or use height.minimum, height.maximum and height.optimum to set the height.
+ Usually, this happens if you set the height property on a table-row or table-cell. The height property is mapped to the block-progression-dimension property where all sub-properties (.minimum, .optimum and .maximum) are set to the same value specified for the height value. If the content of that table row is larger in size than the height you specified you get the above message (because [effective height] > block-progression-dimension.maximum, i.e. the table row must not grow beyond the maximum height). If you want to allow the row to grow as necessary but keep a minimum height, specify block-progression-dimension.minimum="2cm" instead of the height property. block-progression-dimension.maximum will then remain on the default value of "auto" which allows the row to grow as necessary.
+ 
+ ==== Example ====
+ Original:
+ 
+ {{{<fo:table-row height="2cm">}}}
+ 
+ Fixed:
+ 
+ {{{<fo:table-row block-progression-dimension.minimum="2cm">}}}
  
  === Message ===
  
@@ -213, +222 @@

  
  ==== Solution ====
  
- Quite obvious, but still investigating.  This was previously silently ignored and it looks like the table still renders OK.
+ Quite obvious: There's an empty fo:table-body element. The specification says that an fo:table-body must have the following contents: (table-row+|table-cell+). If you get this message but the document renders fine, it means that you have strict validation disabled. FOP can deal with an empty table-body element but due to the wording in the specification, this is still, strictly speaking, an error.
+ 
+ See http://www.w3.org/TR/xsl/slice6.html#fo_table-body for more information.
  
  === Message ===
  

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