Summary: | OutputICCProfile ignored for pdfwrite? | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | i3v |
Component: | Color Management | Assignee: | Michael Vrhel <michael.vrhel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P4 | ||
Version: | 9.26 | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Customer: | Word Size: | --- | |
Attachments: | Example input and output files |
Description
i3v
2019-04-01 01:45:59 UTC
Created attachment 17288 [details]
Example input and output files
First, would you mind tagging any more 'problems' with colour conversion and the pdfwrite device as 'PDF Writer' and not 'Color Management' please ? As I've mentioned several times, the colour management performed by the pdfwrite device is quite different to the regular rednering devices, due to the fact that we want to retain as much information as possible, and *not* convert everything to a specific device space. Tagging the reports with 'colour management' sets the Assignee incorrectly. Comparing the pdfwrite behaviour with a rendering device is not helpful, the results will not often be the same. In this case this is, once again, an aspect of the old colour management scheme, but since setting it does not harm the new scheme, its been left in place. When the old scheme is removed the documentation will be resolved. (In reply to Ken Sharp from comment #2) Thanks for the fix! Just for the reference: Now (since b987c511229ba0b70e6a7691366d530fa8db7444 ), doc/VectorDevices.htm does not mention "OutputICCProfile" at all, which is in line with the fact that it has no effect. |