[jira] [Commented] (PDFBOX-3541) Use /L entry to determine if a linearized file shall be treated as such for PDF/A validation
[
https://issues.apache.org/jira/browse/PDFBOX-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608970#comment-15608970
]
ASF subversion and git services commented on PDFBOX-3541:
-
Commit 1766703 from [~tilman] in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1766703 ]
PDFBOX-3541: also use length to determine whether it's a linearized file
> Use /L entry to determine if a linearized file shall be treated as such for
> PDF/A validation
>
>
> Key: PDFBOX-3541
> URL: https://issues.apache.org/jira/browse/PDFBOX-3541
> Project: PDFBox
> Issue Type: Improvement
> Components: Preflight
>Reporter: Maruan Sahyoun
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> With PDFBOX-3540 the detection of a linearized file which has later been
> updated for PDF/A validation was improved so that provisions can be properly
> applied or ignored. That could be improved by checking the /L entry of the
> linearization dictionary. The *ISO 19005-1:2005/Cor.2:2011* has this:
> {quote}
> In a linearized PDF, if the ID keyword is present in both the first page
> trailer dictionary and the last
> trailer dictionary, the value to both instances of the ID keyword shall be
> identical.
> ...
> This provision shall not apply where the value to the L key in the
> linearization dictionary does not match the actual length of the PDF.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-3541) Use /L entry to determine if a linearized file shall be treated as such for PDF/A validation
[
https://issues.apache.org/jira/browse/PDFBOX-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608969#comment-15608969
]
ASF subversion and git services commented on PDFBOX-3541:
-
Commit 1766702 from [~tilman] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1766702 ]
PDFBOX-3541: also use length to determine whether it's a linearized file
> Use /L entry to determine if a linearized file shall be treated as such for
> PDF/A validation
>
>
> Key: PDFBOX-3541
> URL: https://issues.apache.org/jira/browse/PDFBOX-3541
> Project: PDFBox
> Issue Type: Improvement
> Components: Preflight
>Reporter: Maruan Sahyoun
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> With PDFBOX-3540 the detection of a linearized file which has later been
> updated for PDF/A validation was improved so that provisions can be properly
> applied or ignored. That could be improved by checking the /L entry of the
> linearization dictionary. The *ISO 19005-1:2005/Cor.2:2011* has this:
> {quote}
> In a linearized PDF, if the ID keyword is present in both the first page
> trailer dictionary and the last
> trailer dictionary, the value to both instances of the ID keyword shall be
> identical.
> ...
> This provision shall not apply where the value to the L key in the
> linearization dictionary does not match the actual length of the PDF.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-3541) Use /L entry to determine if a linearized file shall be treated as such for PDF/A validation
[
https://issues.apache.org/jira/browse/PDFBOX-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605836#comment-15605836
]
Tilman Hausherr commented on PDFBOX-3541:
-
I don't see an easy way to access the length of the file from the
TrailerValidationProcess.
What could be done is to expand the preflight context, and to pass fileLen in
PreflightParser after parsin to the preflight context within
PreflightParser.createContext().
> Use /L entry to determine if a linearized file shall be treated as such for
> PDF/A validation
>
>
> Key: PDFBOX-3541
> URL: https://issues.apache.org/jira/browse/PDFBOX-3541
> Project: PDFBox
> Issue Type: Improvement
> Components: Preflight
>Reporter: Maruan Sahyoun
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> With PDFBOX-3540 the detection of a linearized file which has later been
> updated for PDF/A validation was improved so that provisions can be properly
> applied or ignored. That could be improved by checking the /L entry of the
> linearization dictionary. The *ISO 19005-1:2005/Cor.2:2011* has this:
> {quote}
> In a linearized PDF, if the ID keyword is present in both the first page
> trailer dictionary and the last
> trailer dictionary, the value to both instances of the ID keyword shall be
> identical.
> ...
> This provision shall not apply where the value to the L key in the
> linearization dictionary does not match the actual length of the PDF.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
