| Summary: | Illegal entry in bfrange block in ToUnicode CMap | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Zenon Panoussis <redhatbugs> |
| Component: | poppler | Assignee: | Marek Kašík <mkasik> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0 | CC: | jkoten, mhatina, mkasik, tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | poppler-0.12.4-6.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause
Poppler assumes that ToUnicode CMaps contains only 2-digit values <##> but there can be 4-digit values <####> too.
Consequence
"Illegal entry in bfrange block in ToUnicode CMap" appears when going trough pdf file.
Fix
Condition for checking 2-digit values has been extended to check also 4-digit values.
Result
The bug doesn’t present anymore.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-10 20:48:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1271696 | ||
|
Description
Zenon Panoussis
2011-06-05 00:26:46 UTC
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0799.html |