[
https://issues.apache.org/jira/browse/PDFBOX-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827590#comment-15827590
]
Tilman Hausherr edited comment on PDFBOX-3652 at 1/18/17 9:18 PM:
------------------------------------------------------------------
I checked the file with the PDF-Tools PDFA validator. The file is of course not
PDFA but the checks are still interesting:
https://www.pdf-online.com/osa/validate.aspx
{quote}
File Tree1.pdf
Compliance pdf1.5
Result Document does not conform to PDF/A.
Details
Validating file "Tree1.pdf" for conformance level pdf1.5
The value of the key Last is 18 0 R but must be 16 0 R.
The value of the key Last is 18 0 R but must be 13 0 R.
The document does not conform to the requested standard.
The document doesn't conform to the PDF reference (missing required entries,
wrong value types, etc.).
The document's meta data is either missing or inconsistent or corrupt.
Done.
{quote}
PDFBox preflight has this instead:
{quote}
1.4.9 : Outlines invalid, Outline Hierarchy doesn't have Count entry
{quote}
I was wondering why PDFBox preflight just mentions the missing count and not
the other errors, this is because the checks stops at that error. But we do
have a validation of these structures, this was done 2 years ago in PDFBOX-2630
as part of the works in getting Bavaria test suite compliant.
I haven't looked at the change itself, I might commit it but of course the
problem remains after merging.
was (Author: tilman):
I checked the file with the PDF-Tools PDFA validator. The file is of course not
PDFA but the checks are still interesting:
https://www.pdf-online.com/osa/validate.aspx
{quote}
File Tree1.pdf
Compliance pdf1.5
Result Document does not conform to PDF/A.
Details
Validating file "Tree1.pdf" for conformance level pdf1.5
The value of the key Last is 18 0 R but must be 16 0 R.
The value of the key Last is 18 0 R but must be 13 0 R.
The document does not conform to the requested standard.
The document doesn't conform to the PDF reference (missing required entries,
wrong value types, etc.).
The document's meta data is either missing or inconsistent or corrupt.
Done.
{quote}
PDFBox preflight has this instead:
{quote}
1.4.9 : Outlines invalid, Outline Hierarchy doesn't have Count entry
{quote}
I haven't looked at the change itself, I might commit it but of course the
problem remains after merging.
> PDFMergerUtility: The source outline of merged PDF can be end up inside deep
> sub-outline if destination outline contain sub-outline
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: PDFBOX-3652
> URL: https://issues.apache.org/jira/browse/PDFBOX-3652
> Project: PDFBox
> Issue Type: Improvement
> Components: Utilities
> Affects Versions: 2.0.4
> Reporter: Christian Hadi
> Priority: Minor
> Labels: patch, pdfmergerutility
> Attachments: 660775.pdf, after_patch.pdf, before_patch.pdf,
> Inserted.Acrobat.pdf, Merged.Acrobat.pdf, PDFMergerUtility.patch, Tree1.pdf,
> Tree2.pdf, TreeView.png
>
>
> The source outline of merged PDF can be end up inside deep sub-outline if
> destination outline contain sub-outline.
> The patch propose to change this behavior that merged source outline will
> always at the root of destination outline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
