Summary: | "Error: Invalid XRef entry" messages for a valid PDF | ||
---|---|---|---|
Product: | poppler | Reporter: | Thomas Freitag <Thomas.Freitag> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Patch to suppress wrong "Error: Invalid XRef entry" messages |
Description
Thomas Freitag
2012-04-14 00:53:11 UTC
Wouldn't it be better just wrapping the error(errSyntaxError, -1, "Invalid XRef entry"); with that new if? And call the if "complainAboutMissingEntry" ? (In reply to comment #1) > Wouldn't it be better just wrapping the > error(errSyntaxError, -1, "Invalid XRef entry"); > with that new if? And call the if "complainAboutMissingEntry" ? Possible, but I don't think it's really better: why is it necessary to rescan the complete xref section when just looking if the current stream position still belongs to that object? I think, that this scanning code comes due to the fact that a "real" fetch to that object is done, and then try to localize that "missing" object, which is not becessary in this case inmho. I know what you mean, but there's a reconstructXRef that i find kind of scary so i've went the "really secure way". Sorry if i sound like a coward sometimes :D |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.