[
https://issues.apache.org/jira/browse/PDFBOX-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245397#comment-14245397
]
Tilman Hausherr commented on PDFBOX-2564:
-----------------------------------------
The error "Stream was not read" has nothing to do with the /Length, it is a
follow up error because the stream contents are not available. We can't avoid
the follow-up errors at this time. About checking the Length (don't know if
this is done), but I'd think a user would understand that after having a broken
image, its length won't be checked either.
> be more precise with "Stream not read" error
> --------------------------------------------
>
> Key: PDFBOX-2564
> URL: https://issues.apache.org/jira/browse/PDFBOX-2564
> Project: PDFBox
> Issue Type: Sub-task
> Components: Preflight
> Affects Versions: 2.0.0
> Reporter: Ralf Hauser
> Priority: Minor
> Fix For: 2.1.0
>
>
> Currently, the error says:
> "2 : Unknown error, Stream was not read - on page 1"
> So while the validation doesn't really need to bother with the "EOL
> encountered in white run", the pdf/A apparently contains further attributes
> such "/length" that can no longer be confirmed or denied.
> So,
> 1) the error should explain that.
> 2) If there is even not only a total length, but a specific length expected
> for the COSStream, error should mention that among others
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
