[jira] [Updated] (PDFBOX-4408) Object StructParent property does not match entry in parent tree
[ https://issues.apache.org/jira/browse/PDFBOX-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr updated PDFBOX-4408: Component/s: Utilities > Object StructParent property does not match entry in parent tree > > > Key: PDFBOX-4408 > URL: https://issues.apache.org/jira/browse/PDFBOX-4408 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Affects Versions: 2.0.13 >Reporter: Dan Anderson >Assignee: Tilman Hausherr >Priority: Major > Labels: StructureTree > Fix For: 2.0.14, 3.0.0 PDFBox > > Attachments: form-merged-good.pdf, form-merged.pdf, form.pdf > > > After merging 2 documents together, the parent tree entries for the second > page do not match their expected key. For the attached document you can look > at the "Date you are available" field after the merge. In the parent tree > the second page field is located with key of 15. However the object expects > its key to be 21. The /StructParent value is 21 but it should be 15. This > mismatch causes issues with a11y readers and the reading order in Adobe DC. > > The fields brought from the destination document are correct, but fields from > the source document do not match. They continue with the pattern, so the > next field is located at key 16 but the /StructParent value is 22, 17 for 23, > etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Updated] (PDFBOX-4408) Object StructParent property does not match entry in parent tree
[ https://issues.apache.org/jira/browse/PDFBOX-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr updated PDFBOX-4408: Affects Version/s: (was: 3.0.0 PDFBox) 2.0.13 > Object StructParent property does not match entry in parent tree > > > Key: PDFBOX-4408 > URL: https://issues.apache.org/jira/browse/PDFBOX-4408 > Project: PDFBox > Issue Type: Bug >Affects Versions: 2.0.13 >Reporter: Dan Anderson >Priority: Major > Labels: StructureTree > Attachments: form-merged-good.pdf, form-merged.pdf, form.pdf > > > After merging 2 documents together, the parent tree entries for the second > page do not match their expected key. For the attached document you can look > at the "Date you are available" field after the merge. In the parent tree > the second page field is located with key of 15. However the object expects > its key to be 21. The /StructParent value is 21 but it should be 15. This > mismatch causes issues with a11y readers and the reading order in Adobe DC. > > The fields brought from the destination document are correct, but fields from > the source document do not match. They continue with the pattern, so the > next field is located at key 16 but the /StructParent value is 22, 17 for 23, > etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Updated] (PDFBOX-4408) Object StructParent property does not match entry in parent tree
[ https://issues.apache.org/jira/browse/PDFBOX-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr updated PDFBOX-4408: Attachment: form-merged-good.pdf > Object StructParent property does not match entry in parent tree > > > Key: PDFBOX-4408 > URL: https://issues.apache.org/jira/browse/PDFBOX-4408 > Project: PDFBox > Issue Type: Bug >Affects Versions: 3.0.0 PDFBox >Reporter: Dan Anderson >Priority: Major > Labels: StructureTree > Attachments: form-merged-good.pdf, form-merged.pdf, form.pdf > > > After merging 2 documents together, the parent tree entries for the second > page do not match their expected key. For the attached document you can look > at the "Date you are available" field after the merge. In the parent tree > the second page field is located with key of 15. However the object expects > its key to be 21. The /StructParent value is 21 but it should be 15. This > mismatch causes issues with a11y readers and the reading order in Adobe DC. > > The fields brought from the destination document are correct, but fields from > the source document do not match. They continue with the pattern, so the > next field is located at key 16 but the /StructParent value is 22, 17 for 23, > etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Updated] (PDFBOX-4408) Object StructParent property does not match entry in parent tree
[ https://issues.apache.org/jira/browse/PDFBOX-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr updated PDFBOX-4408: Attachment: form-merged.pdf > Object StructParent property does not match entry in parent tree > > > Key: PDFBOX-4408 > URL: https://issues.apache.org/jira/browse/PDFBOX-4408 > Project: PDFBox > Issue Type: Bug >Affects Versions: 3.0.0 PDFBox >Reporter: Dan Anderson >Priority: Major > Labels: StructureTree > Attachments: form-merged.pdf, form.pdf > > > After merging 2 documents together, the parent tree entries for the second > page do not match their expected key. For the attached document you can look > at the "Date you are available" field after the merge. In the parent tree > the second page field is located with key of 15. However the object expects > its key to be 21. The /StructParent value is 21 but it should be 15. This > mismatch causes issues with a11y readers and the reading order in Adobe DC. > > The fields brought from the destination document are correct, but fields from > the source document do not match. They continue with the pattern, so the > next field is located at key 16 but the /StructParent value is 22, 17 for 23, > etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
