Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JHOVE 1.30 / PDF-hul 1.12.5 reports file as "Well-Formed and valid" despite PDF-HUL-1 error #929

Closed
Ka-Markus opened this issue Jul 18, 2024 · 4 comments · Fixed by #925 or #934
Closed
Labels
bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release
Milestone

Comments

@Ka-Markus
Copy link

Same behaviour as #924 (comment), only error is PDF-HUL-1 instead of PDF-HUL-2.

File to reproduce the issue:
https://repository.publisso.de/resource/frl%3A6406767
Leitlinie_Ernaehrung_Mangelernaehrung_Jun_2017.pdf

JHOVE 1.28.0 / PDF-hul, Rel. 1.12.4 reported 40 PDF-HUL-122 errors
JHOVE 1.30.0 / PDF-hul, Rel. 1.12.5 reports 1 PDF-HUL-1 error without offset

Please let me know if I should close the issue in case it's redundant.

@samalloing
Copy link
Collaborator

Hi @Ka-Markus

Thanks for reporting this. This error is fixed with #925. I hope @carl can add it to a new release soon.

Sam

@carlwilson
Copy link
Member

On this now @samalloing

carlwilson added a commit that referenced this issue Aug 1, 2024
- bumped modules, apps and installer to 1.30.1;
- bumped PDF HUL to 1.12.6 to incorporate fix for [#929](#929); and
- installer dependencies.
@carlwilson carlwilson added bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release labels Aug 1, 2024
@Ka-Markus
Copy link
Author

Tested validation of file with the new release JHOVE 1.30.1 / PDF-hul, Rel. 1.12.6.

  • Status is now again "Well-Formed, but not valid" (same as for 1.28.0).
  • Error code chaged, as intended by Sam (PDF-HUL-122 with JHOVE 1.28.0 changed to PDF-HUL-1 with JHOVE 1.30.1).
  • Offset is not available for PDF-HUL-1 but that doesn't seem to be an error.

Issue can be closed from my side. Should I close it?

@samalloing
Copy link
Collaborator

samalloing commented Aug 7, 2024

Hi @Ka-Markus

I looked into your file a little closer and noticed that adding

	} else if (!named && destObj instanceof PdfIndirectObj) {
			_pageDest =  findDirectDest(module, (PdfArray) module.resolveIndirectObject(destObj));
			return;
	}

to the code of jHove makes the file Well-formed and valid. The current implementation doesn't support indirect references at the location on the Destination. I wasn't able to verify it for sure. But adding the above piece of code after

solves the problem

Sam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release
Projects
None yet
3 participants