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

Anthony commented on FOP-2434:
------------------------------

A users comment on the issue:

 
The original problem reported by Anthony did have some of the PDF problems that 
are known to be

Reader/Acrobat issues. However, the example PDF from Anthony, plus the two 
samples created

from the same DITA code with two other rendition utilities submitted by another 
contributor showed,

at 3200% zoom three completely different algorithms for creating the table 
lines.

 

Relying on Adobe alone to fix this will not produce a working result.

 

Anthony’s Example.PDF had what looks like overlaid lines and filled rectangles 
with visible line widths.

Another exampleanthony-xep.pdf showed perfectly joined lines of uniform widths 
using the 45° chamfers

at junctions. The third example anthony-ah.pdf may have used used filled 
rectangles of consistent of line

widths. But the third example also showed some shortened lines not completing 
the junctions.

 

So three different results with three different table line representations from 
three different rendition

engines, to me, speaks loudly of rendition issues and not just PDF issues.

> 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
>
> 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
(v6.3.4#6332)

Reply via email to