Re: Table end line do not appear in the continued page

Hello Tony,
Thanks for your support. im using XSL-Formatter by Antenna House. I've no
idea whether its suporting border-collapse or not.
Actullay i want a table design to be like in the attached file.where there
will be no row border shown accept the header. now when the data will be
populated the table will grow accordingly and as soon as the page break
comes the end of table line will be shown and the table will continue to the
next page.
but i guess thats not possible so far as far as I got the idea from Tonyz
mail.
is it?
thanks any ways.
Regards,
Saqib Javed

n Mon, Jul 21, 2008 at 1:48 AM, Tony Graham <
Tony.Graham@menteithconsulting.com> wrote:

>
> On Sat, Jul 19 2008 08:55:48 +0100, saqib.javed@gmail.com wrote:
> > I am trying to draw a table. every thing is working fine. but the issue
> is that
> > if i give the cell border="0pt" and do not give any other border. to row
> or
> > column. now the issue is that when one page is filled with the data the
> last
> > line is not drawn and the table continues to the next page until the last
> page
> > comes. at the last page this table is closed and the end line is drawn.
> what i
> > want is to close the table in all the pages and continue filling the data
> to
> > the next pages. howz its possible?
>
> You don't provide much to go on.  'border="0pt"' should have no effect
> anyway since you don't set the style, and the default border style is
> 'none'.
>
> You don't say which XSL formatter you are using.  If your formatter
> supports it, you could try border-collapse="collapse-with-precedence"
> [3] on your fo:table so the table's border has precedence (though you
> also don't say what border you are using on the table).
>
> Table borders at page breaks is not completely defined in XSL 1.1, not
> least because XSL 1.0 table processing tried for compatibility with
> CSS2, and CSS2 doesn't say anything about table borders at page breaks
> AFAICT.
>
> A similar question to xsl-editors@w3.org [1] received the response [2]
> that it wasn't possible to modify XSL 1.0 or 1.1 to more fully specify
> the expected results since, whatever would be specified, the extra
> detail would make some of the existing implementations become
> non-compliant.  The response notes that for XSL 2.0 the WG has decided
> to rewrite the text of the table formatting objects to be independent of
> the CSS2 Recommendation.
>
> There's also a section about this in the current XSL 2.0 Requirements
> draft [4].  As always, highlighting that you need this functionality by
> mentioning it when you fill out the requirements survey [5] or using the
> W3C Bugzilla system [6] would let the Working Group know that this
> feature would be important to people.
>
> Regards,
>
>
> Tony Graham                         Tony.Graham@MenteithConsulting.com
> Director                                  W3C XSL FO SG Invited Expert
> Menteith Consulting Ltd
> XML, XSL and XSLT consulting, programming and training
> Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
> Registered in Ireland - No. 428599   http://www.menteithconsulting.com
>  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
> xmlroff XSL Formatter                               http://xmlroff.org
> xslide Emacs mode                  http://www.menteith.com/wiki/xslide
> Unicode: A Primer                               urn:isbn:0-7645-4625-2
>
>
> [1] http://lists.w3.org/Archives/Public/xsl-editors/2007AprJun/0000
> [2] http://lists.w3.org/Archives/Public/xsl-editors/2008JanMar/0012
> [3] http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table-cell
> [4] http://www.w3.org/TR/xslfo20-req/#N66304
> [5] http://www.w3.org/2002/09/wbs/1/xslfo20requirements/
> [6] http://www.w3.org/XML/2008/01/xsl-fo-bugzilla.html
>
>