Bug 691470 - PDF 1.7 FTS: Unknown color space method in JPX stream.
Summary: PDF 1.7 FTS: Unknown color space method in JPX stream.
Status: NOTIFIED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Interpreter (show other bugs)
Version: master
Hardware: PC Linux
: P1 normal
Assignee: Michael Vrhel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-18 15:37 UTC by Alex Cherepanov
Modified: 2011-09-18 21:46 UTC (History)
1 user (show)

See Also:
Customer: 532
Word Size: ---

Attachments
patch (4.56 KB, patch)
2010-08-17 01:18 UTC, Alex Cherepanov 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Cherepanov 2010-07-18 15:37:11 UTC 
Many files display the following warning:
**** Unknown color space method in JPX stream.
**** Warning: image has no /ColorSpace key; assuming /DeviceRGB.
Some images in the files, presumably affected by the warning,
are rendered incorrectly.

fts_17_1700_a4.pdf
fts_17_1701_a4.pdf
fts_17_1702_a4.pdf
fts_17_1703_a4.pdf
fts_18_1805_a4.pdf
fts_18_1812_a4.pdf
Comment 1 Ray Johnston 2010-07-18 18:29:24 UTC 
Update to reflect customer status and ID.
Comment 2 Alex Cherepanov 2010-07-23 20:15:14 UTC 
"Unknown color space method" is an unrestricted ICC-based color space but
setting it now will cause PS errors (instead of wrong images) because
it's not clear yet what to do with alpha channels.
Comment 3 Henry Stiles 2010-07-27 17:12:21 UTC 
Eventually we want to move to openjpeg but assigning to Michael since he has a workaround in Jasper that might address this issue.
Comment 4 Alex Cherepanov 2010-08-17 01:18:30 UTC 
Created attachment 6665 [details]
patch

Don't include opacity channels in the number-of-components count.
Recognize general ICC profile (type 3) and construct a corresponding
ICC-based color space.

This patch fixes 
fts_17_1702_a4.pdf
fts_17_1703_a4.pdf

Other problems are caused by mis-interpretation of the opacity
layer and tracked by the bug 691489.
Comment 5 Alex Cherepanov 2010-08-17 01:27:34 UTC 
The patch has been committed as a rev. 11636.
Comment 6 Marcos H. Woehrmann 2011-09-18 21:46:24 UTC 
Changing customer bugs that have been resolved more than a year ago to closed.