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

Bad trailer not reported #968

Closed
thomashicks opened this issue May 16, 2018 · 0 comments · Fixed by veraPDF/veraPDF-parser#399
Closed

Bad trailer not reported #968

thomashicks opened this issue May 16, 2018 · 0 comments · Fixed by veraPDF/veraPDF-parser#399
Assignees
Labels
bug A product defect that needs fixing P2 Medium priority issues to be scheduled in a future release

Comments

@thomashicks
Copy link

thomashicks commented May 16, 2018

Dev Effort

1D

Description

I had a file which displayed fine in Adobe Acrobat Reader 11.0.23 but when you exit it would ask if you wanted to save changes to the file. While not very intuitive this is apparently an indication that the reader found something about the file it did not like and wanted to fix the issue. If you save the file then it does fix the issue but it changes so many things that it is hard to tell what it did not like in the first place.

Running the file through the current veraPDF 1.12.1 did find some issues but they were unrelated to the problem that Acrobat Reader was alerting on. After some debugging it became clear that the problem was in the fixed format trailer. In text files that terminate with a single <0ah> character (unix format) there should be a space to fill in the place where a <0dh> might normally reside in a DOS format text file. This is so the total character count of each trailer line is 20. This is not visually apparent in most text editors. I have attached two files: one with a good trailer and one with a bad trailer.

Perhaps this could be added to the list of things that are checked by veraPDF.

Thanks!

Tom

pdftestgood.pdf
pdftestbad.pdf

@ghost ghost added bug A product defect that needs fixing P2 Medium priority issues to be scheduled in a future release labels Jan 3, 2019
@ghost ghost added this to the v1.14-m4 milestone Jan 3, 2019
@carlwilson carlwilson removed this from the v1.14-m4 milestone Aug 22, 2019
@carlwilson
Copy link
Contributor

@bdoubrov could you provide an update here please.

@ghost ghost added this to the 1.16 milestone Oct 24, 2019
@carlwilson carlwilson removed this from the 1.20 milestone Feb 10, 2021
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 P2 Medium priority issues to be scheduled in a future release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants