Summary: | patch to remove -diccTransform option, and verify/filing the rest of the testing issues. | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Hin-Tak Leung <htl10> |
Component: | Color Management | Assignee: | Default assignee <ghostpdl-bugs> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | sphinx.pinastri |
Priority: | P4 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- | |
Attachments: | patch to remove the -diccTransform option (and make it the default) |
Description
Hin-Tak Leung
2014-03-29 12:10:12 UTC
(In reply to comment #0) > jointest.ps, Bug688655.ps - seems to some kind of accuracy/grid position > problem. Just look at the original bug reports about how these files are special, I see Bug 688655 - stroking: Incorrect stroking of very wide curves. part of the bitmap looks a bit like this: http://bugs.ghostscript.com/attachment.cgi?id=5487 (from that report). It is worth noting that PCL XL does not support of the full range of postscript line joins. (only 0, 1, 2, 3 - I think ps can go up to 5 or 6?). Line 1236, gs/devices/vector/gdevpx.c - "Igoring invalid linejoin enumerator %d\n" though this code wasn't triggered. In any case, it is possible that this issue (I don't think it is a regression) is that PXL is a high-level vector device, but does not support all the features of postscript, especially about paths and joins. (In reply to comment #0) > Bug692217.pdf - quite major gray-shade difference. The noted difference with -sDEVICE=pxlmono is entirely due to with/without -r300. It should go to Michael or Ray and probably should be looked at together with "Bug 694605 - Differences in color with and without banding" (In reply to comment #0) > Bug692494.pdf - I think I have seen something out of curiosity like this > (part of an image turns its complement color) in a report, but I cannot find > it now. The closest I find is "Bug 694605 - Differences in color with and > without banding", but I remember having seen some sort of comparison of two > rendering where the bottom left portion of page has a green background vs > an orange background... I think it was a bug under either Michael or Henry. > > Bug692666.pdf - border blacked out. Not much idea. Bug692666.pdf with pxlmono turn out to be also due to difference between banding or not, also, i.e. with or without -r300 . But Bug692494.pdf is *not* about banding. (In reply to comment #2) > (In reply to comment #0) > > Bug692217.pdf - quite major gray-shade difference. > > The noted difference with -sDEVICE=pxlmono is entirely due to with/without > -r300. > > It should go to Michael or Ray and probably should be looked at together with > "Bug 694605 - Differences in color with and without banding" Bug692217.pdf itself actually already has a bug about banding vs no banding: "Bug 694973 - Wrong colors when using clist with comparefiles/Bug692217.pdf" (In reply to Hin-Tak Leung from comment #4) > Bug692217.pdf itself actually already has a bug about banding vs no banding: > "Bug 694973 - Wrong colors when using clist with comparefiles/Bug692217.pdf" new bug filed comparefiles/Bug692217.pdf, "Bug 695278 - Significant color differences in banded vs. page mode." probably should be counted as duplicate of the clist problem bug 694973 . An update: while adding cmyk support to the pxl driver, I see that -diccTransform - or rather, the underlying main working routine, gscms_transform_color_buffer() - does not work correctly when -dUseFastColor is also specified. I think maybe "use colour management (in gscms_transform_color_buffer() )" and "do not use colour management (-dUseFastColor)" are fundamentally incompatible, or in any case, does not work correctly at the moment. The impact of this finding is that, there are users (Artifex clients) for which -dUseFastColor is important and who seems to be routinely using it. Therefore this "bug report" should not be processed, until the conflict or compatibility issue with -dUseFastColor, is addressed. i.e. DO NOT PROCEED ON THIS, until further notice. Passing to Henry to have a look. This option is still nor removed. |