Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 399674 [details] The XML file. Description of problem: We use publican to create documents in PDF. Sometimes the tables do not show a line at the bottom of the table border. Version-Release number of selected component (if applicable): publican-1.6-0.fc12.noarch How reproducible: Not all tables show this problem, but I think it happens more often than not. Steps to Reproduce: I will attach the XML Actual results: Sometimes the bottom line is missing from table borders. In the attached PDF, Table 1.1 has a bottom line border, but Table 1.2 does not. Expected results: A complete border around all tables. Additional info: XML and resultant PDF attached will be attached.
Created attachment 399675 [details] The resulting PDF
Created attachment 401627 [details] zoom of table 1.2 Hi, Table 1.2 in the attached PDF does has a bottom border, as can been seen from zooming in. It's probably a rendering issue with your PDF viewer. Maybe we should change the border colour or thickness ...
Wow, I never even saw. Yes, I think changing the thickness (and maybe the color) would help a lot. I know the bottom line is not noticeable when I print it out as is.
Set table border colour to black, made them fatter.
publican-1.6.1-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/publican-1.6.1-0.fc12
publican-1.6.1-0.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/publican-1.6.1-0.fc11
publican-1.6.1-0.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/publican-1.6.1-0.fc13
publican-1.6.1-0.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
publican-1.6.1-0.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
publican-1.6.1-0.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.