Altova Mailing List Archives


Re: [xsl] FO table-body empty validation error

From: "G. Ken Holman" <gkholman@-------------------->
To:
Date: 7/23/2008 12:13:00 AM
At 2008-07-22 10:08 -0700, Karl Stubsjoen wrote:
So the arrangment is legal.

Sorry ... I didn't say that.  I see from the spec that table-body 
cannot be empty:



  http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table-body



You must choose between the row-based row-grouping strategy or the 
cell-based row-grouping strategy for each <table-body> used in your <table>.



That is all I need to know.  I am
outputing a fo file with every transformation.

Then you'll be able to open the FO file and see that the body is, 
indeed, empty as reported by the error message.  It cannot be empty 
to be legal and the processor is correct to complain.



I hope this helps.



. . . . . . . . . . Ken




--
Upcoming XSLT/XSL-FO hands-on courses:      Wellington, NZ 2009-01
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/s/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/s/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.