-
Notifications
You must be signed in to change notification settings - Fork 47
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
ByteRange, incremental update, and CR + LF = EOL #917
ByteRange, incremental update, and CR + LF = EOL #917
Comments
veraPDF 1.11.11 still reports a ByteRange not covering the entire file for B.1-unknown-4.pdf above. |
The logic might still be wrong. Consider this document: |
Suppose a PDF/A-2 document ends with CR, like this one:
B.1-unknown-3.pdf
The ByteRange entry covers the entire document, the document conforms to PDF/A-2. We add an incremental update. The incremental update begins with a LF as the object number must be preceded by an EOL marker (ISO 19005-2:2001, 6.1.9). Now, veraPDF reports that the ByteRange no longer covers the entire document (as signed). This is probably due to the LF being considered to by part of the document (as signed) as together with the CR it forms an EOL marker:
B.1-unknown-4.pdf
That is, the document (as signed) became longer by one byte. Is this really the intended behavior?
(For a PDF writer it's probably safer to start an incremental update with a CR rather than a LF in order to avoid this problem. Doesn't help for existing signed documents, though.)
The text was updated successfully, but these errors were encountered: