[xep-support] Re: Tables with only <fo:table-header> are not rendered close to end of page

Kevin Brown kevin at renderx.com
Tue Sep 25 20:13:21 PDT 2018


OK we'll take it under consideration.

 

 

 

From: Hugo Inacio [mailto:Hugo.Inacio at objective.com] 
Sent: Tuesday, September 25, 2018 7:35 PM
To: kevin at renderx.com; RenderX Community Support List
<xep-support at renderx.com>
Cc: Jim Fretwell <Jim.Fretwell at objective.com>
Subject: RE: [xep-support] Re: Tables with only <fo:table-header> are not
rendered close to end of page

 

Hi Kevin,

 

So for renderX, there has to be content inside the table body for it to show
on output. It still "feels" strange having tables show on the page until it
gets to the page break mark, to where they start disappearing. Also, it
would be good to have some sort of Error log information stating that the
table would not show on output.

 

Thanks,

Hugo

 

From: Xep-support <xep-support-bounces at renderx.com
<mailto:xep-support-bounces at renderx.com> > On Behalf Of Kevin Brown
Sent: Wednesday, 26 September 2018 10:19 AM
To: 'RenderX Community Support List' <xep-support at renderx.com
<mailto:xep-support at renderx.com> >
Cc: Jim Fretwell <Jim.Fretwell at objective.com
<mailto:Jim.Fretwell at objective.com> >
Subject: [xep-support] Re: Tables with only <fo:table-header> are not
rendered close to end of page

 

If I simply open you FO in oXygen, you do realize there are dozens of
errors.

I see this: <fo:table width="100%" border-collapse="collapse" id="d38e5658">

and 10 lines later I see this: <fo:table width="100%"
border-collapse="collapse" id="d38e5658">

 

Those IDs are the same. Gee, another error ... you cannot have a singular
XML document with IDs all the same ... 100s of them.

Step 1) Removed all IDs that are duplicate

Step 2) Removed invalid precedence=true/false on something you have that is
not anything XSL SO

All you content formats in one page, what did you expect?



 

Kevin Brown

RenderX

 

 

-----Original Message-----
From: Xep-support [mailto:xep-support-bounces at renderx.com] On Behalf Of Hugo
Inacio
Sent: Tuesday, September 25, 2018 4:55 PM
To: RenderX Community Support List <xep-support at renderx.com
<mailto:xep-support at renderx.com> >
Cc: Jim Fretwell <Jim.Fretwell at objective.com
<mailto:Jim.Fretwell at objective.com> >
Subject: [xep-support] Re: Tables with only <fo:table-header> are not
rendered close to end of page

 

Thank you for your email. I've checked the spec, and yes, you are right in
saying that the table is not correct without a table-body element. 

I would assume that XEP would treat all tables the same then, meaning none
of the tables should display as none of them are conformant?

 

I have also tested with the following ( valid FO according to spec):  

 

<fo:table-body><fo:table-row><fo:table-cell><fo:block/></fo:table-cell></fo:
table-row></fo:table-body>

 

And still achieve the same unwanted result: Only the tables on the first
page appear, and the tables that are supposed to show up in the second page
do not show. I have added the file for reference.

 

Hugo

 

-----Original Message-----

From: Xep-support < <mailto:xep-support-bounces at renderx.com>
xep-support-bounces at renderx.com> On Behalf Of G. Ken Holman

Sent: Tuesday, 25 September 2018 4:38 AM

To: RenderX Community Support List < <mailto:xep-support at renderx.com>
xep-support at renderx.com>;  <mailto:xep-support at renderx.com>
xep-support at renderx.com

Cc: Jim Fretwell < <mailto:Jim.Fretwell at objective.com>
Jim.Fretwell at objective.com>

Subject: [xep-support] Re: Tables with only <fo:table-header> are not
rendered close to end of page

 

A <table> without a <table-body> is an error, so the fact that anything is
or is not displayed is irrelevant ... you should be using valid XSL-FO.

 

Ref:  <https://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table>
https://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table

 

>Contents:

> 

>(< <https://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table-column>
https://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table-column>table-

>column*,<https://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table-header

>>table-header?,<https://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table

>-footer>table-footer?,<https://www.w3.org/TR/2006/REC-xsl11-20061205/#f

>o_table-body>table-body+)

 

I hope this is helpful.

 

. . . .  Ken

 

At 2018-09-24 01:57 +0000, Hugo Inacio wrote:

>For these three files (tables_with_body.fo, 

>tables_with_empty_body_and_header.fo, tables_with_header_only.fo ), 

>only the first one will show the second page. Meaning that tables that 

>contain only header cells are ignored when being placed on the next 

>page. Is this a render X issue?

> 

>Hugo Inacio

> 

> 

> 

>_______________________________________________

>(*) To unsubscribe, please visit

> <http://lists.renderx.com/mailman/options/xep-support>
http://lists.renderx.com/mailman/options/xep-support

>(*) By using the Service, you expressly agree to these Terms of Service 

> <http://w> http://w ww.renderx.com/terms-of-service.html

 

 

--

Contact info, blog, articles, etc.  <http://www.CraneSoftwrights.com/f/>
http://www.CraneSoftwrights.com/f/ | Check our site for free XML, XSLT,
XSL-FO and UBL developer resources | Streaming hands-on XSLT/XPath 2
training class @ US$45 (5 hours free) |

 

 

_______________________________________________

(*) To unsubscribe, please visit
<http://lists.renderx.com/mailman/options/xep-support>
http://lists.renderx.com/mailman/options/xep-support

(*) By using the Service, you expressly agree to these Terms of Service
<http://w> http://w ww.renderx.com/terms-of-service.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20180925/19ee8c17/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16153 bytes
Desc: not available
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20180925/19ee8c17/attachment-0001.png>


More information about the Xep-support mailing list