| Summary: | [PATCH] PDFOutline: 'endobj' should be preceded by an EOL | ||
|---|---|---|---|
| Product: | Fop - Now in Jira | Reporter: | Matthias Bauer <matthias.bauer.drs> |
| Component: | Assignee: | fop-dev | |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | Oliver.Moehrke |
| Priority: | P2 | ||
| Version: | all | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | patch | ||
*** Bug 51301 has been marked as a duplicate of this bug. *** I applied the patch to the v1.0 source-tree and it solves the compatibility issue with Intarsys PDF/A Live! validator. Thank you. Thanks for reporting, and the patch! I currently have some conflicting changes to the same classes to work out, and I'll gladly incorporate this one. However, instead of fixing this in one spot --the only place where it happens to be wrong-- I will, at the same time, look at the other 12 occurrences of ">>\nendobj\n" and extract those into a single method of PDFObject. At least, that will prevent it from ever reoccurring (assuming that all good devs will copy the existing pattern, that is) resetting P2 open bugs to P3 pending further review increase priority due to presence of a patch |
Created attachment 27071 [details] patch org.apache.fop.pdf.PDFOutline.toPDF() outputs ">> endobj\n". According to PDF/A spec (or at least according to the validators I've used) there has to be a "\n" in front of the endobj tag. (And at every other position in the code we're already outputting a "\n".) The patch changes the output to ">>\nendobj\n".