Bug 52585

Summary: PDF: number-columns-spanned problem with borders
Product: Fop - Now in Jira Reporter: M.H. <mhilpert>
Component: pdfAssignee: fop-dev
Status: NEW ---    
Severity: normal CC: inna.nill
Priority: P3    
Version: 1.0   
Target Milestone: ---   
Hardware: PC   
OS: All   
Attachments: Same XSL-FO with just number-columns-spanned added (below)
Minimal xsl file.
Minimal xml file.
Minimal fo file.

Description M.H. 2012-02-02 18:28:40 UTC
If a table has a row with multiple columns and the row cells have a border (top/bottom) the lines look even for all cells in the row. But if the cell has an additional 

number-columns-spanned="2" 

attribute, the subsequent cell (here: cell 3) will get different top/bottom border line (thickness)!

This sound similar to old Bug 46321 (for RTF).

If we remove number-columns-spanned, the border lines look good again (but of course the text is cut).

So far, we found an ugly workaround by adding "hidden" columns to all tables with 0pt width for this strange output to "hide".
Comment 1 M.H. 2012-02-02 18:42:39 UTC
Created attachment 28254 [details]
Same XSL-FO with just number-columns-spanned added (below)

Example of same XSL-FO code with just 1 difference:

PDF above:
----------
<xsl:template name="t1"><xsl:param name="text">...</xsl:param>
<fo:table-cell background-color="..." border-top-style="solid"  border-bottom-style="solid"  >
<fo:block line-height="10pt"><fo:inline><xsl:value-of select="$text"/></fo:inline></fo:block>
</fo:table-cell></xsl:template>

PDF below (number-columns-spanned="2" added) :
----------------------------------------------
<xsl:template name="t1"><xsl:param name="text">...</xsl:param>
<fo:table-cell number-columns-spanned="2" background-color="..." border-top-style="solid"  border-bottom-style="solid"  >
<fo:block line-height="10pt"><fo:inline><xsl:value-of select="$text"/></fo:inline></fo:block>
</fo:table-cell></xsl:template>
Comment 2 M.H. 2012-02-02 18:44:56 UTC
... the table has more rows (16) and it looks like the third row has (in the faulty example below) additional border above and below.
Comment 3 Glenn Adams 2012-04-07 01:42:38 UTC
resetting P2 open bugs to P3 pending further review
Comment 4 Glenn Adams 2012-04-08 04:47:06 UTC
please provide output PDF file(s) that show problem output
Comment 5 Glenn Adams 2012-04-08 04:48:04 UTC
also provide minimal input FO file
Comment 6 Glenn Adams 2012-04-24 05:48:43 UTC
(In reply to comment #5)
> also provide minimal input FO file

M.H., I am still awaiting your input as requested above (and comment 4). if I see no further input by April 30, I will close this bug due to lack of requested information. Regards, Glenn
Comment 7 Inna Nill 2012-06-19 15:15:01 UTC
I'm having the same issue too. Attached are a minimal xsl and xml files, to convert to PDF. Zoom to 200% or higher to see the issue.
Additionally, I'm in the process of converting from fop 0.20.5 to fop 1.0, and I do not see this issue in fop 0.20.5.

Thanks.
Comment 8 Inna Nill 2012-06-19 15:16:11 UTC
Created attachment 28962 [details]
Minimal xsl file.
Comment 9 Inna Nill 2012-06-19 15:16:30 UTC
Created attachment 28963 [details]
Minimal xml file.
Comment 10 Glenn Adams 2012-06-20 00:37:12 UTC
thanks, but I need a *minimal* input *XSL-FO* file, not an XSL/XML file pair; the input to FOP is XSL-FO; XSL/XML pairs are not XSL-FO, and the built-in function for mapping them to XSL-FO is merely a convenience function that is unrelated to FOP core processing
Comment 11 Inna Nill 2012-06-21 17:26:25 UTC
Created attachment 28981 [details]
Minimal fo file.

Included is an fo file, as requested.
This file was generated using the previously-included xml/xsl pair, using xsltproc. Please let me know if this is what you needed.

Thank you.