summaryrefslogtreecommitdiff
path: root/examples/transparency_example.ps
Commit message (Collapse)AuthorAgeFilesLines
* Squashed commit of the opacity_shape branchMichael Vrhel2020-03-271-4/+4
| | | | | | | | | | | | | | | | | This commit removes shape.alpha and opacity.alpha from the graphic state. This involved removal of methods in the postscript based PDF interpreter, changes in the pdf14 device, changes in pdfwrite, the XPS interpreter, and the PS transparency test file that is present in examples and on the cluster. The goal of this commit was to avoid confusion and conflicts between shape.alpha opacity.alpha and the stroke and fill alpha values (CA ca). This change resulted in progressions in the XPS file. There were changes in a couple PDF files that required some investigation. In particular, the change in the dashed lines of Bug694981.pdf. Robin and I looked at this. Robin determined it was due to differences in stroke_add and stroke_fill not giving identical results. In the end, the new output looks closer the what AR provides.
* Add the ability to allow transparency ops in PostscriptChris Liddell2019-11-051-1/+1
| | | | | | | | | | | -dALLOWPSTRANSPARENCY on the command line will prevent the undefining of the non-standard gs Postscript transparency operators. Driving these operators in the wrong way can cause undefined behavior, hence not allowing them normally. Also, use a better condition for dropping the transparency ops in: examples/transparency_example.ps
* Tweak to better handle undefined transparency opsChris Liddell2019-08-151-1/+4
|
* Tweak examples/transparency_example.psChris Liddell2018-09-131-0/+12
| | | | | So it prints a warning and runs to completion, rather than erroring out when -dSAFER is set.
* Fix bug 696845 SEGV with --saved-pages-test and transparencyRay Johnston2017-11-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a file pushes a pdf14devicefilter (or other compositor) it will still be the currentdevice after the filter is popped when the saved pages printing occurs. We need to check if the device is a forwarding device (as compositors will be when deactivated) and use the target device to print the saved pages. Also, if a device uses the gx_default_dev_spec_op, it will return 0 from the supports_saved_pages call even when it is a printer device. In gdev_prn_forwarding_dev_spec_op, check for a zero return and return true (1). A device that is a printer device that doesn't support saved page printing needs to return < 0 to prevent this. Add a finalize method for gx_device_printer so we can free up the saved- pages-list when the device is freed, but not when the device is closed which can happen if it needs to close due to put_params. Also the return code from the output_page in gx_saved_page_params_process was ignored. Both seen with the file Bug687111.ps and the psdcmyk device. Also for devn devices, such as psdcmyk, we need to save the separation (spot color) names collected during the execution of setcolorspace in the gx_saved_page and set them in the devn_params when rendering. These are not handled by the paramlist. Disable --saved-pages= and --saved-pages-test with PCL and XPS since it was never completely implemented and the partial implementation causes many errors when tested with --saved-pages-test. Note that while the --saved-pages-test option is still accepted as a parameter, it is ignored so that regression testing with --saved-pages-test can run. Regression shows 3343 "diffs", but bmpcmp doesn't show any diffs.
* Fix typo in previous commit s/b PageUsesTransparencyRay Johnston2017-06-211-1/+1
|
* Bug 698087: Heap buffer overflow with confused clist colorspaceRay Johnston2017-06-211-2/+5
| | | | | | | | | | The PDF14 transparency compositor changes the colorspace to Gray (8-bit), but if a 1-bit deep device is the target device, and the normal startup for transparent pages doesn't happen, the playback would write 8-bit data to a 1-bit deep buffer Also fix the transparency_example.ps so that it sets the device param PageUsesTransparency which is expected.
* Fix for transparency_example.ps to set the number of spot colors, Bug 695277.Marcos H. Woehrmann2015-10-291-1/+2
| | | | | | | | | From Michael Vrhel: The ps file transparency_example.ps failed to set the number of spot colors on the page. This information is expected to be provided for the pdf14 device by the PDF interpreter when we are dealing with the separable devices (e.g. psdcmyk, tiffsep)
* Commit of build_consolidation branchChris Liddell2015-07-201-0/+30
Squashed into one commit (see branch for details of the evolution of the branch). This brings gpcl6 and gxps into the Ghostscript build system, and a shared set of graphics library object files for all the interpreters. Also, brings the same configuration options to the pcl and xps products as we have for Ghostscript.