Difference between revisions of "Workflow:Validation Error Analysis and Treatment for PDF-hul 122 Invalid destination - Destination NULL"
(Created page with "{{Infobox COW |status=Production |tools=Pdfcpu, Qpdf, JHOVE, Adobe Acrobat Pro, PDF Checker |input=File with JHOVE validation error PDF-HUL-122 “Invalid Destination” / Wel...") |
|||
| Line 11: | Line 11: | ||
<!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below --> | <!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below --> | ||
| + | |||
| + | The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-122 error. | ||
| + | <b> CAUTION! PDF-HUL-122 errors can be very different in nature and impact. </b> | ||
| + | The process described here can be used for internal document links that are not working. It is a manual workflow. More information about this specific case has been discussed in a blog. The methodology used here is that introduced in https://hdl.handle.net/2142/121092. | ||
| + | |||
| + | Step 1: Validation Error | ||
| + | |||
| + | JHOVE v1.28 PDF-hul v1.12.4 PDF-HUL-122 Invalid Destination with offset given. Well-formed, but not valid. | ||
| + | |||
| + | Step 2: Cross-Check with other Tools | ||
| + | |||
| + | Cross-checked with: | ||
| + | pdfcpu v0.6.0dev relaxed mode - no error | ||
| + | pdfcpu v0.6.0dev strict mode - unrelated error (Font error) | ||
| + | qpdf v9.1.1 - no error | ||
| + | PDF Checker 2.1.0 - no error | ||
| + | |||
| + | Step 3: Matching Results? | ||
| + | |||
| + | No. Error not reported by other tools, most likely due to low priority of error (only impacts validity, not well-formedness). | ||
| + | One additional un-related error picked up. | ||
| + | |||
| + | Step 4: Choose Error to Treat | ||
| + | |||
| + | Original PDF-HUL-122. Ignore Font error. | ||
| + | |||
| + | Step 5A: Locate Error in Spec | ||
| + | |||
| + | ISO 32000-2:2017 12.3.2.4 Named destinations must contain name as well as target destination. In case of internal destinations this is typically an object reference. | ||
| + | |||
| + | Step 5B: Locate Error in File | ||
| + | |||
| + | Offset given by JHOVE only points to place where reference was used in GoTo destination. The reader tries to resolved the named destination used in the GoTo action via the name tree. Here the object is missing and replaced by "Null". | ||
| + | (Rechte_von_Eltern_in_der_Kita_2018_V7_bf.indd:.45593:62)[null/Fit ] | ||
| + | |||
| + | Step 6: Match? | ||
| + | |||
| + | Yes. | ||
| + | |||
| + | Step 7: Fixable? | ||
| + | |||
| + | Yes. | ||
| + | |||
| + | Step 8: Fix | ||
| + | |||
| + | Find location by checking page object the wrong destination is used on. With Adobe Acrobat Pro's "Edit Link" option, the erronous link can be removed and replaced by a correct one, if known. | ||
| + | |||
| + | Step 9: Check | ||
| + | |||
| + | Re-validated file with JHOVE: now well-formed and valid. Link is now actionable. | ||
| + | |||
| + | Step 10: Success? | ||
| + | |||
| + | Yes. | ||
[[File:PDF-hul-122 1.jpg|Textual description]]<br> | [[File:PDF-hul-122 1.jpg|Textual description]]<br> | ||
Revision as of 19:40, 21 January 2024
Workflow Description
The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-122 error. CAUTION! PDF-HUL-122 errors can be very different in nature and impact. The process described here can be used for internal document links that are not working. It is a manual workflow. More information about this specific case has been discussed in a blog. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.
Step 1: Validation Error
JHOVE v1.28 PDF-hul v1.12.4 PDF-HUL-122 Invalid Destination with offset given. Well-formed, but not valid.
Step 2: Cross-Check with other Tools
Cross-checked with: pdfcpu v0.6.0dev relaxed mode - no error pdfcpu v0.6.0dev strict mode - unrelated error (Font error) qpdf v9.1.1 - no error PDF Checker 2.1.0 - no error
Step 3: Matching Results?
No. Error not reported by other tools, most likely due to low priority of error (only impacts validity, not well-formedness). One additional un-related error picked up.
Step 4: Choose Error to Treat
Original PDF-HUL-122. Ignore Font error.
Step 5A: Locate Error in Spec
ISO 32000-2:2017 12.3.2.4 Named destinations must contain name as well as target destination. In case of internal destinations this is typically an object reference.
Step 5B: Locate Error in File
Offset given by JHOVE only points to place where reference was used in GoTo destination. The reader tries to resolved the named destination used in the GoTo action via the name tree. Here the object is missing and replaced by "Null". (Rechte_von_Eltern_in_der_Kita_2018_V7_bf.indd:.45593:62)[null/Fit ]
Step 6: Match?
Yes.
Step 7: Fixable?
Yes.
Step 8: Fix
Find location by checking page object the wrong destination is used on. With Adobe Acrobat Pro's "Edit Link" option, the erronous link can be removed and replaced by a correct one, if known.
Step 9: Check
Re-validated file with JHOVE: now well-formed and valid. Link is now actionable.
Step 10: Success?
Yes.
