[jira] [Commented] (FOP-2434) Varying table border thickness in PDF output

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Commented] (FOP-2434) Varying table border thickness in PDF output

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/FOP-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956680#comment-15956680 ]

Christoffer Nielsen commented on FOP-2434:

[~cbowditch] I might have it worked around by creating 3 tables, 1 for header, 1 for body and 1 for footer.
I increased the border size to 2pt, but the varying thickness was still clearly visible. The other effect was the design looked worse after the borders were bigger.

I clearly understand its a limitation in Acrobat, but if it was possible to fix in fop in a manner which did not require a very large amount of work, then I hope you will reconsider later.

Alternatively it might also fix the issue not to use tables, but inline-blocks instead.

- With my previous comment I just wanted to clear out, that the bug was not only due to colspan.

> Varying table border thickness in PDF output
> --------------------------------------------
>                 Key: FOP-2434
>                 URL: https://issues.apache.org/jira/browse/FOP-2434
>             Project: FOP
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Anthony
>         Attachments: adobe_reader_100%.png, borderThicknessTest.fo, borderThicknessTest_FOP2.0.pdf, simple-table.fo, simple-table.pdf, simple-table.png
> Tables in my documentation vary in border thickness throughout my PDF output. I have determined that it occurs when cells are spanned (across rows and columns).
> I have attempted to fix stylesheets and Adobe settings, and nothing has helped.
> I use Oxygen XML Editor 16.1 with an Apache FOP processor.
> I am unable to attach any sample images or topic.fo file. By request, I will send both.

This message was sent by Atlassian JIRA